Accidentally discovered the root cause of the problem... Still not sure
how to fix it though.
It seems that Axis2 has some trouble parsing input that is 'Web Services
Addressing' encoded. Discovered that by accident when I was trying to
debug the problem, but had a wsa->xsi filter in line to
Rodrigo Ruiz wrote:
I use Axis 1.3, and it generates a different set of classes. I am not
getting any class called "DeviceIDImpl", but an abstract "DeviceID" one.
I think the difference comes from Axis2 XmlBeans support (I see you
activate this option in the command-line). Have you inspected th
I use Axis 1.3, and it generates a different set of classes. I am not
getting any class called "DeviceIDImpl", but an abstract "DeviceID" one.
I think the difference comes from Axis2 XmlBeans support (I see you
activate this option in the command-line). Have you inspected the source
code of "De
wsdl at:
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/XMLVend20.asp
command line:
java -classpath $AXIS2_CLASSPATH org.apache.axis2.wsdl.WSDL2Java -p
expertron_client -d xmlbeans -uri xmlvend-full-2.0.wsdl -ss -t -sd
Example soap request (no response yet) (please forgive th
Mmm, I guess I'm not seeing the whole picture :-/
Could you send the wsdl, and an example of the full request/response
envelopes you are getting? I think it would help me to understand what
is happening :-)
Rodrigo Ruiz
Justin Schoeman wrote:
Rodrigo Ruiz wrote:
Justin,
Starting from a WS
Rodrigo Ruiz wrote:
Justin,
Starting from a WSDL file that uses inheritance, I have successfully
generated the beans, and they keep their hierarchy relationship, using
Axis 1.2.1 (from within a Eclipse with WST). It only re-generates the
beans if they are not in the classpath, so I am able to
Justin,
Starting from a WSDL file that uses inheritance, I have successfully
generated the beans, and they keep their hierarchy relationship, using
Axis 1.2.1 (from within a Eclipse with WST). It only re-generates the
beans if they are not in the classpath, so I am able to customize them,
and
Yes, tried that. Axis1 does not even manage to serialise abstract
classes... As you can see from the extract below, only type information
is included for simple abstract classes, and complex abstract classes
(idmethod) are completely empty:
http://www.nrs.eskom.co.za/xmlvend/revenue/2.0/schem
Have you tried Axis 1?On 2/23/06, Justin Schoeman <[EMAIL PROTECTED]> wrote:
Either you have completely lost me, or we are thinking of different things.Constructors for the objects work, and casting them up for serialisationworks. Deserialisation also works, but casting them down to the
implemented
Either you have completely lost me, or we are thinking of different things.
Constructors for the objects work, and casting them up for serialisation
works. Deserialisation also works, but casting them down to the
implemented class does not...
-justin
robert lazarski wrote:
Sorry to leave
Sorry to leave you hanging Justin, been busy and this question required a bit of thinking.
You can do inheritance and abstract classes via xml binding. See this jira for how it works:
http://issues.apache.org/jira/browse/AXIS2-310 - this got fixed in axis 1.3 and I found a work around for axis
Hi again,
I am begging now - I have tried everything that I can think of. This is
my last effort before scrapping Linux/Apache/Axis for this project and
switching to Widoze/C# :-(
The problem is:
I need to implement a webservice for XMLVend (generated by a standards
body) that uses abstrac
12 matches
Mail list logo
