Re: SimpleTypeMapper xs:date convertion bug
this is fixed already.
thanks,
Amila.
[1]
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/adb/src/org/apache/axis2/databinding/typemapping/SimpleTypeMapper.java?r1=783787r2=835823
2009/12/14 Dinçer Karaduman dincer.karadu...@hititcs.com
Hi All,
I think there is a bug in org\apache\axis2\databinding\typemapping.java in
Axis2 1.5
public static Object makeDate(String source) {
return ConverterUtil.convertToDateTime(source).getTime();
}
this code requires convertToDateTime validation and raises an number format
exception for 12.12.1987 for example.
i think makeDate should be like
public static Object makeDate(String source) {
return ConverterUtil.convertToDate(source);
}
Am i right or is there anything i could not see?
--
*Dinçer Karaduman*
*Analyst Programmer*
*Hitit Bilgisayar Hizmetleri*
Tel : 212 276 15 00 Ext. 124
Fax: 212 276 15 17
www.hititcs.com
*Kişiye özel bu mesaj ve içeriğindeki bilgiler gizlidir. Hitit Bilgisayar
Hizmetleri bu mesajın içeriği ve ekleri ile ilgili olarak hukuksal hiçbir
sorumluluk kabul etmez. Yetkili alıcılardan biri değilseniz, bu mesajın
herhangi bir şekilde ifşa edilmesi, kullanılması, kopyalanması, yayılması
veya mesajda yeralan hususlarla ilgili olarak herhangi bir işlem
yapılmasının kesinlikle yasak olduğunu bildiririz. Böyle bir durumda lütfen
hemen mesajın göndericisini bilgilendiriniz ve mesajı sisteminizden siliniz.
Internet ortamında gönderilen e-posta mesajlarındaki hata ve/veya
eksikliklerden veya virüslerden dolayı mesajın göndericisi herhangi bir
sorumluluk kabul etmemektedir. Teşekkür ederiz. *
*The information contained in this communication may contain confidential
or legally privileged information. Hitit Computer Services doesn't accept
any legal responsibility for the contents and attachments of this message.
If you are not the intended recipient you are hereby notified that any
disclosure, use, copying, distribution or taking any action in reliance on
the contents of this information is strictly prohibited. If you have
received this communication in error, please notify the sender immediately
by responding to this e-mail and then delete it from your system. The sender
does not accept any liability for any errors or omissions or any viruses in
the context of this message which arise as a result of internet
transmission. Thank you. *
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: [Axis2] Adb MTOM bug
On Thu, Oct 1, 2009 at 11:51 PM, Saminda Abeyruwan samin...@gmail.comwrote: Thank you! Saminda On Tue, Sep 29, 2009 at 1:50 AM, Andreas Veithen andreas.veit...@gmail.com wrote: Yes, this has already been fixed in trunk. Yeah, and this issue should occur only if you were in DEBUG mode (or above) in log4j. Thanks, Senaka. Andreas On Tue, Sep 29, 2009 at 07:34, Saminda Abeyruwan samin...@gmail.com wrote: Hi Devs, I am currently using Axis2 1.5 for my research. I have stumble upon a MTOM data binding bug. I have a service which send me a pdf file. The client is generated using adb. The exception I get is attached herewith. I fixed the problem in generated code: where it occurs in parse method of GetResponse (line: 463). This line says, object.set_return(((org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder) ((org.apache.axiom.om.impl.llom.OMStAXWrapper) reader).getBuilder()).getDataHandler(id)); IMHO, prior should be changed to object.set_return(((OMXMLStreamReaderValidator)reader).getDataHandler(id)); to generated code to work. Is this bug already fixed in truck ?. If not I'll open a JIRA and attahced a patch. I am kinda hate to mess up the templates. :-) I have attached a simple service that can be used to re-create this bug. Thank you! Saminda == org.apache.axis2.AxisFault: org.apache.axiom.om.util.OMXMLStreamReaderValidator cannot be cast to org.apache.axiom.om.impl.llom.OMStAXWrapper at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at edu.miami.cs.client.LibraryServiceStub.fromOM(LibraryServiceStub.java:1252) at edu.miami.cs.client.LibraryServiceStub.get(LibraryServiceStub.java:481) at Client.main(Client.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) ==
Re: [Axis2] Adb MTOM bug
Thank you! Saminda On Tue, Sep 29, 2009 at 1:50 AM, Andreas Veithen andreas.veit...@gmail.comwrote: Yes, this has already been fixed in trunk. Andreas On Tue, Sep 29, 2009 at 07:34, Saminda Abeyruwan samin...@gmail.com wrote: Hi Devs, I am currently using Axis2 1.5 for my research. I have stumble upon a MTOM data binding bug. I have a service which send me a pdf file. The client is generated using adb. The exception I get is attached herewith. I fixed the problem in generated code: where it occurs in parse method of GetResponse (line: 463). This line says, object.set_return(((org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder) ((org.apache.axiom.om.impl.llom.OMStAXWrapper) reader).getBuilder()).getDataHandler(id)); IMHO, prior should be changed to object.set_return(((OMXMLStreamReaderValidator)reader).getDataHandler(id)); to generated code to work. Is this bug already fixed in truck ?. If not I'll open a JIRA and attahced a patch. I am kinda hate to mess up the templates. :-) I have attached a simple service that can be used to re-create this bug. Thank you! Saminda == org.apache.axis2.AxisFault: org.apache.axiom.om.util.OMXMLStreamReaderValidator cannot be cast to org.apache.axiom.om.impl.llom.OMStAXWrapper at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at edu.miami.cs.client.LibraryServiceStub.fromOM(LibraryServiceStub.java:1252) at edu.miami.cs.client.LibraryServiceStub.get(LibraryServiceStub.java:481) at Client.main(Client.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) ==
Re: [Axis2] Adb MTOM bug
Yes, this has already been fixed in trunk. Andreas On Tue, Sep 29, 2009 at 07:34, Saminda Abeyruwan samin...@gmail.com wrote: Hi Devs, I am currently using Axis2 1.5 for my research. I have stumble upon a MTOM data binding bug. I have a service which send me a pdf file. The client is generated using adb. The exception I get is attached herewith. I fixed the problem in generated code: where it occurs in parse method of GetResponse (line: 463). This line says, object.set_return(((org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder) ((org.apache.axiom.om.impl.llom.OMStAXWrapper) reader).getBuilder()).getDataHandler(id)); IMHO, prior should be changed to object.set_return(((OMXMLStreamReaderValidator)reader).getDataHandler(id)); to generated code to work. Is this bug already fixed in truck ?. If not I'll open a JIRA and attahced a patch. I am kinda hate to mess up the templates. :-) I have attached a simple service that can be used to re-create this bug. Thank you! Saminda == org.apache.axis2.AxisFault: org.apache.axiom.om.util.OMXMLStreamReaderValidator cannot be cast to org.apache.axiom.om.impl.llom.OMStAXWrapper at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at edu.miami.cs.client.LibraryServiceStub.fromOM(LibraryServiceStub.java:1252) at edu.miami.cs.client.LibraryServiceStub.get(LibraryServiceStub.java:481) at Client.main(Client.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) ==
Re: Howto report a BUG on axis2j
The address of the bug tracker is: http://issues.apache.org/jira Regards, Andreas On Tue, Jul 21, 2009 at 16:37, Meindert Oldenburgermeindert.oldenbur...@pallas-athena.com wrote: Hello, It is possible that i found a serious bug, it cost me days to find out that it is not our application, we think, but tomcat/axis2j webserver combination. Description of our test environment: We have two services in the webserver (tomcat/axis2j), one gives the axis version, and another calculates two numbers and returns the result. This means that both services results in two different wsdl's. Now we have a client that gets the wsdl (libcurl) and tries to find the operation expected to be in the wsdl. GetVersion?wsdl has operation show_version TestService?wsdl has operation calc_numbers Description of the problem: Now we start calling two clients at ones (parallel) xxx times. Each client knows about which operation belongs to a particular web services. Now we think that the web server is not always sending the correct wsdl back to a particular client. To exclude problems on our side, we set-up another machine with the same webservices and call only web-services A from machine A and web-services B from machine B. Now we have no problem. Best regards, Meindert Meindert Oldenburger | Software Engineer Piet Joubertstraat 4 | 7315 AV | Apeldoorn | The Netherlands T: +31 (0)55 368 53 00 | F: +31 (0)55 368 53 11 www.pallas-athena.com Pallas Athena International Business Process Management software solutions
RE: Axis2/c Blocker bug, when this can be fixed? queryString in end point URL is ingored in axis2/c client
Hi Dimuthu Gamage, I have filed a JIRA AXIS2C-1343 for this issue. Please do needful to fix this issue as this is a blocking to use axis2/c 1.5.0. Thanksyou're your support. Thanks -Srini -Original Message- From: Frank Zhou [mailto:fcho...@yahoo.com] Sent: Friday, February 06, 2009 4:48 PM To: Apache AXIS C Developers List Subject: Axis2/c Blocker bug, when this can be fixed? queryString in end point URL is ingored in axis2/c client Hi There, Just wonder when this bug can be fixed, this is really a blocker! It prevents me from using axis2/c 1.5. Thanks! --- On Thu, 2/5/09, Frank Zhou (JIRA) j...@apache.org wrote: From: Frank Zhou (JIRA) j...@apache.org Subject: [jira] Created: (AXIS2C-1343) queryString in end point URL is ingored in axis2/c client To: axis-c-dev@ws.apache.org Date: Thursday, February 5, 2009, 9:25 AM queryString in end point URL is ingored in axis2/c client - Key: AXIS2C-1343 URL: https://issues.apache.org/jira/browse/AXIS2C-1343 Project: Axis2-C Issue Type: Bug Components: core/engine Affects Versions: 1.5.0 Environment: windows XP as well as Unix, I'm using axis2/c to build a web service client component Reporter: Frank Zhou Priority: Blocker I have been consuming a web service by sending the request to the following end point address: http://host:8080/products/servlet/webservices?ver=2.0 This end point location is extracted in the WSDL file. When I was using axis2/c 1.3, server side (built in Java) correctly got the queryString ver=2.0, but when I upgrade to axis2/c 1.5, the server side got null value for the queryString. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Is there a bug with Axiom XPath and Multiple namespaces?
This seems to be an issue that is related to how XML messages are processed in Axis2. I have simplified my example and have noticed that XPath expressions function differently depending on how the XML fragment was constructed. I cannot get an XPath expression to work in an Axis2 service, but I can use the exact same expression on the exact same xml fragment (created with StaXOMBuilder), and it works. Here is a sample XML: ns:makesGet xmlns:ns=http://www.whisolutions.com/PartSelectService/2008-10-07; makesGetParms PSSAccessKeyJoe/PSSAccessKey Password1/Password Year1998/Year UseConfigy/UseConfig Version2008-10-07/Version !--You may enter ANY elements at this point-- /makesGetParms /ns:makesGet The following code returns results when the XML was built with the StaXOMBuilder. It does not return results inside an Axis2 web service, for the same fragment: String xpathString = /a:makesGet/makesGetParms/PSSAccessKey; AXIOMXPath xpathExpression = new AXIOMXPath (xpathString); xpathExpression.addNamespace(a, http://www.whisolutions.com/PartSelectService/2008-10-07;); List listOfNodes = xpathExpression.selectNodes(documentElement); In the web service, I am using the OMElement that is passed to me by the RawXMLINOutMessageReceiver. When I get this element, I process it as follows, before trying the XPath: element.build(); element.detach(); I also tried declaring the namespace: element.declareNamespace(http://www.whisolutions.com/PartSelectService/2008-10-07;, ns); In Eclipse, here are the base properties of the OMElement in an Axis2 web service (Note that when I declare the namespace, I see it, but it doesn't make the XPath work): http://www.nabble.com/file/p19860410/soap.jpg Here are the properties of the OMElement built by the StaxOMBuilder: http://www.nabble.com/file/p19860410/stax.jpg Has anyone successfully used XPath in a web service where the WSDL has a namespace? Here is my current WSDL: http://www.nabble.com/file/p19860410/PartSelect_v1_0.wsdl PartSelect_v1_0.wsdl -- View this message in context: http://www.nabble.com/Is-there-a-bug-with-Axiom-XPath-and-Multiple-namespaces--tp19723540p19860410.html Sent from the Axis - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
1.3.1 Release Manager [was Re: [Axis2] 1.3 release bug]
Can we have a volunteer to be the RM for 1.3.1 please? Thanks, Samisa... Dinesh Premalal wrote: On Wed, Apr 2, 2008 at 2:09 PM, Samisa Abeysinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Samisa Abeysinghe wrote: I happen to find that the libs created with 1.3.0 has the extension so.0.2.0. This should be 0.3.0 I suppose. This calls for a patch release? +1 thanks, Dinesh -- http://nethu.org/ No virus found in this incoming message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.2/1353 - Release Date: 3/31/2008 6:21 PM -- Samisa Abeysinghe Software Architect; WSO2 Inc. http://www.wso2.com/ - Oxygenating the Web Service Platform. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] 1.3 release bug
Samisa Abeysinghe wrote: I happen to find that the libs created with 1.3.0 has the extension so.0.2.0. This should be 0.3.0 I suppose. This calls for a patch release? Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] 1.3 release bug
On Wed, Apr 2, 2008 at 2:09 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Samisa Abeysinghe wrote: I happen to find that the libs created with 1.3.0 has the extension so.0.2.0. This should be 0.3.0 I suppose. This calls for a patch release? +1 thanks, Dinesh -- http://nethu.org/
Re: Re:[Axis2] Axis2-Plugin-Bug?
Hi Matthias, can you post us the method signature in your java application that causes the WSDL to break, This will help us quickly to reproduce the problem and fix, if any. Thanks Lahiru On 10/3/07, Jaliya Ekanayake [EMAIL PROTECTED] wrote: Hi Matthias, It is the GregorianCalendar that causes the trouble and the generated wsdl is not recognized by the plugin. There is an old maling thread regarding this but could not find any outstanding jira about this. http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200401.mbox/[EMAIL PROTECTED] Hope someone in the dev list will help you. Thanks, -jaliya - Original Message - From: [EMAIL PROTECTED] To: Jaliya Ekanayake [EMAIL PROTECTED] Sent: Tuesday, October 02, 2007 9:11 AM Subject: Re:[Axis2] Axis2-Plugin-Bug? Hi Jaliya, for a better understanding of what I did I send you some screenshots of these steps. Hope this helps. Matthias -Ursprüngliche Nachricht- Von: Jaliya Ekanayake [EMAIL PROTECTED] Gesendet: 01.10.07 17:46:54 An: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Betreff: Re:[Axis2] Axis2-Plugin-Bug? Hi Matthias, Please let us know which version of Axis2 you are using. -jaliya -Original Message- From: Matthias Längrich [mailto:[EMAIL PROTECTED] Sent: Monday, October 01, 2007 9:25 AM To: [EMAIL PROTECTED] Subject: Axis2-Plugin-Bug? Jaliya, I just created a small Java-application and used the archiver plugin to get it deployed as a web service. Afterwards, I created a wsdl using the code generator plug in. Everything works fine. Right now I'm trying to generate some client code out of the formerly created wsdl. The wizard asks me to point to the file. I'm doing so using the browse button. The path is correct. I press next and it says me that Specified WSDL is not found!. That's unclear to me since the file is definitely there. Here's the path (don't mind the German words): C:\Dokumente und Einstellungen\laengrich\Eigene Dateien\workspace\WSTest02\time.wsdl I don't think that the spaces are a problem because some steps before, where I had to select a class, they didn't make any problems. The same is true for the backslash. Well, I don't have a clue. How can I get the plugin accepting this wsdl? Yours Sincerely Matthias _ Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179 ___ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: Re:[Axis2] Axis2-Plugin-Bug?
Hi Matthias, It is the GregorianCalendar that causes the trouble and the generated wsdl is not recognized by the plugin. There is an old maling thread regarding this but could not find any outstanding jira about this. http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200401.mbox/[EMAIL PROTECTED] Hope someone in the dev list will help you. Thanks, -jaliya - Original Message - From: [EMAIL PROTECTED] To: Jaliya Ekanayake [EMAIL PROTECTED] Sent: Tuesday, October 02, 2007 9:11 AM Subject: Re:[Axis2] Axis2-Plugin-Bug? Hi Jaliya, for a better understanding of what I did I send you some screenshots of these steps. Hope this helps. Matthias -Ursprüngliche Nachricht- Von: Jaliya Ekanayake [EMAIL PROTECTED] Gesendet: 01.10.07 17:46:54 An: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Betreff: Re:[Axis2] Axis2-Plugin-Bug? Hi Matthias, Please let us know which version of Axis2 you are using. -jaliya -Original Message- From: Matthias Längrich [mailto:[EMAIL PROTECTED] Sent: Monday, October 01, 2007 9:25 AM To: [EMAIL PROTECTED] Subject: Axis2-Plugin-Bug? Jaliya, I just created a small Java-application and used the archiver plugin to get it deployed as a web service. Afterwards, I created a wsdl using the code generator plug in. Everything works fine. Right now I'm trying to generate some client code out of the formerly created wsdl. The wizard asks me to point to the file. I'm doing so using the browse button. The path is correct. I press next and it says me that Specified WSDL is not found!. That's unclear to me since the file is definitely there. Here's the path (don't mind the German words): C:\Dokumente und Einstellungen\laengrich\Eigene Dateien\workspace\WSTest02\time.wsdl I don't think that the spaces are a problem because some steps before, where I had to select a class, they didn't make any problems. The same is true for the backslash. Well, I don't have a clue. How can I get the plugin accepting this wsdl? Yours Sincerely Matthias _ Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179 ___ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] A possible bug in WSDLDataLocator?
YG,
Please log a bug in JIRA. Someone will need to take a very close look
at the code again.
thanks,
dims
On 5/26/07, YG Park [EMAIL PROTECTED] wrote:
Hi,
I'm new to Axis2 and while I was using Axis2 1.2, I encountered a strange
behavior.
The module I was working on was working just fine on my dev machine but when
I deployed a service on our production server, it failed to find the
service.
The production server runs on Apache/Tomcat and has several sites running on
it (using VirtualHost).
I checked the generated WSDL and found out that instead of using the FQDN on
the server,
Axis2 was actually changing the FQDN to an IP address and since Apache
wasn't delegating IP address HOSTs to tomcat, the client using this WS was
giving me 404 (HTTP Not found) error.
I sort of debugged the code and WSDLDataLocator
(org.apache.axis2.dataretrieval) line 125 was causing this problem.
String[] exposedEPRs = theService.getEPRs();
I changed this line to
String[] exposedEPRs = new String[] {serviceURL};
and it's working just fine. However, I can see that an AxisService can have
more than one EPRs and that this is just a workaround.
Has anybody else encountered this problem?
Please let me know.
Plus, I wasn't really sure why line 126-128 exists
if (exposedEPRs == null) {
exposedEPRs = new String[]{theService.getEndpointName()};
}
as theService.getEndpointName() always returns null.
Thanks.
--
Davanum Srinivas :: http://davanum.wordpress.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: DO NOT REPLY [Bug 21519] - [doc/lit] doc/literal parameters used as service name
We don't use Bugzilla any more. Please use JIRA: http://ws.apache.org/axis/bugs.html -- Tom Jordahl Adobe ColdFusion Team -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, April 20, 2007 1:51 PM To: axis-dev@ws.apache.org Subject: DO NOT REPLY [Bug 21519] - [doc/lit] doc/literal parameters used as service name DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG* RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=21519. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND* INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=21519 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2007-04-20 10:50 --- I am developer who is working on XFire web service consuming Axis 1.1 web service. As XFire does not support RPC/encoded use/style, I had to make the Axis side to expose the webservice using doc/literal style. I then encountered this bug 21519. This bug was closed, but I did not see any solution here. Did I miss anything? I assume it a major issue as XFire Axis interoperability would become more and more demanding. Please help. Thanks in advance! Sincerely Feng [EMAIL PROTECTED] -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - 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: Possible Axis 1.4 Bug
Please summarize the problem for us. On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Hello, first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6. We've found an issue wih the namespaces in the SOAP message returned by Axis. In order to follow this issue from the begining to the analysis of the problem, please, follow this thread at NetBeans Enterprise Pack Mailing list: http://www.netbeans.org/servlets/BrowseList?list=nbentpackby=threadfrom=772248 Thank you! [image: BATZ S.COOP] Ibai Perez Arbulu [EMAIL PROTECTED] *BATZ S. COOP *Torrea Auzoa,32 48140 IGORRE, (Bizkaia) - Spain Tfn: +34 946305000 Fax +34 946305020 *http://www.batz.com * *P* *Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da.* *No imprima este mensaje o sus documentos adjuntos, a no ser que sea verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa nuestra* La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y esta destinada a ser leída solo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que esta totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.
RE: Possible Axis 1.4 Bug
Please, read the last 6 mails (from 2007-03-02 on), they sumarize the key subject! P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read client as partner! Thank you! De: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Enviado el: miércoles, 07 de marzo de 2007 15:29 Para: axis-dev@ws.apache.org Asunto: Re: Possible Axis 1.4 Bug Please summarize the problem for us. On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Hello, first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6. We've found an issue wih the namespaces in the SOAP message returned by Axis. In order to follow this issue from the begining to the analysis of the problem, please, follow this thread at NetBeans Enterprise Pack Mailing list: http://www.netbeans.org/servlets/BrowseList?list=nbentpackby=threadfrom=772248 Thank you! BATZ S.COOP Ibai Perez Arbulu [EMAIL PROTECTED] BATZ S. COOP Torrea Auzoa,32 48140 IGORRE, (Bizkaia) - Spain Tfn: +34 946305000 Fax +34 946305020 http://www.batz.com http://www.batz.com/ P Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da. No imprima este mensaje o sus documentos adjuntos, a no ser que sea verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa nuestra La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y esta destinada a ser leída solo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que esta totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.
Re: Possible Axis 1.4 Bug
The last 6 mails don't provide enough information. Please summarize the problem. Include appropriate WSDLs, WSDDs, etc. Thanks, Anne On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Please, read the last 6 mails (from 2007-03-02 on), they sumarize the key subject! P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read client as partner! Thank you! -- *De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED] *Enviado el:* miércoles, 07 de marzo de 2007 15:29 *Para:* axis-dev@ws.apache.org *Asunto:* Re: Possible Axis 1.4 Bug Please summarize the problem for us. On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Hello, first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6. We've found an issue wih the namespaces in the SOAP message returned by Axis. In order to follow this issue from the begining to the analysis of the problem, please, follow this thread at NetBeans Enterprise Pack Mailing list: http://www.netbeans.org/servlets/BrowseList?list=nbentpackby=threadfrom=772248 Thank you! [image: BATZ S.COOP] Ibai Perez Arbulu [EMAIL PROTECTED] *BATZ S. COOP *Torrea Auzoa,32 48140 IGORRE, (Bizkaia) - Spain Tfn: +34 946305000 Fax +34 946305020 *http://www.batz.com * *P* *Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da.* *No imprima este mensaje o sus documentos adjuntos, a no ser que sea verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa nuestra* La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y esta destinada a ser leída solo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que esta totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.
Re: Possible Axis 1.4 Bug
btw -- after you did this: As you can see in the project I send some days before, I took this WSDL and removed the Schema to paste it in the Operacion.xsd file under the http://serv.wsutils.batz.com; http://serv.wsutils.batz.com/ namespace . Then, I imported this XML Schema to the WSDL under the ___http://stiperez:7070/axis/services/Sumador; namespace._ What's wrong with this?? Consider that the In-Line validator of WSDL schemas doesn´t work properly!! Did you then regen the service skeleton using wsdl2java? Anne On 3/7/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: The last 6 mails don't provide enough information. Please summarize the problem. Include appropriate WSDLs, WSDDs, etc. Thanks, Anne On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Please, read the last 6 mails (from 2007-03-02 on), they sumarize the key subject! P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read client as partner! Thank you! -- *De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED] *Enviado el:* miércoles, 07 de marzo de 2007 15:29 *Para:* axis-dev@ws.apache.org *Asunto:* Re: Possible Axis 1.4 Bug Please summarize the problem for us. On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Hello, first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6. We've found an issue wih the namespaces in the SOAP message returned by Axis. In order to follow this issue from the begining to the analysis of the problem, please, follow this thread at NetBeans Enterprise Pack Mailing list: http://www.netbeans.org/servlets/BrowseList?list=nbentpackby=threadfrom=772248 Thank you! [image: BATZ S.COOP] Ibai Perez Arbulu [EMAIL PROTECTED] *BATZ S. COOP *Torrea Auzoa,32 48140 IGORRE, (Bizkaia) - Spain Tfn: +34 946305000 Fax +34 946305020 * http://www.batz.com * *P* * Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da.* *No imprima este mensaje o sus documentos adjuntos, a no ser que sea verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa nuestra* La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y esta destinada a ser leída solo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que esta totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.
RE: Possible Axis 1.4 Bug
All the neccesary information is attatched to those mails (WSDL, WSDD, JARs,...). I changed the WSDL provided by Axis so as to work with Netbeans, but after that, I didn´t change the Axis related part at all! So, I take note, in conclusion, in your opinion, I should regenerate the Java Object (Sumador) from which Axis generates the Web service. Am I right? De: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Enviado el: miércoles, 07 de marzo de 2007 15:49 Para: axis-dev@ws.apache.org Asunto: Re: Possible Axis 1.4 Bug btw -- after you did this: As you can see in the project I send some days before, I took this WSDL and removed the Schema to paste it in the Operacion.xsd file under the http://serv.wsutils.batz.com http://serv.wsutils.batz.com http://serv.wsutils.batz.com/ namespace . Then, I imported this XML Schema to the WSDL under the ___http://stiperez:7070/axis/services/Sumador; namespace._ What's wrong with this?? Consider that the In-Line validator of WSDL schemas doesn´t work properly!! Did you then regen the service skeleton using wsdl2java? Anne On 3/7/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: The last 6 mails don't provide enough information. Please summarize the problem. Include appropriate WSDLs, WSDDs, etc. Thanks, Anne On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Please, read the last 6 mails (from 2007-03-02 on), they sumarize the key subject! P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read client as partner! Thank you! De: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Enviado el: miércoles, 07 de marzo de 2007 15:29 Para: axis-dev@ws.apache.org Asunto: Re: Possible Axis 1.4 Bug Please summarize the problem for us. On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Hello, first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6. We've found an issue wih the namespaces in the SOAP message returned by Axis. In order to follow this issue from the begining to the analysis of the problem, please, follow this thread at NetBeans Enterprise Pack Mailing list: http://www.netbeans.org/servlets/BrowseList?list=nbentpackby=threadfrom=772248 Thank you! BATZ S.COOP Ibai Perez Arbulu [EMAIL PROTECTED] BATZ S. COOP Torrea Auzoa,32 48140 IGORRE, (Bizkaia) - Spain Tfn: +34 946305000 Fax +34 946305020 http://www.batz.com http://www.batz.com/ P Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da. No imprima este mensaje o sus documentos adjuntos, a no ser que sea verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa nuestra La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y esta destinada a ser leída solo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que esta totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.
Re: Possible Axis 1.4 Bug
Yes. If you modify the generated WSDL, you must run WSDL2Java. That should fix your namespace errors. On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: All the neccesary information is attatched to those mails (WSDL, WSDD, JARs,...). I changed the WSDL provided by Axis so as to work with Netbeans, but after that, I didn´t change the Axis related part at all! So, I take note, in conclusion, in your opinion, I should regenerate the Java Object (Sumador) from which Axis generates the Web service. Am I right? -- *De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED] *Enviado el:* miércoles, 07 de marzo de 2007 15:49 *Para:* axis-dev@ws.apache.org *Asunto:* Re: Possible Axis 1.4 Bug btw -- after you did this: As you can see in the project I send some days before, I took this WSDL and removed the Schema to paste it in the Operacion.xsd file under the http://serv.wsutils.batz.com; http://serv.wsutils.batz.com/ namespace . Then, I imported this XML Schema to the WSDL under the ___http://stiperez:7070/axis/services/Sumador; namespace._ What's wrong with this?? Consider that the In-Line validator of WSDL schemas doesn´t work properly!! Did you then regen the service skeleton using wsdl2java? Anne On 3/7/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: The last 6 mails don't provide enough information. Please summarize the problem. Include appropriate WSDLs, WSDDs, etc. Thanks, Anne On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Please, read the last 6 mails (from 2007-03-02 on), they sumarize the key subject! P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read client as partner! Thank you! -- *De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED] *Enviado el:* miércoles, 07 de marzo de 2007 15:29 *Para:* axis-dev@ws.apache.org *Asunto:* Re: Possible Axis 1.4 Bug Please summarize the problem for us. On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote: Hello, first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6. We've found an issue wih the namespaces in the SOAP message returned by Axis. In order to follow this issue from the begining to the analysis of the problem, please, follow this thread at NetBeans Enterprise Pack Mailing list: http://www.netbeans.org/servlets/BrowseList?list=nbentpackby=threadfrom=772248 Thank you! [image: BATZ S.COOP] Ibai Perez Arbulu [EMAIL PROTECTED] *BATZ S. COOP *Torrea Auzoa,32 48140 IGORRE, (Bizkaia) - Spain Tfn: +34 946305000 Fax +34 946305020 *http://www.batz.com * *P* *Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da. * *No imprima este mensaje o sus documentos adjuntos, a no ser que sea verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa nuestra* La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y esta destinada a ser leída solo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que esta totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.
Re: axis2 possible header bug (v.1)
Hi DO; Which Axis2 version are you using , as I remember correct we fixed this issue before 1.0 release. If you have this problem in Axis2 1.0 please create a JIRA. DO wrote: Hello, I am trying to test a service with the header. I auto generated stubs and every time I invoke the service it returns the following message: org.apache.axis2.AxisFault: SOAPEnvelope must contain a body element which is either first or second child element of the SOAPEnvelope. The service works fine if the header is not set. The header is a simple object with 3 string fields. I do not have a header handler on the server side. Any help would be appreciated. Cheers, Denis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soap Fault handling bug?
oops, never mind...must be working too hard. I read the code wrong. No
bug.
Nadir K. Amra
Nadir Amra/Rochester/[EMAIL PROTECTED] wrote on 05/22/2006 08:18:34 PM:
I am looking at how fault handling is done, and I see that we generate
code like the following (using FaultMappingDoc test case) when the
CmplxFaultName does not match:
else
{
const char *detail =
pSoapFault-getSimpleFaultDetail();
bool deleteDetail=false;
if (NULL==detail || 0==strlen(detail))
{
detail=m_pCall-getFaultAsXMLString();
if (NULL==detail)
detail=;
else
deleteDetail=true;
}
OtherFaultException
ofe(pSoapFault-getFaultcode(),
pSoapFault-getFaultstring(),
pSoapFault-getFaultactor(),
detail, iExceptionCode);
if (deleteDetail NULL!=detail)
Axis::AxisDelete( (void *)
const_castchar*(detail), XSD_STRING);
m_pCall-unInitialize();
delete pSoapFault;
throw ofe;
}
My question is whether the call to AxisDelete is a bug, since from what
I
can tell getSimpleFaultDetail() does not return a new pointer.
Nadir K. Amra
-
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: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a schema with the same
namespace and xsd:import to bring in a schema with a different
namespace. So you must change this:
xsd:schema targetNamespace=
http://www.opengis.net/ows
xsd:import namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd
/
/xsd:schema
xsd:schema targetNamespace=
http://www.opengis.net/bla
xsd:import namespace=
http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd /
/xsd:schema
to this:
xsd:schema targetNamespace=
http://www.opengis.net/ows
xsd:include schemaLocation=
./wms_schemas.xsd
/
/xsd:schema
xsd:schema targetNamespace=
http://www.opengis.net/bla
xsd:include schemaLocation=
./wms-pok2.xsd /
/xsd:schema
Anne
On 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Hi
I have a problem with multi-nested includes, and I
thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to
server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - makeTypeElement() was told to create a type
{http://www.opengis.net/bla}zzbb, with no containing
elementAxisFaultfaultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type
{http://www.opengis.net/bla}zzbb, with no containing
elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitacSo my question is it is possible to import in wsdl two difrent schemas?Or
not and it is a bug. I enclose some files which demonstrate this problem. I
hope, that they are good writed because I beginner in soap. If it is not bug,
please write to me, how to solve this problem, because it is wery
important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Hi, I did It, but still the same Server exception.
I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is
my wsdl correct?
Ales
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 4:36
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You must use xsd:include to bring in a schema
with the same namespace and xsd:import to bring in a schema with a
different namespace. So you must change this:
xsd:schema
targetNamespace=" http://www.opengis.net/ows"
xsd:import namespace="http://www.opengis.net/ows "
schemaLocation="./wms_schemas.xsd" //xsd:schema
xsd:schema
targetNamespace=" http://www.opengis.net/bla"
xsd:import namespace=" http://www.opengis.net/bla"schemaLocation="./wms-pok2.xsd"
/
/xsd:schemato this:
xsd:schema
targetNamespace=" http://www.opengis.net/ows"
xsd:include schemaLocation="
./wms_schemas.xsd"
/
/xsd:schema
xsd:schema
targetNamespace=" http://www.opengis.net/bla"
xsd:include schemaLocation="
./wms-pok2.xsd" /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested includes,
and I thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to
server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no containing
elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExceptionfaultSubcode:
faultString: makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no containing
elementfaultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:pocitacSo my question is it is possible to import in wsdl two
difrent schemas?Or not and it is a bug. I enclose some files which
demonstrate this problem. I hope, that they are good writed because I
beginner in soap. If it is not bug, please write to me, how to solve this
problem, because it is wery important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Please post the updated wsdl and schema files.On 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Hi, I did It, but still the same Server exception.
I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is
my wsdl correct?
Ales
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 4:36
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You must use xsd:include to bring in a schema
with the same namespace and xsd:import to bring in a schema with a
different namespace. So you must change this:
xsd:schema
targetNamespace= http://www.opengis.net/ows
xsd:import namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd //xsd:schema
xsd:schema
targetNamespace= http://www.opengis.net/bla
xsd:import namespace= http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd
/
/xsd:schemato this:
xsd:schema
targetNamespace= http://www.opengis.net/ows
xsd:include schemaLocation=
./wms_schemas.xsd
/
/xsd:schema
xsd:schema
targetNamespace= http://www.opengis.net/bla
xsd:include schemaLocation=
./wms-pok2.xsd /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested includes,
and I thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to
server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no containing
elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no containing
elementfaultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible to import in wsdl two
difrent schemas?Or not and it is a bug. I enclose some files which
demonstrate this problem. I hope, that they are good writed because I
beginner in soap. If it is not bug, please write to me, how to solve this
problem, because it is wery important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Here is that files.
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 5:18
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a schema
with a different namespace. So you must change this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:import
namespace="http://www.opengis.net/ows
"
schemaLocation="./wms_schemas.xsd"
//xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:import
namespace="
http://www.opengis.net/bla
"schemaLocation="./wms-pok2.xsd"
/
/xsd:schemato
this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:include
schemaLocation="
./wms_schemas.xsd" /
/xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:include
schemaLocation="
./wms-pok2.xsd" /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files
to server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible to
import in wsdl two difrent schemas?Or not and it is a bug. I enclose
some files which demonstrate this problem. I hope, that they are good
writed because I beginner in soap. If it is not bug, please write to me,
how to solve this problem, because it is wery important.
Thank you
Ales
wms.wsdl
Description: Binary data
wms_schemas.xsd
Description: Binary data
wms-pok2.xsd
Description: Binary data
wms-pok.xsd
Description: Binary data
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
You have a bunch of namespace errors in these files.
Fix them and try again.
I strongly recommend that you use a WSDL editor such as Cape Clear SOA
Editor. (It's free.) See http://www.capescience.com/soa/index.shtml.
The validate function is very handy.
AnneOn 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Here is that files.
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 5:18
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a schema
with a different namespace. So you must change this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:import
namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd
//xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:import
namespace=
http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd
/
/xsd:schemato
this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:include
schemaLocation=
./wms_schemas.xsd /
/xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:include
schemaLocation=
./wms-pok2.xsd /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files
to server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type {http://www.opengis.net/bla}zzbb, with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible to
import in wsdl two difrent schemas?Or not and it is a bug. I enclose
some files which demonstrate this problem. I hope, that they are good
writed because I beginner in soap. If it is not bug, please write to me,
how to solve this problem, because it is wery important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Hi
I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix
them, please help.
Thank you
Ales
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 6:27
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You have a bunch of namespace errors in these files. Fix
them and try again.I strongly recommend that you use a WSDL editor
such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml.
The validate function is very handy.Anne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Here is that files.
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 5:18 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a
schema with a different namespace. So you must change this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:import
namespace="http://www.opengis.net/ows
"
schemaLocation="./wms_schemas.xsd"
//xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:import
namespace="
http://www.opengis.net/bla
"schemaLocation="./wms-pok2.xsd"
/
/xsd:schemato
this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:include
schemaLocation="
./wms_schemas.xsd" /
/xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:include
schemaLocation="
./wms-pok2.xsd" /
/xsd:schemaAnne
On 12/14/05, Ales St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two
difrent namespaces from two difrent xsd files. And then I generate
classes using WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a
--server-side --skeletonDeploy true --NStoPkg urn:Wms=wms
wms.wsdl ) Then I copy files to server and when I wanted to see
server generated wsdl Axis error is generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible
to import in wsdl two difrent schemas?Or not and it is a bug. I
enclose some files which demonstrate this problem. I hope, that they
are good writed because I beginner in soap. If it is not bug, please
write to me, how to solve this problem, because it is wery
important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Sorry, I'm not going to do your homework for you.On 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Hi
I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix
them, please help.
Thank you
Ales
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 6:27
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You have a bunch of namespace errors in these files. Fix
them and try again.I strongly recommend that you use a WSDL editor
such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml
.
The validate function is very handy.Anne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Here is that files.
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 5:18 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a
schema with a different namespace. So you must change this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:import
namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd
//xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:import
namespace=
http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd
/
/xsd:schemato
this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:include
schemaLocation=
./wms_schemas.xsd /
/xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:include
schemaLocation=
./wms-pok2.xsd /
/xsd:schemaAnne
On 12/14/05, Ales St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two
difrent namespaces from two difrent xsd files. And then I generate
classes using WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a
--server-side --skeletonDeploy true --NStoPkg urn:Wms=wms
wms.wsdl ) Then I copy files to server and when I wanted to see
server generated wsdl Axis error is generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type {http://www.opengis.net/bla}zzbb, with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible
to import in wsdl two difrent schemas?Or not and it is a bug. I
enclose some files which demonstrate this problem. I hope, that they
are good writed because I beginner in soap. If it is not bug, please
write to me, how to solve this problem, because it is wery
important.
Thank you
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Ok,I try to solve it by myself, but problem is , that I trying to solve it for one week and still can't find resolution. So I try to askyou, where can I find somegood book or web pages about wsdl i know only this http://www.w3.org/TR/wsdland it is hard for me to find resolution of my problem there. Or do you knew some source where where is my problem solved? Please help Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:54 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Sorry, I'm not going to do your homework for you. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix them, please help. Thank you Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:27 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You have a bunch of namespace errors in these files. Fix them and try again.I strongly recommend that you use a WSDL editor such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml . The validate function is very handy.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Please post the updated wsdl and schema files. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi, I did It, but still the same Server exception. I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is my wsdl correct? Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 4:36 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You must use xsd:include to bring in a schema with the same namespace and xsd:import to bring in a schema with a different namespace. So you must change this: xsd:schema targetNamespace=" http://www.opengis.net/ows" xsd:import namespace="http://www.opengis.net/ows " schemaLocation="./wms_schemas.xsd" //xsd:schema xsd:schema targetNamespace=" http://www.opengis.net/bla" xsd:import namespace=" http://www.opengis.net/bla "schemaLocation="./wms-pok2.xsd" / /xsd:schemato this: xsd:schema targetNamespace=" http://www.opengis.net/ows" xsd:include schemaLocation=" ./wms_schemas.xsd" / /xsd:schema xsd:schema targetNamespace=" http://www.opengis.net/bla" xsd:include schemaLocation=" ./wms-pok2.xsd" / /xsd:schemaAnne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I have a problem with multi-nested includes, and I thing that it is a bug. I use java Axis 1.3. I try in my wsdl file to import two difrent
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Your problems are with schema and namespaces, not with WSDL. In addition to the wsdl spec, you should study these documents: - WS-I Basic Profile: http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html - XML Namespaces: http://www.w3.org/TR/REC-xml-names/ - XML Schema Tutorial: http://www.w3schools.com/schema/default.asp - XML Schema Primer: http://www.w3.org/TR/xmlschema-0/ I think you should work on the assumption that it isn't a bug, but a problem with the way you're importing/including schemas and referencing elements. XML Schema is really complicated, but you're fortunate in that you don't really need to define your elements and types. You just need to import and include the files properly, and reference your elements and types properly. Going back to your first question -- that was caused by the fact that the StyledLayerDescription element references elements (Name, Description, etc) that are defined in the common.xsd schema rather than in the sld.xsd schema, and the sld.xsd schema doesn't x:include common.xsd schema. (They are both in the sld namespace, therefore you must x:include the common.xsd schema rather than x:import it.) As I said to you before, I recommend that you consolidate all the schemas that have the same targetNamespace. That should resolve the problems you're experiencing. AnneOn 12/14/05, Ales St [EMAIL PROTECTED] wrote: Ok,I try to solve it by myself, but problem is , that I trying to solve it for one week and still can't find resolution. So I try to askyou, where can I find somegood book or web pages about wsdl i know only this http://www.w3.org/TR/wsdland it is hard for me to find resolution of my problem there. Or do you knew some source where where is my problem solved? Please help Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:54 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Sorry, I'm not going to do your homework for you. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix them, please help. Thank you Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:27 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You have a bunch of namespace errors in these files. Fix them and try again.I strongly recommend that you use a WSDL editor such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml . The validate function is very handy.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Please post the updated wsdl and schema files. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi, I did It, but still the same Server exception. I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is my wsdl correct? Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 4:36 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You must use xsd:include to bring in a schema with the same namespace and xsd:import to bring in a schema with a different namespace. So you must change this: xsd:schema targetNamespace= http://www.opengis.net/ows xsd:import namespace=http://www.opengis.net/ows schemaLocation=./wms_schemas.xsd //xsd:schema xsd:schema targetNamespace= http://www.opengis.net/bla
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Hi Thank you for your time. I willstudy that documents and I hope, that it help me. Now i know that it is not a bug, because I use Cape Clear SOA Editor and use: Insert -Embedded schema from file, it insert xsd schemas to my wsdl file and it works. But it insert all schema definition, and it is not, what I want. So i try to Schema-Insert schema import ,and it write error: "The prefix "xsd" for element "xsd:import" is not bound. at Line: 1 Character: 175" ,bud when I get to validate xsd. file , everything is Ok. I will work on it and I hope, that I will find a solution. Thank you again for your time, because you help me a lot. Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 9:35 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Your problems are with schema and namespaces, not with WSDL. In addition to the wsdl spec, you should study these documents:- WS-I Basic Profile: http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html- XML Namespaces: http://www.w3.org/TR/REC-xml-names/- XML Schema Tutorial: http://www.w3schools.com/schema/default.asp- XML Schema Primer: http://www.w3.org/TR/xmlschema-0/I think you should work on the assumption that it isn't a bug, but a problem with the way you're importing/including schemas and referencing elements. XML Schema is really complicated, but you're fortunate in that you don't really need to define your elements and types. You just need to import and include the files properly, and reference your elements and types properly.Going back to your first question -- that was caused by the fact that the StyledLayerDescription element references elements (Name, Description, etc) that are defined in the common.xsd schema rather than in the sld.xsd schema, and the sld.xsd schema doesn't x:include common.xsd schema. (They are both in the sld namespace, therefore you must x:include the common.xsd schema rather than x:import it.)As I said to you before, I recommend that you consolidate all the schemas that have the same targetNamespace. That should resolve the problems you're experiencing.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Ok,I try to solve it by myself, but problem is , that I trying to solve it for one week and still can't find resolution. So I try to askyou, where can I find somegood book or web pages about wsdl i know only this http://www.w3.org/TR/wsdland it is hard for me to find resolution of my problem there. Or do you knew some source where where is my problem solved? Please help Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:54 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Sorry, I'm not going to do your homework for you. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix them, please help. Thank you Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:27 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You have a bunch of namespace errors in these files. Fix them and try again.I strongly recommend that you use a WSDL editor such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml . The validate function is very handy.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Please post the updated wsdl and schema files. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi, I did It, but still the same Server exceptio
RE: Is this a bug??
Title: Is this a bug?? I checked my object but it is filled out. Another suggestions Thanks, Parikh, Pratik | Software Engineer | Cerner Corporation | (1)-816-201-1298 | [EMAIL PROTECTED] | www.cerner.com From: Dovholuk, Clint [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 08, 2005 5:11 PMTo: axis-user@ws.apache.orgCc: axis-dev@ws.apache.orgSubject: RE: Is this a bug?? sounds like on your client you are instantiating a java object but not populating the "required" attribute named "id", sending the object to axis, and axis is rejecting the message because the id attribute of the class can't be null. use TCPMon (or whatever) and check the message you're sending and verify that the id is indeed in the message. From: Parikh,Pratik [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 08, 2005 6:08 PMTo: axis-user@ws.apache.orgCc: axis-dev@ws.apache.orgSubject: Is this a bug?? Hi Everyone, I am getting a following exception when I try to send a message thought my client to my web service. I looked around for solution and it seems like it is a bug, but am not sure can some one help me??? I am also using a MQ Logger where it does the same. Please help me??? java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: Non nillable element 'id' is null. java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: java.io.IOException: Non nillable element 'id' is null. at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275) at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1502) at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:978) at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:799) at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208) at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433) at org.apache.axis.message.MessageElement.output(MessageElement.java:1208) at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139) at org.apache.axis.message.MessageElement.output(MessageElement.java:1208) at org.apache.axis.message.MessageElement.getAsString(MessageElement.java:) at com.cerner.endpoint.fsi.axis.handlers.auditing.MQLoggerHandler.invoke(MQLoggerHandler.java:90) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:121) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) Reference Links http://www.opensubscriber.com/message/kandula-dev@ws.apache.org/2450136.html Thanks, Parikh, Pratik CONFIDENTIALITY NOTICEThis message and any included attachmentsare from Cerner Corporation and are intendedonly for the addressee. The informationcontained in this message is confidential andmay constitute inside or non-public informationunder international, federal, or statesecurities laws. Unauthorized forwarding,printing, copying, distribution, or use of suchinformation is strictly prohibited and may beunlawful. If you are not the addressee, pleasepromptly delete this message and notify thesender of the delivery error by e-mail or youmay call Cerner's corporate offices in KansasCity, Missouri, U.S.A at (+1) (816)221-1024. --
Re: New .NET Interop Bug? (regression)
I've opened a new bug on this, and provided a way to test. Could someone please verify the validity of this bug? http://issues.apache.org/jira/browse/AXIS-2050 Dan Tom Jordahl wrote: Dan, This is a document/literal service? Are you using wrapped mode? I don't like the look of the repeated element. What is the WSDL description of getSupportedCodeSystemsResponse? Since there is no type info in the response, I am not sure how .NET (or Axis for that matter, but it probably has some meta-data that says either getSupportedCodeSystemsResponse or getSupportedCodeSystemsReturn is an array) will figure out the repeating element. What XML did RC2 send/receive? -- Tom Jordahl Macromedia Server Development
RE: New .NET Interop Bug? (regression)
Dan, This is a document/literal service? Are you using wrapped mode? I don't like the look of the repeated element. What is the WSDL description of getSupportedCodeSystemsResponse? Since there is no type info in the response, I am not sure how .NET (or Axis for that matter, but it probably has some meta-data that says either getSupportedCodeSystemsResponse or getSupportedCodeSystemsReturn is an array) will figure out the repeating element. What XML did RC2 send/receive? -- Tom Jordahl Macromedia Server Development -Original Message- From: Dan Armbrust [mailto:[EMAIL PROTECTED] Sent: Friday, June 10, 2005 3:05 PM To: axis-dev@ws.apache.org Subject: New .NET Interop Bug? (regression) I'm calling a method which is supposed to return an Array of my object - CodeSystemIdAndVersions Using todays daily build, things work fine as long as I am using axis as the server and the client. But, with a .NET client, when it gets the following response, it only gives me a CodeSystemIdAndVersions array of size 1, which only contains the first item from the response. This didn't happen with 1.2 RC2. Is there anything wrong with this Soap response? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body getSupportedCodeSystemsResponse xmlns=urn://hl7.org/CTSVAPI getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.1050/codeSystem_id codeSystem_nameAcknowledgementCondition/codeSystem_name copyright / codeSystem_versions item29/item /codeSystem_versions /getSupportedCodeSystemsReturn getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.1082/codeSystem_id codeSystem_nameAcknowledgementDetailType/codeSystem_name copyright / codeSystem_versions item142/item /codeSystem_versions /getSupportedCodeSystemsReturn getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.18/codeSystem_id codeSystem_nameAcknowledgementType/codeSystem_name copyright / codeSystem_versions item134/item /codeSystem_versions /getSupportedCodeSystemsReturn getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.6/codeSystem_id codeSystem_nameActClass/codeSystem_name copyright / codeSystem_versions item145/item /codeSystem_versions /getSupportedCodeSystemsReturn /getSupportedCodeSystemsResponse /soapenv:Body /soapenv:Envelope
Re: New .NET Interop Bug? (regression)
Hmm, I'm still puzzled myself.. I'm trying to compare the RC2 WSDL and over the wire messages with what I'm seeing now... and I can't find a difference immediately. Yet it worked then.. and now .NET only gets arrays of size 1 for any of my custom object arrays. I'll do some more investigating, and submit more info. Tom Jordahl wrote: Dan, This is a document/literal service? Are you using wrapped mode? I don't like the look of the repeated element. What is the WSDL description of getSupportedCodeSystemsResponse? Since there is no type info in the response, I am not sure how .NET (or Axis for that matter, but it probably has some meta-data that says either getSupportedCodeSystemsResponse or getSupportedCodeSystemsReturn is an array) will figure out the repeating element. What XML did RC2 send/receive? -- Tom Jordahl Macromedia Server Development -Original Message- From: Dan Armbrust [mailto:[EMAIL PROTECTED]] Sent: Friday, June 10, 2005 3:05 PM To: axis-dev@ws.apache.org Subject: New .NET Interop Bug? (regression) I'm calling a method which is supposed to return an Array of my object - CodeSystemIdAndVersions Using todays daily build, things work fine as long as I am using axis as the server and the client. But, with a .NET client, when it gets the following response, it only gives me a CodeSystemIdAndVersions array of size 1, which only contains the first item from the response. This didn't happen with 1.2 RC2. Is there anything wrong with this Soap response? soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" soapenv:Body getSupportedCodeSystemsResponse xmlns="urn://hl7.org/CTSVAPI" getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.1050/codeSystem_id codeSystem_nameAcknowledgementCondition/codeSystem_name copyright / codeSystem_versions item29/item /codeSystem_versions /getSupportedCodeSystemsReturn getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.1082/codeSystem_id codeSystem_nameAcknowledgementDetailType/codeSystem_name copyright / codeSystem_versions item142/item /codeSystem_versions /getSupportedCodeSystemsReturn getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.18/codeSystem_id codeSystem_nameAcknowledgementType/codeSystem_name copyright / codeSystem_versions item134/item /codeSystem_versions /getSupportedCodeSystemsReturn getSupportedCodeSystemsReturn codeSystem_id2.16.840.1.113883.5.6/codeSystem_id codeSystem_nameActClass/codeSystem_name copyright / codeSystem_versions item145/item /codeSystem_versions /getSupportedCodeSystemsReturn /getSupportedCodeSystemsResponse /soapenv:Body /soapenv:Envelope
Re: New .NET Interop Bug? (regression)
Ok, I'm completely baffeled. The only difference in the SOAP messages generated by 1.2 RC2 compared to todays daily build of 1.2.1 is that 1.2.1 has some extra spaces after the closes on xml tags. I can't believe that would affect things. I attached the messages. Maybe it has to do with the way I am capturing the Soap messages - I'm using a logger on the Axis client - configured like so: deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; handler name=log type=java:edu.mayo.informatics.ctsDemo.XMLInterceptor/ globalConfiguration requestFlow handler type=log/ /requestFlow responseFlow handler type=log/ /responseFlow /globalConfiguration transport name=http pivot=java:org.apache.axis.transport.http.HTTPSender/ transport name=local pivot=java:org.apache.axis.transport.local.LocalSender/ transport name=java pivot=java:org.apache.axis.transport.java.JavaSender/ /deployment Maybe things are being rewritten in some way by the client, before the logger picks up the message? I'll try to get something else set up to actually intercept the .NET messages. I have attached the WSDL as ouput by axis when I go to this address... http:///axis/services/VocabRuntimeService?wsdl for both the RC2 build and the 1.2.1 daily build. The only difference I can see in the WSDL is the way that string arrays are handled. Yet, when I use .NET and generate stubs against RC2, everything works. When I build stubs against 1.2.1 - all of my array return type of complex objects only return 1 item. Here is how I initially generated the WSDL (from an ant verbose mode run, ignore the ant [java] stuff...) [echo] Generating build/wsdl/VocabBrowser.wsdl from org.hl7.CTSVAPI.BrowserOperations [java] Executing 'C:\Program Files\Java\j2sdk_1.4.2_05\jre\bin\java.exe' with arguments: [java] '-classpath' [java] 'C:\Eclipse Projects\general-workspace\CTS\hl7spec\build\idljava\classes;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\xerces.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\xml-apis.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\build\lib\ctsImpl.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\CTSUtility.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\build\wsdljava\classes;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\activation.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\axis-ant.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\axis.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\commons-discovery-0.2.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\commons-logging-1.0.4.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\jaxrpc.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\log4j-1.2.8.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\mail.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\saaj.jar;C:\Eclipse Projects\general-workspace\CTS\hl7spec\extLib\axis\wsdl4j-1.5.1.jar' [java] 'org.apache.axis.wsdl.Java2WSDL' [java] '-o' [java] 'build/wsdl/VocabRuntime.wsdl' [java] '-n' [java] 'urn://hl7.org/CTSVAPI' [java] '-i' [java] 'org.hl7.CTSVAPI.refImpl.RuntimeOperationsImpl' [java] '-lhttp://localhost:8080/axis/services/VocabRuntimeService' [java] '-porg.hl7.cts.types=urn://cts.hl7.org/types' [java] '-porg.hl7.CTSMAPI=urn://hl7.org/CTSMAPI' [java] '-porg.hl7.CTSVAPI=urn://hl7.org/CTSVAPI' [java] '-y' [java] 'WRAPPED' [java] 'org.hl7.CTSVAPI.RuntimeOperations' [java] [java] The ' characters around the executable and arguments are [java] not part of the command. ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=urn://hl7.org/CTSVAPI xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=urn://hl7.org/CTSVAPI xmlns:intf=urn://hl7.org/CTSVAPI xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; !--WSDL created by Apache Axis version: 1.2.1 Built on Jun 10, 2005 (10:05:29 GMT+00:00)-- wsdl:types schema elementFormDefault=qualified targetNamespace=urn://hl7.org/CTSVAPI xmlns=http://www.w3.org/2001/XMLSchema; element name=lookupCodeSystemInfo complexType sequence element name=codeSystem_id type=xsd:string/ element name=codeSystem_name type=xsd:string/ /sequence /complexType /element element name=lookupCodeSystemInfoResponse complexType sequence element name=lookupCodeSystemInfoReturn type=impl:CodeSystemInfo/ /sequence /complexType /element complexType name=CodeSystemIdAndVersions sequence element name=codeSystem_id nillable=true type=xsd:string/ element name=codeSystem_name
Re: New .NET Interop Bug? (regression)
Here is a capture by tcpmon of the .NET request and response of the 1.2.1 server: POST /axis/services/VocabRuntimeService HTTP/1.1 VsDebuggerCausalityData: AwAAABufSZhC3qlJnaszgYT67ZEAAACkBgAArA8AgPMSAAB2AGUAcgBzAGkAbwBuAD0ANwAuADAAOwBhAHUAdABvAGEAdAB0AGEAYwBoAGMAbABzAGkAZAA9AHsANwAwAEYANgA1ADQAMQAxAC0ARgBFADgAQwAtADQAMgA0ADgALQBCAEMARgBGAC0ANwAwADEAQwA4AEIAMgBGADQANQAyADkAfQA7AHMAZQBzAHMAaQBvAG4APQB7AEIAOABEADQARgBEADgANgAtADcANwA4ADAALQA0AEMAMAA0AC0AOQBDAEEAMgAtADgARAA4AEIANQA4ADYAQgBDADMAMwA4AH0A User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2032) Content-Type: text/xml; charset=utf-8 SOAPAction: Content-Length: 371 Expect: 100-continue Host: 127.0.0.1:7080 ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:BodygetSupportedCodeSystems xmlns=urn://hl7.org/CTSVAPItimeout0/timeoutsizeLimit0/sizeLimit/getSupportedCodeSystems/soap:Body/soap:Envelope I attached the response, because it is kind of big. I'll open a bug with all of this stuff so it doesn't get lost a bit later tonight. Dan HTTP/1.1 100 Continue HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=utf-8 Transfer-Encoding: chunked Date: Fri, 10 Jun 2005 20:22:40 GMT 2000 ?xml version=1.0 encoding=utf-8?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;soapenv:BodygetSupportedCodeSystemsResponse
RE: DO NOT REPLY [Bug 8191] - WSDLException when using Emitter t wice and java.lang namespace
Whoa. This looks like a status message from 2002! Something burped in the bugzilla bug base. :-) Tom Jordahl Macromedia Server Development -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, January 06, 2005 12:05 AM To: axis-dev@ws.apache.org Subject: DO NOT REPLY [Bug 8191] - WSDLException when using Emitter twice and java.lang namespace DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG* RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=8191. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND* INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=8191 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-19 14:03 --- Try it now. The private fields are ignored. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: DO NOT REPLY [Bug 21394] - Possible datetime deserialization bug
On 7/14/03 05:32 PM Shellman, Joel [EMAIL PROTECTED] wrote: Can't you create a timezone from the offset? I see. You would have to arbitrarily choose the ID, right? You could keep the offset but because there are multiple timezones with the same offset, is that the problem? To some extend I am guessing here only. Given the fact that you have to support Daylight Savings Time too you can't just use the offset to create the timezone. Jens
RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug
You can certainly send an XML element for which you define your own serializer for that would give you any behavior you neeed. -- Tom Jordahl Macromedia Server Development -Original Message- From: Shellman, Joel [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 12:06 PM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug Okay. I think for me then... Does Axis support a date instead of a datetime? Thanks, -joel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 9:03 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 21394] - Possible datetime deserialization bug DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21394. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21394 Possible datetime deserialization bug --- Additional Comments From [EMAIL PROTECTED] 2003-07-14 16:02 --- I am a bit unclear where the bug lies here, but I will say this - Axis send date/time stamps in UTC specifically to avoid the timezone issues that are being raised. It is understood that sending it this way 'looses' the information about what timezone the time was originally in, but the information is still acurrate. Timezones are strictly for 'display' purposes only, relating a UTC time to what part of the world you live in. I would very much be against changing the serializer to emit datetime in any timezone but +0:00. The deserializer however should understand timezones and always do the right thing. Can you summarize specifically what behavior you want to change in Axis?
RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug
We support xsd:date. I don't know if that serializer does what you need either. Give it a shot. -- Tom Jordahl Macromedia Server Development -Original Message- From: Shellman, Joel [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 12:19 PM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug Right. I thought there already was a date type in XML schema and so was asking if Axis already has support for that. -joel -Original Message- From: Tom Jordahl [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug You can certainly send an XML element for which you define your own serializer for that would give you any behavior you neeed. -- Tom Jordahl Macromedia Server Development -Original Message- From: Shellman, Joel [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 12:06 PM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug Okay. I think for me then... Does Axis support a date instead of a datetime? Thanks, -joel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 9:03 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 21394] - Possible datetime deserialization bug DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21394. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21394 Possible datetime deserialization bug --- Additional Comments From [EMAIL PROTECTED] 2003-07-14 16:02 --- I am a bit unclear where the bug lies here, but I will say this - Axis send date/time stamps in UTC specifically to avoid the timezone issues that are being raised. It is understood that sending it this way 'looses' the information about what timezone the time was originally in, but the information is still acurrate. Timezones are strictly for 'display' purposes only, relating a UTC time to what part of the world you live in. I would very much be against changing the serializer to emit datetime in any timezone but +0:00. The deserializer however should understand timezones and always do the right thing. Can you summarize specifically what behavior you want to change in Axis?
Re: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug
Tom Jordahl wrote: You can certainly send an XML element for which you define your own serializer for that would give you any behavior you neeed. BTW, I send time_t in UTC as a long, as it is the only format that is guaranteed to be understood by things other than axis; .net is a bit patch w.r.t timezones in different ways frm axis.
ATTN: Glen (Re: DO NOT REPLY [Bug 20654] - Java2WSDL gen. duplicate in0 top-level elements of diff types)
Glen, Need help with this one... -- dims --- [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20654. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20654 Java2WSDL gen. duplicate in0 top-level elements of diff types --- Additional Comments From [EMAIL PROTECTED] 2003-07-11 14:41 --- Glen, Can you please help with this one? I've uploaded a test case. compile the classes, deploy using the specified wsdd and look at the auto-generated WSDL for the service. Thanks, dims = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
RE: ATTN: Glen (Re: DO NOT REPLY [Bug 20654] - Java2WSDL gen. duplicate in0 top-level elements of diff types)
You got it, dims. I'm planning to devote some Axis-time this weekend. --Glen -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 10:40 AM To: [EMAIL PROTECTED] Subject: ATTN: Glen (Re: DO NOT REPLY [Bug 20654] - Java2WSDL gen. duplicate in0 top-level elements of diff types) Glen, Need help with this one... -- dims --- [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20654. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20654 Java2WSDL gen. duplicate in0 top-level elements of diff types --- Additional Comments From [EMAIL PROTECTED] 2003-07-11 14:41 --- Glen, Can you please help with this one? I've uploaded a test case. compile the classes, deploy using the specified wsdd and look at the auto-generated WSDL for the service. Thanks, dims = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
RE: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts
OK folks - should I hold off re-kitting 1.1 until this is resolved? --Glen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:04 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133 Problems serializing german umlauts --- Additional Comments From [EMAIL PROTECTED] 2003-06-13 13:04 --- Yes dims, but in my case the system is right now more sophisticated :) So I've tried only the last path between sending the message from my client and getting it on the other side by the SessionBean. Right now I'm creating a testcase for an echo based on the EJB Provider. Regards, Sascha
RE: DO NOT REPLY [Bug 15133] - Problems serializing german umla uts
No (IMHO). Please go ahead. Thanks, dims --- Glen Daniels [EMAIL PROTECTED] wrote: OK folks - should I hold off re-kitting 1.1 until this is resolved? --Glen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:04 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133 Problems serializing german umlauts --- Additional Comments From [EMAIL PROTECTED] 2003-06-13 13:04 --- Yes dims, but in my case the system is right now more sophisticated :) So I've tried only the last path between sending the message from my client and getting it on the other side by the SessionBean. Right now I'm creating a testcase for an echo based on the EJB Provider. Regards, Sascha = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
RE: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts
We have spent a whole week trying to iron out the last few bugs. I think this was the only one of any true significance. (IMO) Whats a few more hours? :) Rick -Original Message- From: Glen Daniels [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:15 AM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts OK folks - should I hold off re-kitting 1.1 until this is resolved? --Glen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:04 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133 Problems serializing german umlauts --- Additional Comments From [EMAIL PROTECTED] 2003-06-13 13:04 --- Yes dims, but in my case the system is right now more sophisticated :) So I've tried only the last path between sending the message from my client and getting it on the other side by the SessionBean. Right now I'm creating a testcase for an echo based on the EJB Provider. Regards, Sascha
RE: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts
Rick, Problem is either in EJB Provider or in users environment. I don't think i'd be able to fix the problem even if we are able to recreate the problem TODAY. We can always do a 1.1a if this turns out to be a whopper (http://dictionary.reference.com/search?q=whopper). -- dims --- Kellogg, Richard [EMAIL PROTECTED] wrote: We have spent a whole week trying to iron out the last few bugs. I think this was the only one of any true significance. (IMO) Whats a few more hours? :) Rick -Original Message- From: Glen Daniels [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:15 AM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts OK folks - should I hold off re-kitting 1.1 until this is resolved? --Glen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:04 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 15133] - Problems serializing german umlauts DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15133 Problems serializing german umlauts --- Additional Comments From [EMAIL PROTECTED] 2003-06-13 13:04 --- Yes dims, but in my case the system is right now more sophisticated :) So I've tried only the last path between sending the message from my client and getting it on the other side by the SessionBean. Right now I'm creating a testcase for an echo based on the EJB Provider. Regards, Sascha = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
RE: DO NOT REPLY [Bug 20679] - SOAPMonitorApplet source/class file missing
Please refer to http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/SoapMonitor for more info on the SOAPMonitorApplet. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2003 10:37 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 20679] - SOAPMonitorApplet source/class file missing DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20679. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20679 SOAPMonitorApplet source/class file missing --- Additional Comments From [EMAIL PROTECTED] 2003-06-11 14:37 --- Have spent some more time on it, and the source code is stored directly under the webapps/axis directory of the distribution. However, it is not easy to find out how to use it. I would suggest adding something like this (only improved) to the user's guide: To use the SOAPMonitor, you need to perform the following steps: 1. Compile and make available the applet that is the client GUI for the monitor. 2. Configure the Axis server to notify the monitor of requests for the relevant services. 3. Configure the Axis server to notify the monitor of responses for the relevant services. Step 1 is easy, assuming you have a working Axis installation: just 'cd' to the webapps/axis directory of the servlet container ($CATALINA_HOME/webapps/axis for Tomcat), and execute the command javac -classpath AXISINSTALLDIR/lib/axis.jar SOAPMonitorApplet.java. This compiles the applet and its nested classes, and makes them available to the servlet container. Step 2 is a little more complicated. For each service that should be monitored, you need to set up a request flow that calls the SOAPMonitor. This means that you need to add the following to the WSDD file that you use to deploy services: deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; handler name=monitor type=java:org.apache.axis.handlers.SOAPMonitorHandler /handler .. mappings and other things service name=MyService provider=java:RPC requestFlow handler type=monitor/ /requestFlow parameter name=className value=com.company.package.MyService/ parameter name=allowedMethods value=*/ /service /deployment That is, first define the monitoring handler, and then ensure that for each service you want to monitor, the monitoring handler will be called before the service is invoked. Step 3 - I haven't succeeded with this one yet, someone there who can help?
RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized))
Hi dims: I'm in (surprise surprise) another meeting, and won't be able to look deeper into this until afternoon or (more likely) tonight. It looked to me like the use case was DII doing mappings from a dynamically read WSDL file to already-existing Java classes? That seems a little weird - i.e. why are you doing DII in this case at all instead of just using stubs? If you've got a working patch for this case, though, feel free to check it in. --Glen -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 10:09 AM To: Glen Daniels Cc: [EMAIL PROTECTED] Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Glen, Uploaded a patch to bugzilla. Can you please try it out? the zip file contains the use case on how this should work as well. Thanks, dims --- Glen Daniels [EMAIL PROTECTED] wrote: I expect to get to it this afternoon - I've been swamped with meetings today (and am about to enter another one! :/)... --G -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 2:00 PM To: [EMAIL PROTECTED] Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Any luck? I spent 5 hours on it yesterday. -- dims --- Glen Daniels [EMAIL PROTECTED] wrote: Yup, I'm on it. --Glen -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 7:47 AM To: [EMAIL PROTECTED] Subject: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Glen, Since tom is away, can you please look? Thanks, dims --- Davanum Srinivas [EMAIL PROTECTED] wrote: Tom, Can you please take a quick look? Does not seem like the bug is fixed yet. Attached a test case in bugzilla. Thanks, -- dims --- [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682 non-AxisFault exceptions don't have details serialized --- Additional Comments From [EMAIL PROTECTED] 2003-05-27 04:13 --- Created an attachment (id=6506) ex04.zip = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com
RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized))
Am on itI am refining the use case as well to NOT use the WSDL stuff. -- dims --- Glen Daniels [EMAIL PROTECTED] wrote: Hi dims: I'm in (surprise surprise) another meeting, and won't be able to look deeper into this until afternoon or (more likely) tonight. It looked to me like the use case was DII doing mappings from a dynamically read WSDL file to already-existing Java classes? That seems a little weird - i.e. why are you doing DII in this case at all instead of just using stubs? If you've got a working patch for this case, though, feel free to check it in. --Glen -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 10:09 AM To: Glen Daniels Cc: [EMAIL PROTECTED] Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Glen, Uploaded a patch to bugzilla. Can you please try it out? the zip file contains the use case on how this should work as well. Thanks, dims --- Glen Daniels [EMAIL PROTECTED] wrote: I expect to get to it this afternoon - I've been swamped with meetings today (and am about to enter another one! :/)... --G -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 2:00 PM To: [EMAIL PROTECTED] Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Any luck? I spent 5 hours on it yesterday. -- dims --- Glen Daniels [EMAIL PROTECTED] wrote: Yup, I'm on it. --Glen -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 7:47 AM To: [EMAIL PROTECTED] Subject: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Glen, Since tom is away, can you please look? Thanks, dims --- Davanum Srinivas [EMAIL PROTECTED] wrote: Tom, Can you please take a quick look? Does not seem like the bug is fixed yet. Attached a test case in bugzilla. Thanks, -- dims --- [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682 non-AxisFault exceptions don't have details serialized --- Additional Comments From [EMAIL PROTECTED] 2003-05-27 04:13 --- Created an attachment (id=6506) ex04.zip = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized))
Done. Checked in a fix that allows a custom exception (JavaBean that extends RemoteException). See samples/faults directory for sample. test/functional/TestFaultsSample for the test case. -- dims --- Davanum Srinivas [EMAIL PROTECTED] wrote: Am on itI am refining the use case as well to NOT use the WSDL stuff. -- dims --- Glen Daniels [EMAIL PROTECTED] wrote: Hi dims: I'm in (surprise surprise) another meeting, and won't be able to look deeper into this until afternoon or (more likely) tonight. It looked to me like the use case was DII doing mappings from a dynamically read WSDL file to already-existing Java classes? That seems a little weird - i.e. why are you doing DII in this case at all instead of just using stubs? If you've got a working patch for this case, though, feel free to check it in. --Glen -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 10:09 AM To: Glen Daniels Cc: [EMAIL PROTECTED] Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Glen, Uploaded a patch to bugzilla. Can you please try it out? the zip file contains the use case on how this should work as well. Thanks, dims --- Glen Daniels [EMAIL PROTECTED] wrote: I expect to get to it this afternoon - I've been swamped with meetings today (and am about to enter another one! :/)... --G -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 2:00 PM To: [EMAIL PROTECTED] Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Any luck? I spent 5 hours on it yesterday. -- dims --- Glen Daniels [EMAIL PROTECTED] wrote: Yup, I'm on it. --Glen -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 7:47 AM To: [EMAIL PROTECTED] Subject: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY [Bug 19682] - non-AxisFault exceptions don't have details serialized)) Glen, Since tom is away, can you please look? Thanks, dims --- Davanum Srinivas [EMAIL PROTECTED] wrote: Tom, Can you please take a quick look? Does not seem like the bug is fixed yet. Attached a test case in bugzilla. Thanks, -- dims --- [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682 non-AxisFault exceptions don't have details serialized --- Additional Comments From [EMAIL PROTECTED] 2003-05-27 04:13 --- Created an attachment (id=6506) ex04.zip = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
RE: DO NOT REPLY [Bug 18530] - org.xml.sax.SAXException: No deserializer defined for array type AcnInfoRow
NOW you have let the cat out of the bag my server is written in gSoap and seems
to be
working
The keyword here is seems.
Here's what you need to do. Write a server using Axis (see my zip file in bugzilla)
and deploy it
on tomcat. (Make sure you generate both the server and client using the same WSDL with
WSDL2Java).
Run tcpmon to intercept the soap messages and compare it to what you get using gSOAP.
THEN tweak
your gSOAP to conform.
Thanks,
dims
--- Allen, Michael E. [EMAIL PROTECTED] wrote:
Dims,
I am sorry to be having so much trouble... I feel like I am missing some key
idea. I tried what you said, but still nothing is working. When I run
AdminClient on the generated deploy.wsdd, I get:
$ java org.apache.axis.client.AdminClient deploy.wsdd
- Processing file deploy.wsdd
- Exception:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: Method apos;deploymentapos; not implemented
faultActor:
[...]
Also, to run only the client software (my server is written in gSoap and
seems to be working), do I need to put AcnInfoRow.class in the
WEB-INF/classes directory? (I did... didn't seem to help)
If this is simply a matter of not reading enough of the documentation,
please point me in the right direction.
Thanks,
Michael
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Monday, March 31, 2003 8:33 PM
To: [EMAIL PROTECTED]
Cc: Allen, Michael E.
Subject: Re: DO NOT REPLY [Bug 18530] - org.xml.sax.SAXException: No
deserializer defined for array type AcnInfoRow
Try starting with
1. A brand new tomcat 4.1.8.
2. Run Java2WSDL on the wsdl to generate both server and client
3. Don't use any other code other than the generated server and client.
Let us know. THIS is definitely a problem with your environment.
Thanks,
dims
--- [EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18530.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18530
org.xml.sax.SAXException: No deserializer defined for array type
AcnInfoRow
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME |
--- Additional Comments From [EMAIL PROTECTED] 2003-04-01
01:47 ---
I have downloaded the tonight's build (Mar 31), copied the jar files both
to
$CATALINA_HOME/common/lib and $CATALINA_HOME/webapps/axis/WEB_INF/lib,
recompiled (ie, ran WSDL2Java), and restarted Tomcat
same exception thrown. Could there be something about my CLASSPATH??
Note that
I have even hard coded the application directory.
==CLASSPATH===
C:\local\home\Java;.;C:\My
Documents\MyWeb\ServletDevelopment;C:\local\Apache-Gr
oup\Tomcat-4.1\common\lib\servlet.jar;C:\local\Apache-Group\Tomcat-4.1\commo
n\li
b\xerces.jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\axis.jar;C:\local\A
pach
e-Group\Tomcat-4.1\common\lib\jaxrpc.jar;C:\local\Apache-Group\Tomcat-4.1\co
mmon
\lib\log4j-1.2.4.jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\commons-log
ging
.jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\wsdl4j.jar;C:\local\Apache-
Grou
p\Tomcat-4.1\common\lib\commons-discovery.jar;C:\local\Apache-Group\Tomcat-4
.1\c
ommon\lib\wsdl4j.jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\saaj.jar;C:
\loc
al\mysql\connector-java\mysql-connector-java-3.0.6-stable\mysql-connector-ja
va-3
.0.6-stable-bin.jar;C:\local\OpenViz_23_eval\java\lib\openviz2.jar;C:\local\
Open
Viz_23_eval\java\lib\jimi.jar;C:\local\OpenViz_23_eval\vizworks\java\lib\cha
rts2
.jar
==Exception==
- Exception:
org.xml.sax.SAXException: No deserializer defined for array type
AcnInfoRow
at org.apache.axis.encoding.ser.ArrayDeserializer.
onStartElement(ArrayDeserializer.java:303)
at org.apache.axis.encoding.DeserializerImpl.
startElement(DeserializerImpl.java:428)
at org.apache.axis.encoding.DeserializationContextImpl.
startElement(DeserializationContextImpl.java:934)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.
java:198)
at org.apache.axis.message.MessageElement.
publishToHandler(MessageElement.java:699)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:224)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:331)
at org.apache.axis.client.Call.invoke(Call.java:2200
Re: DO NOT REPLY [Bug 18530] - org.xml.sax.SAXException: No deserializer defined for array type AcnInfoRow
Try starting with 1. A brand new tomcat 4.1.8. 2. Run Java2WSDL on the wsdl to generate both server and client 3. Don't use any other code other than the generated server and client. Let us know. THIS is definitely a problem with your environment. Thanks, dims --- [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18530. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18530 org.xml.sax.SAXException: No deserializer defined for array type AcnInfoRow [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME | --- Additional Comments From [EMAIL PROTECTED] 2003-04-01 01:47 --- I have downloaded the tonight's build (Mar 31), copied the jar files both to $CATALINA_HOME/common/lib and $CATALINA_HOME/webapps/axis/WEB_INF/lib, recompiled (ie, ran WSDL2Java), and restarted Tomcat same exception thrown. Could there be something about my CLASSPATH?? Note that I have even hard coded the application directory. ==CLASSPATH=== C:\local\home\Java;.;C:\My Documents\MyWeb\ServletDevelopment;C:\local\Apache-Gr oup\Tomcat-4.1\common\lib\servlet.jar;C:\local\Apache-Group\Tomcat-4.1\common\li b\xerces.jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\axis.jar;C:\local\Apach e-Group\Tomcat-4.1\common\lib\jaxrpc.jar;C:\local\Apache-Group\Tomcat-4.1\common \lib\log4j-1.2.4.jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\commons-logging .jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\wsdl4j.jar;C:\local\Apache-Grou p\Tomcat-4.1\common\lib\commons-discovery.jar;C:\local\Apache-Group\Tomcat-4.1\c ommon\lib\wsdl4j.jar;C:\local\Apache-Group\Tomcat-4.1\common\lib\saaj.jar;C:\loc al\mysql\connector-java\mysql-connector-java-3.0.6-stable\mysql-connector-java-3 .0.6-stable-bin.jar;C:\local\OpenViz_23_eval\java\lib\openviz2.jar;C:\local\Open Viz_23_eval\java\lib\jimi.jar;C:\local\OpenViz_23_eval\vizworks\java\lib\charts2 .jar ==Exception== - Exception: org.xml.sax.SAXException: No deserializer defined for array type AcnInfoRow at org.apache.axis.encoding.ser.ArrayDeserializer. onStartElement(ArrayDeserializer.java:303) at org.apache.axis.encoding.DeserializerImpl. startElement(DeserializerImpl.java:428) at org.apache.axis.encoding.DeserializationContextImpl. startElement(DeserializationContextImpl.java:934) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder. java:198) at org.apache.axis.message.MessageElement. publishToHandler(MessageElement.java:699) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:224) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:331) at org.apache.axis.client.Call.invoke(Call.java:2200) at org.apache.axis.client.Call.invoke(Call.java:2099) at org.apache.axis.client.Call.invoke(Call.java:1622) at schaat_allenm.HandTest.main(HandTest.java:61) AxisFault: org.xml.sax.SAXException: No deserializer defined for array type AcnInfoRow = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://platinum.yahoo.com
Re: DO NOT REPLY [Bug 18108] - SOAPEnvelope constructor passes unexpectedly null arguments
James, See http://marc.theaimsgroup.com/?l=axis-devm=104800578623575w=2 -- dims --- James M Snell [EMAIL PROTECTED] wrote: Working on a fix. Running all tests now. - James Snell IBM Emerging Technologies [EMAIL PROTECTED] (877) 511-5082 (voice/fax) ** NEW NUMBER ** (700) 930-1979 (t/l)** NEW NUMBER ** Programming Web Services With SOAP O'Reilly Associates, ISBN 0596000952 Have I not commanded you? Be strong and courageous. Do not be terrified, do not be discouraged, for the Lord your God will be with you whereever you go.- Joshua 1:9 [EMAIL PROTECTED] 03/18/2003 07:51 AM Please respond to axis-dev To [EMAIL PROTECTED] cc bcc Subject DO NOT REPLY [Bug 18108] - SOAPEnvelope constructor passes unexpectedly null arguments DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18108. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18108 SOAPEnvelope constructor passes unexpectedly null arguments --- Additional Comments From [EMAIL PROTECTED] 2003-03-18 15:51 --- Created an attachment (id=5408) patch for message.SOAPEnvelope's constructor = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com
Re: DO NOT REPLY [Bug 17766] - WSDL2Java cannot process documents withfewer operations in a Binding than in the corresp. portType.
Ok, I hadn't looked at the patch in detail. Given the tone of the discussion, it sounded as if the patch was going to allow this type of silliness to occur. Exceptions are good. Sorry for not paying closer attention. I retract my -1 - James Snell IBM Emerging Technologies [EMAIL PROTECTED] (559) 587-1233 (office) (700) 544-9035 (t/l) Programming Web Services With SOAP O'Reilly Associates, ISBN 0596000952 Have I not commanded you? Be strong and courageous. Do not be terrified, do not be discouraged, for the Lord your God will be with you whereever you go.- Joshua 1:9 [EMAIL PROTECTED] 03/07/2003 08:37 AM Please respond to axis-dev To [EMAIL PROTECTED] cc bcc Subject DO NOT REPLY [Bug 17766] - WSDL2Java cannot process documents with fewer operations in a Binding than in the corresp. portType. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17766. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17766 WSDL2Java cannot process documents with fewer operations in a Binding than in the corresp. portType. [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Additional Comments From [EMAIL PROTECTED] 2003-03-07 16:37 --- I believe the new patch throws an error in this situation, rather than just generating uncompilable code. I think this is a good thing, and should be fixed.
RE: DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to u se Keep-Alive
OK, I'm glad you caught it! -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 6:52 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to u se Keep-Alive Eric, Forcing the ByteArrayOutputStream into a String was a bad ideaDIME croaks. See latest cvs, am constructing a ByteArrayInputStream to hold the request body. Thanks, dims --- [EMAIL PROTECTED] wrote: I'm attaching a version of CommonsHTTPSender that works out-of-the box with axis 1.1RC1 and the latest version of commons-httpclient. Basically you need to change the client-config.wsdd file to use CommonsHTTPSender instead of HTTPSender and the right thing will happen. Some notes about this revision: 1. it does not (yet) set up the the configuration on the connection pool to anything other than the default for httpclient. In practice this means that you can only have 2 connections in the pool, per the HTTP RFC (see commons-httpclient for more on this). Clearly the right thing to do is to implement dims' suggested solution. Alan -- any interest in taking this on? 2. My fix also quietly fixes bug # 17539, but not in exactly the same way that dims fixed it when I reported it earlier (I've been hanging back on RC1, don't have real access to CVS at the office, insert other lame excuses). This is probably not a huge issue, but forewarned is forearmed, etc. etc. 3. I have tested this code pretty extensively with a small and large number of threads on an 8 CPU machine. I even wrote a spoof http server to verify that the connections are getting reusued from the server's perspective (I needed to do this because I'm doing a bunch of network performance tuning work and the results were rather strange, an artifact of our lousy internal network, it seems). I also ran it with Optimizeit and am confident that the right number of instances is being created. I even managed to cause intermittent network failures and observed that although an individual request would trigger an axis fault, the other requests in my app would safely acquire a new connection and keep on chuggin'. 4. There is a bug in commons-httpclient that causes it to fail when the client tries to chunk data *to* the server. I have therefore disabled upward chunking using the workaround that is suggested on the commons-httpclient bugzilla entry. This is commented in the source code for the invoke method. 5. One weakness of hooking up httpclient and axis is that their I/O layers are not entirely compatible. That is, axis wants to write its message on an output stream, while httpclient wants to read the request body from an input stream. The solution, such as it is, is to buffer the data in CommonsHTTPSender. This would be bad if you're sending SOAP messages with enormous attachments. The strategy I took was this: all state (cookies, and the like) remains in the MessageContext object. The only state added to CommonsHTTPClient is the MultiThreadedHttpConnectionManager instance. This means that the actual HttpClient instances are themselves discarded between requests, with any session information transferred to/from the MessageContext objects at the end/beginning of the invocation. I believe that this is consistent with the Axis architecture and that it does a decent job of hiding the fact that the commons-httpclient library is being used as the transport provider from the rest of the framework. Eric -Original Message- From: Alan Moore [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 3:07 PM To: '[EMAIL PROTECTED]' Subject: RE: DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to u se Keep-Alive Eric, I could *really* use this feature so if you need help getting it working let me know and I'll be glad to help code and/or test. alan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 1:59 PM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to use Keep-Alive DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16522. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16522 Allow Axis HTTP 1.1 clients to use Keep-Alive --- Additional Comments From [EMAIL PROTECTED] 2003-03-05 21:58 --- Eric, Any patches to CommonsHTTPSender would be VERY welcome. You can extend the DefaultHTTPTransportClientProperties/TransportClientProperties model to support properties for the commons-httpclient pool config. Thanks, dims ATTACHMENT part 2 application/octet-stream name=CommonsHTTPSender.java = Davanum Srinivas - http
RE: DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to use Keep-Alive
Eric, I could *really* use this feature so if you need help getting it working let me know and I'll be glad to help code and/or test. alan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 1:59 PM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to use Keep-Alive DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16522. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16522 Allow Axis HTTP 1.1 clients to use Keep-Alive --- Additional Comments From [EMAIL PROTECTED] 2003-03-05 21:58 --- Eric, Any patches to CommonsHTTPSender would be VERY welcome. You can extend the DefaultHTTPTransportClientProperties/TransportClientProperties model to support properties for the commons-httpclient pool config. Thanks, dims
Re: DO NOT REPLY [Bug 17188] - Problem generating complexType
unsubscribe
Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning
- Original Message - From: James M Snell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, February 18, 2003 18:18 Subject: Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning I recommend that we do a RC2 release anyway. Freeze the development, test for obvious errors, give it a week, release, all done. :-) +1 - James Snell IBM Emerging Technologies [EMAIL PROTECTED] (559) 587-1233 (office) (700) 544-9035 (t/l) Programming Web Services With SOAP O'Reilly Associates, ISBN 0596000952 Have I not commanded you? Be strong and courageous. Do not be terrified, do not be discouraged, for the Lord your God will be with you whereever you go.- Joshua 1:9 Steve Loughran [EMAIL PROTECTED] 02/18/2003 09:30 AM Please respond to axis-dev To [EMAIL PROTECTED] cc bcc Subject Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning - Original Message - From: Glen Daniels [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 17, 2003 20:35 Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning James writes: In the meantime, if others can start working through the bug list also, it would be very helpful :-) +1! Post-release donuts are on me if we can get a good percentage of these bugs resolved. :) As someone with no qualms about shipping stuff with known bugs (in preference for shipping stuff with unknown bugs), I want to remind people that we agreed to only work on critical bugs between RC1 and 1.1 final. Any change can introduce unforseen consequences, and it is the last minute quick fixes without a full beta-test that often turn out to be troublespots in shipping code, primarily because without the widespread tests there is no way to find out what the consequences of the change are. If everyone is going to rush ahead patching things, then we are going to have to do an RC2 release, completely lock down the CVS branch to all but the most critical defects, then ship the final product two weeks later.
RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning
Yup, I agree with this too. I'm not going to be able to cut another release until Monday at the earliest, though, and SOAPbuilders is coming up next week. My preference would be to push off the release by a week - wait until SOAPBuilders is over (2/28), and Sam and I have made whatever SOAP-1.2 changes are needed in Seattle, then release RC2, and final a week later. Thoughts? --Glen -Original Message- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 12:29 PM To: [EMAIL PROTECTED] Subject: Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning - Original Message - From: James M Snell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, February 18, 2003 18:18 Subject: Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning I recommend that we do a RC2 release anyway. Freeze the development, test for obvious errors, give it a week, release, all done. :-) +1 - James Snell IBM Emerging Technologies [EMAIL PROTECTED] (559) 587-1233 (office) (700) 544-9035 (t/l) Programming Web Services With SOAP O'Reilly Associates, ISBN 0596000952 Have I not commanded you? Be strong and courageous. Do not be terrified, do not be discouraged, for the Lord your God will be with you whereever you go.- Joshua 1:9 Steve Loughran [EMAIL PROTECTED] 02/18/2003 09:30 AM Please respond to axis-dev To [EMAIL PROTECTED] cc bcc Subject Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning - Original Message - From: Glen Daniels [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 17, 2003 20:35 Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning James writes: In the meantime, if others can start working through the bug list also, it would be very helpful :-) +1! Post-release donuts are on me if we can get a good percentage of these bugs resolved. :) As someone with no qualms about shipping stuff with known bugs (in preference for shipping stuff with unknown bugs), I want to remind people that we agreed to only work on critical bugs between RC1 and 1.1 final. Any change can introduce unforseen consequences, and it is the last minute quick fixes without a full beta-test that often turn out to be troublespots in shipping code, primarily because without the widespread tests there is no way to find out what the consequences of the change are. If everyone is going to rush ahead patching things, then we are going to have to do an RC2 release, completely lock down the CVS branch to all but the most critical defects, then ship the final product two weeks later.
Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning
- Original Message - From: Glen Daniels [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 09:37 Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning Yup, I agree with this too. I'm not going to be able to cut another release until Monday at the earliest, though, and SOAPbuilders is coming up next week. My preference would be to push off the release by a week - wait until SOAPBuilders is over (2/28), and Sam and I have made whatever SOAP-1.2 changes are needed in Seattle, then release RC2, and final a week later. Thoughts? +1 it'd be good to have the latest soapbuilder fixes in.
Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning
+1 to getting soapbuilder's fixes in. -- dims --- Steve Loughran [EMAIL PROTECTED] wrote: - Original Message - From: Glen Daniels [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 09:37 Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning Yup, I agree with this too. I'm not going to be able to cut another release until Monday at the earliest, though, and SOAPbuilders is coming up next week. My preference would be to push off the release by a week - wait until SOAPBuilders is over (2/28), and Sam and I have made whatever SOAP-1.2 changes are needed in Seattle, then release RC2, and final a week later. Thoughts? +1 it'd be good to have the latest soapbuilder fixes in. = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com
Re: DO NOT REPLY [Bug 17218] - wsdl2java tool prefixes boolean accessors with is
I believe, and the spec concurs, that the isFoo pattern is optional: http://java.sun.com/products/javabeans/docs/beans.101.pdf 8.3.2 Boolean properties In addition, for boolean properties, we allow a getter method to match the pattern: public boolean is PropertyName(); This isPropertyName method may be provided instead of a getPropertyName meth-od, or it may be provided in addition to a getPropertyName method. --- But that is kind of beside the point. The key thing is that isFoo() is legit. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 12:53 Subject: DO NOT REPLY [Bug 17218] - wsdl2java tool prefixes boolean accessors with is DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17218. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17218 wsdl2java tool prefixes boolean accessors with is [EMAIL PROTECTED] changed: What|Removed |Added -- -- Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-02-19 20:53 --- Um, no. :) Go read the JavaBeans spec, it actually requires that boolean accessors are named is and not get. The names of the XML elements/attributes are opaque to us, which is as they should be. We just generate getters/setters based on type. We could, I suppose, say IF the element is an xsd:boolean AND starts with is then don't double the is... but then you'd get element name=isildorWasStupid type=xsd:boolean/ and things would break. So I'm marking this INVALID.
Re: DO NOT REPLY [Bug 14162] - Round 5 BaseType WSDL needs additional schema built-in types
Not yet. The folks responsible for the WSDL have not yet come up with the final version. Thanks, dims --- [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14162. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14162 Round 5 BaseType WSDL needs additional schema built-in types --- Additional Comments From [EMAIL PROTECTED] 2003-02-18 00:43 --- Dims: is this resolved yet? = Davanum Srinivas - http://webservices.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com
Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwingClassCastException when assigning
I recommend that we do a RC2 release anyway. Freeze the development, test for obvious errors, give it a week, release, all done. :-) - James Snell IBM Emerging Technologies [EMAIL PROTECTED] (559) 587-1233 (office) (700) 544-9035 (t/l) Programming Web Services With SOAP O'Reilly Associates, ISBN 0596000952 Have I not commanded you? Be strong and courageous. Do not be terrified, do not be discouraged, for the Lord your God will be with you whereever you go.- Joshua 1:9 Steve Loughran [EMAIL PROTECTED] 02/18/2003 09:30 AM Please respond to axis-dev To [EMAIL PROTECTED] cc bcc Subject Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning - Original Message - From: Glen Daniels [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 17, 2003 20:35 Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning James writes: In the meantime, if others can start working through the bug list also, it would be very helpful :-) +1! Post-release donuts are on me if we can get a good percentage of these bugs resolved. :) As someone with no qualms about shipping stuff with known bugs (in preference for shipping stuff with unknown bugs), I want to remind people that we agreed to only work on critical bugs between RC1 and 1.1 final. Any change can introduce unforseen consequences, and it is the last minute quick fixes without a full beta-test that often turn out to be troublespots in shipping code, primarily because without the widespread tests there is no way to find out what the consequences of the change are. If everyone is going to rush ahead patching things, then we are going to have to do an RC2 release, completely lock down the CVS branch to all but the most critical defects, then ship the final product two weeks later.
RE: DO NOT REPLY [Bug 11306] - Use of Runnable in Call object violates J2EE rules in J2EE environment
Can you really say FIXED then? More like LATER, no? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 8:24 PM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 11306] - Use of Runnable in Call object violates J2EE rules in J2EE environment DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11306. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11306 Use of Runnable in Call object violates J2EE rules in J2EE environment [EMAIL PROTECTED] changed: What|Removed |Added -- -- Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-02-18 01:24 --- The new async stuff should resolve all this in time.
RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps, throwing ClassCastException when assigning
James writes: In the meantime, if others can start working through the bug list also, it would be very helpful :-) +1! Post-release donuts are on me if we can get a good percentage of these bugs +resolved. :) --Glen
