RE: SOAP Namespace

"Alan D. Cabrera" <[email protected]>
Newsgroups gmane.comp.java.mx4j.devel
Message-ID <[email protected]>
Two things.  The first is really teeney, I prefer to use "_" instead of
".".  Second, I think that the name should be something like
www.mx4j.org instead of mx4j.sourceforge.net, since mx4j is really an
entity that at the moment happens to reside at sf.net, not a business
entity of Source Forge.

http://www.mx4j.org/remote/soap/1_0

JMHO.


Regards,
Alan

-----Original Message-----
From: Bordet, Simone [mailto:[email protected]] 
Sent: Thursday, October 09, 2003 3:45 AM
To: MX4J-Dev (E-mail)
Subject: [Mx4j-devel] SOAP Namespace

I posted on axis-dev asking for best practices on choosing namespaces,
and got no answer.
However, an interesting discussion has been held on geronimo-dev about
similar argument, and I am now convinced that the namespace should have
a version indicator that represent the implementation version.
About the remote JMX version, I think we will support the latest one in
any case, like we do with JMX, so it is redundant to specify it.

I propose to use 

http://mx4j.sourceforge.net/remote/soap/1.0

as namespace for the SOAP implementation.

Any comment ?

Simon


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Mx4j-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mx4j-devel


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.