Re: document literal stub problems
Bobby,
If you are using existing binaries to try out Axis C++, then you will have
problems. You should build new binaries from SVN and try again. I
believe VC++ project or ant can be used to build the new binaries.
Yes, we plan on releasing new binaries.some time.
Nadir Amra
Bobby Lawrence robe...@jlab.org wrote on 04/29/2009 04:31:33 PM:
[image removed]
document literal stub problems
Bobby Lawrence
to:
axis-c-user
04/29/2009 04:32 PM
Please respond to Apache AXIS C User List
Ok - I see a lot of people complaining about getting the C++ client
talking to an Axis Java service and running into serialization
issues (the server side complaining about unknown elements).
I am running into the same issue, but I think I know what the real
problem is.
First off, Axis requires that you call Stub.setOperation() or
nothing will exist in the Body of your SOAP envelope. Ok - that all
fine an dandy because you end up with an XML element with the name of
the
service in your SOAP body. Except that you still have to add your
parameter.
Well - parameters in document literal services don't get wrapped
within another element.
If you have a doc/lit service that has an operation called
echoString and the parameter type is an xsd:string, the
echoString element in the SOAP body is understood to contain the
string parameternot a separate element that contains the string
parameter.
When you add a parameter in the Stub (usually generated for you),
Axis C++ adds another element to the 'operation/method' element of
the SOAP body, so you end up with something like this (not exactly
because of other Stub generation issues discussed later):
ns1:echoString xmlns:ns1=http://some.namespace.org;
myStringParamsome string/myStringParam
/ns1:echoString
For a document/literal service, the SOAP body should look like this:
ns1:echoString xmlns:ns1=http://some.namespace.org;
some string
/ns1:echoString
At first I thought it had something to do with my generated Stub.
When I first used WSDLWs to generate my Stub, it ignored my
parameters completely.
This is because of a un-documented option to the tool -w (for
whether or not to generate wrapped types). Well - this option is
referenced in the Axis C++ webpage for the tool, but you can't use
the option because
of the code in the org.apache.axis.wsdl.wsdl2ws.WSDL2Ws Java tool.
if(clargparser.isSet(w) !wrapped.equalsIgnoreCase
(clargparser.getOptionBykey(w)))
{
usage();
return false;
}
Essentially, if you pass the -w option, anything except wrapped
will abort processing of the tool, even though nonwrapped is an
option.
I had to create my own WSDL2Ws tool to get around this issue, but it
doesn't solve the problem.
Even with the nonwrapped option, the method calls to the Stub have
the correct signature now, but the Stub still generates a wrapped
element with the addParameter method invocation on the Call.
I can't find a way around this. Maybe if I checked out the Axis C++
source code and modified it and built it myself.
Every other client I've created for this type of service works
except the Axis C++ client...
Also - the generated Stubs have a slight bug in them in that the
method checkFault on the Call object should take in the service's
namespace as the second parameter, but the generated code puts the
endpointURI in for this param.
I haven't gotten far enough to find out if this is an issue, but it
probably is...
Anyway - I just wanted to let folks know that this is probably a bug
in the Axis C++ Call object design.
There needs to be a way to add un-wrapped parameters to an operation
to support document/literal services.
--
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robe...@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
Re: document literal stub problems
Thanx Nadir.
I will checkout the code and try to build the binaries.
When is the next major release?
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robe...@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
Nadir Amra wrote:
Bobby,
If you are using existing binaries to try out Axis C++, then you will have
problems. You should build new binaries from SVN and try again. I
believe VC++ project or ant can be used to build the new binaries.
Yes, we plan on releasing new binaries.some time.
Nadir Amra
Bobby Lawrence robe...@jlab.org wrote on 04/29/2009 04:31:33 PM:
[image removed]
document literal stub problems
Bobby Lawrence
to:
axis-c-user
04/29/2009 04:32 PM
Please respond to Apache AXIS C User List
Ok - I see a lot of people complaining about getting the C++ client
talking to an Axis Java service and running into serialization
issues (the server side complaining about unknown elements).
I am running into the same issue, but I think I know what the real
problem is.
First off, Axis requires that you call Stub.setOperation() or
nothing will exist in the Body of your SOAP envelope. Ok - that all
fine an dandy because you end up with an XML element with the name of
the
service in your SOAP body. Except that you still have to add your
parameter.
Well - parameters in document literal services don't get wrapped
within another element.
If you have a doc/lit service that has an operation called
echoString and the parameter type is an xsd:string, the
echoString element in the SOAP body is understood to contain the
string parameternot a separate element that contains the string
parameter.
When you add a parameter in the Stub (usually generated for you),
Axis C++ adds another element to the 'operation/method' element of
the SOAP body, so you end up with something like this (not exactly
because of other Stub generation issues discussed later):
ns1:echoString xmlns:ns1=http://some.namespace.org;
myStringParamsome string/myStringParam
/ns1:echoString
For a document/literal service, the SOAP body should look like this:
ns1:echoString xmlns:ns1=http://some.namespace.org;
some string
/ns1:echoString
At first I thought it had something to do with my generated Stub.
When I first used WSDLWs to generate my Stub, it ignored my
parameters completely.
This is because of a un-documented option to the tool -w (for
whether or not to generate wrapped types). Well - this option is
referenced in the Axis C++ webpage for the tool, but you can't use
the option because
of the code in the org.apache.axis.wsdl.wsdl2ws.WSDL2Ws Java tool.
if(clargparser.isSet(w) !wrapped.equalsIgnoreCase
(clargparser.getOptionBykey(w)))
{
usage();
return false;
}
Essentially, if you pass the -w option, anything except wrapped
will abort processing of the tool, even though nonwrapped is an
option.
I had to create my own WSDL2Ws tool to get around this issue, but it
doesn't solve the problem.
Even with the nonwrapped option, the method calls to the Stub have
the correct signature now, but the Stub still generates a wrapped
element with the addParameter method invocation on the Call.
I can't find a way around this. Maybe if I checked out the Axis C++
source code and modified it and built it myself.
Every other client I've created for this type of service works
except the Axis C++ client...
Also - the generated Stubs have a slight bug in them in that the
method checkFault on the Call object should take in the service's
namespace as the second parameter, but the generated code puts the
endpointURI in for this param.
I haven't gotten far enough to find out if this is an issue, but it
probably is...
Anyway - I just wanted to let folks know that this is probably a bug
in the Axis C++ Call object design.
There needs to be a way to add un-wrapped parameters to an operation
to support document/literal services.
--
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robe...@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
Re: document literal stub problems
Bobby, good question. I have been stating that I plan to release version
1.6 for a while nowand have not done so due to lack of time.
However, it is on my list of things to do. Maybe by end of year (unless a
committer out there would like to volunteer to be release manager :-))
Nadir Amra
Bobby Lawrence robe...@jlab.org wrote on 04/29/2009 04:55:38 PM:
[image removed]
Re: document literal stub problems
Bobby Lawrence
to:
Apache AXIS C User List
04/29/2009 04:57 PM
Please respond to Apache AXIS C User List
Thanx Nadir.
I will checkout the code and try to build the binaries.
When is the next major release?
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robe...@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
Nadir Amra wrote:
Bobby,
If you are using existing binaries to try out Axis C++, then you will
have
problems. You should build new binaries from SVN and try again. I
believe VC++ project or ant can be used to build the new binaries.
Yes, we plan on releasing new binaries.some time.
Nadir Amra
Bobby Lawrence robe...@jlab.org wrote on 04/29/2009 04:31:33 PM:
[image removed]
document literal stub problems
Bobby Lawrence
to:
axis-c-user
04/29/2009 04:32 PM
Please respond to Apache AXIS C User List
Ok - I see a lot of people complaining about getting the C++ client
talking to an Axis Java service and running into serialization
issues (the server side complaining about unknown elements).
I am running into the same issue, but I think I know what the real
problem is.
First off, Axis requires that you call Stub.setOperation() or
nothing will exist in the Body of your SOAP envelope. Ok - that all
fine an dandy because you end up with an XML element with the name of
the
service in your SOAP body. Except that you still have to add your
parameter.
Well - parameters in document literal services don't get wrapped
within another element.
If you have a doc/lit service that has an operation called
echoString and the parameter type is an xsd:string, the
echoString element in the SOAP body is understood to contain the
string parameternot a separate element that contains the string
parameter.
When you add a parameter in the Stub (usually generated for you),
Axis C++ adds another element to the 'operation/method' element of
the SOAP body, so you end up with something like this (not exactly
because of other Stub generation issues discussed later):
ns1:echoString xmlns:ns1=http://some.namespace.org;
myStringParamsome string/myStringParam
/ns1:echoString
For a document/literal service, the SOAP body should look like this:
ns1:echoString xmlns:ns1=http://some.namespace.org;
some string
/ns1:echoString
At first I thought it had something to do with my generated Stub.
When I first used WSDLWs to generate my Stub, it ignored my
parameters completely.
This is because of a un-documented option to the tool -w (for
whether or not to generate wrapped types). Well - this option is
referenced in the Axis C++ webpage for the tool, but you can't use
the option because
of the code in the org.apache.axis.wsdl.wsdl2ws.WSDL2Ws Java tool.
if(clargparser.isSet(w) !wrapped.equalsIgnoreCase
(clargparser.getOptionBykey(w)))
{
usage();
return false;
}
Essentially, if you pass the -w option, anything except wrapped
will abort processing of the tool, even though nonwrapped is an
option.
I had to create my own WSDL2Ws tool to get around this issue, but it
doesn't solve the problem.
Even with the nonwrapped option, the method calls to the Stub have
the correct signature now, but the Stub still generates a wrapped
element with the addParameter method invocation on the Call.
I can't find a way around this. Maybe if I checked out the Axis C++
source code and modified it and built it myself.
Every other client I've created for this type of service works
except the Axis C++ client...
Also - the generated Stubs have a slight bug in them in that the
method checkFault on the Call object should take in the service's
namespace as the second parameter, but the generated code puts the
endpointURI in for this param.
I haven't gotten far enough to find out if this is an issue, but it
probably is...
Anyway - I just wanted to let folks know that this is probably a bug
in the Axis C++ Call object design.
There needs to be a way to add un-wrapped parameters to an operation
to support document/literal services.
--
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robe...@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
Re: document literal stub problems
Problem is, I'm not a big C++ developer.
I'm more Java, but I'm trying to build a simple service client executable...
Is there any other way to get a more recent binary?
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robe...@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
Nadir Amra wrote:
Bobby,
If you are using existing binaries to try out Axis C++, then you will have
problems. You should build new binaries from SVN and try again. I
believe VC++ project or ant can be used to build the new binaries.
Yes, we plan on releasing new binaries.some time.
Nadir Amra
Bobby Lawrence robe...@jlab.org wrote on 04/29/2009 04:31:33 PM:
[image removed]
document literal stub problems
Bobby Lawrence
to:
axis-c-user
04/29/2009 04:32 PM
Please respond to Apache AXIS C User List
Ok - I see a lot of people complaining about getting the C++ client
talking to an Axis Java service and running into serialization
issues (the server side complaining about unknown elements).
I am running into the same issue, but I think I know what the real
problem is.
First off, Axis requires that you call Stub.setOperation() or
nothing will exist in the Body of your SOAP envelope. Ok - that all
fine an dandy because you end up with an XML element with the name of
the
service in your SOAP body. Except that you still have to add your
parameter.
Well - parameters in document literal services don't get wrapped
within another element.
If you have a doc/lit service that has an operation called
echoString and the parameter type is an xsd:string, the
echoString element in the SOAP body is understood to contain the
string parameternot a separate element that contains the string
parameter.
When you add a parameter in the Stub (usually generated for you),
Axis C++ adds another element to the 'operation/method' element of
the SOAP body, so you end up with something like this (not exactly
because of other Stub generation issues discussed later):
ns1:echoString xmlns:ns1=http://some.namespace.org;
myStringParamsome string/myStringParam
/ns1:echoString
For a document/literal service, the SOAP body should look like this:
ns1:echoString xmlns:ns1=http://some.namespace.org;
some string
/ns1:echoString
At first I thought it had something to do with my generated Stub.
When I first used WSDLWs to generate my Stub, it ignored my
parameters completely.
This is because of a un-documented option to the tool -w (for
whether or not to generate wrapped types). Well - this option is
referenced in the Axis C++ webpage for the tool, but you can't use
the option because
of the code in the org.apache.axis.wsdl.wsdl2ws.WSDL2Ws Java tool.
if(clargparser.isSet(w) !wrapped.equalsIgnoreCase
(clargparser.getOptionBykey(w)))
{
usage();
return false;
}
Essentially, if you pass the -w option, anything except wrapped
will abort processing of the tool, even though nonwrapped is an
option.
I had to create my own WSDL2Ws tool to get around this issue, but it
doesn't solve the problem.
Even with the nonwrapped option, the method calls to the Stub have
the correct signature now, but the Stub still generates a wrapped
element with the addParameter method invocation on the Call.
I can't find a way around this. Maybe if I checked out the Axis C++
source code and modified it and built it myself.
Every other client I've created for this type of service works
except the Axis C++ client...
Also - the generated Stubs have a slight bug in them in that the
method checkFault on the Call object should take in the service's
namespace as the second parameter, but the generated code puts the
endpointURI in for this param.
I haven't gotten far enough to find out if this is an issue, but it
probably is...
Anyway - I just wanted to let folks know that this is probably a bug
in the Axis C++ Call object design.
There needs to be a way to add un-wrapped parameters to an operation
to support document/literal services.
--
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robe...@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
Re: Fault/Exception Handling on Axis2
On Sat, Apr 25, 2009 at 4:35 AM, John Eapen j1ea...@gmail.com wrote:
Hi ,
We are in the process of migrating from Axis1 to Axis2 and using Axis2
1.4.1. ( using adb )
I am having some trouble understanding the code generation regarding Fault
handling and mapping to Java Exceptions.
1. In Axis2, why are exceptions based of wsdl messages and not xsd elements
as was the case in axis1. ?
within the generated Exception class there is an ADBBean class corresponding
to the xsd element.
2. Is this an issue with wrapping/unwrapping of exceptions or something to
do with wsdl version (2.0 Vs 1.1) ?
I know, things are proabably better with WSDL 2.0 but we are still on
wsdl 1.1, since I am not sure about wsdl 2 adoption.
3. In Axis2, how does one create a exception class hierarchy. ( fault2
extends fault1 etc etc ...) since its based on messages.
In wsdl I think you can not extend a soap fault from another. Always fault
message refers to an xsd element.
But you can have extensions with complex types refer to the wsdl.
thanks,
Amila.
In my opinion, Axis1 was much better in this regard.
Appreciate any insight
Thanks
John
---
public example.WithdrawResponse withdraw(example.Withdraw param0)
throws InsufficientFundFaultMessage,
AccountNotExistFaultMessage
{
...
}
The WSDL sections are ..
wsdl:message name=InsufficientFundFaultMessage
wsdl:part element=tns:InsufficientFundFault name=fault/
/wsdl:message
wsdl:message name=AccountNotExistFaultMessage
wsdl:part element=tns:AccountNotExistFault name=fault/
/wsdl:message
element name=AccountNotExistFault
complexType
sequence
element name=account type=xsd:string/
/sequence
/complexType
/element
element name=InsufficientFundFault
complexType
sequence
element name=account type=xsd:string/
element name=balance type=xsd:int/
element name=requestedFund type=xsd:int/
/sequence
/complexType
/element
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
[Axis2] Stub creation fails.
Hi, I am trying to invoke the method on a stub generated using axis2 1.3. The method fails throwing the following: _operationClient.execute(*true*); The above line throws the follwoing exception: java.lang.NullPointerException at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:191) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) Thanks Ps
axis2 and jboss
Hi, I am using jboss-4.3 and axis-1.4.1. In our application we are using some webservice as client and to access that WS we are using axis-1.4.1. All things are working fine except logs. I need to print all request/response in my application in logs. I have added category name=org.apache.axis2 priority value=ALL/ /category In my log4j.xml. It is logging everything from axis2 but not request/response xmls. Let me know if something needs to be corrected. Thanks in advance. Regards, Prateek Jain Senior Software Engineer Tel. +91-124-3936144 | Mob. +91-9958646136 iSmart Panache (I) Solutions Pvt. Ltd. Plot No. 52, Sector 32, Institutional Area, Gurgaon 122001, Haryana www.ismartpanache.com http://www.ismartpanache.com/ http://www.ismartpanache.com/ - Expectations ::: causes all troubles -
How to auto instantiate ServiceClass after deploying
Hello, is there a way to instantiate the ServiceClass defined by service.xml right after the service is deployed? By default this class would be instantiated after the very first call of this webservice arrives. Regards, Martin
triggerActionNotSupportedFault -- The [action] cannot be processed at the receiver
Hello, I'm creating BPEL Workflow with Netbeans and Apache ODE (BPEL engine). Apache ODE is running with axis2 on Tomcat 5.5.27. I've deployed my Workflow and a Web Service wich is used by my workflow. I've tested my Web Service with SoapUI, and all it's OK. When I test my Workflow with SoapUI, I have a timeout error. And the Tomcat server throw the error : [WARN] triggerActionNotSupportedFault: messageContext: [MessageContext: logID=urn:uuid:9AEEEA7E64BAE6D4E31241008449207] problemAction: [ERROR] The [action] cannot be processed at the receiver. org.apache.axis2.AxisFault: The [action] cannot be processed at the receiver. at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:373) at org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionNotSupportedFault(AddressingFaultsHelper.java:336) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractActionInformation(AddressingInHandler.java:522) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:239) at org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:152) Do you need more details about the tomcat's error ? Do you know this problem ? how to solve it ? Thank you.
Re: [ANNOUNCE] Axis2 1.5 Release Candidate ready for testing
On Fri, Apr 17, 2009 at 2:05 AM, Glen Daniels g...@thoughtcraft.com wrote:
Thanks, Andreas. Martin, the test you refer to doesn't fail for me when I
build... are you seeing this error when doing a mvn clean install?
Incidentally, I'm in the midst of fixing the poms to include NOTICE and
LICENSE files in all the jars (thanks to Dan Kulp for pointing this out on
IM). Keith just let me know this morning that the WSO2 folks found an
issue
they'd like to fix as well, so pending those changes I'll roll out another
RC
hopefully by EOD tomorrow, then maybe get a VOTE started early next week.
I committed the changes which Keith has mentioned. And fixed some issues in
the distribution module.
I think we can put another RC shortly.
thanks,
Amila.
Thanks,
--Glen
Andreas Veithen wrote:
The code for the Version class in the codegen module is generated by
an invocation of the maven-antrun-plugin plugin during the
generate-test-sources phase. Please have a look at the pom.xml file.
Note that this class has nothing to do with the version service that
is part of the distribution.
Andreas
On Thu, Apr 16, 2009 at 13:39, Martin Gainty mgai...@hotmail.com
wrote:
Good Morning Glenn/Andreas
noting the version of Version.java from the distro located t
http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/distribution/1.5/http://people.apache.org/%7Egdaniels/stagingRepo/org/apache/axis2/distribution/1.5/
package sample.axisversion;
public class Version {
public String getVersion() throws Exception {
return Hi - the Axis2 version is +
org.apache.axis2.Version.getVersionText();
}
}
i see this error in /modules/codegen/target/surefire-reports/
TEST-org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.xml
testcase time=0.11
classname=org.apache.axis2.wsdl.codegen.XML2JavaMappingTest
name=testVersion
error message=sample.axisversion.xsd.Version
type=java.lang.ClassNotFoundExceptionjava.lang.ClassNotFoundException:
sample.axisversion.xsd.Version
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.testVersion(XML2JavaMappingTest.java:22)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
/error
/testcase
seems like the package sample.axisversion.xsd.Version
is not the actual java class version located at
sample.axisversion.Version
Martin
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung /
Note
de déni et de confidentialité
This message is confidential. If you should not be the intended
receiver,
then we ask politely to report. Each
How do I force axis2 to include a SOAPAction http header
I'm using axis2 1.4.1 and adb to call a .Net web service. I keep getting a response saying: System.Web.Services.Protocols.SoapException: Unable to handle request without a valid action parameter. Please supply a valid soap action. I enabled the wire.header logs and it is sending action in the Content-Type header, but it is not sending the SOAPAction header at all, not even as an empty string . I have tried setting options.setAction and options.setProperty( org.apache.axis2.Constants.Configuration.DISABLE_SOAP_ACTION, org.apache.axis2.Constants.VALUE_FALSE); but that hasn't helped. Any help would be greatly appreciated. Thanks, Chris Gunn Senior Programmer L-3 Communications
RE: How do I force axis2 to include a SOAPAction http header
I'm sort of new myself to SOAP and web services, but from what I've read you may want to investigate the differences between SOAP 1.1 and SOAP 1.2 and double check the SOAP version that your .NET services expects. One change between 1.1 and 1.2 is how the action header stuff is handled. Axis 2 is probably doing the right thing given the SOAP version you're using. Mark -Original Message- From: christopher.g...@l-3com.com [mailto:christopher.g...@l-3com.com] Sent: Wednesday, April 29, 2009 9:33 AM To: axis-user@ws.apache.org Subject: How do I force axis2 to include a SOAPAction http header I'm using axis2 1.4.1 and adb to call a .Net web service. I keep getting a response saying: System.Web.Services.Protocols.SoapException: Unable to handle request without a valid action parameter. Please supply a valid soap action. I enabled the wire.header logs and it is sending action in the Content-Type header, but it is not sending the SOAPAction header at all, not even as an empty string . I have tried setting options.setAction and options.setProperty( org.apache.axis2.Constants.Configuration.DISABLE_SOAP_ACTION, org.apache.axis2.Constants.VALUE_FALSE); but that hasn't helped. Any help would be greatly appreciated. Thanks, Chris Gunn Senior Programmer L-3 Communications
RE: How do I force axis2 to include a SOAPAction http header
In that case, how do I force axis2 to choose SOAP 1.1 so that it will send the SOAPAction header? Thanks, Chris Gunn Senior Programmer L-3 Communications -Original Message- From: Salisbury, Mark [mailto:mark.salisb...@hp.com] Sent: Wednesday, April 29, 2009 11:42 AM To: axis-user@ws.apache.org Subject: RE: How do I force axis2 to include a SOAPAction http header I'm sort of new myself to SOAP and web services, but from what I've read you may want to investigate the differences between SOAP 1.1 and SOAP 1.2 and double check the SOAP version that your .NET services expects. One change between 1.1 and 1.2 is how the action header stuff is handled. Axis 2 is probably doing the right thing given the SOAP version you're using. Mark -Original Message- From: christopher.g...@l-3com.com [mailto:christopher.g...@l-3com.com] Sent: Wednesday, April 29, 2009 9:33 AM To: axis-user@ws.apache.org Subject: How do I force axis2 to include a SOAPAction http header I'm using axis2 1.4.1 and adb to call a .Net web service. I keep getting a response saying: System.Web.Services.Protocols.SoapException: Unable to handle request without a valid action parameter. Please supply a valid soap action. I enabled the wire.header logs and it is sending action in the Content-Type header, but it is not sending the SOAPAction header at all, not even as an empty string . I have tried setting options.setAction and options.setProperty( org.apache.axis2.Constants.Configuration.DISABLE_SOAP_ACTION, org.apache.axis2.Constants.VALUE_FALSE); but that hasn't helped. Any help would be greatly appreciated. Thanks, Chris Gunn Senior Programmer L-3 Communications
Re: How do I force axis2 to include a SOAPAction http header
For soap 1.1: serviceClient.getOptions().setSoapVersionURI(org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI); For soap 1.2: serviceClient.getOptions().setSoapVersionURI(org.apache.axiom.soap.SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI); christopher.g...@l-3com.com wrote: In that case, how do I force axis2 to choose SOAP 1.1 so that it will send the SOAPAction header? Thanks, Chris Gunn Senior Programmer L-3 Communications -Original Message- From: Salisbury, Mark [mailto:mark.salisb...@hp.com] Sent: Wednesday, April 29, 2009 11:42 AM To: axis-user@ws.apache.org Subject: RE: How do I force axis2 to include a SOAPAction http header I'm sort of new myself to SOAP and web services, but from what I've read you may want to investigate the differences between SOAP 1.1 and SOAP 1.2 and double check the SOAP version that your .NET services expects. One change between 1.1 and 1.2 is how the action header stuff is handled. Axis 2 is probably doing the right thing given the SOAP version you're using. Mark -Original Message- From: christopher.g...@l-3com.com [mailto:christopher.g...@l-3com.com] Sent: Wednesday, April 29, 2009 9:33 AM To: axis-user@ws.apache.org Subject: How do I force axis2 to include a SOAPAction http header I'm using axis2 1.4.1 and adb to call a .Net web service. I keep getting a response saying: System.Web.Services.Protocols.SoapException: Unable to handle request without a valid action parameter. Please supply a valid soap action. I enabled the wire.header logs and it is sending action in the Content-Type header, but it is not sending the SOAPAction header at all, not even as an empty string . I have tried setting options.setAction and options.setProperty( org.apache.axis2.Constants.Configuration.DISABLE_SOAP_ACTION, org.apache.axis2.Constants.VALUE_FALSE); but that hasn't helped. Any help would be greatly appreciated. Thanks, Chris Gunn Senior Programmer L-3 Communications
Re: Fw: [Axis2] single wsdl, multiple operations -- tomcat running out of thread
After enabling logging for http client, I can see the connection getting
released back to the pool:
2009-04-29 14:28:19,729 DEBUG [org.apache.commons.httpclient.HttpConnection] -
enter HttpConnection.getRequestOutputStream()
2009-04-29 14:28:19,729 DEBUG [org.apache.commons.httpclient.HttpConnection] -
enter HttpConnection.getRequestOutputStream()
2009-04-29 14:28:19,776 DEBUG [httpclient.wire.content] - d1e[\r][\n]
2009-04-29 14:28:19,776 DEBUG [httpclient.wire.content] - ?xml
version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://ws.xxx.com;[\n]
2009-04-29 14:28:19,885 DEBUG [httpclient.wire.content] - [\n]
2009-04-29 14:28:19,885 DEBUG [httpclient.wire.content] -
/soapenv:Body/soapenv:Envelope
2009-04-29 14:28:20,010 DEBUG [httpclient.wire.content] - [\r]
2009-04-29 14:28:20,010 DEBUG [httpclient.wire.content] - [\n]
2009-04-29 14:28:20,010 DEBUG [httpclient.wire.content] - 0
2009-04-29 14:28:20,010 DEBUG [httpclient.wire.content] - [\r]
2009-04-29 14:28:20,010 DEBUG [httpclient.wire.content] - [\n]
2009-04-29 14:28:20,010 DEBUG [org.apache.commons.httpclient.HttpConnection] -
enter HttpConnection.isResponseAvailable()
2009-04-29 14:28:20,010 DEBUG [org.apache.commons.httpclient.HttpConnection] -
enter HttpConnection.releaseConnection()
2009-04-29 14:28:20,010 DEBUG [org.apache.commons.httpclient.HttpConnection] -
Releasing connection back to connection manager.
--- On Tue, 4/28/09, jshr...@yahoo.com wrote:
Subject: Fw: [Axis2] single wsdl, multiple operations -- tomcat running out of
thread
To: axis-user@ws.apache.org
Date: Tuesday, April 28, 2009, 4:34 PM
--- On Tue, 4/28/09, Jay jshr...@yahoo.com wrote:
From: Jayashree Krishnamoorthy jshr...@yahoo.com
Subject: [Axis2] single wsdl, multiple operations -- tomcat running out of
thread
To: axis-user@ws.apache.org
Date: Tuesday, April 28, 2009, 4:05 PM
Hi
I have 2 operations in a single wsdl and the client code is as follows:
this.port = new HelloWorldStub();
ServiceClient serviceClient = port._getServiceClient();
Options options = serviceClient.getOptions();
if ( this.url != null )
{
EndpointReference epr = new EndpointReference( this.url );
options.setTo( epr );
}
options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);
public sayHello1()
{
port.sayHello1();
}
public sayHello2()
{
port.sayHello2();
}
During load test, Address_Already_Bound error was getting thrown. So the
Reuse Option was set. However now, the tomcat runs of thread and the thread
dump has the following message:
http-80-Processor36 prio=5 tid=63 WAITING
at java.lang.Object.wait(Native Method)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:509)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:394)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:176)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:305)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
at com.xxx.hello.HelloServiceStub.changePassword(HelloServiceStub.java:288)
I am really clueless about what the issue is. Read through different forums
and link and got confused. Greatly appreciate help and this issue is
happening in production.
:-((
Product Stack: Axis2 1.3, Tomcat 5.5, Java 5
Thanks in advance
Jay
maven build error Plugin's descriptor contains the wrong version: SNAPSHOT
Hello, I'm unable to build Axis 2 java from source. I downloaded SVN version 768341 from http://svn.apache.org/repos/asf/webservices/axis2/trunk. Then I followed instructions on the install guide (http://ws.apache.org/axis2/1_4_1/installationguide.html), and installed Maven from http://maven.apache.org/download.html. Any suggestions on why I might be seeing this error are appreciated. Mark Here's my build log: D:\yoda\axis2\javamvn install [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Axis2 - Parent [INFO] Apache Axis2 - Kernel [INFO] Apache Axis2 - Data Binding [INFO] Apache Axis2 - Transport - Local [INFO] Apache Axis2 - Transport - HTTP [INFO] Apache Axis2 - Code Generation [INFO] Apache Axis2 - ADB Codegen [INFO] Apache Axis2 - tool - MAR Maven Plugin [INFO] Apache Axis2 - Addressing [INFO] Apache Axis2 - Java2WSDL [INFO] Apache Axis2 - Fast Infoset [INFO] Apache Axis2 - Clustering [INFO] Apache Axis2 - Scripting [INFO] Apache Axis2 - JAXB-RI Data Binding [INFO] Apache Axis2 - SAAJ [INFO] Apache Axis2 - Metadata [INFO] Apache Axis2 - JAXWS [INFO] Apache Axis2 - JAXWS Integration Tests [INFO] Apache Axis2 - JiBX Data Binding [INFO] Apache Axis2 - JSON [INFO] Apache Axis2 - MTOM Policy [INFO] Apache Axis2 - spring [INFO] Apache Axis2 - OSGi Integration [INFO] Apache Axis2 - XMLBeans Data Binding [INFO] Apache Axis2 - Integration [INFO] Apache Axis2 - MEX [INFO] Apache Axis2 - MTOM Policy module [INFO] Apache Axis2 - Ping [INFO] Apache Axis2 - tool - AAR Maven Plugin [INFO] Apache Axis2 - Version Service [INFO] Apache Axis2 - SOAP Monitor [INFO] Apache Axis2 - tool - Ant Plugin [INFO] Apache Axis2 - Root [INFO] Apache Axis2 - tool - Eclipse Codegen Plugin [INFO] Apache Axis2 - tool - Eclipse service Plugin [INFO] Apache Axis2 - tool - Intellij IDEA Plugin [INFO] Apache Axis2 - tool - Java2WSDL Maven Plugin [INFO] Apache Axis2 - tool - WSDL2Code Maven Plugin [INFO] Apache Axis2 - CORBA [INFO] Apache Axis2 - JAXWS (mar) [INFO] Apache Axis2 - Web Application module [INFO] Apache Axis2 - Samples Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:pom:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom 4K downloaded (maven-bundle-plugin-1.4.0.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom [INFO] Unable to find resource 'org.apache.felix:felix:pom:1.0.2' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom 13K downloaded (felix-1.0.2.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:maven-plugin:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar 134K downloaded (maven-bundle-plugin-1.4.0.jar) [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from ws-zones Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-mar-maven-plugin/SNAPSHOT/axis2-mar-maven-plugin-20090424.213913-2417.jar 17K downloaded (axis2-mar-maven-plugin-20090424.213913-2417.jar) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager getting plugin 'org.apache.axis2:axis2-mar-maven-plugin': Plugin 'org.apache.axis2:axis2-mar-maven-plugin:20090424.213913-2417' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: SNAPSHOT [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Fri Apr 24 16:01:11 MDT 2009 [INFO] Final Memory: 9M/16M [INFO] D:\yoda\axis2\javamvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Axis2 - Parent [INFO] Apache Axis2 - Kernel [INFO] Apache Axis2 - Data Binding [INFO] Apache Axis2 - Transport - Local [INFO] Apache Axis2 - Transport - HTTP [INFO] Apache
Re: maven build error Plugin's descriptor contains the wrong version: SNAPSHOT
Hi Mark, Before you build the top level Axis2 project move to following two modules and try to build them first , after that you can build the Axis2 project with Maven. Hope this will work. 1. axis2-aar-maven-plugin 2. axis2-mar-maven-plugin Thanks, On Thu, Apr 30, 2009 at 12:34 AM, Salisbury, Mark mark.salisb...@hp.com wrote: Hello, I’m unable to build Axis 2 java from source. I downloaded SVN version 768341 from http://svn.apache.org/repos/asf/webservices/axis2/trunk. Then I followed instructions on the install guide (http://ws.apache.org/axis2/1_4_1/installationguide.html), and installed Maven from http://maven.apache.org/download.html. Any suggestions on why I might be seeing this error are appreciated. Mark Here’s my build log: D:\yoda\axis2\javamvn install [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Axis2 - Parent [INFO] Apache Axis2 - Kernel [INFO] Apache Axis2 - Data Binding [INFO] Apache Axis2 - Transport - Local [INFO] Apache Axis2 - Transport - HTTP [INFO] Apache Axis2 - Code Generation [INFO] Apache Axis2 - ADB Codegen [INFO] Apache Axis2 - tool - MAR Maven Plugin [INFO] Apache Axis2 - Addressing [INFO] Apache Axis2 - Java2WSDL [INFO] Apache Axis2 - Fast Infoset [INFO] Apache Axis2 - Clustering [INFO] Apache Axis2 - Scripting [INFO] Apache Axis2 - JAXB-RI Data Binding [INFO] Apache Axis2 - SAAJ [INFO] Apache Axis2 - Metadata [INFO] Apache Axis2 - JAXWS [INFO] Apache Axis2 - JAXWS Integration Tests [INFO] Apache Axis2 - JiBX Data Binding [INFO] Apache Axis2 - JSON [INFO] Apache Axis2 - MTOM Policy [INFO] Apache Axis2 - spring [INFO] Apache Axis2 - OSGi Integration [INFO] Apache Axis2 - XMLBeans Data Binding [INFO] Apache Axis2 - Integration [INFO] Apache Axis2 - MEX [INFO] Apache Axis2 - MTOM Policy module [INFO] Apache Axis2 - Ping [INFO] Apache Axis2 - tool - AAR Maven Plugin [INFO] Apache Axis2 - Version Service [INFO] Apache Axis2 - SOAP Monitor [INFO] Apache Axis2 - tool - Ant Plugin [INFO] Apache Axis2 - Root [INFO] Apache Axis2 - tool - Eclipse Codegen Plugin [INFO] Apache Axis2 - tool - Eclipse service Plugin [INFO] Apache Axis2 - tool - Intellij IDEA Plugin [INFO] Apache Axis2 - tool - Java2WSDL Maven Plugin [INFO] Apache Axis2 - tool - WSDL2Code Maven Plugin [INFO] Apache Axis2 - CORBA [INFO] Apache Axis2 - JAXWS (mar) [INFO] Apache Axis2 - Web Application module [INFO] Apache Axis2 - Samples Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:pom:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom 4K downloaded (maven-bundle-plugin-1.4.0.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom [INFO] Unable to find resource 'org.apache.felix:felix:pom:1.0.2' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom 13K downloaded (felix-1.0.2.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:maven-plugin:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar 134K downloaded (maven-bundle-plugin-1.4.0.jar) [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from ws-zones Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-mar-maven-plugin/SNAPSHOT/axis2-mar-maven-plugin-20090424.213913-2417.jar 17K downloaded (axis2-mar-maven-plugin-20090424.213913-2417.jar) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager getting plugin 'org.apache.axis2:axis2-mar-maven-plugin': Plugin 'org.apache.axis2:axis2-mar-maven-plugin:20090424.213913-2417' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: SNAPSHOT [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total
RE: maven build error Plugin's descriptor contains the wrong version: SNAPSHOT
Thanks, I actually tried that (I saw a post on another thread that suggested building those modules first). I still got the same error after a successful mvn install of those modules. Mark -Original Message- From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: Wednesday, April 29, 2009 2:07 PM To: axis-user@ws.apache.org Subject: Re: maven build error Plugin's descriptor contains the wrong version: SNAPSHOT Hi Mark, Before you build the top level Axis2 project move to following two modules and try to build them first , after that you can build the Axis2 project with Maven. Hope this will work. 1. axis2-aar-maven-plugin 2. axis2-mar-maven-plugin Thanks, On Thu, Apr 30, 2009 at 12:34 AM, Salisbury, Mark mark.salisb...@hp.com wrote: Hello, I’m unable to build Axis 2 java from source. I downloaded SVN version 768341 from http://svn.apache.org/repos/asf/webservices/axis2/trunk. Then I followed instructions on the install guide (http://ws.apache.org/axis2/1_4_1/installationguide.html), and installed Maven from http://maven.apache.org/download.html. Any suggestions on why I might be seeing this error are appreciated. Mark Here’s my build log: D:\yoda\axis2\javamvn install [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Axis2 - Parent [INFO] Apache Axis2 - Kernel [INFO] Apache Axis2 - Data Binding [INFO] Apache Axis2 - Transport - Local [INFO] Apache Axis2 - Transport - HTTP [INFO] Apache Axis2 - Code Generation [INFO] Apache Axis2 - ADB Codegen [INFO] Apache Axis2 - tool - MAR Maven Plugin [INFO] Apache Axis2 - Addressing [INFO] Apache Axis2 - Java2WSDL [INFO] Apache Axis2 - Fast Infoset [INFO] Apache Axis2 - Clustering [INFO] Apache Axis2 - Scripting [INFO] Apache Axis2 - JAXB-RI Data Binding [INFO] Apache Axis2 - SAAJ [INFO] Apache Axis2 - Metadata [INFO] Apache Axis2 - JAXWS [INFO] Apache Axis2 - JAXWS Integration Tests [INFO] Apache Axis2 - JiBX Data Binding [INFO] Apache Axis2 - JSON [INFO] Apache Axis2 - MTOM Policy [INFO] Apache Axis2 - spring [INFO] Apache Axis2 - OSGi Integration [INFO] Apache Axis2 - XMLBeans Data Binding [INFO] Apache Axis2 - Integration [INFO] Apache Axis2 - MEX [INFO] Apache Axis2 - MTOM Policy module [INFO] Apache Axis2 - Ping [INFO] Apache Axis2 - tool - AAR Maven Plugin [INFO] Apache Axis2 - Version Service [INFO] Apache Axis2 - SOAP Monitor [INFO] Apache Axis2 - tool - Ant Plugin [INFO] Apache Axis2 - Root [INFO] Apache Axis2 - tool - Eclipse Codegen Plugin [INFO] Apache Axis2 - tool - Eclipse service Plugin [INFO] Apache Axis2 - tool - Intellij IDEA Plugin [INFO] Apache Axis2 - tool - Java2WSDL Maven Plugin [INFO] Apache Axis2 - tool - WSDL2Code Maven Plugin [INFO] Apache Axis2 - CORBA [INFO] Apache Axis2 - JAXWS (mar) [INFO] Apache Axis2 - Web Application module [INFO] Apache Axis2 - Samples Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:pom:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom 4K downloaded (maven-bundle-plugin-1.4.0.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom [INFO] Unable to find resource 'org.apache.felix:felix:pom:1.0.2' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom 13K downloaded (felix-1.0.2.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:maven-plugin:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar 134K downloaded (maven-bundle-plugin-1.4.0.jar) [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from ws-zones Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-mar-maven-plugin/SNAPSHOT/axis2-mar-maven-plugin-20090424.213913-2417.jar 17K downloaded (axis2-mar-maven-plugin-20090424.213913-2417.jar) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager getting plugin
Re: maven build error Plugin's descriptor contains the wrong version: SNAPSHOT
A recent post on this list indicated that this is a problem specific to Maven 2.1.x. Axis2 builds fine with Maven 2.0.x. Note that the plugin Maven is complaining about is built using maven-plugin-plugin. Therefore I believe this is a problem with Maven itself, not Axis2. Andreas On Wed, Apr 29, 2009 at 22:31, Salisbury, Mark mark.salisb...@hp.com wrote: Thanks, I actually tried that (I saw a post on another thread that suggested building those modules first). I still got the same error after a successful mvn install of those modules. Mark -Original Message- From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: Wednesday, April 29, 2009 2:07 PM To: axis-user@ws.apache.org Subject: Re: maven build error Plugin's descriptor contains the wrong version: SNAPSHOT Hi Mark, Before you build the top level Axis2 project move to following two modules and try to build them first , after that you can build the Axis2 project with Maven. Hope this will work. 1. axis2-aar-maven-plugin 2. axis2-mar-maven-plugin Thanks, On Thu, Apr 30, 2009 at 12:34 AM, Salisbury, Mark mark.salisb...@hp.com wrote: Hello, I’m unable to build Axis 2 java from source. I downloaded SVN version 768341 from http://svn.apache.org/repos/asf/webservices/axis2/trunk. Then I followed instructions on the install guide (http://ws.apache.org/axis2/1_4_1/installationguide.html), and installed Maven from http://maven.apache.org/download.html. Any suggestions on why I might be seeing this error are appreciated. Mark Here’s my build log: D:\yoda\axis2\javamvn install [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Axis2 - Parent [INFO] Apache Axis2 - Kernel [INFO] Apache Axis2 - Data Binding [INFO] Apache Axis2 - Transport - Local [INFO] Apache Axis2 - Transport - HTTP [INFO] Apache Axis2 - Code Generation [INFO] Apache Axis2 - ADB Codegen [INFO] Apache Axis2 - tool - MAR Maven Plugin [INFO] Apache Axis2 - Addressing [INFO] Apache Axis2 - Java2WSDL [INFO] Apache Axis2 - Fast Infoset [INFO] Apache Axis2 - Clustering [INFO] Apache Axis2 - Scripting [INFO] Apache Axis2 - JAXB-RI Data Binding [INFO] Apache Axis2 - SAAJ [INFO] Apache Axis2 - Metadata [INFO] Apache Axis2 - JAXWS [INFO] Apache Axis2 - JAXWS Integration Tests [INFO] Apache Axis2 - JiBX Data Binding [INFO] Apache Axis2 - JSON [INFO] Apache Axis2 - MTOM Policy [INFO] Apache Axis2 - spring [INFO] Apache Axis2 - OSGi Integration [INFO] Apache Axis2 - XMLBeans Data Binding [INFO] Apache Axis2 - Integration [INFO] Apache Axis2 - MEX [INFO] Apache Axis2 - MTOM Policy module [INFO] Apache Axis2 - Ping [INFO] Apache Axis2 - tool - AAR Maven Plugin [INFO] Apache Axis2 - Version Service [INFO] Apache Axis2 - SOAP Monitor [INFO] Apache Axis2 - tool - Ant Plugin [INFO] Apache Axis2 - Root [INFO] Apache Axis2 - tool - Eclipse Codegen Plugin [INFO] Apache Axis2 - tool - Eclipse service Plugin [INFO] Apache Axis2 - tool - Intellij IDEA Plugin [INFO] Apache Axis2 - tool - Java2WSDL Maven Plugin [INFO] Apache Axis2 - tool - WSDL2Code Maven Plugin [INFO] Apache Axis2 - CORBA [INFO] Apache Axis2 - JAXWS (mar) [INFO] Apache Axis2 - Web Application module [INFO] Apache Axis2 - Samples Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:pom:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.pom 4K downloaded (maven-bundle-plugin-1.4.0.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom [INFO] Unable to find resource 'org.apache.felix:felix:pom:1.0.2' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/felix/1.0.2/felix-1.0.2.pom 13K downloaded (felix-1.0.2.pom) Downloading: http://ws.zones.apache.org/repository2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar [INFO] Unable to find resource 'org.apache.felix:maven-bundle-plugin:maven-plugin:1.4.0' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/felix/maven-bundle-plugin/1.4.0/maven-bundle-plugin-1.4.0.jar 134K downloaded (maven-bundle-plugin-1.4.0.jar) [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.axis2:axis2-mar-maven-plugin:SNAPSHOT: checking for updates from ws-zones Downloading:
Xmlbeans unwrapped code generation
Currently unwrapped xml code generation fails to compile. I believe this is a known issue. Are there any news about when this is going to be fixed? Bosko
