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:
                <dependency>
                        <groupId>org.apache.axis2</groupId>
                        <artifactId>axis2-jws-api</artifactId>
                        <version>1.4</version>
                </dependency>
                <dependency>
                        <groupId>org.apache.axis2</groupId>
                        <artifactId>axis2-spring</artifactId>
                        <version>1.4</version>
                </dependency>
                <dependency>
                        <groupId>org.apache.axis2</groupId>
                        <artifactId>axis2</artifactId>
                        <version>1.4</version>
                </dependency>

I tried to send a screenshot of the WAR WEB-INF/lib contents, but it got bounced back due to size.

I am definitely trying to steer clear of the old Axis for the primary reason that its not really supported any longer, plus Axis2 is supposedly much faster. The requirement to have WSDL 1.1 is because apparently thats all FlexBuilder supports, and since this is my target client, I have to cater to it. Originally I was trying to use the Adobe BlazeDS messaging instead of Axis2 web services, but that didn't work either. At this point I am just grabbing for straws in hopes I can get something to work.
On May 2, 2008, at 9:39 AM, David Brown wrote:

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 difference. Go back to Apache Axis and look specifically at: http://www.apache.org/dyn/closer.cgi/ws/axis/ 1_4. Also, see: http://www.ws-i.org/. HTH.

Michael Bauer wrote ..
 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, and
modified the services.xml to grab the Impl class from Spring.

The end-goal is to have a web service that I can import using
FlexBuilder 3's WS import function.  When I kicked off the process,
however, FlexBuilder complained that the WSDL 2.0 file produced was
not a valid WSDL.  Further digging showed that FlexBuilder doesn't
seem to support WSDL 2.0, so I tried to follow the recommendation of
the WSDL 1.1 page and set the useOriginalwsdl to false (it was set to
true).  However, doing so leaves a nasty stack trace:

08:58:43,038 ERROR [STDERR]
org.apache.axis2.deployment.DeploymentException: The following error
occurred during schema generation: null
08:58:43,039 ERROR [STDERR]     at
org
.apache
.axis2
.deployment
.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java: 106)
08:58:43,039 ERROR [STDERR]     at
org
.apache
.axis2
.deployment
.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java: 110)
08:58:43,039 ERROR [STDERR]     at
org
.apache
.axis2
.deployment
.repository .util.ArchiveReader.processServiceGroup(ArchiveReader.java:
179)
08:58:43,039 ERROR [STDERR]     at
org
.apache .axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:81)
08:58:43,039 ERROR [STDERR]     at
org
.apache
.axis2
.deployment
.repository.util.DeploymentFileData.deploy(DeploymentFileData.java: 136)
     ...


Whats interesting is further below in the stack trace:
     ...
08:58:43,081 ERROR [STDERR] Caused by: org.apache.axis2.AxisFault:
Axis2 Can't find Spring's ApplicationContext
08:58:43,081 ERROR [STDERR]     at
org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
08:58:43,081 ERROR [STDERR]     at
org
.apache
.axis2
.extensions
.spring
.receivers
.SpringAppContextAwareObjectSupplier
.getServiceObject(SpringAppContextAwareObjectSupplier.java:63)
08:58:43,081 ERROR [STDERR]     ... 159 more

Through some research on Google, I found an article suggesting this
was a coding problem in Axis2:  http://www.mail-archive.com/[EMAIL 
PROTECTED]/msg23055.html

It says its been resolved, but I just updated my maven2 POMs to pull
Axis2 1.4 (was using Axis2 1.3), and I still get the same problem.  I
even removed all the 1.3 generated files and re-generated them all
using Axis2 1.4 version of wsdl2java.sh.  I am not quite sure I
understand the bug report fully, nor how to fix it.

I could really use some assistance here.



Michael Bauer
[EMAIL PROTECTED]
http://www.codechimp.net
Yet some, not wise, go to the other side of the globe, to barbarous and unhealthy regions, and devote ten or twenty years, in that they may live,-that is, keep comfortably warm,- and die in New England at last.

Henry David Thoreau - Walden - 1845


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Michael Bauer
[EMAIL PROTECTED]
http://www.codechimp.net





Reply via email to