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]
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]
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] ?xml version=1.0 encoding=ISO-8859-1? !-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you under the Apache License, Version 2.0 (the ~ License); you may not use this file except in compliance ~ with the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, ~ software distributed under the License is distributed on an ~ AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~ KIND, either express or implied. See the License for the ~ specific language governing permissions and limitations ~ under the License. -- !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; web-app display-nameApache-Axis2/display-name servlet servlet-nameAxisServlet/servlet-name display-nameApache-Axis Servlet/display-name servlet-classorg.apache.axis2.transport.http.AxisServlet/servlet-class !--init-param-- !--param-nameaxis2.xml.path/param-name-- !--param-value/WEB-INF/conf/axis2.xml/param-value-- !--param-nameaxis2.xml.url/param-name-- !--param-valuehttp://localhot/myrepo/axis2.xml/param-value-- !--param-nameaxis2.repository.path/param-name-- !--param-value/WEB-INF/param-value-- !--param-nameaxis2.repository.url/param-name-- !--param-valuehttp://localhot/myrepo/param-value-- !--/init-param-- load-on-startup1/load-on-startup /servlet servlet servlet-nameAxisAdminServlet/servlet-name display-nameApache-Axis AxisAdmin Servlet (Web Admin)/display-name servlet-class org.apache.axis2.transport.http.AxisAdminServlet/servlet-class /servlet servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/servlet/AxisServlet/url-pattern
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-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] - 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
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
please try nightly it should work with unqualified as well. thanks, dims 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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLBeans binding issue
The nice thing about xmlbeans is that if the WSDL validates, xmlbeans will support it since it guarantees %100 xml schema support. So run your wsdl thru a validator like WTP from eclipse, and if it qualifies, xmlbeans via axis2 willl most likely work with it (otherwise its a bug). HTH, Robert 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]
