 |
BOOK: Professional XML Development with Apache Tools  | This is the forum to discuss the Wrox book Professional XML Development with Apache Tools: Xerces, Xalan, FOP, Cocoon, Axis, Xindice by Theodore W. Leung; ISBN: 9780764543555 - Read more about Professional XML Development with Apache Tools: Xerces, Xalan, FOP, Cocoon, Axis, Xindice or buy the book from your favorite retailer
- Download the code for Professional XML Development with Apache Tools: Xerces, Xalan, FOP, Cocoon, Axis, Xindice
|
|
Welcome to the p2p.wrox.com Forums.
You are currently viewing the BOOK: Professional XML Development with Apache Tools section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|

February 16th, 2004, 07:45 AM
|
|
Registered User
|
|
Join Date: Feb 2004
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Unable to execute Axis Client
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultSubcode:
faultString:
MessageType: 2
MessageNum: 8961
MessageText: Required element expected in the input XML document
AppendedText: <Address_2>
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
MessageType: 2
MessageNum: 8961
MessageText: Required element expected in the input XML document
AppendedText: <Address_2>
at com.remedy.arsys.api.Proxy.ARXMLCreateEntry(Native Method)
at com.remedy.arsys.api.Util.ARXMLCreateEntry(Util.ja va:2646)
at com.remedy.arsys.ws.services.ARService.performOper ation(DashOB3391:57
0)
at com.remedy.arsys.ws.services.ARService.processRequ est(DashOB3391:142)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.axis.providers.java.MsgProvider.process Message(MsgProvider
.java:206)
at org.apache.axis.providers.java.JavaProvider.invoke (JavaProvider.java:
289)
at org.apache.axis.strategies.InvocationStrategy.visi t(InvocationStrateg
y.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain .java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.jav a:120)
at org.apache.axis.server.AxisServer.invoke(AxisServe r.java:312)
at org.apache.axis.transport.http.AxisServlet.doPost( AxisServlet.java:57
7)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:853)
at com.newatlanta.servletexec.ServletExec.CallServlet Service(ServletExec
.java:1679)
at com.newatlanta.servletexec.SERequestDispatcher.for wardServlet(SEReque
stDispatcher.java:274)
at com.newatlanta.servletexec.SERequestDispatcher.for ward(SERequestDispa
tcher.java:191)
at com.newatlanta.servletexec.ApplicationInfo.process ApplRequest(Applica
tionInfo.java:1390)
at com.newatlanta.servletexec.ServerHostInfo.processA pplRequest(ServerHo
stInfo.java:1243)
at com.newatlanta.servletexec.ServletExec.ProcessRequ est(ServletExec.jav
a:1235)
at com.newatlanta.servletexec.ServletExec.ProcessRequ est(ServletExec.jav
a:1113)
MessageType: 2
MessageNum: 8961
MessageText: Required element expected in the input XML document
AppendedText: <Address_2>
at org.apache.axis.message.SOAPFaultBuilder.createFau lt(SOAPFaultBuilder
.java:260)
at org.apache.axis.message.SOAPFaultBuilder.endElemen t(SOAPFaultBuilder.
java:169)
at org.apache.axis.encoding.DeserializationContextImp l.endElement(Deseri
alizationContextImpl.java:1015)
at org.apache.xerces.parsers.SAXParser.endElement(SAX Parser.java:1403)
at org.apache.xerces.validators.common.XMLValidator.c allEndElement(XMLVa
lidator.java:1456)
at org.apache.xerces.framework.XMLDocumentScanner$Con tentDispatcher.disp
atch(XMLDocumentScanner.java:1260)
at org.apache.xerces.framework.XMLDocumentScanner.par seSome(XMLDocumentS
canner.java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLPar ser.java:1081)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:3 74)
at org.apache.axis.encoding.DeserializationContextImp l.parse(Deserializa
tionContextImpl.java:242)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPar t.java:538)
at org.apache.axis.Message.getSOAPEnvelope(Message.ja va:376)
at org.apache.axis.client.Call.invokeEngine(Call.java :2583)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
at com.primustel.pas.data.troubleticket.proxybeans.VO IP_OrdersSoapBindin
gStub.opCreate(VOIP_OrdersSoapBindingStub.java:255 )
at TestItAxis.main(TestItAxis.java:104)
|
|

May 13th, 2004, 11:59 AM
|
|
Registered User
|
|
Join Date: May 2004
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Shailendert,
I have the same problem with executing the axis client trying to communicate to Remedy's ARSystem. Were you able to figure out how to solve the problem? Thanks in advance for your help.
Swabhav
|
|

May 13th, 2004, 12:27 PM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
What is this about? Perhaps if the questions were asked in the proper forums people would be able to help.
Hal Levy
Web Developer, PDI Inc.
NOT a Wiley/Wrox Employee
|
|

May 13th, 2004, 12:48 PM
|
|
Registered User
|
|
Join Date: May 2004
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Hal,
I am sorry, the original posting did not have all the details. Since I had the exact same set of error messages I posted the questions to the author without any further details.
I am using Apache Axis as the framework to implement my web services client. The web services server has been configured through the product called ARSystems from Remedy. I get the error messages posted in the original message when I attempt to run the client. I am a newbie to web services, I am looking for some hints on where to start....
Swabhav
|
|

