Hi John,
Can we decide on this?

On 6/7/06, John Kaputin <[EMAIL PROTECTED]> wrote:
Chathura,
The dates in the URIs are changing as drafts of the WSDL 2.0 spec get
published. So for example, the latest version for in-out is
"http://www.w3.org/2006/01/wsdl/in-out"; .  My initial thinking was that we
(Woden and users of Woden) should support the latest version, given that
eventually the WSDL 2.0 spec will be finalized as a W3C Recommendation and
those dates will be fixed.   However, this Recommendation will most likely
not happen until around Jan 2007 and we do want Woden used before then. So
maybe a semantic model of the MEPs would be better than an absolute
representation? I'll give this some thought post M5 and wait to see what
other's have to say.

John Kaputin




             Deepal jayasinghe
             <[EMAIL PROTECTED]
             m>                                                         To
                                       [email protected]
             07/06/2006 08:40                                           cc

                                                                   Subject
             Please respond to         Re: MEP version issue
             [EMAIL PROTECTED]
                  he.org








Chathura;
I to encountered that problem yesterday, what I am thinking is we need
to change Axis2 to support both or latest .

Chathura Herath wrote:

> Hi,
> Can we have an internal static final representation for the MEP's
> other than the URI. Reason fo r raising this issue is that MEP uris do
> change and Axis2's MEP uri's are different version that of the woden
> MEP URIs. So i am having a hard time comparing them with axis2's woden
> URIs.  So what i propose is somethims like the following
>
> public class WodenMEPVersionResolver{
>
> public static final int WODEN_IN_OUT_MEP =0;
> .......
>
> public static final String IN_OUT_MEP_URI_VERSION_08_04 =
> "http://www.w3.org/2004/08/wsdl/in-out";;
> public static final String IN_OUT_MEP_URI_VERSION_03_04 =
> "http://www.w3.org/2004/03/wsdl/in-out";;
> etc....
>
>
>
> public static int getMEP(URI somemepURI){
>
>  if(IN_OUT_MEP_URI_VERSION_08_04.equals(somemepuri.toString()) ||
>       IN_OUT_MEP_URI_VERSION_03_04.equals(somemepuri.toString()){
>
>    return WODEN_IN_OUT_MEP;
> } else if(...){
>
> }......
>
>
> }
> }
>
> This way we introduce the semantic meaning of the MEP uri and it is
> indeed the semantic meaning that we (applications like axis2) is
> interested in
>
> Comments??
>


--
Thanks,
Deepal
................................................................
~Future is Open~


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to