RE: Axis 1.4 and Java 1.6 - SOAPElement problem
It seems that the SOAPElement object is always created as
com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl when Java 1.6
is used. May be some library within Java 1.6 has this class? Has anyone
else seen the same thing?
Arijit
Microsoft is not the answer.
Microsoft is the question.
NO (or Linux) is the answer.
-- source unknown
From: Arijit Mukherjee [mailto:[EMAIL PROTECTED]
Sent: 14 November 2007 15:19
To: axis-user@ws.apache.org
Cc: Hugo Hiden
Subject: Axis 1.4 and Java 1.6 - SOAPElement problem
Hi All
So long I was using Axis 1.2.1 and Java 1.5, and was able to
successfully add my custom XML document within a SOAPMessage. I create
the XML document using castor-generated java bindings and combining them
into a DOM, and then using the following routine to get a SOAPElement
from the DOM:
public static SOAPElement
convertDOMToSOAPElement(javax.xml.soap.SOAPEnvelope env, Node DOMNode)
throws SOAPException {
//Test that DOMNode is of type
org.w3c.dom.Node.ELEMENT_NODE.
if ((DOMNode.getNodeType()) != Node.ELEMENT_NODE)
throw new SOAPException("DOMNode must of type
ELEMENT_NODE");
SOAPFactory elementFactory = SOAPFactory.newInstance();
SOAPElement se =
elementFactory.createElement(DOMNode.getLocalName());
mLog.debug("element class: " + se.getClass().getName());
if (DOMNode.hasAttributes()) {
NamedNodeMap DOMAttributes =
DOMNode.getAttributes();
int noOfAttributes = DOMAttributes.getLength();
for (int i = 0; i < noOfAttributes; i++) {
org.w3c.dom.Node attr = DOMAttributes.item(i);
se.addAttribute(env.createName(attr.getLocalName(), attr.getPrefix(),
attr.getNamespaceURI()),
attr.getNodeValue());
}
}
if (DOMNode.hasChildNodes()) {
NodeList children = DOMNode.getChildNodes();
for (int i = 0; i < children.getLength(); i++) {
Node child = children.item(i);
switch (child.getNodeType()) {
case
org.w3c.dom.Node.PROCESSING_INSTRUCTION_NODE:
break;
case org.w3c.dom.Node.DOCUMENT_TYPE_NODE:
break;
case org.w3c.dom.Node.CDATA_SECTION_NODE:
case org.w3c.dom.Node.COMMENT_NODE:
case org.w3c.dom.Node.TEXT_NODE: {
se.addTextNode(child.getNodeValue());
break;
}
default:
se.addChildElement(convertDOMToSOAPElement(env, child));
}
}//end of for
}//end of if
return se;
}
Once the SOAPElement is returned, I used to add it as a child
element to my main SOAPBodyElement:
SOAPEnvelope envelope = new SOAPEnvelope();
//Create the root element
Document outputDocument = XMLUtils.newDocument(new
ByteArrayInputStream(impl.tm.getBytes()));
System.out.println("Document Element: " +
outputDocument.getDocumentElement().getNodeName());
SOAPBody bdy = (SOAPBody) envelope.getBody();
SOAPBodyElement csReq = (SOAPBodyElement)
bdy.addBodyElement(envelope.createName(DynasoarConstants.DYNASOAR_SERVIC
E_REQUEST));
SOAPElement elem1 =
convertDOMToSOAPElement(envelope, outputDocument.getDocumentElement());
csReq.addChildElement(elem1);
Recently I upgraded to Axis 1.4 and Java 1.6, and started
getting a class cas exception about not being able to cast a
com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl object to
org.apache.axis.message.MessageElement at the
csReq.addChildElement(elem1) statement. But ideally the object returned
from the routing should be javax.xml.SOAPElement. I reverted back to
Java 1.5, and the same code is back working.
Are there any known issues with Axis 1.4 and Java 1.6?
Thanx in advance
Regards
Arijit
Microsoft is not the answer.
Microsoft is the question.
NO (or Linux) is the answer.
-- source unknown
Axis 1.4 and Java 1.6 - SOAPElement problem
Hi All
So long I was using Axis 1.2.1 and Java 1.5, and was able to
successfully add my custom XML document within a SOAPMessage. I create
the XML document using castor-generated java bindings and combining them
into a DOM, and then using the following routine to get a SOAPElement
from the DOM:
public static SOAPElement
convertDOMToSOAPElement(javax.xml.soap.SOAPEnvelope env, Node DOMNode)
throws SOAPException {
//Test that DOMNode is of type org.w3c.dom.Node.ELEMENT_NODE.
if ((DOMNode.getNodeType()) != Node.ELEMENT_NODE)
throw new SOAPException("DOMNode must of type
ELEMENT_NODE");
SOAPFactory elementFactory = SOAPFactory.newInstance();
SOAPElement se =
elementFactory.createElement(DOMNode.getLocalName());
mLog.debug("element class: " + se.getClass().getName());
if (DOMNode.hasAttributes()) {
NamedNodeMap DOMAttributes = DOMNode.getAttributes();
int noOfAttributes = DOMAttributes.getLength();
for (int i = 0; i < noOfAttributes; i++) {
org.w3c.dom.Node attr = DOMAttributes.item(i);
se.addAttribute(env.createName(attr.getLocalName(),
attr.getPrefix(),
attr.getNamespaceURI()),
attr.getNodeValue());
}
}
if (DOMNode.hasChildNodes()) {
NodeList children = DOMNode.getChildNodes();
for (int i = 0; i < children.getLength(); i++) {
Node child = children.item(i);
switch (child.getNodeType()) {
case org.w3c.dom.Node.PROCESSING_INSTRUCTION_NODE:
break;
case org.w3c.dom.Node.DOCUMENT_TYPE_NODE:
break;
case org.w3c.dom.Node.CDATA_SECTION_NODE:
case org.w3c.dom.Node.COMMENT_NODE:
case org.w3c.dom.Node.TEXT_NODE: {
se.addTextNode(child.getNodeValue());
break;
}
default:
se.addChildElement(convertDOMToSOAPElement(env,
child));
}
}//end of for
}//end of if
return se;
}
Once the SOAPElement is returned, I used to add it as a child element to
my main SOAPBodyElement:
SOAPEnvelope envelope = new SOAPEnvelope();
//Create the root element
Document outputDocument = XMLUtils.newDocument(new
ByteArrayInputStream(impl.tm.getBytes()));
System.out.println("Document Element: " +
outputDocument.getDocumentElement().getNodeName());
SOAPBody bdy = (SOAPBody) envelope.getBody();
SOAPBodyElement csReq = (SOAPBodyElement)
bdy.addBodyElement(envelope.createName(DynasoarConstants.DYNASOAR_SERVIC
E_REQUEST));
SOAPElement elem1 = convertDOMToSOAPElement(envelope,
outputDocument.getDocumentElement());
csReq.addChildElement(elem1);
Recently I upgraded to Axis 1.4 and Java 1.6, and started getting a
class cas exception about not being able to cast a
com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl object to
org.apache.axis.message.MessageElement at the
csReq.addChildElement(elem1) statement. But ideally the object returned
from the routing should be javax.xml.SOAPElement. I reverted back to
Java 1.5, and the same code is back working.
Are there any known issues with Axis 1.4 and Java 1.6?
Thanx in advance
Regards
Arijit
Microsoft is not the answer.
Microsoft is the question.
NO (or Linux) is the answer.
-- source unknown
RE: Deserializer error
I have seen this error several times - and it seems that it is only
associated with services deployed using the AdminClient. The error is
erratic in nature and goes away after one or two deployment attempts
(after restarting the tomcat). The same service if packed as a WAR file
does not generate this error - which might raise a question - does the
AdminClient fail to load the proper classes at times?
Arijit
>-Original Message-
>From: Patrick Quinn [mailto:[EMAIL PROTECTED]
>Sent: 08 July 2005 16:39
>To: Anne Thomas Manes; axis-user@ws.apache.org
>Subject: Deserializer error
>
>Hi
>
>I ran the customer WSDL through Cape Clear SOA Editor and it
>passed validation.
>
>So I am back to square one really with this error:
>
>ERRORorg.xml.sax.SAXException: Deserializing parameter
>'ProvidentResponse': could not find deserializer for type
>{http://ProvidentConnector.ProvidentResponseToOrch}ProvidentResponse
>
>
>I have learnt the following:
>
>Running Axis WSDL2Java on the customer WSDL generates a deploy.wsdd
>which, when deployed via the AdminClient, creates a Service whose
>associated WSDL
>(http://192.168.1.150:8880/axis/services/ProvidentConnector_Pro
>videntRec
>eiver_ProvidentWSPortSoap?WSDL)
>seems to be broken (as evidenced by the errors you have seen).
>
>
>I conclude that there are 3 possibilities here:
>1) the customer WSDL is subtly wrong
>2) I should be altering the auto-generated deploy.wsdd file somehow
>3) there is a bug somewhere in Axis
>
>Any thoughts?
>
>Thanks
>
>Pat
>
>-Original Message-
>From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
>Sent: 08 July 2005 15:39
>To: Patrick Quinn; axis-user@ws.apache.org
>Subject: Re: Error seen on BizTalk client request to my web service
>
>
>Pat,
>
>Download the Cape Clear SOA Editor and check it yourself. The tool's
>free, and I find it very useful for writing and validating WSDL.
>
>See http://www.capescience.com/soa/index.shtml.
>
>Anne
>
>On 7/8/05, Patrick Quinn <[EMAIL PROTECTED]> wrote:
>> Hi Anne
>>
>> It looks like you ran the WSDL derived from
>>
>http://192.168.1.150:8880/axis/services/ProvidentConnector_ProvidentRe
>> ce
>> iver_ProvidentWSPortSoap?WSDL
>>
>> ... ie the 'regenerated' WSDL from the deployment. I've no
>idea where
>> that gets 'tns1:' from. :-/
>>
>> Would it be possible to check the original customer WSDL with your
>> Cape Clear editor and let me know whether you see
>similar/any errors?
>> (customer WSDL below).
>>
>> Many thanks
>>
>> Pat
>>
>>
>>
>>
>>
>> > xmlns:s1="http://ProvidentConnector.ProvidentResponseToOrch";
>> xmlns:http="http://schemas.xmlsoap.org
>> /wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>> xmlns:s="http://www.w3.org/2001/XMLSchema";
>> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
>> xmlns:tns="http://namespace.accenture.com/";
>> xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/";
>> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
>> targetNamespace="http://namespace.accenture.com/";
>> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
>>
>>> targetNamespace="http://namespace.accenture.com/";>
>> > namespace="http://ProvidentConnector.ProvidentResponseToOrch"; />
>>
>>
>>
>>> ref="s1:ProvidentResponse" />
>>
>>
>>
>>
>>
>>
>>> type="s:string" />
>>
>>
>>
>>
>>> targetNamespace="http://ProvidentConnector.ProvidentResponseToOrch";>
>> />
>>
>>
>> > name="REQUESTID" type="s:string" />
>> > name="SO_RESULT_CODE" type="s:string" />
>> > name="SO_PROV_DATE" type="s:string" />
>> > name="SO_ERR_DESC" type="s:string" />
>> > name="XML_SORESULT" type="s:string" />
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> > name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
>>
>>
>>
>>
>>
>> > name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap"
>> type="tns:ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
>>http://schemas.xmlsoap.org/soap/http";
>> style="document" />
>>
>> >
>soapAction="http://namespace.accenture.com/ProvidentConnector_P
>rovidentR
>> eceiver_ProvidentWSPort
>> /SOPResponse" style="document" />
>>
>>
>>
>>
>>
>>
>>
>>
>> > name="ProvidentConnector_ProvidentReceiver_ProvidentWSPort">
>>http://schemas.xmlsoap.org/wsdl/";>BizTalk
>> assembly "ProvidentConnector, Version=1.0.0.0, Culture=neutral,
>> PublicKeyToken=ae7c9e263f196bff" published web
>service.
>>> name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap"
>>
>binding="tns:ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
>> >
>location="http://localhost/ProvidentConnector/ProvidentWSPort.asmx"; />
>>
>>
>>
>>
>>
>>
>> -Original Message-
>> From: Anne Thomas Manes [mailto:[EMAIL PROTEC
RE: Problem running WSDL2Java
Hi This is a warning - you can ignore it. WSDL2Java would still generate the stubs and skeletons... AM >-Original Message- >From: Miller, Janet [mailto:[EMAIL PROTECTED] >Sent: 29 June 2005 16:10 >To: axis-user@ws.apache.org >Subject: RE: Problem running WSDL2Java > >But I am not even using Tomcat when I run the wsdl2Java. > >-Original Message- >From: Patrick Quinn [mailto:[EMAIL PROTECTED] >Sent: Wednesday, June 29, 2005 10:41 AM >To: axis-user@ws.apache.org >Subject: RE: Problem running WSDL2Java > > >I'm a newbie too, but I thought I'd reply in case somebody else doesn't >get back to you. I think you are meant to include a log4j.properties >file in the $CATALINA_HOME/common/lib area. Maybe this is >related to the >problem? Just guessing, sorry! Pat > >-Original Message- >From: Miller, Janet [mailto:[EMAIL PROTECTED] >Sent: 29 June 2005 15:29 >To: axis-user@ws.apache.org >Subject: Problem running WSDL2Java > > >I am a newbie. I have just installed Axis and tried to WSDL2Java for >the first time, but I am getting the following error: > >log4j:WARN No appenders could be found for logger >(org.apache.axis.i18n.ProjectR esourceBundle). log4j:WARN Please >initialize the log4j system properly. > > >Why do I need to have log4j setup to run the WSDL2Java utility? The >Axis documentation doesn't say anything about this or how to do this. >Where does the log4j.xml file need to be? Does anyone have a basic >log4j.xml file that they could point me to that will work with >WSDL2Java? > >Thanks, > >Jan > >__ >This email has been scanned by the MessageLabs Email Security System. >For more information please visit http://www.messagelabs.com/email >__ >
RE: WSDL2Java genertion bug?
Title: RE: WSDL2Java genertion bug? Yes, this is http://issues.apache.org/bugzilla/show_bug.cgi?id=11290 It has been opened in 2002 and it's still unresolved. But this is an important feature. Any idea when this would be resolved? Castor already allows this kind of serialization/deserialization, but I was trying to move away from Castor - seems like I still have to stick to it till Axis resolves these issues. Arijit _ From: Arijit Mukherjee Sent: 15 June 2005 15:21 To: 'axis-user@ws.apache.org' Subject: WSDL2Java genertion bug? Hi All I have a schema which contains a certain complexType such as: Please note the "maxOccurs" in the sequence within the complex type "tupleType". A valid XML corresponding to this schema (as generated by XMLSpy) looks like: String String String String String String But the generated code doesn't correspond to this multiple occurrences of the "name-type" pair. I can add another element (say item) and make this unbounded, so that the XML bit would look like: Text Text Text Text Text Text Axis generated code does cater for this (if the extra element is added to the schema). But why would it be required if the first bit of XML is perfectly valid as per the schema definitions? Is this a bug in the Axis code generation? Is it already in the bugzilla? Regards Arijit "And when the night is cloudy, There is still a light that shines on me, Shine on until tomorrow, let it be. " John Lennon/Paul McCartney
WSDL2Java genertion bug?
Title: WSDL2Java genertion bug? Hi All I have a schema which contains a certain complexType such as: Please note the "maxOccurs" in the sequence within the complex type "tupleType". A valid XML corresponding to this schema (as generated by XMLSpy) looks like: String String String String String String But the generated code doesn't correspond to this multiple occurrences of the "name-type" pair. I can add another element (say item) and make this unbounded, so that the XML bit would look like: Text Text Text Text Text Text Axis generated code does cater for this (if the extra element is added to the schema). But why would it be required if the first bit of XML is perfectly valid as per the schema definitions? Is this a bug in the Axis code generation? Is it already in the bugzilla? Regards Arijit "And when the night is cloudy, There is still a light that shines on me, Shine on until tomorrow, let it be. " John Lennon/Paul McCartney
RE: Axis, Spring and Hibernate
What if you persist the session factory? Opening a session during each start will mean you will have to load the hibernate config properties each time (unless ofcourse spring does something for that)...This (persisting the session factory and loading the config properties only once) improved my server's performance a little... De-serialization does ofcourse take some time - but I wasn't actually able to measure the amount of time taken just for the serialization/deserialization...that would have given a better picture... Cheers A >-Original Message- >From: Koney, Satish [mailto:[EMAIL PROTECTED] >Sent: 14 March 2005 09:31 >To: axis-user@ws.apache.org >Subject: RE: Axis, Spring and Hibernate > >Ya...I could have used lazy="true" >but that requires the sesssion to be open when those elements >are accessed. > >But I am using spring to maintain the sessions...It is opening >at the start of the method and closing session when it is done >with that. so by the time the elements are accessed in my >client web applicatoin the sesssion is getting closed. that >results in exceptions > >probably, I talked much about hibernate in Axis forum...but i >believe that >(De) serialzation is consuming time > >Thanks, >. > > >> -Original Message- >> From:Arijit Mukherjee [SMTP:[EMAIL PROTECTED] >> Sent:Monday, March 14, 2005 2:24 PM >> To: axis-user@ws.apache.org >> Subject: RE: Axis, Spring and Hibernate >> >> If you are using hibernate-style beans (that is, collections are >> represented as sets/bags), you can set the option for "lazy >loading" - >> in which case when you are retrieving one object, hibernate will not >> retrieve all the children unless asked to do so. This will >reduce the >> time for mapping the relations and their children back into relevant >> objects. >> >> I have a similar problem because I am using Axis-generated stubs >> (which contains arrays for collections - and this rules out the >> possibility of lazy loading)... >> >> Arijit >> >> >-Original Message- >> >From: Koney, Satish [mailto:[EMAIL PROTECTED] >> >Sent: 14 March 2005 07:57 >> >To: axis-user@ws.apache.org >> >Subject: RE: Axis, Spring and Hibernate >> > >> >it is not taking 20 minutes for executing the queries..the queries >> >are executed fast.. >> >the problem is with constructing those retrvied records >into objects... >> > >> >Can someone plz help!! >> > >> > >> >> -Original Message- >> >> From: Sebastien Mayemba Mbokoso >> >[SMTP:[EMAIL PROTECTED] >> >> Sent: Sunday, March 13, 2005 11:43 AM >> >> To: axis-user@ws.apache.org >> >> Subject: Re: Axis, Spring and Hibernate >> >> >> >> I am using Hibernaete in my current project with Axis too. >> >It's not an >> >> Axis issue but just a Hibernate trouble. You have to >investigate in >> >> the Hibernate Forum. >> >> 20 minutes for executing a queries it's not possible. My >databases >> >> contains 32 tables with so many relationships and so many tables >> >> are full. My queries don't spend a lot of time as yours. >> >> >> >> >> >> Sebastien >> >> >> >> >> >> On Sat, 12 Mar 2005 10:52:28 -0500, Koney, Satish >> >> <[EMAIL PROTECTED]> wrote: >> >> > Hi, >> >> > >> >> > I have two modules in my application. >> >> > The first one is a webservice. (Axis 1.1, spring 1.1.3 >> >> > and >> >> Hibernate >> >> > 2.1.6 ) This web service is responsible for fetching, updating, >> >> > deleting the records in database. >> >> > >> >> > The second one is web application which is >consuming this >> >> > web service. It is purely for presentation. >> >> > It does not do anything other than presentation. >> >> > >> >> > The problem I am facing now is, when I request Hibernate >> >for records >> >> > in >> >> one >> >> > table, it is executing so many queries. >> >> > It is fetching records from the tables which have foreign-key >> >> > relation >> >> with >> >> > that table. So when the web application is using this web >> >> >
RE: Axis, Spring and Hibernate
If you are using hibernate-style beans (that is, collections are represented as sets/bags), you can set the option for "lazy loading" - in which case when you are retrieving one object, hibernate will not retrieve all the children unless asked to do so. This will reduce the time for mapping the relations and their children back into relevant objects. I have a similar problem because I am using Axis-generated stubs (which contains arrays for collections - and this rules out the possibility of lazy loading)... Arijit >-Original Message- >From: Koney, Satish [mailto:[EMAIL PROTECTED] >Sent: 14 March 2005 07:57 >To: axis-user@ws.apache.org >Subject: RE: Axis, Spring and Hibernate > >it is not taking 20 minutes for executing the queries..the >queries are executed fast.. >the problem is with constructing those retrvied records into objects... > >Can someone plz help!! > > >> -Original Message- >> From:Sebastien Mayemba Mbokoso >[SMTP:[EMAIL PROTECTED] >> Sent:Sunday, March 13, 2005 11:43 AM >> To: axis-user@ws.apache.org >> Subject: Re: Axis, Spring and Hibernate >> >> I am using Hibernaete in my current project with Axis too. >It's not an >> Axis issue but just a Hibernate trouble. You have to investigate in >> the Hibernate Forum. >> 20 minutes for executing a queries it's not possible. My databases >> contains 32 tables with so many relationships and so many tables are >> full. My queries don't spend a lot of time as yours. >> >> >> Sebastien >> >> >> On Sat, 12 Mar 2005 10:52:28 -0500, Koney, Satish >> <[EMAIL PROTECTED]> wrote: >> > Hi, >> > >> > I have two modules in my application. >> > The first one is a webservice. (Axis 1.1, spring 1.1.3 and >> Hibernate >> > 2.1.6 ) This web service is responsible for fetching, updating, >> > deleting the records in database. >> > >> > The second one is web application which is consuming this >> > web service. It is purely for presentation. >> > It does not do anything other than presentation. >> > >> > The problem I am facing now is, when I request Hibernate >for records >> > in >> one >> > table, it is executing so many queries. >> > It is fetching records from the tables which have foreign-key >> > relation >> with >> > that table. So when the web application is using this web service, >> > it is taking lot of time to load the page. ( 20 minutes just to >> > display 5-6 records) >> > >> > On the Axis side, how can I control the >(De)serialization of >> objects >> > that I am getting from the web service? >> > >> > Please help!!! >> > >> > Thanks, >> > . >> > >> > >> > Confidential: This electronic message and all contents contain >> information >> > from Syntel, Inc. which may be privileged, confidential or >otherwise >> > protected from disclosure. The information is intended to >be for the >> > addressee only. If you are not the addressee, any >disclosure, copy, >> > distribution or use of the contents of this message is >prohibited. >> > If >> you >> > have received this electronic message in error, please notify the >> > sender immediately and destroy the original message and all copies. >> > >> > >Confidential: This electronic message and all contents >contain information from Syntel, Inc. which may be privileged, >confidential or otherwise protected from disclosure. The >information is intended to be for the addressee only. If you >are not the addressee, any disclosure, copy, distribution or >use of the contents of this message is prohibited. If you >have received this electronic message in error, please notify >the sender immediately and destroy the original message and all copies. > >