May 13th, 2004, 12:55 PM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
I don't think we have an appropriate forum for this. I don't think there are any WROX books on the topic. I'm not sure anyone will be able to hlep you here- but you might luck out.
Since it's in this forum- for feedback- it might not even get seen by someone who knows.
I'd look for an apache forum.
Hal Levy
Web Developer, PDI Inc.
NOT a Wiley/Wrox Employee
|
|

May 13th, 2004, 01:25 PM
|
 |
Wrox Staff
Points: 18,059, Level: 58 |
|
|
Join Date: May 2003
Posts: 1,906
Thanks: 62
Thanked 139 Times in 101 Posts
|
|
Actually, we do have a book related to this: Professional XML Development with Apache Tools. :)
http://www.wrox.com/books/0764543555.shtml
I'll move this thread to the forum for that book.
Jim Minatel
Senior Acquisitions Editor
Wiley Technology Publishing
WROX Press
Jim's Book of the week: Professional InfoPath 2003 - http://www.wrox.com/books/0764557130.shtml
|
|

July 22nd, 2006, 05:06 PM
|
|
Registered User
|
|
Join Date: Jul 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Swabhav - Did you ever found a solution to this problem..Would appreciate if you could help me if already had a solution..
Thanks a lot!!
-Sandy
Quote:
quote:Originally posted by swabhav
Hi Hal,
I am sorry, the original posting did not have all the details. Since I had the exact same set of error messages I posted the questions to the author without any further details.
I am using Apache Axis as the framework to implement my web services client. The web services server has been configured through the product called ARSystems from Remedy. I get the error messages posted in the original message when I attempt to run the client. I am a newbie to web services, I am looking for some hints on where to start....
Swabhav
|
|
|

August 1st, 2006, 09:51 AM
|
|
Registered User
|
|
Join Date: Aug 2006
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Swabhav, shailendert,
I also have the exact same problem, communicating to a Remedy
Web Service. Got past the Authentication problem, now this!?!?!?
Anyone figure this out?
Thanks,
Tim
|
|

August 1st, 2006, 02:47 PM
|
|
Registered User
|
|
Join Date: Aug 2006
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Here's the fix !!! Thanks to Dan Hardy....
Dan Hardy
Wed, 19 Jul 2006 11:42:43 -0700
I figured this out, after stepping through the axis source code. (Good thing
the source is available!)
The Axis generated stubs (from WSDL2Java) set all of the method parameters to
be in the header (specifically, lines of code in the stub look like this next
fragmenet, where the next to last parameter is true). This controls whether
input parameters are passed in the header or body. I don't see a WSDL2Java
option to change this - it always generates them this way.
param = new org.apache.axis.description.ParameterDesc(new
javax.xml.namespace.QName("urn:ESS_Change_Submit", "type"),
org.apache.axis.description.ParameterDesc.IN, new
javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema";, "string"),
java.lang.String.class, true, false);
Now that would explain why Remedy thinks the parameter is missing. It
apparently is looking in the body only, not the header.
I went through the stub classes and manually changed all of them to be false so
the parameters are in the body. Then it works!
Question: Is this a bug in Axis, a bug in Remedy, or both? Should Remedy
support having the parameters be in the header (which seems the default for
Axis/WSDL2Java at least based on Remedy's WSDL?) At the very least there seems
to be a pretty painful incompatibility between Remedy and Axis here.
Dan
|
|

April 2nd, 2007, 01:28 AM
|
|
Registered User
|
|
Join Date: Apr 2007
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Dan
Did this worked for u.
I tried the same thing, but it is not working.
Following is the exception am getting when I try to access he service in ARSystem.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString:
MessageType: 2
MessageNum: 8961
MessageText: Required element expected in the input XML document
AppendedText: <Assigned_To>
faultActor:
faultNode:
faultDetail:
Quote:
quote:Originally posted by thiggins
Here's the fix !!! Thanks to Dan Hardy....
Dan Hardy
Wed, 19 Jul 2006 11:42:43 -0700
I figured this out, after stepping through the axis source code. (Good thing
the source is available!)
The Axis generated stubs (from WSDL2Java) set all of the method parameters to
be in the header (specifically, lines of code in the stub look like this next
fragmenet, where the next to last parameter is true). This controls whether
input parameters are passed in the header or body. I don't see a WSDL2Java
option to change this - it always generates them this way.
param = new org.apache.axis.description.ParameterDesc(new
javax.xml.namespace.QName("urn:ESS_Change_Submit", "type"),
org.apache.axis.description.ParameterDesc.IN, new
javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema";, "string"),
java.lang.String.class, true, false);
Now that would explain why Remedy thinks the parameter is missing. It
apparently is looking in the body only, not the header.
I went through the stub classes and manually changed all of them to be false so
the parameters are in the body. Then it works!
Question: Is this a bug in Axis, a bug in Remedy, or both? Should Remedy
support having the parameters be in the header (which seems the default for
Axis/WSDL2Java at least based on Remedy's WSDL?) At the very least there seems
to be a pretty painful incompatibility between Remedy and Axis here.
Dan
|
|
|
 |