I have a WSDL that I made to generate the server-side skeletons. Is
there somewhere in my WAR/services.xml that I need to put it and
reference to it to force Axis2 to use mine?
On May 2, 2008, at 11:20 AM, robert lazarski wrote:
I'm the wrong person to help on POJO issues. However, you ha
I'm the wrong person to help on POJO issues. However, you have full
control of the types by writing your own WSDL and XML schema via the
"contract first" style of development. Alternatively, use java2wsdl
and "code first" which may give you better results for your needs.
HTH,
Robert
On Fri, May
Also, I just noticed you are using
SpringAppContextAwareObjectSupplier. When connecting axis2 via a
spring instance loaded from the servlet container, use
SpringServletContextObjectSupplier . Try that and let us know if you
still have problems.
On Fri, May 2, 2008 at 12:09 PM, robert lazarski
<[EM
Disregard the last email. It was my lack of reading the fine-print
that caught me there.
I am still having another issue, however. The entire reason I went
through the process of defining the service by the WSDL was because
when I deployed the POJO it made all the types "anyType". This w
Read the springframework docs. Axis2 is not responsible for loading
spring, and services.xml is an axis2 file. All services.xml does is
connect axis2 to an already loaded spring. The easiest way to load
spring, as shown in http://ws.apache.org/axis2/1_4/spring.html , is to
put in the web.xml a few
am pretty sure I am using Axis2 version 1.4. I was using Axis2
version 1.3, but upgraded to 1.4 to see if the latest build fixed the
problem. My pom.xml can confirm:
org.apache.axis2
axis2-jws-api
1.4
Well you seem to have a lot of problems! Let me try and help you with
the spring stuff...
The error you point to is an advanced use case, and while I'm
confident it works because I tested it, I suggest you try something
simpler. The link you point to, while old, never the less tries to
init spring
Axis2 1.4? r u sure? If you use the now unsupported Axis 1.4 it should generate
wsdl1.1 (rpc/encoded). You in all-likelihood will not get any Axis2 guru
support on using Axis 1.4. I have had this problem myself at one time. The
difference between rpc/encoded and document/literal is a major diffe
am getting really desperate for help here. Its possible that my
emails are not making it to the group, but I hope someone can get me
pointed in the right direction.
I am trying to deploy a WS in Axis2 that was created using
wsdl2java.sh. I took the generated files, extended the Skeleton,
I am getting really desperate for help here. Its possible that my
emails are not making it to the group, but I hope someone can get me
pointed in the right direction.
I am trying to deploy a WS in Axis2 that was created using
wsdl2java.sh. I took the generated files, extended the Skeleton
10 matches
Mail list logo
