You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Vadim Chekan (JIRA)" <ji...@apache.org> on 2008/07/10 06:56:00 UTC
[jira] Created: (CAMEL-690) XMPP component has wrong documentation
XMPP component has wrong documentation
--------------------------------------
Key: CAMEL-690
URL: https://issues.apache.org/activemq/browse/CAMEL-690
Project: Apache Camel
Issue Type: Bug
Components: documentation
Affects Versions: 1.3.0
Reporter: Vadim Chekan
XMPP component page http://activemq.apache.org/camel/xmpp.html states that uri is "xmpp:hostname[:port][/room]". But in fact it does not work: the room is not recognised for "xmpp:jabber.org/room33". There is missing // to make it a valid hierarchical uri. See http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html
Fix:
the url should be "xmpp://vchekan@jabber.org/room33". Notice "//".
Also: according to the code it is possible to set a user name like this:
xmpp://[login@]hostname[:port][/room]
which would be nice to mention.
Also it is not clear at all how to set up password. Without password there is not too much use of this component so it is critical to document it.
If I am provided with access to confluence, I could fix it on my own. Mu login is "vchekan".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-690) XMPP component has wrong documentation
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-690:
------------------------------
Patch Info: (was: [Patch Available])
> XMPP component has wrong documentation
> --------------------------------------
>
> Key: CAMEL-690
> URL: https://issues.apache.org/activemq/browse/CAMEL-690
> Project: Apache Camel
> Issue Type: Bug
> Components: documentation
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Vadim Chekan
> Fix For: 1.5.0
>
>
> XMPP component page http://activemq.apache.org/camel/xmpp.html states that uri is "xmpp:hostname[:port][/room]". But in fact it does not work: the room is not recognised for "xmpp:jabber.org/room33". There is missing // to make it a valid hierarchical uri. See http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html
> Fix:
> the url should be "xmpp://vchekan@jabber.org/room33". Notice "//".
> Also: according to the code it is possible to set a user name like this:
> xmpp://[login@]hostname[:port][/room]
> which would be nice to mention.
> Also it is not clear at all how to set up password. Without password there is not too much use of this component so it is critical to document it.
> If I am provided with access to confluence, I could fix it on my own. Mu login is "vchekan".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-690) XMPP component has wrong documentation
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-690:
------------------------------
Fix Version/s: 1.5.0
Affects Version/s: 1.4.0
> XMPP component has wrong documentation
> --------------------------------------
>
> Key: CAMEL-690
> URL: https://issues.apache.org/activemq/browse/CAMEL-690
> Project: Apache Camel
> Issue Type: Bug
> Components: documentation
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Vadim Chekan
> Fix For: 1.5.0
>
>
> XMPP component page http://activemq.apache.org/camel/xmpp.html states that uri is "xmpp:hostname[:port][/room]". But in fact it does not work: the room is not recognised for "xmpp:jabber.org/room33". There is missing // to make it a valid hierarchical uri. See http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html
> Fix:
> the url should be "xmpp://vchekan@jabber.org/room33". Notice "//".
> Also: according to the code it is possible to set a user name like this:
> xmpp://[login@]hostname[:port][/room]
> which would be nice to mention.
> Also it is not clear at all how to set up password. Without password there is not too much use of this component so it is critical to document it.
> If I am provided with access to confluence, I could fix it on my own. Mu login is "vchekan".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-690) XMPP component has wrong documentation
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-690.
-------------------------------
Resolution: Fixed
Thanks for the reporting. There are a few tickets on the XMPP slated for 1.5 with features to set password and more.
> XMPP component has wrong documentation
> --------------------------------------
>
> Key: CAMEL-690
> URL: https://issues.apache.org/activemq/browse/CAMEL-690
> Project: Apache Camel
> Issue Type: Bug
> Components: documentation
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Vadim Chekan
> Fix For: 1.5.0
>
>
> XMPP component page http://activemq.apache.org/camel/xmpp.html states that uri is "xmpp:hostname[:port][/room]". But in fact it does not work: the room is not recognised for "xmpp:jabber.org/room33". There is missing // to make it a valid hierarchical uri. See http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html
> Fix:
> the url should be "xmpp://vchekan@jabber.org/room33". Notice "//".
> Also: according to the code it is possible to set a user name like this:
> xmpp://[login@]hostname[:port][/room]
> which would be nice to mention.
> Also it is not clear at all how to set up password. Without password there is not too much use of this component so it is critical to document it.
> If I am provided with access to confluence, I could fix it on my own. Mu login is "vchekan".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.