J2ME and Axis2
Hi! Some exotic question. Is it possible to deploy Axis2 service (not client!) +XMLBeans (preferable or may be other binding) to J2ME CDC, providing there is working servlet-container? Best regards, Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ALEServiceMessageReceiverInOut 1.3-RC2
Hi!
After wsdl2java code generation you can see:
public class ALEServiceMessageReceiverInOut extends
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver{...
where AbstractInOutSyncMessageReceiver is marked as deprecated. What is the
right approach: use AbstractInOutSyncMessageReceiver? Something else?
Thanks,
Anton
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: XMLBeans binding issue
axis2-soapmonitor-1.3-SNAPSHOT.jar was absent in
axis2-SNAPSHOT-war.zip 15 244 540 17.07.2007 09:22
Антон
> -Original Message-
> From: robert lazarski [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 19, 2007 12:14 AM
> To: axis-user@ws.apache.org
> Subject: Re: XMLBeans binding issue
>
> Might be an issue with the nightlies. Are you using the axis2.war from
> the nightlies? Do you have axis2-soapmonitor-1.3-SNAPSHOT.jar and that
> is where you are getting the applet classes from?
>
> Thanks,
> Robert
>
> On 7/18/07, Anton Zhilin <[EMAIL PROTECTED]> wrote:
> > I just receive error page.
> >
> > HTTP Status 503 - Servlet SOAPMonitorService is currently unavailable
> > type Status report
> > message Servlet SOAPMonitorService is currently unavailable
> > description The requested service (Servlet SOAPMonitorService is
> currently
> > unavailable) is not currently available.
> > Apache Tomcat/4.1.31
> >
> > I configured it as usual (in 1.2 it works).
> > SOAPMonitorApplet*.class was copied from 1.2 distribution, because
> > WEB-INF/lib/axis2-soapmonitor-*.jar is absent ("You can directly get
> the
> > compiled applet classes from the WEB-INF/lib/axis2-soapmonitor-*.jar
> which
> > is inside the extracted axis2.war." in manual). I'm I wrong?
> >
> > Configs are attached.
> >
> > Anton.
> >
> > > -Original Message-
> > > From: robert lazarski [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, July 18, 2007 11:46 PM
> > > To: axis-user@ws.apache.org
> > > Subject: Re: XMLBeans binding issue
> > >
> > > What problem did you have with the soap monitor ?
> > >
> > > Robert
> > >
> > > On 7/18/07, Anton Zhilin <[EMAIL PROTECTED]> wrote:
> > > > Thank you very much! It seams to work!
> > > >
> > > > The only problem now is I can't make SOAP-monitor in SNAPSHOT to
> work.
> > > So I
> > > > need some time to test everything with another tool.
> > > >
> > > > I hope this fix will be in next version.
> > > >
> > > > A.
> > > >
> > > > > please try nightly it should work with unqualified as well.
> > > > >
> > > > > thanks,
> > > > > dims
> > > > >
> > > > >
> > > > > --
> > > > > Davanum Srinivas :: http://davanum.wordpress.com
> > > >
> > > > >
> > > > > On 7/17/07, Anton Zhilin <[EMAIL PROTECTED]> wrote:
> > > > > > Hello,
> > > > > >
> > > > > > Can somebody tell me, is possible to set up Axis2 Web-Service
> based
> > > on
> > > > > > existing WSDL, if WSDL has an attribute
> > > > > elementFormDefault="UNqualified"?
> > > > > >
> > > > > > I now the "decision", that works: turn the attribute to
> > > > > > elementFormDefault="qualified". But I have predefined WSDL and
> MUST
> > > have
> > > > > > "unqualified" value.
> > > > > >
> > > > > > Similar questions arisen many times, but the only remedy was
> > > > > > elementFormDefault="qualified".
> > > > > > (The last time it seems was
> > > > > > http://www.mail-archive.com/axis-
> [EMAIL PROTECTED]/msg26184.html)
> > > > > >
> > > > > > Is there decision for XMLBeans? Other bindings? Or I should use
> > > > > different
> > > > > > framework?
> > > > > >
> > > > > > I use XMLBeans binding, Axis2 1.2, JDK 1.4.2_15, Tomcat 4.1.
> > > > > >
> > > > > > Thanks in advance,
> > > > > > Anton
> > > > > >
> > > > > >
> > > > > >
> > > > > >
>
> > > -
> > > > > > 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]
> > > >
> > > >
> > > >
> -
> > > > 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]
> >
> > -
> > 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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: XMLBeans binding issue
I just receive error page.
HTTP Status 503 - Servlet SOAPMonitorService is currently unavailable
type Status report
message Servlet SOAPMonitorService is currently unavailable
description The requested service (Servlet SOAPMonitorService is currently
unavailable) is not currently available.
Apache Tomcat/4.1.31
I configured it as usual (in 1.2 it works).
SOAPMonitorApplet*.class was copied from 1.2 distribution, because
WEB-INF/lib/axis2-soapmonitor-*.jar is absent ("You can directly get the
compiled applet classes from the WEB-INF/lib/axis2-soapmonitor-*.jar which
is inside the extracted axis2.war." in manual). I'm I wrong?
Configs are attached.
Anton.
> -Original Message-
> From: robert lazarski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 18, 2007 11:46 PM
> To: axis-user@ws.apache.org
> Subject: Re: XMLBeans binding issue
>
> What problem did you have with the soap monitor ?
>
> Robert
>
> On 7/18/07, Anton Zhilin <[EMAIL PROTECTED]> wrote:
> > Thank you very much! It seams to work!
> >
> > The only problem now is I can't make SOAP-monitor in SNAPSHOT to work.
> So I
> > need some time to test everything with another tool.
> >
> > I hope this fix will be in next version.
> >
> > A.
> >
> > > please try nightly it should work with unqualified as well.
> > >
> > > thanks,
> > > dims
> > >
> > >
> > > --
> > > Davanum Srinivas :: http://davanum.wordpress.com
> >
> > >
> > > On 7/17/07, Anton Zhilin <[EMAIL PROTECTED]> wrote:
> > > > Hello,
> > > >
> > > > Can somebody tell me, is possible to set up Axis2 Web-Service based
> on
> > > > existing WSDL, if WSDL has an attribute
> > > elementFormDefault="UNqualified"?
> > > >
> > > > I now the "decision", that works: turn the attribute to
> > > > elementFormDefault="qualified". But I have predefined WSDL and MUST
> have
> > > > "unqualified" value.
> > > >
> > > > Similar questions arisen many times, but the only remedy was
> > > > elementFormDefault="qualified".
> > > > (The last time it seems was
> > > > http://www.mail-archive.com/axis-user@ws.apache.org/msg26184.html)
> > > >
> > > > Is there decision for XMLBeans? Other bindings? Or I should use
> > > different
> > > > framework?
> > > >
> > > > I use XMLBeans binding, Axis2 1.2, JDK 1.4.2_15, Tomcat 4.1.
> > > >
> > > > Thanks in advance,
> > > > Anton
> > > >
> > > >
> > > >
> > > >
> -
> > > > 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]
> >
> >
> > -
> > 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]
http://java.sun.com/dtd/web-app_2_3.dtd";>
Apache-Axis2
AxisServlet
Apache-Axis Servlet
org.apache.axis2.transport.http.AxisServlet
1
AxisAdminServlet
Apache-Axis AxisAdmin Servlet (Web Admin)
org.apache.axis2.transport.http.AxisAdminServlet
AxisServlet
/servlet/AxisServlet
AxisServlet
*.jws
AxisServlet
/services/*
AxisAdminServlet
/axis2-admin/*
index.jsp
index.html
/axis2-web/index.jsp
404
/axis2-web/Error/error404.jsp
500
/axis2-web/Error/error500.jsp
SOAPMonitorService
SOAPMonitorService
org.apache.axis2.soapmonitor.servlet.SOAPMonitorService
1
SOAPMonitorService
/SOAPMonitor
true
false
false
false
3
RE: XMLBeans binding issue
Thank you very much! It seams to work! The only problem now is I can't make SOAP-monitor in SNAPSHOT to work. So I need some time to test everything with another tool. I hope this fix will be in next version. A. > please try nightly it should work with unqualified as well. > > thanks, > dims > > > -- > Davanum Srinivas :: http://davanum.wordpress.com > > On 7/17/07, Anton Zhilin <[EMAIL PROTECTED]> wrote: > > Hello, > > > > Can somebody tell me, is possible to set up Axis2 Web-Service based on > > existing WSDL, if WSDL has an attribute > elementFormDefault="UNqualified"? > > > > I now the "decision", that works: turn the attribute to > > elementFormDefault="qualified". But I have predefined WSDL and MUST have > > "unqualified" value. > > > > Similar questions arisen many times, but the only remedy was > > elementFormDefault="qualified". > > (The last time it seems was > > http://www.mail-archive.com/axis-user@ws.apache.org/msg26184.html) > > > > Is there decision for XMLBeans? Other bindings? Or I should use > different > > framework? > > > > I use XMLBeans binding, Axis2 1.2, JDK 1.4.2_15, Tomcat 4.1. > > > > Thanks in advance, > > Anton > > > > > > > > - > > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XMLBeans binding issue
Hello, Can somebody tell me, is possible to set up Axis2 Web-Service based on existing WSDL, if WSDL has an attribute elementFormDefault="UNqualified"? I now the "decision", that works: turn the attribute to elementFormDefault="qualified". But I have predefined WSDL and MUST have "unqualified" value. Similar questions arisen many times, but the only remedy was elementFormDefault="qualified". (The last time it seems was http://www.mail-archive.com/axis-user@ws.apache.org/msg26184.html) Is there decision for XMLBeans? Other bindings? Or I should use different framework? I use XMLBeans binding, Axis2 1.2, JDK 1.4.2_15, Tomcat 4.1. Thanks in advance, Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
