You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Pantvaidya, Vishwajit" <vp...@selectica.com> on 2007/11/28 03:49:41 UTC
[Axis2] 1.3 bug - services.xml mentions
ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated
code
I used Axis2 1.3 release wsdl2java to generate code and services.xml and find that the code is missing the ECMServiceMessageReceiverInOnly class. So when I build the aar and deploy it I get java.lang.ClassNotFoundException: ...ECMServiceMessageReceiverInOnly".
services.xml has:
<messageReceiver mep=http://www.w3.org/ns/wsdl/in-only class="...ECMServiceMessageReceiverInOnly"/>
<messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="...ECMServiceMessageReceiverInOut"/>
But the wsdl2java generated code has the ECMServiceMessageReceiverRobustInOnly class instead of ECMServiceMessageReceiverInOnly.
Then I tried wsdl2java with the Nov 9 nightly build and it deployed fine. I saw that the generated services.xml has:
<messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="...ECMServiceMessageReceiverInOut"/>
<messageReceiver mep="http://www.w3.org/ns/wsdl/robust-in-only" class="...ECMServiceMessageReceiverRobustInOnly"/>
and both the messagereceiver classes are generated by wsdl2java.
Is this a known problem in axis2-1.3 that was fixed later? If not - I could add it to the note I am planning to submit on the migration to axis2.
- Vish.
Re: [Axis2] 1.3 bug - services.xml mentions ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated code
Posted by Amila Suriarachchi <am...@gmail.com>.
I generated the code for your wsdl and in services.xml it generates it like
this
<messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="
com.selectica.ws.ecm.ECMServiceSoapMessageReceiverInOut"/>
<messageReceiver mep="http://www.w3.org/ns/wsdl/robust-in-only"
class="com.selectica.ws.ecm.ECMServiceSoapMessageReceiverRobustInOnly"/>
if you have time please check. with a new nighly build.
And also it is better to make sure you system works with axis2-SNAPSHOT. in
this way you can guarantee that you system works with next Axis2 release.
thanks,
Amila.
On Nov 30, 2007 7:01 AM, Pantvaidya, Vishwajit <vp...@selectica.com>
wrote:
> Wsdl attached (basically the services.xml is out of sync with the java
> code when I use Axis2 1.3 GA for wsdl2java).
>
>
>
> I am currently using the Nov 9 nightly for wsdl2java and 1.3 GA at runtime
> and that is working. I was just trying to see if I can use 1.3 GA release
> for wsdljava as well so that I can completely do away with the nightly
> build.
>
>
>
>
>
> - Vish.
>
>
> ------------------------------
>
> *From:* Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
> *Sent:* Thursday, November 29, 2007 2:30 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: [Axis2] 1.3 bug - services.xml mentions
> ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated
> code
>
>
>
> I tested with this wsdl, but seems good.
> can you attach your wsdl?
>
> Amila
>
> On Nov 29, 2007 3:40 PM, Amila Suriarachchi <amilasuriarachchi@gmail.com >
> wrote:
>
> this must be due to a change I recently did to remove depreciated class.
> I'll look at into it.
>
> Could you please attach your wsdl?
>
>
>
>
> On Nov 28, 2007 8:19 AM, Pantvaidya, Vishwajit < vpantvai@selectica.com>
> wrote:
>
> I used Axis2 1.3 release wsdl2java to generate code and services.xml and
> find that the code is missing the ECMServiceMessageReceiverInOnly class. So
> when I build the aar and deploy it I get java.lang.ClassNotFoundException:
> ...ECMServiceMessageReceiverInOnly".
>
>
>
> services.xml has:
>
> <messageReceiver mep=http://www.w3.org/ns/wsdl/in-onlyclass="...ECMServiceMessageReceiverInOnly"/>
>
> <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"
> class="...ECMServiceMessageReceiverInOut"/>
>
> But the wsdl2java generated code has the
> ECMServiceMessageReceiverRobustInOnly class instead of
> ECMServiceMessageReceiverInOnly.
>
>
>
> Then I tried wsdl2java with the Nov 9 nightly build and it deployed fine.
> I saw that the generated services.xml has:
>
> <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"
> class="...ECMServiceMessageReceiverInOut"/>
>
> <messageReceiver mep="http://www.w3.org/ns/wsdl/robust-in-only"
> class="…ECMServiceMessageReceiverRobustInOnly"/>
>
> and both the messagereceiver classes are generated by wsdl2java.
>
>
>
> Is this a known problem in axis2-1.3 that was fixed later? If not – I
> could add it to the note I am planning to submit on the migration to axis2.
>
>
>
>
>
> - Vish.
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
--
Amila Suriarachchi,
WSO2 Inc.
RE: [Axis2] 1.3 bug - services.xml mentions
ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated
code
Posted by "Pantvaidya, Vishwajit" <vp...@selectica.com>.
Wsdl attached (basically the services.xml is out of sync with the java code when I use Axis2 1.3 GA for wsdl2java).
I am currently using the Nov 9 nightly for wsdl2java and 1.3 GA at runtime and that is working. I was just trying to see if I can use 1.3 GA release for wsdljava as well so that I can completely do away with the nightly build.
- Vish.
________________________________
From: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
Sent: Thursday, November 29, 2007 2:30 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] 1.3 bug - services.xml mentions ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated code
I tested with this wsdl, but seems good.
can you attach your wsdl?
Amila
On Nov 29, 2007 3:40 PM, Amila Suriarachchi <amilasuriarachchi@gmail.com <ma...@gmail.com> > wrote:
this must be due to a change I recently did to remove depreciated class.
I'll look at into it.
Could you please attach your wsdl?
On Nov 28, 2007 8:19 AM, Pantvaidya, Vishwajit < vpantvai@selectica.com<ma...@selectica.com>> wrote:
I used Axis2 1.3 release wsdl2java to generate code and services.xml and find that the code is missing the ECMServiceMessageReceiverInOnly class. So when I build the aar and deploy it I get java.lang.ClassNotFoundException: ...ECMServiceMessageReceiverInOnly".
services.xml has:
<messageReceiver mep=http://www.w3.org/ns/wsdl/in-only class="...ECMServiceMessageReceiverInOnly"/>
<messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="...ECMServiceMessageReceiverInOut"/>
But the wsdl2java generated code has the ECMServiceMessageReceiverRobustInOnly class instead of ECMServiceMessageReceiverInOnly.
Then I tried wsdl2java with the Nov 9 nightly build and it deployed fine. I saw that the generated services.xml has:
<messageReceiver mep="http://www.w3.org/ns/wsdl/in-out" class="...ECMServiceMessageReceiverInOut"/>
<messageReceiver mep="http://www.w3.org/ns/wsdl/robust-in-only" class="...ECMServiceMessageReceiverRobustInOnly"/>
and both the messagereceiver classes are generated by wsdl2java.
Is this a known problem in axis2-1.3 that was fixed later? If not - I could add it to the note I am planning to submit on the migration to axis2.
- Vish.
--
Amila Suriarachchi,
WSO2 Inc.
--
Amila Suriarachchi,
WSO2 Inc.
Re: [Axis2] 1.3 bug - services.xml mentions ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated code
Posted by Amila Suriarachchi <am...@gmail.com>.
I tested with this wsdl, but seems good.
can you attach your wsdl?
Amila
On Nov 29, 2007 3:40 PM, Amila Suriarachchi <am...@gmail.com>
wrote:
> this must be due to a change I recently did to remove depreciated class.
> I'll look at into it.
>
> Could you please attach your wsdl?
>
>
>
>
> On Nov 28, 2007 8:19 AM, Pantvaidya, Vishwajit < vpantvai@selectica.com>
> wrote:
>
> > I used Axis2 1.3 release wsdl2java to generate code and services.xmland find that the code is missing the ECMServiceMessageReceiverInOnly class.
> > So when I build the aar and deploy it I get
> > java.lang.ClassNotFoundException: ...ECMServiceMessageReceiverInOnly".
> >
> >
> >
> > services.xml has:
> >
> > <messageReceiver mep=http://www.w3.org/ns/wsdl/in-onlyclass="...ECMServiceMessageReceiverInOnly"/>
> >
> > <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"
> > class="...ECMServiceMessageReceiverInOut"/>
> >
> > But the wsdl2java generated code has the
> > ECMServiceMessageReceiverRobustInOnly class instead of
> > ECMServiceMessageReceiverInOnly.
> >
> >
> >
> > Then I tried wsdl2java with the Nov 9 nightly build and it deployed
> > fine. I saw that the generated services.xml has:
> >
> > <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"
> > class="...ECMServiceMessageReceiverInOut"/>
> >
> > <messageReceiver mep="http://www.w3.org/ns/wsdl/robust-in-only"
> > class="…ECMServiceMessageReceiverRobustInOnly"/>
> >
> > and both the messagereceiver classes are generated by wsdl2java.
> >
> >
> >
> > Is this a known problem in axis2-1.3 that was fixed later? If not – I
> > could add it to the note I am planning to submit on the migration to axis2.
> >
> >
> >
> >
> >
> > - Vish.
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
--
Amila Suriarachchi,
WSO2 Inc.
Re: [Axis2] 1.3 bug - services.xml mentions ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated code
Posted by Amila Suriarachchi <am...@gmail.com>.
this must be due to a change I recently did to remove depreciated class.
I'll look at into it.
Could you please attach your wsdl?
On Nov 28, 2007 8:19 AM, Pantvaidya, Vishwajit <vp...@selectica.com>
wrote:
> I used Axis2 1.3 release wsdl2java to generate code and services.xml and
> find that the code is missing the ECMServiceMessageReceiverInOnly class. So
> when I build the aar and deploy it I get java.lang.ClassNotFoundException:
> ...ECMServiceMessageReceiverInOnly".
>
>
>
> services.xml has:
>
> <messageReceiver mep=http://www.w3.org/ns/wsdl/in-onlyclass="...ECMServiceMessageReceiverInOnly"/>
>
> <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"
> class="...ECMServiceMessageReceiverInOut"/>
>
> But the wsdl2java generated code has the
> ECMServiceMessageReceiverRobustInOnly class instead of
> ECMServiceMessageReceiverInOnly.
>
>
>
> Then I tried wsdl2java with the Nov 9 nightly build and it deployed fine.
> I saw that the generated services.xml has:
>
> <messageReceiver mep="http://www.w3.org/ns/wsdl/in-out"
> class="...ECMServiceMessageReceiverInOut"/>
>
> <messageReceiver mep="http://www.w3.org/ns/wsdl/robust-in-only"
> class="…ECMServiceMessageReceiverRobustInOnly"/>
>
> and both the messagereceiver classes are generated by wsdl2java.
>
>
>
> Is this a known problem in axis2-1.3 that was fixed later? If not – I
> could add it to the note I am planning to submit on the migration to axis2.
>
>
>
>
>
> - Vish.
>
--
Amila Suriarachchi,
WSO2 Inc.