Re: Transport trace

Hi Mark Excellent This is very useful in case of XML Parser library too damitha On Wed, 2005-01-12 at 20:37, Mark Whitlock wrote: I have enabled trace in the transport library. So if you build using ant and switch trace on you'll get entry/exit/catch trace from transport methods now. The

[jira] Assigned: (AXISCPP-375) setPrefix() in IAttribute class does not check whether the given namespace prefix is declared or not

[ http://issues.apache.org/jira/browse/AXISCPP-375?page=history ] Roshan Weerasuriya reassigned AXISCPP-375: -- Assign To: Roshan Weerasuriya setPrefix() in IAttribute class does not check whether the given namespace prefix is declared or not

Re: IHandlerSoapSerializer-getHeaderBlock()

hi Andrew, 2) If getFirstHeaderBlock() has been called and any number of getNextHeaderBlock() calls have been made, getHeaderBlock() always returns the first header block, but doesn't reposition in the list like getFirstHeaderBlock() does. So what's the point of getHeaderBlock()? Can it

[jira] Commented: (AXISCPP-374) No usage information for setSOAPMethodAttribute() functions in API docs

[ http://issues.apache.org/jira/browse/AXISCPP-374?page=comments#action_57574 ] Roshan Weerasuriya commented on AXISCPP-374: hi Manohar, what do you exactly mean by how to verify the values set by these APIs? And also you say However,

[jira] Commented: (AXISCPP-374) No usage information for setSOAPMethodAttribute() functions in API docs

[ http://issues.apache.org/jira/browse/AXISCPP-374?page=comments#action_57575 ] Manohar commented on AXISCPP-374: - Hi Roshan, Thanks for the reply. The API docs doesn't provide info about when to call setSOAPMethodAttribute() APIs in the client

Re: Fw: Removing generetd source from cvs [was:Re: cvs commit: ws-axis/c/tests/client/interop/round1/gen_src SimpleTestSoap.cpp]

+1 to option 2. ___ Adrian Dick ([EMAIL PROTECTED]) Mark Whitlock/UK/[EMAIL PROTECTED] wrote on 13/01/2005 11:18:14: +1 to option 2 Mark Whitlock IBM - Forwarded by Mark Whitlock/UK/IBM on 13/01/2005 11:16 - Samisa

Re: Removing generetd source from cvs [was:Re: cvs commit: ws-axis/c/tests/client/interop/round1/gen_src SimpleTestSoap.cpp]

Option 2 please +1 John Hawkins Samisa Abeysinghe [EMAIL PROTECTED] 13/01/2005 11:06 Please respond to Apache AXIS C Developers List To Apache AXIS C Developers List axis-c-dev@ws.apache.org, [EMAIL PROTECTED] cc Subject Re: Removing generetd source from cvs [was:Re: cvs

[jira] Commented: (AXISCPP-374) No usage information for setSOAPMethodAttribute() functions in API docs

[ http://issues.apache.org/jira/browse/AXISCPP-374?page=comments#action_57580 ] Roshan Weerasuriya commented on AXISCPP-374: hi Manohar, This method can be used at any time which the user needs. There are no pre-requirements to be done

Transport trace

If you build the transport library with anything other than ant or MSVC, please define AXISTRACE_LIBRARY to the compiler when building the transport and channel libraries. I have updated the ant build and Fred is updating MSVC. Apologies for the inconvenience, Mark Mark Whitlock IBM

RE: Fw: Platform specific class

Yes, lets delay the APR usage to later version. However, how much time you think itwould take impl., integrate and test only the OO model (PAL) with required functionalities we needed? regards -Lilantha -Original Message-From: John Hawkins [mailto:[EMAIL PROTECTED]Sent: Thursday,

RE: Fw: Platform specific class

Let me get something started and see where that leads us...we should be able to contain it for 1.5, as long as someone can do the makefile modifications Lilantha Darshana [EMAIL PROTECTED] wrote on 01/13/2005 12:17:11 PM: Yes, lets delay the APR usage to later version. However, how

Proposal - release versioning and branching model.

Title: Proposal - release versioning and branching model. Hi All, I was thinking about the maturity scale of the Axis C++ compare to axis java and others. It seems like we move very fast in our release versioning and does not make much progress on the maturity scale of the project. Now

Server code generation from WSDL - Bug??

Hi. I've been having some problems with a web service whose code skeleton I generated using the wsdl2ws tool available in Axis. Using C++ as the target language, I started having problems with receiving messages in (generated) clients, also in C++. After breaking out GDB and Ethereal, I

[jira] Created: (AXIS-1760) Axis and EJB Providers

Axis and EJB Providers -- Key: AXIS-1760 URL: http://issues.apache.org/jira/browse/AXIS-1760 Project: Axis Type: Bug Components: Deployment / Registries Versions: 1.0-rc2 Environment: jboss-4.0.1RC1, axis-1_2RC2-bin Reporter:

[jira] Updated: (AXIS-1761) Deserialization of SOAP(document/literal) went wrong because of Introspection Problem

[ http://issues.apache.org/jira/browse/AXIS-1761?page=history ] Andre Genser updated AXIS-1761: --- Attachment: BeanDeserializer.java Only a bad work arround to handle document/literal/wrapped SOAP messages Deserialization of SOAP(document/literal) went

[jira] Commented: (AXIS-1761) Deserialization of SOAP(document/literal) went wrong because of Introspection Problem

[ http://issues.apache.org/jira/browse/AXIS-1761?page=comments#action_57583 ] Davanum Srinivas commented on AXIS-1761: Please upload the soap message that is being deserialized and the wsdl/xsd as well. thanks, dims Deserialization of

[jira] Updated: (AXIS-1761) Deserialization of SOAP(document/literal) went wrong because of Introspection Problem

[ http://issues.apache.org/jira/browse/AXIS-1761?page=history ] Andre Genser updated AXIS-1761: --- Attachment: eai-wsdl.zip - Complex WSDL with XML Schemata - Example SOAP Response and Request Deserialization of SOAP(document/literal) went wrong because

Axis 1391 and Axis 1567

Hello, We have deployed a web app in tomcat. The web app has webservices client that invokes a .net webservices. We have used Axis for the webservice client. The application is running fine on dev,test and staging env. But, it goes out of memory (java.lang.OutofMemory) on prod enviornment. The

Axis hanging when entropy expires

Hi, A colleague was recently trying to set up Axis 1.2 RC2 on his development machine. He got as far as seeing the root page, and having HappyAxis display OK. Also, he was able to view the list of services, and download the wsdl from them Unfortunately, attempting to call any end-point

[jira] Created: (AXIS-1762) xs:list attributes do not deserialize

xs:list attributes do not deserialize - Key: AXIS-1762 URL: http://issues.apache.org/jira/browse/AXIS-1762 Project: Axis Type: Bug Components: Serialization/Deserialization Versions: current (nightly) Reporter:

[jira] Updated: (AXIS-1752) xs:list attributes do not serialize

[ http://issues.apache.org/jira/browse/AXIS-1752?page=history ] Steve Green updated AXIS-1752: -- Attachment: 1752_try2.patch This patch replaces the previous patch. xs:list attributes do not serialize --- Key:

RE: Axis hanging when entropy expires

Thanks for the info Bob. I would say that Axis should NOT need to protect itself against core Java APIs from failing in this manner. Putting this kind of call in a timed thread seems like way too much overkill to me. It is great that you posted this, as anyone searching the archives can find

[jira] Updated: (AXIS-1762) xs:list attributes do not deserialize

[ http://issues.apache.org/jira/browse/AXIS-1762?page=history ] Steve Green updated AXIS-1762: -- Attachment: 1762.patch This patch is one way to fix the problem. xs:list attributes do not deserialize - Key:

[jira] Updated: (AXIS-1752) xs:list attributes do not serialize

[ http://issues.apache.org/jira/browse/AXIS-1752?page=history ] Steve Green updated AXIS-1752: -- Attachment: 1752.diff-u diff -u version of the previous patch xs:list attributes do not serialize --- Key:

[jira] Commented: (AXIS-1763) Would be nice to have an Ant task to fill in the *StubBindingImpl.java file

[ http://issues.apache.org/jira/browse/AXIS-1763?page=comments#action_57596 ] Brian Davis commented on AXIS-1763: --- Ack, I mean *SoapBindingImpl.java. The task I wrote is used like this: taskdef name=fixwsdl2java

[jira] Created: (AXIS-1763) Would be nice to have an Ant task to fill in the *StubBindingImpl.java file

Would be nice to have an Ant task to fill in the *StubBindingImpl.java file --- Key: AXIS-1763 URL: http://issues.apache.org/jira/browse/AXIS-1763 Project: Axis Type: Improvement Components:

[jira] Updated: (AXIS-1763) Would be nice to have an Ant task to fill in the *StubBindingImpl.java file

[ http://issues.apache.org/jira/browse/AXIS-1763?page=history ] Brian Davis updated AXIS-1763: -- Attachment: FixWSDL2JavaTask.java Would be nice to have an Ant task to fill in the *StubBindingImpl.java file

[jira] Updated: (AXIS-1763) Would be nice to have an Ant task to fill in the *StubBindingImpl.java file

[ http://issues.apache.org/jira/browse/AXIS-1763?page=history ] Brian Davis updated AXIS-1763: -- Attachment: after.java This is the my file after running this task. The task I ran is as described in my Comment. Would be nice to have an Ant task to fill

[jira] Updated: (AXIS-1762) xs:list attributes do not deserialize

[ http://issues.apache.org/jira/browse/AXIS-1762?page=history ] Steve Green updated AXIS-1762: -- Attachment: 1762.diff-u diff -u version of the patch xs:list attributes do not deserialize - Key: AXIS-1762

[jira] Created: (AXIS-1764) Add an XmlBean Serializer and Deserializer to Axis

Add an XmlBean Serializer and Deserializer to Axis -- Key: AXIS-1764 URL: http://issues.apache.org/jira/browse/AXIS-1764 Project: Axis Type: New Feature Components: Serialization/Deserialization Versions:

[jira] Updated: (AXIS-1764) Add an XmlBean Serializer and Deserializer to Axis

[ http://issues.apache.org/jira/browse/AXIS-1764?page=history ] Jonathan Colwell updated AXIS-1764: --- Attachment: XmlBeanSerializer.java Add an XmlBean Serializer and Deserializer to Axis --

[jira] Updated: (AXIS-1764) Add an XmlBean Serializer and Deserializer to Axis

[ http://issues.apache.org/jira/browse/AXIS-1764?page=history ] Jonathan Colwell updated AXIS-1764: --- Attachment: XmlBeanDeserializer.java Add an XmlBean Serializer and Deserializer to Axis --

[jira] Updated: (AXIS-1764) Add an XmlBean Serializer and Deserializer to Axis

[ http://issues.apache.org/jira/browse/AXIS-1764?page=history ] Jonathan Colwell updated AXIS-1764: --- Attachment: XmlBeanSerializerFactory.java Add an XmlBean Serializer and Deserializer to Axis --

[jira] Updated: (AXIS-1764) Add an XmlBean Serializer and Deserializer to Axis

[ http://issues.apache.org/jira/browse/AXIS-1764?page=history ] Jonathan Colwell updated AXIS-1764: --- Attachment: XmlBeanDeserializerFactory.java Add an XmlBean Serializer and Deserializer to Axis --

can't access axis webservice using .net client

I have a doc/literal axis webservice. Axis 1.1 worked fine with my .net client. But when i switched the axis.jar to version 1.2, I get the following exception: [1/13/05 17:20:19:498 PST] 527f4938 WebGroup E SRVE0026E: [Servlet Error]-[class org.apache.axis.SOAPPart does not implement

Re: can't access axis webservice using .net client

Monika, Looks like a class resp. a jar conflict with your server jars (saaj.jar,...). Which server are you using? Websphere? There are several threads on this topic. Use IncompatibleClassChangeError as keyword. Yves On Thu, 2005-01-13 at 17:55 -0800, Monika Gorkani wrote: I have a