Re: Inaccessible WSDL files after enabling both HTTP and HTTPS in Axis2/Tomcat
Michael, This looks like another example of the issue described in AXIS2-4465. Not sure if it is possible to make this work properly in 1.5.1, but in the current trunk the configuration mechanism to enable HTTP and HTTPS in a servlet environment is much more transparent (and known to work properly). Andreas [1] http://people.apache.org/~veithen/axis2/1_6/servlet-transport.html On Mon, Feb 8, 2010 at 14:10, Doughty, Michael michael_doug...@bmc.com wrote: I have a problem that I am hoping someone could shed some light on. I have enabled both HTTP and one-way HTTPS in my Tomcat 6 instance. Likewise, I have added the correct configuration information to my axis2.xml in the war distribution of Axis2 1.5.1. The HTTP port is 8080 and the HTTPS port is 8443. They are running on a 1.5 JRE. Doing so seems to work ok. The Web services are all accessible at both the HTTP and HTTPS endpoints, so there seems to be no real issue there. However, the WSDL and XSD files are inaccessible. The same endpoints that allow SOAP requests no longer allow any of these “GET” requests to access WSDL and XSD files: “?wsdl”, “?wsdl=somefile.wsdl”, “?xsd=somefile.xsd”. In all cases, I get the message “Internal server error”. This happens whether or not I use the HTTP or HTTPS endpoints to access them. Note that I can still access these files directly by simply adding “/somefile.wsdl” to the end of the endpoint, but this is undesirable in the case of the main WSDL of the service as the service endpoints are not replaced properly. Note that this happens whether or not I explicitly declare the available transports in services.xml for the services in question. I found a FAQ somewhere that said I needed to make sure that xalan-2.7.0.jar was copied into the lib directory of the war distribution, but that file is already there. Is there something else I need to do here to make this work? Or is this a known issue that cannot be worked around at this time?
Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1
On Tue, Feb 2, 2010 at 10:06, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Andreas, Summary: Builds using MAVEN 2.2.1 Source Code used, Cmd window NetBeans IDE 6.8 Maven Flags downloaded by SVN Tortoise Maven 2.2.1 external Maven 2.2.1 Ant 1.7.0 external Ant 1.7.0 C:\asf\webservices\axis2\tags\java\v1.5.1 fails fails -Dmave.test.skip=true C:\asf\webservices\axis2\tags\java\v1.5.1 success success .NA. C:\asf\webservices\axis2\trunk\java success success -Dmave.test.skip=true C:\asf\webservices\axis2\trunk\java success success .NA. Builds using MAVEN 3.0-SNAPSHOT AXIS2 is not yet maven 3.0-Snapshot ready! If you have NetBeans IDE 6.8 with the internal or external maven 3.0-snapshot then you are unable to open the axis2 root POM correctly. However one is still able to build some off the axis2 components/artifacts correctly. In short AXIS2 Trunk sources and earlier are not yet ready for MAVEN 3.0-SNAPSHOT! Josef Maven 3.0 (alpha-6) actually works surprisingly well on the Axis2 build. There are only two issues: - A duplicate dependency declaration in the integration module; this is now fixed. - The root POM has an antrun execution that depends on the output of several of its sub-modules by directly accessing modules/xxx/target/classes, but no provisions are made to make sure that these modules are built before the antrun execution. Depending on the output of other modules in that way is bad practice, and leads to unstable/unpredictable build. With Maven 2.0 the build order is such that it works correctly, but this is probably more a coincidence. We will probably have to use some maven-assembly-plugin magic to do this correctly and to make the build order predictable. Andreas
Re: Axis2 JAX-WS: The service class cannot be found for this AxisService
Note that the portName=HelloPort in your implementation class is not
consistent with the WSDL you posted earlier. This should be
helloPort. Maybe that could be the reason. BTW, what do the logs
say?
Andreas
On Mon, Feb 1, 2010 at 23:37, Daniel Walsh walsh94...@gmail.com wrote:
Andreas:
The annotations generated by wsimport are:
HelloService:
@WebServiceClient(name = HelloService, targetNamespace = com/wb/hello,
wsdlLocation = file:/C:/axis2-1.5.1/hello2/service/hello.wsdl)
HelloPortType:
@WebService(name = helloPortType, targetNamespace = com/wb/hello)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@XmlSeeAlso({
ObjectFactory.class
})
HelloPort:
@WebService(name = helloPort, targetNamespace = com/wb/hello)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@XmlSeeAlso({
ObjectFactory.class
})
I'm not sure why, but based on timestamps wsimport right now isn't
generating HelloPortType. On the other hand, it isn't referenced anywhere in
any of the other code, so I don't know if it matters.
Dan
On Mon, Feb 1, 2010 at 1:51 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Can you show me the annotations on HelloService, HelloPortType and
HelloPort?
Andreas
On Mon, Feb 1, 2010 at 21:12, Daniel Walsh walsh94...@gmail.com wrote:
Andreas,
I annotated my service class per your example and I am still getting the
No
annotated classes found in the jar message when I click on the link
Faulty Services
c:\tomcat-6.0.20\webapps\axis2\WEB-INF\servicejars\HelloService.jar
on the list services page at
http://localhost:8080/axis2/services/listServices;
My annotated implementation class, HelloPortImpl, is pretty simple:
package com.wb.hello;
import java.io.PrintStream;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
import javax.xml.bind.annotation.XmlSeeAlso;
@WebService(endpointInterface = com.wb.hello.HelloPort,
serviceName = HelloService,
portName = HelloPort,
targetNamespace = com/wb/hello,
wsdlLocation = META-INF/hello.wsdl)
public class HelloPortImpl implements HelloPort {
@WebMethod
@WebResult(name = helloResponseElement, targetNamespace =
com/wb/hello, partName = parameters)
public HelloResponseType hello(HelloRequestType helloRequestType) {
HelloResponseType helloResponseType = new HelloResponseType();
helloResponseType.setResponse(Hello +
helloRequestType.getRequest());
return helloResponseType;
}
}
And the class shows up in the jar file:
$ jar tvf
c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar
0 Mon Feb 01 12:11:02 PST 2010 META-INF/
71 Mon Feb 01 12:11:02 PST 2010 META-INF/MANIFEST.MF
890 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPort.class
1095 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortImpl.class
898 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortType.class
752 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloRequestType.class
758 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloResponseType.class
2003 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloService.class
1708 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/ObjectFactory.class
230 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/package-info.class
1804 Mon Feb 01 12:11:00 PST 2010 META-INF/hello.wsdl
805 Mon Feb 01 12:11:00 PST 2010 META-INF/helloSchema.xsd
296 Sat Jan 30 16:26:00 PST 2010 META-INF/service.xml
If you have any thoughts as to why I can't get this thing to deploy I
would
sure be happy to hear them.
Dan
andreas.veit...@gmail.com wrote:
Dan,
Actually the error message should read No @WebService annotated
service implementations found or something like that :-)
In fact, you also need to annotate your service implementation with
@WebService. Note that while this is the same annotation type than on
the service interface (generated by wsimport), the attributes have a
different meaning. There is an example here [1]. Note that this
requirement is not specific to Axis2, but comes from JSR-109/181.
Andreas
[1]
https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/veithen/AXIS2-4611/jaxws-calculator-aar/src/main/java/org/apache/axis2/jaxws/calculator/impl/CalculatorImpl.java
On Thu, Jan 28, 2010 at 19:46, Daniel Walsh walsh94...@gmail.com
wrote:
Andreas,
Thanks for the tip. I would never have figured that out by myself.
Unfortunately, simply moving the services/HelloService.aar file to
servicejars/HelloServices.jar seems to have made things worse.
Whereas
before I saw the service listed as deployed on the listServices page
(but
got the exception when trying to run the client), now the service
doesn't
even deploy. Clicking
Re: next release
There are no plans for 1.6 yet. If there is sufficient demand, we could do a maintenance release (1.5.2), but this would assume that the fix for your issue could be merged to the 1.5 branch. Do you have a reference to the JIRA or the SVN commit for that issue? Andreas On Tue, Feb 2, 2010 at 17:19, Larry Gilliam lgill...@innovim.com wrote: Hello, There is a bug in Axis2 1.5 affecting us (http://modis.gsfc.nasa.gov/) which is fixed in the latest trunk. We'd prefer to wait until the next release to deploy a new version. Is there any ETA for a release? It appears the last was in October and they come every few months. I appreciate any info, thanks. -Larry Gilliam
Re: next release
Unfortunately the issue is not linked to a Subversion commit (which is the precondition to be able to merge the fix to the 1.5 branch). Maybe Keith or Amila have an idea where in the code this was fixed? Andreas On Tue, Feb 2, 2010 at 18:04, Larry Gilliam lgill...@innovim.com wrote: Andreas Veithen wrote: There are no plans for 1.6 yet. If there is sufficient demand, we could do a maintenance release (1.5.2), but this would assume that the fix for your issue could be merged to the 1.5 branch. Do you have a reference to the JIRA or the SVN commit for that issue? Sorry I should have included that. Here is the issue: http://issues.apache.org/jira/browse/AXIS2-4492 Its still marked unresolved, but the reporter is no longer on the project and I can verify that the issue is fixed as of SVN r894701. A maintenance release would be sufficient for us, FWIW. Thanks again.
Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1
On Tue, Feb 2, 2010 at 10:06, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Andreas, Summary: Builds using MAVEN 2.2.1 Source Code used, Cmd window NetBeans IDE 6.8 Maven Flags downloaded by SVN Tortoise Maven 2.2.1 external Maven 2.2.1 Ant 1.7.0 external Ant 1.7.0 C:\asf\webservices\axis2\tags\java\v1.5.1 fails fails -Dmave.test.skip=true C:\asf\webservices\axis2\tags\java\v1.5.1 success success .NA. C:\asf\webservices\axis2\trunk\java success success -Dmave.test.skip=true C:\asf\webservices\axis2\trunk\java success success .NA. Builds using MAVEN 3.0-SNAPSHOT AXIS2 is not yet maven 3.0-Snapshot ready! If you have NetBeans IDE 6.8 with the internal or external maven 3.0-snapshot then you are unable to open the axis2 root POM correctly. However one is still able to build some off the axis2 components/artifacts correctly. In short AXIS2 Trunk sources and earlier are not yet ready for MAVEN 3.0-SNAPSHOT! Josef You are probably one of the first persons to attempt building Axis2 with Maven 3.0. Normally Maven 3.0 is meant to be a drop-in replacement for Maven 2.x so there should be no major problems. I will give it a try. Andreas
Re: unsubscribe
You need to send a mail to axis-user-unsubscr...@ws.apache.org On Mon, Feb 1, 2010 at 07:54, amardeep singh khera amardeepsinghkh...@gmail.com wrote:
Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1
Josef, Please see AXIS2-3290 and AXIS2-4460. This issue has been fixed recently in the trunk. Andreas On Mon, Feb 1, 2010 at 16:35, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Hi all, I’ve used subversion to catch down axis2 /trunk/java/ /tags/java/v1.5.1 /branches/java/v1.5 Then I used a Vista cmd window and maven 2.2.1 to build axis2 CD C:\asf\webservices\axis2\tags\java\v1.5.1 C:\asf\webservices\axis2\tags\java\v1.5.1 mvn install And all was built perfect, greatre success, error free. Now I struggle with the same doing it from with NetBeans 6.8, using external maven 2.2.1 from the same location as done using maven from the vista cmd window C:\asf\webservices\axis2\tags\java\v1.5.1ant -version Apache Ant version 1.7.1 compiled on June 27 2008 C:\asf\webservices\axis2\tags\java\v1.5.1 It fails while building JAXWS Integration Tests Any ideas and hints welcome. What can I do to get my axis2 cleanly built using NetBeans IDE 6.8 and maven 2.2.1 ? I will use NB 6.8 for debugging axis2 running on a Integrity OpenVMS maschine under Tomcat, with a NetBeans IDE debugger attached to the JVM on OpenVMS. Regards Josef.Stadelmann @Axa-winterthur.ch NetBeans: Executing 'C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat -Dmaven.test.skip=true -Dnetbeans.execution=true -Dmaven.repo.local=C:\Users\C770817\.m2\repository --errors -e clean install' NetBeans: JAVA_HOME=C:\Program Files\JAVA\jdk1.6.0_14 + Error stacktraces are turned on. Scanning for projects... Building Apache Axis2 - JAXWS Integration Tests task-segment: [clean, install] [clean:clean] Deleting directory C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target [resources:resources] Using default encoding to copy filtered resources. [compiler:compile] No sources to compile [antrun:run] Executing tasks [mkdir] Created dir: C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema [mkdir] Created dir: C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\src [mkdir] Created dir: C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\classes [echo] Generating JAX-B classes from XSDs [echo] Generating java from soap 11 [echo] Generating java from echo.xsd [echo] Generating java from stock1.xsd [echo] Generating java from stock2.xsd [echo] Generating java from samplemtom.xsd [echo] Generating java from greeterTypes.xsd [echo] Generating java from ProxyDocLitWrapped.wsdl [echo] Generating java from AddNumbers.wsdl [echo] Generating java from ProxyDocLitnonWrapped.wsdl [echo] Generating java from samplemtomjpeg.wsdl [echo] Generating java from RPCLit.wsdl [echo] Generating java from RPCLitSWA.wsdl [echo] Generating java from gorilla_dlw.wsdl [echo] Generating java from SOAP12Echo.wsdl [echo] Generating java from AddNumbersHandler.wsdl [echo] Generating java from async_doclitwr.wsdl [echo] Generating java from async_doclitwr2.wsdl [echo] Generating java from FaultyWebService.wsdl [echo] Generating java from FaultsService.wsdl [echo] Generating java from jaxbsource [echo] Generating java from doclit_nonwrap.wsdl for javabean endpoint [echo] support [echo] Generating java from doclitwrap.wsdl for javabean endpoint [echo] support [echo] Generating java from doclitbare.wsdl for javabean endpoint [echo] support [echo] Generating java from EchoMessage.wsdl for javabean endpoint [echo] support [echo] Generating java from resourceinjection.wsdl for javabean [echo] endpoint Resource Injection support [echo] Generating java from AnyType.wsdl for javabean endpoint [echo] AnyType support [echo] Generating java from MessageContext.wsdl for message context [echo] properties support [echo] Generating java from WSDLMultiTests.wsdl [echo] Generating java from Polymorphic shapes.wsdl for javabean [echo] endpoint support [echo] Generating java from SOAPActionTest.wsdl [echo] Generating java from rpclitenum.wsdl [echo] Generating java from AddNumbersHandler.wsdl [echo] Generating java from rpclitstringarray.wsdl [echo] Generating java from swamtomservice.wsdl Executed tasks [resources:testResources] Using default encoding to
Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1
On Mon, Feb 1, 2010 at 17:35, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Thank you Andreas, But why does under NetBeans IDE control, maven build/makes only 26 files while running maven in a vista cmd window maven builds/makes 50 files. And that is what the error says. File not found ... osn't it? NetBeans somehow decided to run the build with maven.test.skip set to true. That is what causes the AppleFinderService issue (we figured that out last weekend after several people had a look into that issue). Looking at the POM I do not understand why this file and others are not built when maven is used from NetBeans IDE. So your saying that I have no choice to have a error free build using NetBeans IDE 6.8. I tried to build error free from the trunk sources and in absence of a well running build I switched to the tags/v1.5.1 sources, which did it perfectly when I used maven 2.2.1 from a Vista cmd window, but fails now with the latest greatest NetBeans IDE 6.8 Does this imply that you had a build failure using the trunk sources and plain Maven? Then I like to formulate my question differently. What source code version of axis2 shall I use to have an error free build using NetBeans IDE 6.8 with external maven 2.2.1 and ant 1.7? Our priority is to have a build that works correctly with (plain) Maven. We do not systematically test importing the sources into various IDEs, so it's impossible to tell which version works with the particular combination of tools you are using. However, we are happy to fix issues that occur with specific IDEs (if the required fix has no negative impact on the normal Maven build) when they are reported. E.g., myself, from time to time I fix issues to simplify working with the sources in Eclipse. Thank you Josef -Ursprüngliche Nachricht- Von: Andreas Veithen [mailto:andreas.veit...@gmail.com] Gesendet: Montag, 1. Februar 2010 17:03 An: axis-user@ws.apache.org Betreff: Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1 Josef, Please see AXIS2-3290 and AXIS2-4460. This issue has been fixed recently in the trunk. Andreas On Mon, Feb 1, 2010 at 16:35, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Hi all, I've used subversion to catch down axis2 /trunk/java/ /tags/java/v1.5.1 /branches/java/v1.5 Then I used a Vista cmd window and maven 2.2.1 to build axis2 CD C:\asf\webservices\axis2\tags\java\v1.5.1 C:\asf\webservices\axis2\tags\java\v1.5.1 mvn install And all was built perfect, greatre success, error free. Now I struggle with the same doing it from with NetBeans 6.8, using external maven 2.2.1 from the same location as done using maven from the vista cmd window C:\asf\webservices\axis2\tags\java\v1.5.1ant -version Apache Ant version 1.7.1 compiled on June 27 2008 C:\asf\webservices\axis2\tags\java\v1.5.1 It fails while building JAXWS Integration Tests Any ideas and hints welcome. What can I do to get my axis2 cleanly built using NetBeans IDE 6.8 and maven 2.2.1 ? I will use NB 6.8 for debugging axis2 running on a Integrity OpenVMS maschine under Tomcat, with a NetBeans IDE debugger attached to the JVM on OpenVMS. Regards Josef.Stadelmann @Axa-winterthur.ch NetBeans: Executing 'C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat -Dmaven.test.skip=true -Dnetbeans.execution=true -Dmaven.repo.local=C:\Users\C770817\.m2\repository --errors -e clean install' NetBeans: JAVA_HOME=C:\Program Files\JAVA\jdk1.6.0_14 + Error stacktraces are turned on. Scanning for projects... Building Apache Axis2 - JAXWS Integration Tests task-segment: [clean, install] [clean:clean] Deleting directory C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target [resources:resources] Using default encoding to copy filtered resources. [compiler:compile] No sources to compile [antrun:run] Executing tasks [mkdir] Created dir: C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema [mkdir] Created dir: C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\src [mkdir] Created dir: C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\classes [echo] Generating JAX-B classes from XSDs [echo] Generating java from soap 11 [echo] Generating java from echo.xsd [echo] Generating java from stock1.xsd [echo] Generating java from stock2.xsd [echo] Generating java from samplemtom.xsd [echo] Generating java from greeterTypes.xsd [echo] Generating java from ProxyDocLitWrapped.wsdl [echo] Generating java from AddNumbers.wsdl [echo] Generating java from ProxyDocLitnonWrapped.wsdl [echo] Generating java from
Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1
On Mon, Feb 1, 2010 at 18:10, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Andreas, The problem I am faced with is twofold. 1. When I turn oft in NetBeans IDE 6.8 under Option at the Maven tag the checkbox labeled: Skip test for any build executions not directly related to testing those resulting in forcing the maven command having a -Dmaven.test.skip=true on board, then turning this flag OFF in the option menu for maven makes all test classes generated (around 50) and then the dedicated copy tasks as shown in the POM runs but al tests run as well (very lengthy) Therefore: To get an error free build using NetBeans IDE 6.8 and maven 2.2.1 I have to work for JAXWS Integration with this flag set to OFF 2. And maybe I get something wrong here but maybe of interest to you: When I use the vista cmd window ... mvn -Dmaven.test.skip=true clean install The build C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integrationmvn -Dmaven.test.skip=true clean install fails too. That is the issue we fixed last weekend. See: http://svn.apache.org/viewvc?view=revisionrevision=904780 So are you saying I have to use the POM from the trunk for JAXWS Integration to build correctly? OR Where do you think it was fixed; sorry but I am not getting more insight reading the two JIRA's Josef -Ursprüngliche Nachricht- Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Gesendet: Montag, 1. Februar 2010 17:35 An: axis-user@ws.apache.org Betreff: AW: help needed building axis2 using NetBeans 6.8 and maven 2.2.1 Thank you Andreas, But why does under NetBeans IDE control, maven build/makes only 26 files while running maven in a vista cmd window maven builds/makes 50 files. And that is what the error says. File not found ... osn't it? Looking at the POM I do not understand why this file and others are not built when maven is used from NetBeans IDE. So your saying that I have no choice to have a error free build using NetBeans IDE 6.8. I tried to build error free from the trunk sources and in absence of a well running build I switched to the tags/v1.5.1 sources, which did it perfectly when I used maven 2.2.1 from a Vista cmd window, but fails now with the latest greatest NetBeans IDE 6.8 Then I like to formulate my question differently. What source code version of axis2 shall I use to have an error free build using NetBeans IDE 6.8 with external maven 2.2.1 and ant 1.7? Thank you Josef -Ursprüngliche Nachricht- Von: Andreas Veithen [mailto:andreas.veit...@gmail.com] Gesendet: Montag, 1. Februar 2010 17:03 An: axis-user@ws.apache.org Betreff: Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1 Josef, Please see AXIS2-3290 and AXIS2-4460. This issue has been fixed recently in the trunk. Andreas On Mon, Feb 1, 2010 at 16:35, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Hi all, I've used subversion to catch down axis2 /trunk/java/ /tags/java/v1.5.1 /branches/java/v1.5 Then I used a Vista cmd window and maven 2.2.1 to build axis2 CD C:\asf\webservices\axis2\tags\java\v1.5.1 C:\asf\webservices\axis2\tags\java\v1.5.1 mvn install And all was built perfect, greatre success, error free. Now I struggle with the same doing it from with NetBeans 6.8, using external maven 2.2.1 from the same location as done using maven from the vista cmd window C:\asf\webservices\axis2\tags\java\v1.5.1ant -version Apache Ant version 1.7.1 compiled on June 27 2008 C:\asf\webservices\axis2\tags\java\v1.5.1 It fails while building JAXWS Integration Tests Any ideas and hints welcome. What can I do to get my axis2 cleanly built using NetBeans IDE 6.8 and maven 2.2.1 ? I will use NB 6.8 for debugging axis2 running on a Integrity OpenVMS maschine under Tomcat, with a NetBeans IDE debugger attached to the JVM on OpenVMS. Regards Josef.Stadelmann @Axa-winterthur.ch NetBeans: Executing 'C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat -Dmaven.test.skip=true -Dnetbeans.execution=true -Dmaven.repo.local=C:\Users\C770817\.m2\repository --errors -e clean install' NetBeans: JAVA_HOME=C:\Program Files\JAVA\jdk1.6.0_14 + Error stacktraces are turned on. Scanning for projects... Building Apache Axis2 - JAXWS Integration Tests task-segment: [clean, install] [clean:clean] Deleting directory C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target [resources:resources] Using default encoding to copy filtered resources. [compiler:compile] No sources to compile [antrun:run] Executing tasks [mkdir] Created dir: C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema [mkdir] Created dir: C:\asf\webservices\axis2\tags
Re: Axis2 JAX-WS: The service class cannot be found for this AxisService
Can you show me the annotations on HelloService, HelloPortType and HelloPort?
Andreas
On Mon, Feb 1, 2010 at 21:12, Daniel Walsh walsh94...@gmail.com wrote:
Andreas,
I annotated my service class per your example and I am still getting the No
annotated classes found in the jar message when I click on the link
Faulty Services
c:\tomcat-6.0.20\webapps\axis2\WEB-INF\servicejars\HelloService.jar
on the list services page at
http://localhost:8080/axis2/services/listServices;
My annotated implementation class, HelloPortImpl, is pretty simple:
package com.wb.hello;
import java.io.PrintStream;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
import javax.xml.bind.annotation.XmlSeeAlso;
@WebService(endpointInterface = com.wb.hello.HelloPort,
serviceName = HelloService,
portName = HelloPort,
targetNamespace = com/wb/hello,
wsdlLocation = META-INF/hello.wsdl)
public class HelloPortImpl implements HelloPort {
@WebMethod
@WebResult(name = helloResponseElement, targetNamespace =
com/wb/hello, partName = parameters)
public HelloResponseType hello(HelloRequestType helloRequestType) {
HelloResponseType helloResponseType = new HelloResponseType();
helloResponseType.setResponse(Hello + helloRequestType.getRequest());
return helloResponseType;
}
}
And the class shows up in the jar file:
$ jar tvf
c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar
0 Mon Feb 01 12:11:02 PST 2010 META-INF/
71 Mon Feb 01 12:11:02 PST 2010 META-INF/MANIFEST.MF
890 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPort.class
1095 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortImpl.class
898 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortType.class
752 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloRequestType.class
758 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloResponseType.class
2003 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloService.class
1708 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/ObjectFactory.class
230 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/package-info.class
1804 Mon Feb 01 12:11:00 PST 2010 META-INF/hello.wsdl
805 Mon Feb 01 12:11:00 PST 2010 META-INF/helloSchema.xsd
296 Sat Jan 30 16:26:00 PST 2010 META-INF/service.xml
If you have any thoughts as to why I can't get this thing to deploy I would
sure be happy to hear them.
Dan
andreas.veit...@gmail.com wrote:
Dan,
Actually the error message should read No @WebService annotated
service implementations found or something like that :-)
In fact, you also need to annotate your service implementation with
@WebService. Note that while this is the same annotation type than on
the service interface (generated by wsimport), the attributes have a
different meaning. There is an example here [1]. Note that this
requirement is not specific to Axis2, but comes from JSR-109/181.
Andreas
[1]
https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/veithen/AXIS2-4611/jaxws-calculator-aar/src/main/java/org/apache/axis2/jaxws/calculator/impl/CalculatorImpl.java
On Thu, Jan 28, 2010 at 19:46, Daniel Walsh walsh94...@gmail.com wrote:
Andreas,
Thanks for the tip. I would never have figured that out by myself.
Unfortunately, simply moving the services/HelloService.aar file to
servicejars/HelloServices.jar seems to have made things worse. Whereas
before I saw the service listed as deployed on the listServices page
(but
got the exception when trying to run the client), now the service
doesn't
even deploy. Clicking through the faulty services link on the
listServices
page gives me this:
Error: No annotated classes found in the jar:
file:/c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar.
Service deployment failed.
Looking for annotations in just the .java files generated by wsimport
-keep
-verbose hello.wsdl (the .class files of which are in the jar file) I
find
the following (I used grep ^@ | sort)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@WebService(name = helloPort, targetNamespace = com/wb/hello)
@WebServiceClient(name = HelloService, targetNamespace =
com/wb/hello,
wsdlL
ocation =
file:/C:/Documents%20and%20Settings/dan/My%20Documents/tmp/hello2/ser
vice/hello.wsdl)
@XmlAccessorType(XmlAccessType.FIELD)
@XmlAccessorType(XmlAccessType.FIELD)
@XmlRegistry
@XmlSeeAlso({
@XmlType(name = helloRequestType, propOrder = {
@XmlType(name = helloResponseType, propOrder = {
@javax.xml.bind.annotation.XmlSchema(namespace = com/wb/hello)
Clearly, there are lots of annotations, so the error message is
incorrect.
I'm not sure what to do at this point.
Dan
On Wed, Jan 27, 2010 at 12:46 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Daniel,
Please have
Re: [Error]WstxInputFactory cannot be located
sorry, I think I've sended twice the message... No, but somehow the attachment got lost.
Re: Axis2: SampleService example from Axis 2 webpage gets exception
That probably means that the Axis2 version you used to compile the code is not the same as the one deployed in Tomcat. In particular, axis2-std-1.0-bin doesn't sound good. If you are starting with Axis2 you should use version 1.5.1, unless there is a particular requirement to use a version as old as 1.0. Andreas On Fri, Jan 29, 2010 at 19:23, Daniel Walsh walsh94...@gmail.com wrote: I'm trying to build and run the SampleService example from the Apache Axis2 webpage at http://ws.apache.org/axis2/1_5_1/userguide-buildingservices.html#buildservices listings 8-10. When I try to run the client I get org.apache.axis2.AxisFault: org.apache.axiom.om.OMFactory.createOMText(Lorg/apache/axiom/om/OMElement;Ljava/lang/String;)Lorg/apache/axiom/om/OMText; I tried putting the message into Google and it came up with no results. I figured that as a newbie I would try the first example and build from there, but I don't have any idea what the error message means or what I should do about it. Can anyone help me out here? Thanks, Dan -- Here is a detailed description of what I did, in case it helps: What I did was to cut and paste SampleService, services.xml and SampleClient from listings 8-10 of http://ws.apache.org/axis2/1_5_1/userguide-buildingservices.html#buildservices into org/apache/axis2/axis2userguide/SampleService.java, META-INF/services.xml and org/apache/axis2/axis2userguide/SampleClient.java respectively. I also copied all the axis2 libraries from axis2-std-1.0-bin/lib into ../lib. I then wrote (in cygwin bash) a simple shell script to build and deploy the service: export CLASSPATH=`echo ../lib/*.jar | tr ' ' ';'` echo classpath $CLASSPATH javac org/apache/axis2/axis2userguide/SampleService.java jar cf SampleService.aar org/apache/axis2/axis2userguide/SampleService.class META-INF/services.xml cp SampleService.aar /cygdrive/c/tomcat-6.0.20/webapps/axis2/WEB-INF/services I ran the above script, shut down tomcat and brought it up again, and I saw the service deployed in http://localhost:8080/axis2/services/listServices I then wrote another shell script to compile and run the client: export CLASSPATH=`echo ../lib/*.jar | tr ' ' ';'` echo classpath $CLASSPATH javac org/apache/axis2/axis2userguide/SampleClient.java java -cp $CLASSPATH;. org/apache/axis2/axis2userguide/SampleClient When I run this script I get the error mentioned above: org.apache.axis2.AxisFault: org.apache.axiom.om.OMFactory.createOMText(Lorg/apache/axiom/om/OMElement;Ljava/lang/String;)Lorg/apache/axiom/om/OMText; I swear I literally copied the SampleService, service.xml and SampleClient from code listings 8-10 respectively, except that I had to change line 33 of SampleClient because it breaks a quoted string across two lines and the compiler won't allow that. I changed nothing else from the example.
Re: [Error]WstxInputFactory cannot be located (with the attachment)
Phillippe, There are two possible reasons: * The obvious one would be that the wstx-asl JAR is missing. Since JRE 1.6 ships with a StAX implementation (which Axiom would then use instead of Woodstox), while JRE 1.5 does not, this may explain why the code runs successfully in one environment, while it fails in the other. * The more subtle explanation would be that Axiom attempts to load the StAX implementation from the wrong class loader. By default, Axiom loads the StAX implementation from the thread context class loader. If OpenOffice sets up the runtime environment in such a way that the thread context class loader is different from the class loader that is used to load your code, then this error may occur. If this is the case, you have two options: set the thread context class loader yourself or call StAXUtils.setFactoryPerClassLoader(false) to change Axiom's behavior. Andreas On Fri, Jan 29, 2010 at 23:21, Philippe Denis ph.de...@gmail.com wrote: Hello everybody, I created my web service in eclipse and then I created my web service client with the command wsdl2java. The service client works correctly when I test it in eclipse. However, I'd integrate my web service client in OpenOffice. I know OpenOffice and I know how to integrate a package in OpenOffice. However, when I integrate my web service client in OpenOffice, I receive an error (attached with the mail). I don't understand the reason because it's exactly the same package that I tested in eclipse. Do you understand what means the error? Could you tell me some clues to solve my problem? I'd be glad if you find a solution, Thank you very much. Philippe NOTE : I use : - Mac os 10.5 - Axis 2 1.4.1 - Apache 5.5
Re: Loading Axis2 repository from classpath instead of file system
Yes, this is possible, but you need to add services.list and modules.list files so that Axis2 is able to locate your services and modules. By searching for these two names on the internet and in the mailing list archives, you should be able to find some examples. If not, let us know and we will try to find a sample. Andreas On Thu, Jan 28, 2010 at 16:32, Stephanos Piperoglou stephanos.piperog...@db.com wrote: Hi everyone, Short version: Is there a way to load the Axis2 repository using the class loader? Long version: I have got my client running, but I can only manage to initialise the repository from the file system using ConfigurationContextFactory.createConfigurationContextFromFileSystem. However, I would like to package up the repository in my JAR file and load it using the class loader to increase portability. This doesn't seem to work: URL clientRepo = getClass().getResource(/axis2repo); ConfigurationContextFactory.createConfigurationContextFromURIs(null, clientRepo); ... even though clientRepo.toExternalForm() seems to resolve to the correct place and I can use .getResourceAsStream() to read the files in the repository. Regards, Stephanos Piperoglou Price Control GTO - BAC IT +44 20 754 59007 This mail is transmitted to you on behalf of the Great East London Software Company Diese Post wird Ihnen im Namen der Great East London Software Company übermittelt *Stephanos Piperoglou stephanos.piperoglou+exter...@db.comstephanos.piperoglou%2bexter...@db.com * 28/01/2010 14:20 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Unable to engage module : rampart [RESOLVED] Apologies, it seems the repository wasn't being picked up by the classloader. Regards, Stephanos Piperoglou Price Control GTO - BAC IT +44 20 754 59007 This mail is transmitted to you on behalf of the Great East London Software Company Diese Post wird Ihnen im Namen der Great East London Software Company übermittelt *Stephanos Piperoglou stephanos.piperoglou+exter...@db.comstephanos.piperoglou%2bexter...@db.com * 28/01/2010 13:51 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Unable to engage module : rampart Hi, I have a web service client that ran perfectly under Axis2 (stub generated using ADB bindings) until the provider (not under my control) added WS-Security and now requires username/password auth. I have tried with little success to integrate Rampart into our set-up. What I did, piecing things together from various how-tos: 1. Added all the rampart jars to the classpath 2. Created a client Axis2 repository (I didn't have one of those before) containing conf/, services/ and modules/ 3. Put the two .mar files in /modules 4. Created an axis2.xml config file in conf/ (attached) 5. Added the following around my stub creation code: *final* ConfigurationContext ctx = ConfigurationContextFactory.* createConfigurationContextFromURIs*(*null*, clientRepo); *final* OpenPvsServiceStub openPvs = *new*OpenPvsServiceStub(ctx, serviceAddress); *final* ServiceClient sc = openPvs._getServiceClient(); sc.engageModule(rampart); *final* Options options = *new* Options(); options.setUserName(stephanos.piperog...@db.com); options.setPassword(x); sc.setOverrideOptions(options); This causes: org.apache.axis2.AxisFault: Unable to engage module : rampart Any ideas would be greatly appreciated. Regards, Stephanos Piperoglou Price Control GTO - BAC IT +44 20 754 59007 This mail is transmitted to you on behalf of the Great East London Software Company Diese Post wird Ihnen im Namen der Great East London Software Company übermittelt --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.[attachment axis2.xml deleted by Stephanos Piperoglou/ext/dbcom] --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender
Re: Axis2 JAX-WS: The service class cannot be found for this AxisService
Dan,
Actually the error message should read No @WebService annotated
service implementations found or something like that :-)
In fact, you also need to annotate your service implementation with
@WebService. Note that while this is the same annotation type than on
the service interface (generated by wsimport), the attributes have a
different meaning. There is an example here [1]. Note that this
requirement is not specific to Axis2, but comes from JSR-109/181.
Andreas
[1]
https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/veithen/AXIS2-4611/jaxws-calculator-aar/src/main/java/org/apache/axis2/jaxws/calculator/impl/CalculatorImpl.java
On Thu, Jan 28, 2010 at 19:46, Daniel Walsh walsh94...@gmail.com wrote:
Andreas,
Thanks for the tip. I would never have figured that out by myself.
Unfortunately, simply moving the services/HelloService.aar file to
servicejars/HelloServices.jar seems to have made things worse. Whereas
before I saw the service listed as deployed on the listServices page (but
got the exception when trying to run the client), now the service doesn't
even deploy. Clicking through the faulty services link on the listServices
page gives me this:
Error: No annotated classes found in the jar:
file:/c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar.
Service deployment failed.
Looking for annotations in just the .java files generated by wsimport -keep
-verbose hello.wsdl (the .class files of which are in the jar file) I find
the following (I used grep ^@ | sort)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@WebService(name = helloPort, targetNamespace = com/wb/hello)
@WebServiceClient(name = HelloService, targetNamespace = com/wb/hello,
wsdlL
ocation =
file:/C:/Documents%20and%20Settings/dan/My%20Documents/tmp/hello2/ser
vice/hello.wsdl)
@XmlAccessorType(XmlAccessType.FIELD)
@XmlAccessorType(XmlAccessType.FIELD)
@XmlRegistry
@XmlSeeAlso({
@XmlType(name = helloRequestType, propOrder = {
@XmlType(name = helloResponseType, propOrder = {
@javax.xml.bind.annotation.XmlSchema(namespace = com/wb/hello)
Clearly, there are lots of annotations, so the error message is incorrect.
I'm not sure what to do at this point.
Dan
On Wed, Jan 27, 2010 at 12:46 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Daniel,
Please have a look at AXIS2-4611 [1]. If deploying as a servicejar is
not an option for you, feel free to vote for the issue and leave a
comment.
Andreas
[1] https://issues.apache.org/jira/browse/AXIS2-4611
On Wed, Jan 27, 2010 at 21:32, Daniel Walsh walsh94...@gmail.com wrote:
I have written a simple hello application in Axis2 JAX-WS and when I run
my client I am getting an error that the service class cannot be found. In
this email I'm including the exact message, my services.xml file, a jar
output of my aar file, my wsdl file, my schema file, a snippet from the
available services webpage and a stacktrace from catalina.out.
I wrote the services.xml, the schema and the wsdl files by hand and
generated all the classes (except HelloClient, my client class) by
wsimport
-keep -verbose hello.wsdl.
I have tried every Google search I can think of and have looked at
several tutorials and dozens of mail archives without finding out the
answer. If you can help, I would really appreciate it.
--
The error message I get when I run the client (java -cp HelloService.jar
com/wb/hello/HelloClient) is:
Exception in thread main javax.xml.ws.soap.SOAPFaultException:
java.lang.RuntimeException: The service class cannot be found for this
AxisService.
--
My services.xml file is simple:
service name=HelloService
parameter name=ServiceClasscom.wb.hello.HelloService/parameter
operation name=hello
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out;
class=org.apache.axis2.jaxws.server.JAXWSMessageReceiver/
/operation
/service
--
When I go to /cygdrive/c/tomcat-6.0.20/webapps/axis2/WEB-INF/services
and jar the aar file, the service class is there:
$ jar tvf HelloService.aar
0 Tue Jan 26 14:41:52 PST 2010 META-INF/
71 Tue Jan 26 14:41:52 PST 2010 META-INF/MANIFEST.MF
1287 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloClient.class
886 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloPort.class
898 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloPortType.class
752 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloRequestType.class
758 Tue Jan 26 14
Re: Axis213 Soap request and response logging issue
Please stop spamming this list by sending the same post repeatedly. There
are plenty of articles on the Web discussing SOAP message logging in Axis2.
Did you actually do your own research?
On Wed, Jan 27, 2010 at 12:01, arockia.s...@aciworldwide.com wrote:
Thanks Regards,
Arockia
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error has
misdirected this email, please notify the sender immediately and destroy
this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions expressed
in this email are those of the author personally.
From: arockia.s...@aciworldwide.com To:
axis-...@ws.apache.org
Date: 01/26/2010 11:10 PM
Subject: Re: Axis213 Soap request and response logging issue
--
Thanks Regards,
Arockia
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error has
misdirected this email, please notify the sender immediately and destroy
this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions expressed
in this email are those of the author personally.
From: arockia.s...@aciworldwide.com To: axis-...@ws.apache.org Date:
01/26/2010
10:57 PM Subject: Re: Axis213 Soap request and response logging issue
--
Thanks Regards,
Arockia
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error has
misdirected this email, please notify the sender immediately and destroy
this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions expressed
in this email are those of the author personally.
From: arockia.s...@aciworldwide.com To: axis-...@ws.apache.org Date:
01/26/2010
07:36 PM Subject: Axis213 Soap request and response logging issue
--
Hi All,
In axis213 for Soap REQUEST AND RESPONSE LOGGING I put the below entry in
the configuration file called balilogger.lcf.
# To log SOAP Messages enable this
log4j.logger.org.apache.axis2.transport.http=DEBUG, LOGFILE
# LOGFILE is set to be a File appender using a PatternLayout.
log4j.appender.LOGFILE=bali.utils.BaliRollingFileAppender
log4j.appender.LOGFILE.File=..//logs//${currentDate}//axismessages.log
log4j.appender.LOGFILE.MaxFileSize=200MB
log4j.appender.LOGFILE.MaxBackupIndex=100
log4j.appender.LOGFILE.LogRetentionDays=7
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%d{DATE};[%t];%p;%m%n
It is not logging soap envelop and soap body. It logs some other related
information in axismessages.log file
But in Axis1 architecture it works fine.It is logging soap envelop and soap
body also with other related information .
I just put log4j.logger.org.apache.axis.transport.http=DEBUG, LOGFILE
so please help me to find out the issue.
Thanks Regards,
Arockia
This email message and any attachments may contain confidential,
proprietary or non-public information. The information is intended solely
for the designated recipient(s). If an addressing or transmission error has
misdirected this email, please notify the sender immediately and destroy
this email. Any review, dissemination, use or reliance upon this
information by unintended recipients is prohibited. Any opinions expressed
in this email are those of the author personally.
Re: Axis2 JAX-WS: The service class cannot be found for this AxisService
Daniel, Please have a look at AXIS2-4611 [1]. If deploying as a servicejar is not an option for you, feel free to vote for the issue and leave a comment. Andreas [1] https://issues.apache.org/jira/browse/AXIS2-4611 On Wed, Jan 27, 2010 at 21:32, Daniel Walsh walsh94...@gmail.com wrote: I have written a simple hello application in Axis2 JAX-WS and when I run my client I am getting an error that the service class cannot be found. In this email I'm including the exact message, my services.xml file, a jar output of my aar file, my wsdl file, my schema file, a snippet from the available services webpage and a stacktrace from catalina.out. I wrote the services.xml, the schema and the wsdl files by hand and generated all the classes (except HelloClient, my client class) by wsimport -keep -verbose hello.wsdl. I have tried every Google search I can think of and have looked at several tutorials and dozens of mail archives without finding out the answer. If you can help, I would really appreciate it. -- The error message I get when I run the client (java -cp HelloService.jar com/wb/hello/HelloClient) is: Exception in thread main javax.xml.ws.soap.SOAPFaultException: java.lang.RuntimeException: The service class cannot be found for this AxisService. -- My services.xml file is simple: service name=HelloService parameter name=ServiceClasscom.wb.hello.HelloService/parameter operation name=hello messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.jaxws.server.JAXWSMessageReceiver/ /operation /service -- When I go to /cygdrive/c/tomcat-6.0.20/webapps/axis2/WEB-INF/services and jar the aar file, the service class is there: $ jar tvf HelloService.aar 0 Tue Jan 26 14:41:52 PST 2010 META-INF/ 71 Tue Jan 26 14:41:52 PST 2010 META-INF/MANIFEST.MF 1287 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloClient.class 886 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloPort.class 898 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloPortType.class 752 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloRequestType.class 758 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloResponseType.class 2079 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/HelloService.class 1708 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/ObjectFactory.class 230 Tue Jan 26 14:41:52 PST 2010 com/wb/hello/package-info.class 1794 Tue Jan 26 14:41:50 PST 2010 META-INF/hello.wsdl 805 Tue Jan 26 14:41:50 PST 2010 META-INF/helloSchema.xsd 301 Tue Jan 26 14:41:36 PST 2010 META-INF/services.xml -- My wsdl file is: ?xml version=1.0 encoding=UTF-8 standalone=yes? definitions targetNamespace=com/wb/hello name=hello xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:tns=com/wb/hello xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; !-- define schema elements for helloRequest, helloResponse -- types xsd:schema xsd:import namespace=com/wb/hello schemaLocation=helloSchema.xsd/ /xsd:schema /types !-- define messages for helloRequest, helloResponse elements -- message name=helloRequestMessage part name=name element=tns:helloRequestElement/ /message message name=helloResponseMessage part name=result element=tns:helloResponseElement/ /message !-- define port for helloRequest, hello Response messages -- portType name=helloPort operation name=hello input message=tns:helloRequestMessage/ output message=tns:helloResponseMessage/ /operation /portType !-- define binding for hello operation -- binding name=helloBinding type=tns:helloPort soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ operation name=hello soap:operation soapAction=/ input soap:body use=literal/ /input output soap:body use=literal/ /output /operation /binding !-- finally, define the service -- service name=HelloService port name=helloPort binding=tns:helloBinding soap:address location=http://localhost:8080/axis2/services/HelloService/ /port /service /definitions
Re: Axis2 maven plugin: repository 301 Moved Permanently
That is because java.net messed up their repository. See [1] for details. Note that this thread discusses a problem with building the Axis2 sources (which is a bit different from just using axis2-wsdl2code-maven-plugin), but the root cause is the same. Andreas [1] http://markmail.org/message/a5kluack6ylws2k3 On Tue, Jan 26, 2010 at 11:25, Dzmitry Lazerka dlaze...@gmail.com wrote: Hello, I get several errors while using axis2-wsdl2code-maven-plugin, just one of them: Downloading: http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-xmlbeans/1.5.1/axis2-xmlbeans-1.5.1.pom [INFO] Unable to find resource 'org.apache.axis2:axis2-xmlbeans:pom:1.5.1' in repository apache-ws-snapshots2 (http://ws.zones.apache.org/repository2) Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/axis2/axis2-xmlbeans/1.5.1/axis2-xmlbeans-1.5.1.pom [INFO] Unable to find resource 'org.apache.axis2:axis2-xmlbeans:pom:1.5.1' in repository tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository) Downloading: http://repo1.maven.org/eclipse/org/apache/axis2/axis2-xmlbeans/1.5.1/axis2-xmlbeans-1.5.1.pom [INFO] Unable to find resource 'org.apache.axis2:axis2-xmlbeans:pom:1.5.1' in repository eclipse-repo (http://repo1.maven.org/eclipse) Downloading: https://maven-repository.dev.java.net/nonav/repository//org.apache.axis2/poms/axis2-xmlbeans-1.5.1.pom 367b downloaded (axis2-xmlbeans-1.5.1.pom) [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'b44c461d6051ba2c4de115ff3f4f03ebb446353e'; remote = '!DOCTYPE' - RETRYING Downloading: https://maven-repository.dev.java.net/nonav/repository//org.apache.axis2/poms/axis2-xmlbeans-1.5.1.pom 367b downloaded (axis2-xmlbeans-1.5.1.pom) [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'b44c461d6051ba2c4de115ff3f4f03ebb446353e'; remote = '!DOCTYPE' - IGNORING [WARNING] POM for 'org.apache.axis2:axis2-xmlbeans:pom:1.5.1:runtime' is invalid. Its dependencies (if any) will NOT be available to the current build. I discovered that it occurs because several servers provide an html error message along with 301, like these: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://download.java.net/maven/1/org.apache.maven/poms/maven-plugin-api-2.0.7.pom;here/a./p hr addressApache Server at maven-repository.dev.java.net Port 443/address /body/html That prevents me from using axis2-wsdl2code-maven-plugin. Do you know any workaround of this? My plugin configuration is: plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId configuration wsdlFilepartner.wsdl/wsdlFile outputDirectorysrc/outputDirectory packageNameorg.apatar.salesforce-api/packageName /configuration executions execution goals goalwsdl2code/goal /goals /execution /executions /plugin - Best regards, Dzmitry Lazerka, Altoros Systems +375 (29) 502-9579 dzmitry.laze...@altoros.com
Re: archive lib directory and 3rd party libraries (axis2/tomcat 6)
Try adding the following parameter on the service: parameter name=ServiceTCCL locked=falsecomposite/parameter Andreas On Mon, Jan 25, 2010 at 18:22, Charles Galpin cgal...@lhsw.com wrote: Hi All I am still running into problems with this. I previously moved all the jars I needed into the WEB-INF/lib directory and was able to continue working. But as I add more services (more .aar files) I am now running into strange unpredictable differences that I do not understand. For example, I have two services packaged in their own .aar files and if deployed independently they run just fine. Simply deploying both together causes the second one loaded to have mysterious problems like a java.sql.SQLException no suitable driver found for jdbc:sqlserver://.. when the sql3jdbc jar file is in both the .aar and WEB-INF/lib directory and (and as I said works fine standalone). Does anyone have any advice on how to get my services to run together happily? Assume I am not concerned with isolating each service from each other in terms of security. I read on Amila's blog that some class loading settings can be modified but it's not clear exactly what ramifications it will have or if it will even help my problems. I am not sure if this is causing my problems, but due to wanting to be able to override the properties file in the .aar file when deployed in different environments, in the service lifecycle init method I attempt to find the properties file in the axis classpath before trying the .arr, using first axisService.getClass().getClassLoader(0.gerResourceAsStream(propsFilename); and if not found then using this.getClass().getClassLoader(0.gerResourceAsStream(propsFilename); Could this be messing up the class loading sequence, and if yes, how can I achieve the same effect without using the axis class loader first? thanks, charles On Dec 1, 2009, at 2:29 PM, Charles Galpin wrote: Hi Sameera Ok, this is starting to make a little more sense. I was not aware the WebappClassLoader could not see classes in the .aar. Can this be changed? I have access to the source of the client.corba.* packages, but they are just calling org.omg.CORBA.ORB.init which is doing the class loading and thats from rt.jar in the java distro afaik. The ORB loaded is a configurable option which is why it uses the class loader. Here is another exception stack you may find useful. I had run into this problem as well as various other classes not loading a while ago and made a few changes until getting my service working, and one of them was to pass -Djava.library.path=%PATH%;blahblah in on the commandline when starting tomcat. Removing this changes the error to a perhaps little more revealing message (after understanding about the TCCL limitation) 13:38:58 ERROR- Error initializing CORBA ORB. Unexpected CORBA error. org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation org.jacorb.orb.ORB vmcid: 0x0 minor code: 0 completed: No 13:38:58 DEBUG- Stack trace: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation org.jacorb.orb.ORB vmcid: 0x0 minor code: 0 completed: No at org.omg.CORBA.ORB.create_impl(ORB.java:297) at org.omg.CORBA.ORB.init(ORB.java:336) at client.corba.BaseCORBAApp.initCORBA(BaseCORBAApp.java:134) at client.corba.BaseCORBAService.startService(BaseCORBAService.java:100) at client.project.dcol.publish.corba.WebServiceDataCollectionService.webInit(WebServiceDataCollectionService.java:170) at client.project.dcol.GDPI.ServiceBase$ServiceThread.run(ServiceBase.java:318) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: org.jacorb.orb.ORB at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.omg.CORBA.ORB.create_impl(ORB.java:295) ... 6 more 13:38:58 ERROR- Aborted due to startup failure. Aborted due to startup failure: Error initializing CORBA ORB. Unexpected CORBA error. Is there any other way to work around this other than putting the libraries in the axis2/WEB-INF/lib directory? To be clear I have other problems beside this. A good example is we have a custom log4j appender we use which is in Shared.jar. This cannot be found either unless it's in axis2/WEB-INF/lib but your description explains that one too. thanks, charles On Dec 1, 2009, at 1:28 PM, Sameera Jayasoma wrote: Hi Charles On Tue, Dec 1, 2009 at 11:27 PM, Charles Galpin cgal...@lhsw.com wrote: Hi Sameera Yes this is what is happening and what is expected. The org.omg.CosNotifyFilter.InvalidGrammar class is in jacorb.jar which is in the .aar
Re: archive lib directory and 3rd party libraries (axis2/tomcat 6)
Charles, According to the stack trace you posted, the error occurs inside a thread that is neither managed by the servlet container, nor by Axis2: 13:38:58 DEBUG- Stack trace: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation org.jacorb.orb.ORB vmcid: 0x0 minor code: 0 completed: No at org.omg.CORBA.ORB.create_impl(ORB.java:297) at org.omg.CORBA.ORB.init(ORB.java:336) at client.corba.BaseCORBAApp.initCORBA(BaseCORBAApp.java:134) at client.corba.BaseCORBAService.startService(BaseCORBAService.java:100) at client.project.dcol.publish.corba.WebServiceDataCollectionService.webInit(WebServiceDataCollectionService.java:170) at client.project.dcol.GDPI.ServiceBase$ServiceThread.run(ServiceBase.java:318) at java.lang.Thread.run(Thread.java:619) How and where is this thread created? Andreas On Mon, Jan 25, 2010 at 20:23, Charles Galpin cgal...@lhsw.com wrote: Thanks Andreas I added this to both services being loaded, rebuilt and ran, but no change. The composite class loader was one of the options described in Amil's blog and as I understand it, it is supposed to use both the TCCL and the service class loader. But I guess I still don't understand the class loading because this jar is in all the places the class loaders should be looking so I don't see how it matters which one it uses. I also tried the EnableChildFirstClassLoading parameter as well but no help. Thanks, charles On Jan 25, 2010, at 1:53 PM, Andreas Veithen wrote: Try adding the following parameter on the service: parameter name=ServiceTCCL locked=falsecomposite/parameter Andreas On Mon, Jan 25, 2010 at 18:22, Charles Galpin cgal...@lhsw.com wrote: Hi All I am still running into problems with this. I previously moved all the jars I needed into the WEB-INF/lib directory and was able to continue working. But as I add more services (more .aar files) I am now running into strange unpredictable differences that I do not understand. For example, I have two services packaged in their own .aar files and if deployed independently they run just fine. Simply deploying both together causes the second one loaded to have mysterious problems like a java.sql.SQLException no suitable driver found for jdbc:sqlserver://.. when the sql3jdbc jar file is in both the .aar and WEB-INF/lib directory and (and as I said works fine standalone). Does anyone have any advice on how to get my services to run together happily? Assume I am not concerned with isolating each service from each other in terms of security. I read on Amila's blog that some class loading settings can be modified but it's not clear exactly what ramifications it will have or if it will even help my problems. I am not sure if this is causing my problems, but due to wanting to be able to override the properties file in the .aar file when deployed in different environments, in the service lifecycle init method I attempt to find the properties file in the axis classpath before trying the .arr, using first axisService.getClass().getClassLoader(0.gerResourceAsStream(propsFilename); and if not found then using this.getClass().getClassLoader(0.gerResourceAsStream(propsFilename); Could this be messing up the class loading sequence, and if yes, how can I achieve the same effect without using the axis class loader first? thanks, charles On Dec 1, 2009, at 2:29 PM, Charles Galpin wrote: Hi Sameera Ok, this is starting to make a little more sense. I was not aware the WebappClassLoader could not see classes in the .aar. Can this be changed? I have access to the source of the client.corba.* packages, but they are just calling org.omg.CORBA.ORB.init which is doing the class loading and thats from rt.jar in the java distro afaik. The ORB loaded is a configurable option which is why it uses the class loader. Here is another exception stack you may find useful. I had run into this problem as well as various other classes not loading a while ago and made a few changes until getting my service working, and one of them was to pass -Djava.library.path=%PATH%;blahblah in on the commandline when starting tomcat. Removing this changes the error to a perhaps little more revealing message (after understanding about the TCCL limitation) 13:38:58 ERROR- Error initializing CORBA ORB. Unexpected CORBA error. org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation org.jacorb.orb.ORB vmcid: 0x0 minor code: 0 completed: No 13:38:58 DEBUG- Stack trace: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation org.jacorb.orb.ORB vmcid: 0x0 minor code: 0 completed: No at org.omg.CORBA.ORB.create_impl(ORB.java:297) at org.omg.CORBA.ORB.init(ORB.java:336) at client.corba.BaseCORBAApp.initCORBA(BaseCORBAApp.java:134) at client.corba.BaseCORBAService.startService(BaseCORBAService.java:100
Re: archive lib directory and 3rd party libraries (axis2/tomcat 6)
Charles, That might actually explain the issue. Here is some additional info: * ORB.init looks up classes from the thread context class loader (I checked that in the JRE sources). * ServiceTCCL=composite means that Axis2 sets the TCCL to the service class loader when entering a service method and resets it after the method exits. * A new thread that is being created inherits the TCCL from its parent thread (see Javadoc of java.lang.Thread). However, it is possible that Axis2 doesn't take the ServiceTCCL property into account when executing a lifecycle method (maybe that should be considered as a bug). This would mean that your thread ends up with the TCCL set to the Web app class loader. Since the thread is managed by your service, you can obviously set the TCCL for that thread to whatever you want (It will have no impact on Axis2 nor on the servlet container). I would try to set it to the service class loader (You should be able to get a reference to that class loader from the parameters passed to the lifecycle method). Andreas On Mon, Jan 25, 2010 at 21:28, Charles Galpin cgal...@lhsw.com wrote: It's just a thread spawned from the lifecycle init method using new Thread()… The general idea is we have an existing code base that used to be launched as commandline apps. I am now launching them in a thread from my web services, and web enabling them. Admittedly there were not designed or built to be used this way, but I don't think there should be anything stopping me from doing this. The Corba initialization occurs in the client.corba.* packages, but they are just calling org.omg.CORBA.ORB.init which is doing the class loading and thats from rt.jar in the java distro afaik. The ORB loaded is a configurable option which is why it uses the class loader (IE not in my control). I got past this one by putting the corba.jar into WEB-INF/lib. The SQLException I describe below occurs when a call is made to DriveManager.getConnection(..) and works fine loading a single service/.aar charles On Jan 25, 2010, at 3:12 PM, Andreas Veithen wrote: Charles, According to the stack trace you posted, the error occurs inside a thread that is neither managed by the servlet container, nor by Axis2: 13:38:58 DEBUG- Stack trace: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation org.jacorb.orb.ORB vmcid: 0x0 minor code: 0 completed: No at org.omg.CORBA.ORB.create_impl(ORB.java:297) at org.omg.CORBA.ORB.init(ORB.java:336) at client.corba.BaseCORBAApp.initCORBA(BaseCORBAApp.java:134) at client.corba.BaseCORBAService.startService(BaseCORBAService.java:100) at client.project.dcol.publish.corba.WebServiceDataCollectionService.webInit(WebServiceDataCollectionService.java:170) at client.project.dcol.GDPI.ServiceBase$ServiceThread.run(ServiceBase.java:318) at java.lang.Thread.run(Thread.java:619) How and where is this thread created? Andreas On Mon, Jan 25, 2010 at 20:23, Charles Galpin cgal...@lhsw.com wrote: Thanks Andreas I added this to both services being loaded, rebuilt and ran, but no change. The composite class loader was one of the options described in Amil's blog and as I understand it, it is supposed to use both the TCCL and the service class loader. But I guess I still don't understand the class loading because this jar is in all the places the class loaders should be looking so I don't see how it matters which one it uses. I also tried the EnableChildFirstClassLoading parameter as well but no help. Thanks, charles On Jan 25, 2010, at 1:53 PM, Andreas Veithen wrote: Try adding the following parameter on the service: parameter name=ServiceTCCL locked=falsecomposite/parameter Andreas On Mon, Jan 25, 2010 at 18:22, Charles Galpin cgal...@lhsw.com wrote: Hi All I am still running into problems with this. I previously moved all the jars I needed into the WEB-INF/lib directory and was able to continue working. But as I add more services (more .aar files) I am now running into strange unpredictable differences that I do not understand. For example, I have two services packaged in their own .aar files and if deployed independently they run just fine. Simply deploying both together causes the second one loaded to have mysterious problems like a java.sql.SQLException no suitable driver found for jdbc:sqlserver://.. when the sql3jdbc jar file is in both the .aar and WEB-INF/lib directory and (and as I said works fine standalone). Does anyone have any advice on how to get my services to run together happily? Assume I am not concerned with isolating each service from each other in terms of security. I read on Amila's blog that some class loading settings can be modified but it's not clear exactly what ramifications it will have or if it will even help my problems. I am not sure if this is causing my problems, but due to wanting to be able to override
Re: archive lib directory and 3rd party libraries (axis2/tomcat 6)
On Mon, Jan 25, 2010 at 22:15, Charles Galpin cgal...@lhsw.com wrote: Hi Andreas I tried setting the TCCL to both the class loader of the service context as well as the service group context before starting the threaD, but still no change. I guess this leaves me with a couple of questions. 1. Do subsequent threads spawned inherit the same TCCL? I'm pretty sure other threads are spawned by this thread which then go on to do the work. I think that the constructor of java.lang.Thread takes over the TCCL from the current thread. The Javadoc of java.lang.Thread should give a detailed explanation of this. 2. How can I tell what class loader is being used? Just log whatever this.getClassLoader() returns anywhere I care? Thread.currentThread().getContextClassLoader() (not to be confused with Class#getClassLoader()) 3. Is init perhaps the wrong place to be firing this off? I originally tried in the startUp method but iirc member variables initialized here were not retained when the service methods were invoked. Unfortunately I'm not familiar enough with the lifecycle methods to answer that question. thanks, charles On Jan 25, 2010, at 3:57 PM, Andreas Veithen wrote: Charles, That might actually explain the issue. Here is some additional info: * ORB.init looks up classes from the thread context class loader (I checked that in the JRE sources). * ServiceTCCL=composite means that Axis2 sets the TCCL to the service class loader when entering a service method and resets it after the method exits. * A new thread that is being created inherits the TCCL from its parent thread (see Javadoc of java.lang.Thread). However, it is possible that Axis2 doesn't take the ServiceTCCL property into account when executing a lifecycle method (maybe that should be considered as a bug). This would mean that your thread ends up with the TCCL set to the Web app class loader. Since the thread is managed by your service, you can obviously set the TCCL for that thread to whatever you want (It will have no impact on Axis2 nor on the servlet container). I would try to set it to the service class loader (You should be able to get a reference to that class loader from the parameters passed to the lifecycle method). Andreas
Re: Axis2 1.5.1 Upgrade Problem with Spring and Jetty 7
The following line indicates that the XMLInputFactory class is not from the org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 artifact (Geronimo's version has fewer than 158 lines): at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:158) Try to figure out where this class is loaded from. Andreas On Fri, Jan 15, 2010 at 19:12, jcaristi jcari...@whisolutions.com wrote: iksrazal wrote: Do you have a Caused by section in your stacktrace? Anyways, one thing to check is to make sure you have the right stax-api and wstx-asl jars in your classpath. - R There is no caused by section. Also, it looks like these jars are dependencies of only the axis2-spring jar. A search of the Maven dependency:tree for stax and wstx lists only one for each, both under axis2-spring. I checked the WEB-INF lib folder of the generated WAR, and there are no other stax or wstx jars there. Here is the axis2-spring section of the dependency tree: [INFO] +- org.apache.axis2:axis2-spring:jar:1.5.1:compile [INFO] | +- org.apache.ws.commons.axiom:axiom-api:jar:1.2.8:compile [INFO] | | +- org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.1:compile [INFO] | | +- org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.2:compile [INFO] | | \- jaxen:jaxen:jar:1.1.1:compile [INFO] | +- org.apache.ws.commons.axiom:axiom-impl:jar:1.2.8:compile [INFO] | +- org.apache.ws.commons.axiom:axiom-dom:jar:1.2.8:compile [INFO] | +- xalan:xalan:jar:2.7.0:compile [INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.4:compile [INFO] | +- org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1:compile [INFO] | +- commons-io:commons-io:jar:1.4:compile [INFO] | \- org.apache.axis2:axis2-kernel:jar:1.5.1:compile [INFO] | +- org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar:1.1.2:compile [INFO] | +- org.apache.geronimo.specs:geronimo-jta_1.1_spec:jar:1.1:compile [INFO] | +- javax.servlet:servlet-api:jar:2.3:compile [INFO] | +- commons-fileupload:commons-fileupload:jar:1.2:compile [INFO] | +- wsdl4j:wsdl4j:jar:1.6.2:compile [INFO] | +- org.apache.ws.commons.schema:XmlSchema:jar:1.4.3:compile [INFO] | +- org.apache.woden:woden-api:jar:1.0M8:compile [INFO] | | \- xerces:xmlParserAPIs:jar:2.6.0:compile [INFO] | \- org.apache.woden:woden-impl-dom:jar:1.0M8:compile -- View this message in context: http://old.nabble.com/Axis2-1.5.1-Upgrade-Problem-with-Spring-and-Jetty-7-tp27180100p27181273.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Axis2 1.5.1 service handling is very slow
The type of databinding cannot account for this delay. I would suggest to take a thread dump and try to understand where Axis2 is blocking. Andreas On Wed, Jan 13, 2010 at 13:04, Bruno Simioni brunosimi...@gmail.com wrote: Maybe using JAXB annotations on Java return objects, you can speed up the process. Bruno. On Wed, Jan 13, 2010 at 9:51 AM, Martin Gerner martin.ger...@postgrad.manchester.ac.uk wrote: Hi all, I'm running a simple web service which receives a string from the client, processes it and returns an array of custom objects (nothing complicated, they're just data holders containing a few ints, strings and booleans). While the actual serverside processing performed by my server code is performed very fast, the response times from the server are very large and seem to be linear in the number of returned objects. A short example: if I send a string to the server which results in 0 objects being returned, the response from the server is received just a few milliseconds after the request is made. If the string is modified such that it returns one object, that increases to 8 seconds, and if it returns two objects it increases to 16 seconds. In all cases, I can see that the actual processing takes less than a second, so the web service java code that I've deployed is handling the requests quickly. All responses are small in size - the largest is ~900 bytes (so I can't imagine that it's an XML transformation issue). Using packet sniffers, I can see that the delay definitely is occurring on the server side (for the last example, I could see the POST packet going to the server, and then the response packet coming back 16 seconds later). Going by client and server log timings, I can see that the delay occurs after processing rather than before. I'm running axis2 1.5.1 with default settings, have tested it running on both the bundled SimpleAxisServer and Tomcat (both on a Debian server) and am using a very simple client based on code auto-generated by axis from the WSDL (running in Windows). Does anybody here have any clue as to what's causing the delays? It seems clear enough that it's something in the internal axis2 system, but as I'm quite new to axis2 I'm having difficulties locating the issue. Best wishes, Martin Gerner
Re: JAXB (2.1) and AXIS2 (1.5.1)
This probably means that JAXB is trying to look up ObjectFactory and jaxb.index from the wrong class loader. This may happen if the JAXB JARs are loaded by the application class loader, while the generated code is loaded from the service class loader. One solution would be to use the variant of the JAXBContext.newInstance method that takes a class loader as parameter. Andreas On Wed, Jan 13, 2010 at 13:28, Oded Onn oded@mobixell.com wrote: Hi, I am deploying a WS under tomcat 5.5 and Java JDK is 1.5.0_08. I use some external jars that include code which was generated with JAXB 2.1 (using Ant XJC Task). The code is built from the xml schema without any error using the same JAXB libs as used in Axis2: jaxb-xjc-2.1.7.jar activation-1.1.jar jaxb-api-2.1.jar jaxb-impl-2.1.7.jar jsr173_api.jar When calls (client requests) to the server are made, the code try to get a marshaller for a class that is derived from the schema myMarshaller = JAXBContext.newInstance(fromShema.class.getPackage().getName()).createMarshaller(); Upon creation of the JAXBContext, the server throws the exception: java.lang.ExceptionInInitializerError . . . Caused by: java.lang.IllegalStateException: javax.xml.bind.JAXBException: com.mobixell.mwc.acquisitionconfiguration.schema doesnt contain ObjectFactory.class or jaxb.index . . . Caused by: javax.xml.bind.JAXBException: com.mobixell.mwc.acquisitionconfiguration.schema doesnt contain ObjectFactory.class or jaxb.index at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:183) 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:585) at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:133) at javax.xml.bind.ContextFinder.find(ContextFinder.java:286) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244) at com.mobixell.mwc.psm.AcquisitionDatabase.init(AcquisitionDatabase.java:69) ... 14 more Originally, the auto-generated jars were not created with the jaxb.index file. I understand that it is not a must to have a jaxb.index if you have an ObjectFactory class. However, I tried adding the appropriate jaxb.index files anyway, and it still doesn’t work. Any ideas why Axis2 has problems with the JAXB generated classes? I am really lost on that one and would appreciate any help. Thanks! Oded
Re: Building axis2-1.5.1 with maven2 fails, due to wrong repos?
Maybe it helps to empty the /home/kadmin/.m2/repository/org/apache/ws/commons/axiom folder to force Maven to download the corrupted artifacts again. Andreas On Wed, Jan 13, 2010 at 12:14, Patrick Kirsch p-kir...@gmx.de wrote: Hey, I know it is a silly question but I'm facing the following problem: when I'm trying to build axis-1.5.1 from the source with maven2 (mvn install as in /1/) it fails due to it could not download the dependencies. - See: http://ws.zones.apache.org/repository2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom [INFO] Unable to find resource 'org.apache.maven.shared:file-management:pom:1.2' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://repo1.maven.org/maven2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom Downloading: http://ws.zones.apache.org/repository2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom [INFO] Unable to find resource 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://ws.zones.apache.org/repository2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom [INFO] Unable to find resource 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository apache-ws-snapshots2 (http://ws.zones.apache.org/repository2) Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom [INFO] Unable to find resource 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository) Downloading: http://repo1.maven.org/eclipse/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom [INFO] Unable to find resource 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository eclipse-repo (http://repo1.maven.org/eclipse) etc. ... - afterwards it stops with: [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure error: error reading /home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar; error in opening zip file error: error reading /home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-impl/1.2.8/axiom-impl-1.2.8.jar; error in opening zip file error: error reading I guess I'm using a wrong repository although I did not change anything of the defaults coming along with axis2-1.5.1-src.zip. This leads me to another question, how did you set up your axis2 build environment? (I'm aware of Maven HowTos, eg. http://maven.apache.org/run-maven/index.html and http://ws.apache.org/axis2/maven-help.html /1/, but they didn't helped me further) Thanks and Regards, Patrick
Re: Building axis2-1.5.1 with maven2 fails, due to wrong repos?
Now I remember. The problem occurs because java.net messed up their repository. On the trunk we fixed that [1]. You will have to do the same change to the 1.5.1 sources (or set up something in your Maven settings.xml to override the settings in Axis2). Andreas [1] http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/parent/pom.xml?r1=835405r2=835404pathrev=835405 On Wed, Jan 13, 2010 at 14:01, Patrick Kirsch p-kir...@gmx.de wrote: Andreas Veithen schrieb: Maybe it helps to empty the /home/kadmin/.m2/repository/org/apache/ws/commons/axiom folder to force Maven to download the corrupted artifacts again. Well it turns out that: /home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar contains: title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://download.java.net/maven/1/org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar;here/a./p hr addressApache Server at maven-repository.dev.java.net Port 443/address BUT, the given redirect results on the host download.java.net in 404: Not Found The requested object does not exist on this server. The link you followed is either outdated, inaccurate, or the server has been instructed not to let you have it. Now, I see none of the requested mirrors does provide the axiom package in this version 1.2.8. requested are: http://ws.zones.apache.org/repository2, http://tomcat.apache.org/dev/dist/m2-repository, http://repo1.maven.org/eclipse. See: http://ws.zones.apache.org/repository2/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar [INFO] Unable to find resource 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository ws-zones (http://ws.zones.apache.org/repository2) Downloading: http://ws.zones.apache.org/repository2/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar [INFO] Unable to find resource 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository apache-ws-snapshots2 (http://ws.zones.apache.org/repository2) Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar [INFO] Unable to find resource 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository) Downloading: http://repo1.maven.org/eclipse/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar [INFO] Unable to find resource 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository eclipse-repo (http://repo1.maven.org/eclipse) Downloading: https://maven-repository.dev.java.net/nonav/repository//org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar 373b downloaded (axiom-api-1.2.8.jar) [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '047b09bdb4cff4f03d94f2390bc3fa79c659ec99'; remote = '!DOCTYPE' - RETRYING Downloading: https://maven-repository.dev.java.net/nonav/repository//org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar 373b downloaded (axiom-api-1.2.8.jar) Does anyone catches this problem? Andreas Regards, Patrick
Re: MTOM causes ADBException: Unexpected subelement
I fixed multiple issues with MTOM and ADB after the 1.5 branch was created. Can you test this service with an Axis2 snapshot? Andreas On Tue, Jan 12, 2010 at 03:48, Mike Borozdin mi...@docusign.com wrote: Hi! I have a Java Axis2 client that seems to encounter an error on the same exact XML structure if part of it is moved into an MTOM attachment. The more complete stack is cited at the end. I have checked the WSDL and the response complies with the response XML for more info on the WSDL you can get it here. https://demo.docusign.net/api/3.0/api.asmx?WSDL The way the web service is configured is that it will only generate an MTOM attachment if the subelement exceeds a certain size. I am attaching Example1 and Example2 which show working vs. not working. Axis Libraries used are 1.5.1. Does anyone have any idea what could be causing this? The element that's triggering an exception is Label.../Label Thank you! WORKING RESPONSE soap:Envelope xmlns:xop=http://www.w3.org/2004/08/xop/include; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; soap:Header wsa:Actionhttp://www.docusign.net/API/3.0/RequestStatusResponse/wsa:Action wsa:MessageIDurn:uuid:48cbb69a-9357-4745-bc1f-83c736ba1d90/wsa:MessageID wsa:RelatesTourn:uuid:04ade417-d078-4e64-a047-0bf7876b43fd/wsa:RelatesTo wsa:Tohttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:To wsse:Security wsu:Timestamp wsu:Id=Timestamp-a8485bff-bc8d-463c-ab75-91f3e925e94e wsu:Created2010-01-11T20:41:51Z/wsu:Created wsu:Expires2010-01-11T20:46:51Z/wsu:Expires /wsu:Timestamp /wsse:Security /soap:Header soap:Body RequestStatusResponse xmlns=http://www.docusign.net/API/3.0; RequestStatusResult RecipientStatuses RecipientStatus TypeSigner/Type Emailnolongema...@gmail.com/Email UserNameMike Borozdin/UserName RoutingOrder1/RoutingOrder Sent2010-01-11T12:41:14.62/Sent Delivered2010-01-11T12:41:21.013/Delivered Signed2010-01-11T12:41:50.12/Signed DeclineReason xsi:nil=true / StatusCompleted/Status RecipientIPAddress97.65.97.246/RecipientIPAddress ClientUserIdunknown-web-user/ClientUserId IDCheckInformation AddressInformation Street193 S Jackson St/Street1 Street2#8329/Street2 CitySeattle/City StateWA/State Zip98102/Zip /AddressInformation SSN4Information SSN4X0LT+NRxPAvOz0U6NcLadg==/SSN4 /SSN4Information /IDCheckInformation CustomFields / TabStatuses TabStatus TabTypeSignHere/TabType StatusSigned/Status XPosition135/XPosition YPosition283/YPosition TabLabel / TabName / TabValue / /TabStatus TabStatus TabTypeDateSigned/TabType StatusSigned/Status XPosition683/XPosition YPosition333/YPosition TabLabel / TabName / TabValue1/11/2010/TabValue /TabStatus TabStatus TabTypeFullName/TabType StatusSigned/Status XPosition141/XPosition YPosition420/YPosition TabLabel / TabName / TabValueMike Borozdin/TabValue /TabStatus TabStatus TabTypeTitle/TabType StatusSigned/Status XPosition689/XPosition YPosition422/YPosition TabLabelJob Title/TabLabel TabName / TabValuetest/TabValue /TabStatus TabStatus TabTypeCompany/TabType StatusSigned/Status XPosition664/XPosition YPosition616/YPosition TabLabel / TabName / TabValuetest/TabValue /TabStatus TabStatus TabTypeCustom/TabType StatusActive/Status XPosition906/XPosition YPosition693/YPosition TabLabelBusiness Type/TabLabel TabNameRadio Button/TabName TabValue / /TabStatus TabStatus TabTypeCustom/TabType StatusActive/Status XPosition1045/XPosition
Re: Axis2 1.5.1 service handling is very slow
The issue seems to be as follows: * For POJO services, Axis2 uses the JRE's bean introspector to detect the properties of the POJOs. * Following the Java Beans standard, the introspector attempts to find BeanInfo classes corresponding to these POJOs. BeanInfo classes are optional and rarely used in this context. * Axis2 uses the service class loader to introspect the beans. This is not a standard class loader, but a component specific to Axis2 (DeploymentClassLoader) which uses a different strategy to load the classes. I had a quick look at the code, and it appears that in order to load a class, it needs to scan all the JARs used by the service archive. Conclusion: in this case, Axis2 repeatedly attempts to load non existing classes from a class loader that uses a suboptimal strategy to load resources from JARs. Unfortunately, I'm not very familiar with the POJO and class loading parts of Axis2. Maybe some of the other developers can shed some light on the following questions: * Shouldn't the POJO code cache the results returned by the bean introspector? * Why is the DeploymentClassLoader implemented in this way? My guess is that it is to avoid file locking issues. Thus, it is only used when hot deployment is enabled? Andreas On Wed, Jan 13, 2010 at 15:24, Martin Gerner martin.ger...@postgrad.manchester.ac.uk wrote: I've attached a full thread dump. I'd greatly appreciate any help in determining the cause, as I'm quite a novice when it comes to Axis2 and its internal workings. CPU usage for the java process goes up to 100% when it's blocking. The top parts of a few dumps (taken at different times to get an idea about whether it's the same thing blocking): HttpConnection-8080-1 prio=10 tid=0x08c06c00 nid=0x1c77 runnable [0x2e9fe000] java.lang.Thread.State: RUNNABLE at java.util.zip.Inflater.inflateBytes(Native Method) at java.util.zip.Inflater.inflate(Inflater.java:223) - locked 0xa65b86e0 (a java.util.zip.Inflater) at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:135) at java.util.zip.ZipInputStream.read(ZipInputStream.java:146) at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92) at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70) at org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:198) at org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:178) at org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:81) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) - locked 0x34220a70 (a org.apache.axis2.deployment.DeploymentClassLoader) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.beans.Introspector.instantiate(Introspector.java:1453) [...] HttpConnection-8080-2 prio=10 tid=0x08a4fc00 nid=0x1cf6 runnable [0x2e9ad000] java.lang.Thread.State: RUNNABLE at java.util.zip.ZipInputStream.readFully(ZipInputStream.java:403) at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:361) at java.util.zip.ZipInputStream.read(ZipInputStream.java:148) at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92) at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70) at org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:198) at org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:178) at org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:81) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) - locked 0x342afa70 (a org.apache.axis2.deployment.DeploymentClassLoader) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.beans.Introspector.instantiate(Introspector.java:1453) Best wishes, Martin Gerner On 13/01/2010 12:30, Andreas Veithen wrote: The type of databinding cannot account for this delay. I would suggest to take a thread dump and try to understand where Axis2 is blocking. Andreas On Wed, Jan 13, 2010 at 13:04, Bruno Simioni brunosimi...@gmail.com wrote: Maybe using JAXB annotations on Java return objects, you can speed up the process. Bruno. On Wed, Jan 13, 2010 at 9:51 AM, Martin Gerner martin.ger...@postgrad.manchester.ac.uk wrote: Hi all, I'm running a simple web service which receives a string from the client, processes it and returns an array of custom objects (nothing complicated, they're just data holders containing a few ints, strings and booleans). While the actual serverside processing performed by my server code is performed very fast, the response times from the server are very large and seem to be linear in the number of returned objects. A short example: if I send a string to the server which results in 0 objects being returned
Re: Does Axiom support element ref attribute
Håkon,
Can you provide the full stack trace of the error?
Andreas
2010/1/5 Håkon Sagehaug hakon.sageh...@uni.no:
Hi
I think it was after, looks like the date for the patch was 30 of October,
and I tried it in December.
Håkon
2010/1/3 Andreas Veithen andreas.veit...@gmail.com
Håkon,
Was that with a snapshot before or after the change done by Amila [1].
Andreas
[1] http://svn.apache.org/viewvc?view=revisionrevision=831203
2009/12/22 Håkon Sagehaug hakon.sageh...@uni.no:
Hi
As far as I remember, the same as for axis 1.5.1 applies for
axis2-snapshot
cheers, håkon
2009/12/21 Andreas Veithen andreas.veit...@gmail.com
What about Axis2 snapshot with security enabled?
Andreas
2009/12/14 Håkon Sagehaug hakon.sageh...@uni.no:
Hi Andreas,
Set up that works,
schema looks like this(with the ref attribute)
xsd:element ref=eyb:MessageBoard minOccurs=0 /
Using axis2 1.5.1, using axiom 1.2.8.jar and security disabled
Not working
Using axis2 1.5.1, using axiom 1.2.8.jar and security enabled
hope this helps
cheers, Håkon
2009/12/12 Andreas Veithen andreas.veit...@gmail.com
Håkon,
I believe it is a problem in ADB (or was, because Amila implemented
a
workaround). Can you please let us know precisely which combinations
(Axis2 version; security enabled/disabled) work and which ones
don't?
Andreas
2009/12/11 Håkon Sagehaug hakon.sageh...@uni.no:
Hi Andreas,
Thanks for the pointer, it worked when I used the axis2 snapshot,
but
I
my
service I also have security enabled and then I got the same
message,
but I
guess from reading the thread that was expected.
Is this an issue for rampart, axis2 or axiom?
cheers, Hå
2009/12/10 Andreas Veithen andreas.veit...@gmail.com
This issue has been discussed here:
http://markmail.org/thread/w5yziktixvjn7ubl
Andreas
2009/12/10 Håkon Sagehaug hakon.sageh...@uni.no:
Hi all,
I had a element in a schema that referred another element like
this
xsd:element ref=eyb:MessageBoard minOccurs=0 /
So when I when I called my service and this element was
returned
the
serialization through an exception like this
[ERROR] Could not get parser from data source for element
{http://esysbio.org/service/UserManagement}GetUserResponse
javax.xml.stream.XMLStreamException: the prefix == Already
exists
for
namespace == http://esysbio.org/common/schema
I then changed my element to take the type instead of referring
to
the
element
xsd:element name=MessageBoard
type=eyb:MessageBoardType
minOccurs=0 /
Then the service returned the correct response. So i was
wondering
if
this
is a limitation of axiom?
I use axis2 .5 and axiom 1.2.8, also tried with
axiom-1.2.9-SNAPSHOT
but
same issue.
Any hint
cheers, Håkon
--
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
Re: Does Axiom support element ref attribute
Håkon,
Was that with a snapshot before or after the change done by Amila [1].
Andreas
[1] http://svn.apache.org/viewvc?view=revisionrevision=831203
2009/12/22 Håkon Sagehaug hakon.sageh...@uni.no:
Hi
As far as I remember, the same as for axis 1.5.1 applies for axis2-snapshot
cheers, håkon
2009/12/21 Andreas Veithen andreas.veit...@gmail.com
What about Axis2 snapshot with security enabled?
Andreas
2009/12/14 Håkon Sagehaug hakon.sageh...@uni.no:
Hi Andreas,
Set up that works,
schema looks like this(with the ref attribute)
xsd:element ref=eyb:MessageBoard minOccurs=0 /
Using axis2 1.5.1, using axiom 1.2.8.jar and security disabled
Not working
Using axis2 1.5.1, using axiom 1.2.8.jar and security enabled
hope this helps
cheers, Håkon
2009/12/12 Andreas Veithen andreas.veit...@gmail.com
Håkon,
I believe it is a problem in ADB (or was, because Amila implemented a
workaround). Can you please let us know precisely which combinations
(Axis2 version; security enabled/disabled) work and which ones don't?
Andreas
2009/12/11 Håkon Sagehaug hakon.sageh...@uni.no:
Hi Andreas,
Thanks for the pointer, it worked when I used the axis2 snapshot, but
I
my
service I also have security enabled and then I got the same message,
but I
guess from reading the thread that was expected.
Is this an issue for rampart, axis2 or axiom?
cheers, Hå
2009/12/10 Andreas Veithen andreas.veit...@gmail.com
This issue has been discussed here:
http://markmail.org/thread/w5yziktixvjn7ubl
Andreas
2009/12/10 Håkon Sagehaug hakon.sageh...@uni.no:
Hi all,
I had a element in a schema that referred another element like
this
xsd:element ref=eyb:MessageBoard minOccurs=0 /
So when I when I called my service and this element was returned
the
serialization through an exception like this
[ERROR] Could not get parser from data source for element
{http://esysbio.org/service/UserManagement}GetUserResponse
javax.xml.stream.XMLStreamException: the prefix == Already
exists
for
namespace == http://esysbio.org/common/schema
I then changed my element to take the type instead of referring to
the
element
xsd:element name=MessageBoard type=eyb:MessageBoardType
minOccurs=0 /
Then the service returned the correct response. So i was wondering
if
this
is a limitation of axiom?
I use axis2 .5 and axiom 1.2.8, also tried with
axiom-1.2.9-SNAPSHOT
but
same issue.
Any hint
cheers, Håkon
--
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
Re: axis2 configuration fine tuning: Local Transport and transportReceiver
Gennady, AxisServlet will always process requests received through the servlet container, and the transportReceiver settings in axis2.xml have no impact on this. These settings are only used to generate the proper endpoint URIs in the WSDL (original or generated). Note that this is only true for the servlet transport. For other transports, the transportReceiver settings also determine how the transport receives requests. Andreas On Tue, Dec 29, 2009 at 12:16, Gennady Shumakher gshumak...@gmail.com wrote: Andreas, thanks for clarification. According to AXIS2-4465 the documentation is on its way, but I'd like to be sure we configure that properly. I am running on 1.5.1 and would like to support both http, https and we use useOriginalwsdl=true (so wsdl is served as is, no generation). As I see from the code the AxisServlet does implements TransportListener directly that mentioned as problematic in AXIS2-4465... Anyhow the current behavior I face that if no explicit transportReceiver defined in axis2.xml the services both via http and https work as expected via the ports defined for web application and ?wsdl returns wsdl document. But if axis2.xml is configured as: transportReceiver name=default class=org.apache.axis2.transport.http.AxisServlet / the services http/s work well, but ?wsdl request fails with null exception. Do I miss something in configuration to make it work? Thanks, Gennady On Mon, Dec 28, 2009 at 07:36, wrote: Hi, I am fine tuning axis2 configuration for our use cases which are stateless web services available over http(s) only. Now I wonder regarding relevance of Local Transport settings in our scenario. Unfortunately I couldn't fine the documentation on that topic, but I suppose it is optimized for calls within the same web application? The local transport is primarily used in unit tests. Not sure if it is usable in a production environment. Additionally we embed axis2 within our web application. I successfully tested that in this case the default transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer can be removed so ports and other parameters are defined by web application connection. But I wonder how that works if I don't have any explicit configuration for transportReceiver, are there some defaults? The issue AXIS2-4465 sheds some light on how transport receivers are/were managed by AxisServlet. Thanks, Gennady
Re: java.util.date convertion to UnsignedInt problem
Ram,
You cannot convert the result of Date#getTime() to UnsignedInt because
UnsignedInt is a representation of the XML Schema type called
unsignedInt, and the value space of this type is limited to values
less than or equal to 4294967295 (see my link).
Andreas
On Mon, Dec 28, 2009 at 13:28, ram ram_ku...@yahoo.co.in wrote:
Hi,
Thanks andreas. But the below link could not solve my problem. Any one
pls suggest me how to fix this issue
Thanks Regards,
Ram
--- On Sat, 5/12/09, Andreas Veithen andreas.veit...@gmail.com wrote:
From: Andreas Veithen andreas.veit...@gmail.com
Subject: Re: java.util.date convertion to UnsignedInt problem
To: axis-user@ws.apache.org
Date: Saturday, 5 December, 2009, 4:04 PM
Please have a look at [1].
Andreas
[1] http://www.w3.org/TR/xmlschema-2/#unsignedInt
On Fri, Dec 4, 2009 at 17:13, Anup Mayank anup.may...@gmail.com wrote:
/** validate the value against the xsd definition */
79 public static boolean isValid(long iValue) {
80 return !((iValue 0L) || (iValue 4294967295L));
81 }
This is the source code of Unsigned int where it validates if a number is
of proper value or not. I am not sure how the particular max number is
chosen. But since your date value is out of range it is throwing exception.
Axis folks please explain this range?
Anup
On Fri, Dec 4, 2009 at 8:01 AM, ram ram_ku...@yahoo.co.in wrote:
Hi,
I am trying to convert java.util.date to UnsignedInt(). I am getting
NumberFormatException
I am fetching the date from database. I am converting unsignedInt() like
the following
new UnsignedInt(info.getdate.getTime())
when i print date i am getting 1259937492847. so where do i am
doing mistake.
Can any onehelp to fix this issue.
Thanks Regards,
Ram
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
Re: axis2 configuration fine tuning: Local Transport and transportReceiver
On Mon, Dec 28, 2009 at 07:36, Gennady Shumakher gshumak...@gmail.com wrote: Hi, I am fine tuning axis2 configuration for our use cases which are stateless web services available over http(s) only. Now I wonder regarding relevance of Local Transport settings in our scenario. Unfortunately I couldn't fine the documentation on that topic, but I suppose it is optimized for calls within the same web application? The local transport is primarily used in unit tests. Not sure if it is usable in a production environment. Additionally we embed axis2 within our web application. I successfully tested that in this case the default transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer can be removed so ports and other parameters are defined by web application connection. But I wonder how that works if I don't have any explicit configuration for transportReceiver, are there some defaults? The issue AXIS2-4465 sheds some light on how transport receivers are/were managed by AxisServlet. Thanks, Gennady
Re: Transfering CDATA with SOAP
There is a more thorough discussion of this feature in the user guide: http://people.apache.org/~veithen/axiom/userguide/ch04.html#factory.properties If thinks are still unclear after reading through this part of the guide, please feel free to ask more questions. Andreas On Thu, Dec 17, 2009 at 18:14, Florian Stegmaier steg...@dimis.fim.uni-passau.de wrote: Dear all, i´m using axis for transferring xml based data. Now i got the problem, that this data possibly contains a CDATA section. After looking around, i found a partial answer here: http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200904.mbox/%3c781947940.1240056795312.javamail.j...@brutus%3e Ok, this hints are quiet useful. With the help of setting the coalescing flag of the XMLInputFactory to false, i am able to store the CDATA section correctly in my OMElement. After that, i transfer it using ServiceClient.sendReceive(OMElement). And here is the next problem. After transmitting the OMElement, the CDATA fragment is gone at the receivers side and all XML related characters are escaped, e.g. by lt;. The bug report says, that i have to edit the global property file of the factories...but where should they be stored? Do i have to create it? How can i solve this problem? It would be nice, if anybody could help me with this issue. Best, Florian _ Dipl. Inf. Florian Stegmaier Chair of Distributed Information Systems University of Passau Innstr. 43 94032 Passau Room 248 ITZ Tel.: +49 851 509 3063 Fax: +49 851 509 3062 steg...@dimis.fim.uni-passau.de _ Quote of the week: Computer. This is a Class-A compulsory directive. Compute, to the last digit, the value of pi. (Spock)
Re: Does Axiom support element ref attribute
What about Axis2 snapshot with security enabled?
Andreas
2009/12/14 Håkon Sagehaug hakon.sageh...@uni.no:
Hi Andreas,
Set up that works,
schema looks like this(with the ref attribute)
xsd:element ref=eyb:MessageBoard minOccurs=0 /
Using axis2 1.5.1, using axiom 1.2.8.jar and security disabled
Not working
Using axis2 1.5.1, using axiom 1.2.8.jar and security enabled
hope this helps
cheers, Håkon
2009/12/12 Andreas Veithen andreas.veit...@gmail.com
Håkon,
I believe it is a problem in ADB (or was, because Amila implemented a
workaround). Can you please let us know precisely which combinations
(Axis2 version; security enabled/disabled) work and which ones don't?
Andreas
2009/12/11 Håkon Sagehaug hakon.sageh...@uni.no:
Hi Andreas,
Thanks for the pointer, it worked when I used the axis2 snapshot, but I
my
service I also have security enabled and then I got the same message,
but I
guess from reading the thread that was expected.
Is this an issue for rampart, axis2 or axiom?
cheers, Hå
2009/12/10 Andreas Veithen andreas.veit...@gmail.com
This issue has been discussed here:
http://markmail.org/thread/w5yziktixvjn7ubl
Andreas
2009/12/10 Håkon Sagehaug hakon.sageh...@uni.no:
Hi all,
I had a element in a schema that referred another element like this
xsd:element ref=eyb:MessageBoard minOccurs=0 /
So when I when I called my service and this element was returned the
serialization through an exception like this
[ERROR] Could not get parser from data source for element
{http://esysbio.org/service/UserManagement}GetUserResponse
javax.xml.stream.XMLStreamException: the prefix == Already exists
for
namespace == http://esysbio.org/common/schema
I then changed my element to take the type instead of referring to
the
element
xsd:element name=MessageBoard type=eyb:MessageBoardType
minOccurs=0 /
Then the service returned the correct response. So i was wondering if
this
is a limitation of axiom?
I use axis2 .5 and axiom 1.2.8, also tried with axiom-1.2.9-SNAPSHOT
but
same issue.
Any hint
cheers, Håkon
--
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science(BCCS)
Uni BCCS/Uni Research
hakon.sageh...@uni.no, phone +47 55584125
Re: UNSUBSCRIBE
Please send a mail to axis-user-unsubscr...@ws.apache.org On Mon, Dec 21, 2009 at 20:34, Luke Balding lbald...@gbehavior.com wrote:
Re: Services.xml
You can set the AxisService.SUPPORT_SINGLE_OP flag so that all messages are routed to the single operation defined by the service. Andreas On Fri, Dec 18, 2009 at 02:16, Rahul Rulz ragul...@yahoo.com wrote: Hi Deepal, Thanks for your reply..Yes what you have pointed is right. Is there any ways I could remove the action from the service URL so that any action with respect to a service comes into the same message receiver..? I mean irrespective of the action(even null),all the messages should be directed to the message receiver that handles the service..? Thanks, Rahul. --- On Fri, 12/18/09, Deepal jayasinghe deep...@gmail.com wrote: From: Deepal jayasinghe deep...@gmail.com Subject: Re: Services.xml To: axis-user@ws.apache.org Date: Friday, December 18, 2009, 6:29 AM Hi Rahul, I forgot something, if you have the operation name as part of the url then you do not need to worry too much about the SOAPAction. For example say you have a service called Foo and an operation called xyz, then if you have the service url as follows, then Axis2 will do the right thing. http://localhost:8080/axis2/services/Foo/xyz Thanks, Deepal Hi Deepal, thanks for your reply. I had a look at the dispatchers and there are 3 among them which would do 1. SOAPActionBasedDispatcher - The requests would contain SOAPAction as NULL too. How do I go about for this case 2. AddressingBasedDispatcher - NA in this case 3. SOAPMessageBodyBasedDispatcher - NA in this case. Below is my services.xml which works in this way: Am able to have any Action mapping provided i include that operation in the endpoint i.e normal endpoint : http://localhost:8080/axis2/services/myService whereas to achieve the result for any SOAPaction http://localhost:8080/axis2/services/myService/Action * service name=myService scope=application description InoutMessage receiver myservice /description module ref=module1/ messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=sample.api.service.myServiceInOutMessageReceiver/ /messageReceivers operation name=operation1 mep=http://www.w3.org/2004/08/wsdl/in-out; class=sample.api.service. myServiceInOutMessageReceiver actionMappingAction/actionMapping /operation /service * * *Can you please guide me as to how I can change the above to suit the requirement..If am Action from the endpoint and include somewhere in the codes,it would be great. Thanks, Rahul. --- On *Fri, 12/18/09, Deepal Jayasinghe /dee...@opensource.lk/* wrote: From: Deepal Jayasinghe dee...@opensource.lk Subject: Re: Services.xml To: axis-user@ws.apache.org Date: Friday, December 18, 2009, 4:52 AM For that you need to create a dispatcher (a handler). If you are familiar with Axis2 code base you can look at some of the default dispatchers and modify that to suite for your requirement. In fact we have dispatcher called SOAPActionBased dispatcher, that would be the ideal one. Thanks., Deepal Rahul Rulz wrote: Hello Axis2 Users, I have created the service from scratch and am using InOut message receiver for the same. I would like to call the message receiver for the requests which comes in with any SOAP action or null Soap action. Could any one tell me the way to achieve this... Thanks, Rahul. -- Thank you! http://blogs.deepal.org http://deepal.org -- Thank you! http://blogs.deepal.org http://deepal.org
Re: Does Axiom support element ref attribute
Håkon,
I believe it is a problem in ADB (or was, because Amila implemented a
workaround). Can you please let us know precisely which combinations
(Axis2 version; security enabled/disabled) work and which ones don't?
Andreas
2009/12/11 Håkon Sagehaug hakon.sageh...@uni.no:
Hi Andreas,
Thanks for the pointer, it worked when I used the axis2 snapshot, but I my
service I also have security enabled and then I got the same message, but I
guess from reading the thread that was expected.
Is this an issue for rampart, axis2 or axiom?
cheers, Hå
2009/12/10 Andreas Veithen andreas.veit...@gmail.com
This issue has been discussed here:
http://markmail.org/thread/w5yziktixvjn7ubl
Andreas
2009/12/10 Håkon Sagehaug hakon.sageh...@uni.no:
Hi all,
I had a element in a schema that referred another element like this
xsd:element ref=eyb:MessageBoard minOccurs=0 /
So when I when I called my service and this element was returned the
serialization through an exception like this
[ERROR] Could not get parser from data source for element
{http://esysbio.org/service/UserManagement}GetUserResponse
javax.xml.stream.XMLStreamException: the prefix == Already exists for
namespace == http://esysbio.org/common/schema
I then changed my element to take the type instead of referring to the
element
xsd:element name=MessageBoard type=eyb:MessageBoardType
minOccurs=0 /
Then the service returned the correct response. So i was wondering if
this
is a limitation of axiom?
I use axis2 .5 and axiom 1.2.8, also tried with axiom-1.2.9-SNAPSHOT but
same issue.
Any hint
cheers, Håkon
--
Re: Does Axiom support element ref attribute
This issue has been discussed here: http://markmail.org/thread/w5yziktixvjn7ubl
Andreas
2009/12/10 Håkon Sagehaug hakon.sageh...@uni.no:
Hi all,
I had a element in a schema that referred another element like this
xsd:element ref=eyb:MessageBoard minOccurs=0 /
So when I when I called my service and this element was returned the
serialization through an exception like this
[ERROR] Could not get parser from data source for element
{http://esysbio.org/service/UserManagement}GetUserResponse
javax.xml.stream.XMLStreamException: the prefix == Already exists for
namespace == http://esysbio.org/common/schema
I then changed my element to take the type instead of referring to the
element
xsd:element name=MessageBoard type=eyb:MessageBoardType
minOccurs=0 /
Then the service returned the correct response. So i was wondering if this
is a limitation of axiom?
I use axis2 .5 and axiom 1.2.8, also tried with axiom-1.2.9-SNAPSHOT but
same issue.
Any hint
cheers, Håkon
--
Re: Axis2 1.4 not preserving CDATA
On Mon, Dec 7, 2009 at 23:43, Ramya K Grama ramyakgr...@gmail.com wrote: I dont understand. It is a simple case where a Axis2 webservice, implemented with XMLBeans databinding, needs to send CDATA out in the response XML, preserved/intact - without characters being escaped. This is not supported since in the context of a Web service, since this is not a valid requirement (because the consumer must not make a difference between a CDATA section and an equivalent text node). If you have a consumer of your service that requires a CDATA section, you should challenge that requirement. And from what I understood from your previous reply is that this can be done by using AXIOM APIs to set the contentType to CDATA. Which makes sense to me, but need some help with the API - how could one get hold of the underlying AXIOM element from XMLBeans inorder to set the contenttype to CDATA. You will have to inspect the generated code to see if it is possible to get hold of the OMElement produced from the bean. On Mon, Dec 7, 2009 at 5:09 PM, Andreas Veithen andreas.veit...@gmail.com wrote: I'm not aware of any XML data binding framework that would allow you to control whether something is serialized as a text node or a CDATA section. This is by design, because the difference between a text node and a CDATA section is only syntactic, but has no semantic meaning. This implies that any system that processes a CDATA section differently from an equivalent text node should be considered as broken. At least that is the what most people in the industry believe. Andreas On Mon, Dec 7, 2009 at 21:49, Ramya K Grama ramyakgr...@gmail.com wrote: Thanks for the quick reply! I am using XMLBeans 2.3.0. I am not using AXIOM APIs directly to create the response elements. Hence, I am not using OMText directly. From the XMLBean api, I am able to use only setText and have not found a way to passin the CDATA type (neither in an overloaded setText nor in a setType). Could you please share a code snippet showing how to pass the CDATA type using XMLBeans or how to get the OMText node from the XMLBean object. With XMLBeans I have operationNameDocument object. How do I get an OMText out of it to be able to set the Type. On Mon, Dec 7, 2009 at 3:39 PM, Andreas Veithen andreas.veit...@gmail.com wrote: XMLInputFactory.properties can be used to preserve CDATA sections when using Axiom to _parse_ an XML document (By default CDATA sections are transformed to text nodes and coalesced with adjacent text nodes). On the other hand, creating CDATA sections in output documents is something that Axiom has always supported. Probably what you are doing is to create an OMText node with type TEXT and content ![CDATA[ROSEANNA]]. In the output document, this gets of course escaped. What you need to do instead is to create an OMText node with type CDATA and content ROSEANNA. Andreas On Mon, Dec 7, 2009 at 20:45, Ramya K Grama ramyakgr...@gmail.com wrote: Hello, We have been having issues with CDATA not being preserved by Axis2. In the response xml, the '' are escaped to 'lt;' So instead of someTagName![CDATA[ROSEANNA]]/someTagName we get someTagNamelt;![CDATA[ROSEANNA]]gt;/someTagName in the response. Reading this http://people.apache.org/~veithen/synapse/faq.html#cdata suggestion, we tried creating XMLInputFactory.properties file containing this single line - javax.xml.stream.isCoalescing=false and placed the file under WEB-INF/classes and retried, again the same result. We are using Axis21.4, XMLBeans 2.3.0, Tomcat 6. The other idea was to programatically replace the escape characters using regular expressions - which I think is really not needed. Any help is highly appreciated.
Re: Axis2 1.4 not preserving CDATA
XMLInputFactory.properties can be used to preserve CDATA sections when using Axiom to _parse_ an XML document (By default CDATA sections are transformed to text nodes and coalesced with adjacent text nodes). On the other hand, creating CDATA sections in output documents is something that Axiom has always supported. Probably what you are doing is to create an OMText node with type TEXT and content ![CDATA[ROSEANNA]]. In the output document, this gets of course escaped. What you need to do instead is to create an OMText node with type CDATA and content ROSEANNA. Andreas On Mon, Dec 7, 2009 at 20:45, Ramya K Grama ramyakgr...@gmail.com wrote: Hello, We have been having issues with CDATA not being preserved by Axis2. In the response xml, the '' are escaped to 'lt;' So instead of someTagName![CDATA[ROSEANNA]]/someTagName we get someTagNamelt;![CDATA[ROSEANNA]]gt;/someTagName in the response. Reading this http://people.apache.org/~veithen/synapse/faq.html#cdata suggestion, we tried creating XMLInputFactory.properties file containing this single line - javax.xml.stream.isCoalescing=false and placed the file under WEB-INF/classes and retried, again the same result. We are using Axis21.4, XMLBeans 2.3.0, Tomcat 6. The other idea was to programatically replace the escape characters using regular expressions - which I think is really not needed. Any help is highly appreciated.
Re: Axis2 1.4 not preserving CDATA
I'm not aware of any XML data binding framework that would allow you to control whether something is serialized as a text node or a CDATA section. This is by design, because the difference between a text node and a CDATA section is only syntactic, but has no semantic meaning. This implies that any system that processes a CDATA section differently from an equivalent text node should be considered as broken. At least that is the what most people in the industry believe. Andreas On Mon, Dec 7, 2009 at 21:49, Ramya K Grama ramyakgr...@gmail.com wrote: Thanks for the quick reply! I am using XMLBeans 2.3.0. I am not using AXIOM APIs directly to create the response elements. Hence, I am not using OMText directly. From the XMLBean api, I am able to use only setText and have not found a way to passin the CDATA type (neither in an overloaded setText nor in a setType). Could you please share a code snippet showing how to pass the CDATA type using XMLBeans or how to get the OMText node from the XMLBean object. With XMLBeans I have operationNameDocument object. How do I get an OMText out of it to be able to set the Type. On Mon, Dec 7, 2009 at 3:39 PM, Andreas Veithen andreas.veit...@gmail.com wrote: XMLInputFactory.properties can be used to preserve CDATA sections when using Axiom to _parse_ an XML document (By default CDATA sections are transformed to text nodes and coalesced with adjacent text nodes). On the other hand, creating CDATA sections in output documents is something that Axiom has always supported. Probably what you are doing is to create an OMText node with type TEXT and content ![CDATA[ROSEANNA]]. In the output document, this gets of course escaped. What you need to do instead is to create an OMText node with type CDATA and content ROSEANNA. Andreas On Mon, Dec 7, 2009 at 20:45, Ramya K Grama ramyakgr...@gmail.com wrote: Hello, We have been having issues with CDATA not being preserved by Axis2. In the response xml, the '' are escaped to 'lt;' So instead of someTagName![CDATA[ROSEANNA]]/someTagName we get someTagNamelt;![CDATA[ROSEANNA]]gt;/someTagName in the response. Reading this http://people.apache.org/~veithen/synapse/faq.html#cdata suggestion, we tried creating XMLInputFactory.properties file containing this single line - javax.xml.stream.isCoalescing=false and placed the file under WEB-INF/classes and retried, again the same result. We are using Axis21.4, XMLBeans 2.3.0, Tomcat 6. The other idea was to programatically replace the escape characters using regular expressions - which I think is really not needed. Any help is highly appreciated.
Re: java.util.date convertion to UnsignedInt problem
Please have a look at [1].
Andreas
[1] http://www.w3.org/TR/xmlschema-2/#unsignedInt
On Fri, Dec 4, 2009 at 17:13, Anup Mayank anup.may...@gmail.com wrote:
/** validate the value against the xsd definition */
79 public static boolean isValid(long iValue) {
80 return !((iValue 0L) || (iValue 4294967295L));
81 }
This is the source code of Unsigned int where it validates if a number is of
proper value or not. I am not sure how the particular max number is chosen.
But since your date value is out of range it is throwing exception. Axis
folks please explain this range?
Anup
On Fri, Dec 4, 2009 at 8:01 AM, ram ram_ku...@yahoo.co.in wrote:
Hi,
I am trying to convert java.util.date to UnsignedInt(). I am getting
NumberFormatException
I am fetching the date from database. I am converting unsignedInt() like
the following
new UnsignedInt(info.getdate.getTime())
when i print date i am getting 1259937492847. so where do i am
doing mistake.
Can any onehelp to fix this issue.
Thanks Regards,
Ram
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
Re: [axis2:UTF-8]
Axis2 of course does handle charset encoding correctly. However this
only works if the request conforms to the SOAP specs. If you have
encoding issues, this almost certainly means that the Web service
_client_ is broken.
Andreas
On Wed, Dec 2, 2009 at 16:01, Vaibhav Arya
vaibhav.a...@otssolutions.com wrote:
Hi chinmoy,
Thanks for your reply…
I have also used this technique which you have mentioned. For now, I got
this work around. But I’m sure; there must be a setting to handle character
encoding. It may be in axis2.xml or in the services.xml inside .aar file.
This needs to be clear because sometimes it becomes very necessary to work
in UTF environment.
Regards,
Vaibhav Kr. Arya
From: Chinmoy Chakraborty [mailto:cch...@gmail.com]
Sent: Wednesday, December 02, 2009 19:02
To: axis-user@ws.apache.org
Subject: Re: [axis2:UTF-8]
I found the same problem with Axis 1.4 but not sure about Axis2. In my case
the incoming SOAP included some CYRILIC characters which Axis 1.4 did not
recognise.
So I had to write a filter, modify the SOAP (replace chanracter greater than
146 by # + c + ;) and pass the modified request to the filter chain.
This solved my purpose. Let me know if this solution suites your
requirement. I can share my code if you want.
Chinmoy
On Wed, Dec 2, 2009 at 5:41 PM, Vaibhav Arya vaibhav.a...@otssolutions.com
wrote:
Hi All,
I have a web-service developed in axis2. How can I make my web-service
support UTF-8 encoding?
It is not supporting special characters ((char) 199). And replacing it with
the ‘?’ sign. I presume that by setting the character encoding to UTF-8,
this problem can be solved. But don’t know how to set character encoding?
Can I use following…
HttpServletRequest request = (HttpServletRequest)
messageContext.getProperty (HTTPConstants.MC_HTTP_SERVLETREQUEST);
try{request.setCharacterEncoding(UTF-8);}catch(Exception
encex){log4jcat.info(error while setting encoding UTF-8 : +
encex.toString());}
Please suggest…
===
Private, Confidential and Privileged. This e-mail and any files and
attachments transmitted with it are confidential and/or privileged. They are
intended solely for the use of the intended recipient. The content of this
e-mail and any file or attachment transmitted with it may have been changed
or altered without the consent of the author. If you are not the intended
recipient, please note that any review, dissemination, disclosure,
alteration, printing, circulation or Transmission of this e-mail and/or any
file or attachment transmitted with it, is prohibited and may be unlawful.
If you have received this e-mail or any file or attachment transmitted with
it in error please notify OTS Solutions at i...@otssolutions.com
===
===
Private, Confidential and Privileged. This e-mail and any files and
attachments transmitted with it are confidential and/or privileged. They are
intended solely for the use of the intended recipient. The content of this
e-mail and any file or attachment transmitted with it may have been changed
or altered without the consent of the author. If you are not the intended
recipient, please note that any review, dissemination, disclosure,
alteration, printing, circulation or Transmission of this e-mail and/or any
file or attachment transmitted with it, is prohibited and may be unlawful.
If you have received this e-mail or any file or attachment transmitted with
it in error please notify OTS Solutions at i...@otssolutions.com
===
Re: Axis2 standalone server + Acegi
As far as I know, there is no out-of-the-box integration between Axis2 (and Rampart) and Acegi. Andreas On Fri, Dec 4, 2009 at 17:26, Philippe A. futhar...@gmail.com wrote: Hello! I am currently reading on Acegi as we'd like to use it for our project. Does the axis2 standalone server have sufficient functionality to support Acegi? Thanks!
Re: Problems when calling getOMElement
Håkon,
I don't think it is supported. At least I didn't find anything related
to mixed content models in the ADB-related code.
Andreas
2009/11/25 Håkon Sagehaug hakon.sageh...@uni.no:
Hi,
I had a closer look at the schema I'm trying to get data from and all
elements look like this
xs:complexType name=BlastOutput_program mixed=true
xs:choice minOccurs=0 maxOccurs=unbounded/
/xs:complexType
So I was wondering if adb supports this? Because now I can't get the values
either. Do one have to write a own parser when dealing with mixed content.
cheers, Håkon
2009/11/24 Andreas Veithen andreas.veit...@gmail.com
Håkon,
Can you provide a test case that reproduces the problem (preferably in
the form of a Maven or Eclipse project)?
Andreas
2009/11/23 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
I now tried with axiom 1.2.9-SNAPSHOT and axis2 1.5.1 release, but the
problem is the same. My code looks like this
OMElement omResp = resp.getGetResultResponse().getOMElement(
GetResultResponse.MY_QNAME,
OMAbstractFactory.getOMFactory());
guess the standard way of getting the OM element. Any other int on how
to
solve this?
cheers, Håkon
2009/11/21 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I'll try on monday, thanks for the help
cheers, Hakon
2009/11/20 Andreas Veithen andreas.veit...@gmail.com
Can you test this with a snapshot version?
Andreas
2009/11/20 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
hi
The problem is occurs using 1.4 and axiom 1.2.8. I can extract the
values
using the java objects, but when I use the #getOmElement() I get the
just
the XML without values, so my thought was the serialization or
something
like this.
cheers, Hakon
2009/11/20 Andreas Veithen andreas.veit...@gmail.com
Does this problem occur with snapshot versions of Axis2 and Axiom?
Andreas
On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
here is a sample code
InDict inDict = new InDict();
ArrayOfKeyValueOfstringstring
arrayOfKeyValueOfstringstring
=
new
ArrayOfKeyValueOfstringstring();
inDict.setInDict(arrayOfKeyValueOfstringstring);
KeyValueOfstringstring_type0[]
keyValueOfstringstring_type0
=
new
KeyValueOfstringstring_type0[1];
keyValueOfstringstring_type0[0] = new
KeyValueOfstringstring_type0();
keyValueOfstringstring_type0[0].setKey(One Element
Array);
keyValueOfstringstring_type0[0].setValue(One Element
Array);
arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);
try {
OMElement omElement =
inDict.getOMElement(InDict.MY_QNAME,
OMAbstractFactory.getOMFactory());
System.out.println(OMElement == +
omElement.toString());
} catch (ADBException e) {
e.printStackTrace();
}
thanks,
Amila.
On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen
andreas.veit...@gmail.com
wrote:
Håkon,
I think you need to give a bit more context. What version of
Axis2?
What version of Axiom? Code snippet showing what you are trying
to
do,
etc.
Andreas
2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
Anybody did this, go from adb object through a xslt
transfomation?
Or having problem getting values out from a XML message when
the
tyep
attribute is used for the data type of the element.
cheers, Håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
To provide more information, we want to do xslt
transformation
to
our
generated client side object. And as far as I know we need
the
OmElement of
the generated type to do so, but when this don't give back
the
values
just
the XML with no values, there is not much to transform. So we
need a
hint on
how this can be done.
cheers, håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
Any tips on this. stange if it won't work?
2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
I've got a client that calls a ws and using adb as the
databinding(client side), then we want to get a string
representation
of the
obejct. We execute object.getOMElement(), the method
returns
only
the xml
element and not the actual value inside the element. So
this
element
here
ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
programblastp/ns2:BlastOutput_program
Would returns this string
ns2:BlastOutput_program/ns2
Re: Configuring Axis2 using SSL
This is probably yet another instance of the issue described in AXIS2-4465 (which is fixed in trunk). Andreas On Tue, Nov 24, 2009 at 10:12, Moritz Mädler m...@moritz-maedler.de wrote: Hi, we want to provide our service also via SSL. Our Axis 1.5 runs as an application in Tomcat 6 which we already configured for listening for SSL-Connections. When I call the WSDL using SSL Axis2 sets the wsdl-port-address as https://serviceurl:80/SERVICE. This is not working as the Port 80 is added misleadingly. I don't know how to fix that and especially keep both transports http and https as we want to use the old clients were we could not change the address to the new https one. I hope you can help!? Thanks alot! Moritz
Re: Question on Issue : AXIS2-4374
Nirav, If I remember well, the fix is in a single file, namely the code generation template. You can see the change here: [1]. What you need to do is to check out the tag for the 1.5.1 release, apply the same changes to these sources and rebuild Axis2 (or at least the adb-codegen module). Since only the template is changed, it is sufficient to use the modified version for code generation, but you can continue to use an unchanged 1.5.1 version at runtime. Andreas [1] http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate.xsl?view=diffr1=788465r2=788466pathrev=788466 On Tue, Nov 24, 2009 at 17:27, Nirav Shah snirav.s...@gmail.com wrote: Hi There, Can someone please tell me what all changes are needed to fix this issue ? I am running Axis2.1.5.1 and I cannot Upgrade to a Snapshot release, though i can upgrade few jars relating to the Code Generation. However, when i tried Upgrading to the ADB CodeGen Snapshot version, it forces me to upgrade the Axi2-ADB jar and also the Axiom jars... Would appreciate if someone could help me with this. Regards, Nirav S.
Re: Configuring Axis2 using SSL
On Tue, Nov 24, 2009 at 13:56, Moritz Mädler m...@moritz-maedler.de wrote: Hi Andreas! Thanks for your quick reply. Is it fixed in the 1.5.1 release, too? No, it is scheduled for 1.6. If we discard the unsecured address and only provide the https-address is there a way to set it by hand? I'm not sure that I understand the idea. Can you explain a bit further? Thanks alot! This is probably yet another instance of the issue described in AXIS2-4465 (which is fixed in trunk). Andreas On Tue, Nov 24, 2009 at 10:12, Moritz Mädler m...@moritz-maedler.de wrote: Hi, we want to provide our service also via SSL. Our Axis 1.5 runs as an application in Tomcat 6 which we already configured for listening for SSL-Connections. When I call the WSDL using SSL Axis2 sets the wsdl-port-address as https://serviceurl:80/SERVICE. This is not working as the Port 80 is added misleadingly. I don't know how to fix that and especially keep both transports http and https as we want to use the old clients were we could not change the address to the new https one. I hope you can help!? Thanks alot! Moritz
Re: Problems when calling getOMElement
Håkon,
Can you provide a test case that reproduces the problem (preferably in
the form of a Maven or Eclipse project)?
Andreas
2009/11/23 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
I now tried with axiom 1.2.9-SNAPSHOT and axis2 1.5.1 release, but the
problem is the same. My code looks like this
OMElement omResp = resp.getGetResultResponse().getOMElement(
GetResultResponse.MY_QNAME,
OMAbstractFactory.getOMFactory());
guess the standard way of getting the OM element. Any other int on how to
solve this?
cheers, Håkon
2009/11/21 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I'll try on monday, thanks for the help
cheers, Hakon
2009/11/20 Andreas Veithen andreas.veit...@gmail.com
Can you test this with a snapshot version?
Andreas
2009/11/20 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
hi
The problem is occurs using 1.4 and axiom 1.2.8. I can extract the
values
using the java objects, but when I use the #getOmElement() I get the
just
the XML without values, so my thought was the serialization or
something
like this.
cheers, Hakon
2009/11/20 Andreas Veithen andreas.veit...@gmail.com
Does this problem occur with snapshot versions of Axis2 and Axiom?
Andreas
On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
here is a sample code
InDict inDict = new InDict();
ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring
=
new
ArrayOfKeyValueOfstringstring();
inDict.setInDict(arrayOfKeyValueOfstringstring);
KeyValueOfstringstring_type0[] keyValueOfstringstring_type0
=
new
KeyValueOfstringstring_type0[1];
keyValueOfstringstring_type0[0] = new
KeyValueOfstringstring_type0();
keyValueOfstringstring_type0[0].setKey(One Element Array);
keyValueOfstringstring_type0[0].setValue(One Element
Array);
arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);
try {
OMElement omElement =
inDict.getOMElement(InDict.MY_QNAME,
OMAbstractFactory.getOMFactory());
System.out.println(OMElement == +
omElement.toString());
} catch (ADBException e) {
e.printStackTrace();
}
thanks,
Amila.
On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen
andreas.veit...@gmail.com
wrote:
Håkon,
I think you need to give a bit more context. What version of Axis2?
What version of Axiom? Code snippet showing what you are trying to
do,
etc.
Andreas
2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
Anybody did this, go from adb object through a xslt
transfomation?
Or having problem getting values out from a XML message when the
tyep
attribute is used for the data type of the element.
cheers, Håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
To provide more information, we want to do xslt transformation
to
our
generated client side object. And as far as I know we need the
OmElement of
the generated type to do so, but when this don't give back the
values
just
the XML with no values, there is not much to transform. So we
need a
hint on
how this can be done.
cheers, håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
Any tips on this. stange if it won't work?
2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
I've got a client that calls a ws and using adb as the
databinding(client side), then we want to get a string
representation
of the
obejct. We execute object.getOMElement(), the method returns
only
the xml
element and not the actual value inside the element. So this
element
here
ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
programblastp/ns2:BlastOutput_program
Would returns this string
ns2:BlastOutput_program/ns2:BlastOutput_program
We where wondering if it had anything to to with the xsi:type
attribute?
Any tips on how to solve this, or another way of getting a
string
representatioon of the object using adb as the databinding?
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB
Re: Problems when calling getOMElement
Does this problem occur with snapshot versions of Axis2 and Axiom?
Andreas
On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
here is a sample code
InDict inDict = new InDict();
ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring = new
ArrayOfKeyValueOfstringstring();
inDict.setInDict(arrayOfKeyValueOfstringstring);
KeyValueOfstringstring_type0[] keyValueOfstringstring_type0 = new
KeyValueOfstringstring_type0[1];
keyValueOfstringstring_type0[0] = new
KeyValueOfstringstring_type0();
keyValueOfstringstring_type0[0].setKey(One Element Array);
keyValueOfstringstring_type0[0].setValue(One Element Array);
arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);
try {
OMElement omElement = inDict.getOMElement(InDict.MY_QNAME,
OMAbstractFactory.getOMFactory());
System.out.println(OMElement == + omElement.toString());
} catch (ADBException e) {
e.printStackTrace();
}
thanks,
Amila.
On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Håkon,
I think you need to give a bit more context. What version of Axis2?
What version of Axiom? Code snippet showing what you are trying to do,
etc.
Andreas
2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
Anybody did this, go from adb object through a xslt transfomation?
Or having problem getting values out from a XML message when the tyep
attribute is used for the data type of the element.
cheers, Håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
To provide more information, we want to do xslt transformation to our
generated client side object. And as far as I know we need the
OmElement of
the generated type to do so, but when this don't give back the values
just
the XML with no values, there is not much to transform. So we need a
hint on
how this can be done.
cheers, håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
Any tips on this. stange if it won't work?
2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
I've got a client that calls a ws and using adb as the
databinding(client side), then we want to get a string representation
of the
obejct. We execute object.getOMElement(), the method returns only
the xml
element and not the actual value inside the element. So this element
here
ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
programblastp/ns2:BlastOutput_program
Would returns this string
ns2:BlastOutput_program/ns2:BlastOutput_program
We where wondering if it had anything to to with the xsi:type
attribute?
Any tips on how to solve this, or another way of getting a string
representatioon of the object using adb as the databinding?
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Problems when calling getOMElement
Can you test this with a snapshot version?
Andreas
2009/11/20 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
hi
The problem is occurs using 1.4 and axiom 1.2.8. I can extract the values
using the java objects, but when I use the #getOmElement() I get the just
the XML without values, so my thought was the serialization or something
like this.
cheers, Hakon
2009/11/20 Andreas Veithen andreas.veit...@gmail.com
Does this problem occur with snapshot versions of Axis2 and Axiom?
Andreas
On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
here is a sample code
InDict inDict = new InDict();
ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring =
new
ArrayOfKeyValueOfstringstring();
inDict.setInDict(arrayOfKeyValueOfstringstring);
KeyValueOfstringstring_type0[] keyValueOfstringstring_type0 =
new
KeyValueOfstringstring_type0[1];
keyValueOfstringstring_type0[0] = new
KeyValueOfstringstring_type0();
keyValueOfstringstring_type0[0].setKey(One Element Array);
keyValueOfstringstring_type0[0].setValue(One Element Array);
arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);
try {
OMElement omElement = inDict.getOMElement(InDict.MY_QNAME,
OMAbstractFactory.getOMFactory());
System.out.println(OMElement == + omElement.toString());
} catch (ADBException e) {
e.printStackTrace();
}
thanks,
Amila.
On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen
andreas.veit...@gmail.com
wrote:
Håkon,
I think you need to give a bit more context. What version of Axis2?
What version of Axiom? Code snippet showing what you are trying to do,
etc.
Andreas
2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
Anybody did this, go from adb object through a xslt transfomation?
Or having problem getting values out from a XML message when the tyep
attribute is used for the data type of the element.
cheers, Håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
To provide more information, we want to do xslt transformation to
our
generated client side object. And as far as I know we need the
OmElement of
the generated type to do so, but when this don't give back the
values
just
the XML with no values, there is not much to transform. So we need a
hint on
how this can be done.
cheers, håkon
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
Any tips on this. stange if it won't work?
2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi all,
I've got a client that calls a ws and using adb as the
databinding(client side), then we want to get a string
representation
of the
obejct. We execute object.getOMElement(), the method returns only
the xml
element and not the actual value inside the element. So this
element
here
ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
programblastp/ns2:BlastOutput_program
Would returns this string
ns2:BlastOutput_program/ns2:BlastOutput_program
We where wondering if it had anything to to with the xsi:type
attribute?
Any tips on how to solve this, or another way of getting a string
representatioon of the object using adb as the databinding?
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
Re: Problems when calling getOMElement
Håkon, I think you need to give a bit more context. What version of Axis2? What version of Axiom? Code snippet showing what you are trying to do, etc. Andreas 2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no: Hi Anybody did this, go from adb object through a xslt transfomation? Or having problem getting values out from a XML message when the tyep attribute is used for the data type of the element. cheers, Håkon 2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no Hi To provide more information, we want to do xslt transformation to our generated client side object. And as far as I know we need the OmElement of the generated type to do so, but when this don't give back the values just the XML with no values, there is not much to transform. So we need a hint on how this can be done. cheers, håkon 2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no Hi all, Any tips on this. stange if it won't work? 2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no Hi all, I've got a client that calls a ws and using adb as the databinding(client side), then we want to get a string representation of the obejct. We execute object.getOMElement(), the method returns only the xml element and not the actual value inside the element. So this element here ns2:BlastOutput_program xsi:type=ns2:BlastOutput_ programblastp/ns2:BlastOutput_program Would returns this string ns2:BlastOutput_program/ns2:BlastOutput_program We where wondering if it had anything to to with the xsi:type attribute? Any tips on how to solve this, or another way of getting a string representatioon of the object using adb as the databinding? cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) hakon.sageh...@bccs.uib.no, phone +47 55584125 -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) hakon.sageh...@bccs.uib.no, phone +47 55584125 -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) hakon.sageh...@bccs.uib.no, phone +47 55584125 -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) hakon.sageh...@bccs.uib.no, phone +47 55584125
Re: Additional characters in Axis2 SOAP message
Please see: http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1 On Tue, Nov 17, 2009 at 04:12, Lawrence Yao mla...@gmail.com wrote: Hello all, I have written a client using Axis2 (version 1.5) that attempts to access a Web service written in C#/mono. Whenever I attempt to connect, I receive the following exception: org.apache.axis2.AxisFault: Could not deserialize Soap message I noticed that the SOAP message sent to the server is incorrectly formatted and contains additional characters. I captured the entire message shown below: POST /Import.asmx HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: http://127.0.0.1:8080/Import.asmx/Import; User-Agent: Axis2 Host: localhost:8080 Transfer-Encoding: chunked 193 ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyns1:rdthImport xmlns:ns1=http://127.0.0.1:8080/Import.asmx;ns1:codesInCode/ns1:codesInns1:startdateIn01/01/2003/ns1:startdateInns1:enddateIn15/01/2003/ns1:enddateInns1:resultid46525511.csv/ns1:resultid/ns1:rdthImport/soapenv:Body/soapenv:Envelope 0 In my opinion, the characters 193 and 0 should not appear where they are (before and after the XML message, respectively). Once, I also got 1b3 to appear in place of 193 when the contents of the XML message was different. I believe these additional characters are causing the Could not deserialize Soap message exception above, because I have written a PHP client to connect to the same Web service and it worked. When comparing the two SOAP messages, the PHP client's message did not have these additional characters. I have tested that this happens when using Axis2 versions 1.4.1, 1.5 and 1.5.1. Oddly enough, I did not encounter problems when using Axis2 clients to connect to Axis2 Web services. Any ideas? Thanks, Lawrence.
Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
On Fri, Nov 13, 2009 at 15:46, Vincent DiPrenda vincent.dipre...@us.fujitsu.com wrote: I'm new to this forum, and have been searching for details of the implementation of SOAP/JMS. I've got a few questions, if somebody will be kind enough to help me out. 1. I've read some posts stating that the implementation has been pulled from axis2, and now exists in the ws-commons subproject. I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi, but can't seem to find the implementation. Am I looking in the right place, if not, please let me know where I can find the jar. I'm assuming once it's found, it's a simple matter of including it in the lib directory of axis 2. We are in the process of releasing the transports. Since it is the first release at its new home, there is no site yet. A preview is available at [1]. [1] http://people.apache.org/~veithen/transport/ 2. I've noticed some people have had luck with MQ. If there are any tutorials regarding the procedures I would be grateful. (Most of the stuff I've seen is based on older versions and seem to be reliant on features on 4.1 or older of axis2. If they're still relevant, that's fine, but I don't want to assume. That should be enough to get me started. Thanks, Vinnie
Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
Vinnie, Nightly builds are available from [1]. However, I'm not sure if these are builds of the trunk (the current development version) or the branch (the code that will become version 1.0). A guess it's the trunk. However, for the JMS transport there should not be much difference between the two. Andreas [1] http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-transport-jms/1.0-SNAPSHOT/ On Fri, Nov 13, 2009 at 20:12, Vincent DiPrenda vincent.dipre...@us.fujitsu.com wrote: Thanks Andreas, I'm assuming the code in the ws-commons will be available for use as a jar file under the Axis2 environment. Is that also available to preview at this point? Asankha was kind enough to send me the a link to the source of the JMS transport code, but I'm not quite sure of how it's indented to be integrated. Thanks Vinnie -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Friday, November 13, 2009 2:00 PM To: axis-user@ws.apache.org Subject: Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions. On Fri, Nov 13, 2009 at 15:46, Vincent DiPrenda vincent.dipre...@us.fujitsu.com wrote: I'm new to this forum, and have been searching for details of the implementation of SOAP/JMS. I've got a few questions, if somebody will be kind enough to help me out. 1. I've read some posts stating that the implementation has been pulled from axis2, and now exists in the ws-commons subproject. I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi, but can't seem to find the implementation. Am I looking in the right place, if not, please let me know where I can find the jar. I'm assuming once it's found, it's a simple matter of including it in the lib directory of axis 2. We are in the process of releasing the transports. Since it is the first release at its new home, there is no site yet. A preview is available at [1]. [1] http://people.apache.org/~veithen/transport/ 2. I've noticed some people have had luck with MQ. If there are any tutorials regarding the procedures I would be grateful. (Most of the stuff I've seen is based on older versions and seem to be reliant on features on 4.1 or older of axis2. If they're still relevant, that's fine, but I don't want to assume. That should be enough to get me started. Thanks, Vinnie
Re: character converted to lt; in request XML
Can you post a code snippet showing what you are doing? Andreas On Wed, Nov 11, 2009 at 21:46, Selvaraj, Peter (eBusiness) peter.selva...@thehartford.com wrote: I'm using axiom OMElement to build the request, below solution didn't resolve this issue. Any idea? Thanks Regards, Peter R Selvaraj From: jose.ferre...@gmail.com [mailto:jose.ferre...@gmail.com] On Behalf Of José Ferreiro Sent: Wednesday, November 11, 2009 3:31 PM To: axis-user@ws.apache.org Subject: Re: character converted to lt; in request XML This is a work around I found. It is a but into wss4j. This problem does not happend if you do not use encryption or other. See methods below on: http://commons.apache.org/lang/api/org/apache/commons/lang/StringEscapeUtils.html you should escape sent response by server org.apache.commons.lang.StringEscapeUtils.escapeXml and then on the client you should unscape received response org.apache.commons.lang.StringEscapeUtils.unescapeXml Hope this helps. On Wed, Nov 11, 2009 at 8:38 PM, Selvaraj, Peter (eBusiness) peter.selva...@thehartford.com wrote: Hi, Could you please let me know how did you solve this using apache common utilities? Any sample code you have? Thanks Regards, Peter R Selvaraj From: jose.ferre...@gmail.com [mailto:jose.ferre...@gmail.com] On Behalf Of José Ferreiro Sent: Wednesday, November 11, 2009 2:36 PM To: axis-user@ws.apache.org Subject: Re: character converted to lt; in request XML Is this the payload? I had simular issue when using WSS4J, which if I am not wrong is within Rampart. I solved the solution by escaping the using appche commons utilities if I am not wrong. Both at client and server side. Hope this helps. On Wed, Nov 11, 2009 at 8:19 PM, Selvaraj, Peter (eBusiness) peter.selva...@thehartford.com wrote: Hi, I'm using Axis2 1.4 and Rampart 1.4 java client which creates the request xml and invokes the webservice. In the request xml, I can see the character is converted to lt; Because of this I get ErrorResponse from the webservice. Any idea how to avoid this character conversion. Thanks Regards, Peter R Selvaraj This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- José Ferreiro Systems Analysis and Design Specialist MSc in Communication Systems, EPFL. Think little goals and expect little achievements. Think big goals and win big success. David Joseph Schwartz This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- José Ferreiro Systems Analysis and Design Specialist MSc in Communication Systems, EPFL. Think little goals and expect little achievements. Think big goals and win big success. David Joseph Schwartz This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
Re: Generated WSDL HTTPS Port not 8443
On Tue, Nov 10, 2009 at 18:31, v2cg4ss ssel...@datamentors.com wrote: I just tried the nightly build of 10-Nov-2009 14:33 and the endpoints look good: wsdl:service name=MyWS - wsdl:port name=MyWSHttpsSoap11Endpoint binding=ns:MyWSSoap11Binding soap:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.NetEffectWS_1HttpsSoap11Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpSoap11Endpoint binding=ns:MyWSSoap11Binding soap:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap11Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpSoap12Endpoint binding=ns:MyWSSoap12Binding soap12:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpSoap12Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpsSoap12Endpoint binding=ns:MyWSSoap12Binding soap12:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsSoap12Endpoint/; / /wsdl:port - wsdl:port name=MyWSHttpsEndpoint binding=ns:MyWSHttpBinding http:address location=https://localhost:8443/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpsEndpoint/; / /wsdl:port - wsdl:port name=MyWSHttpEndpoint binding=ns:MyWSHttpBinding http:address location=http://localhost:8080/axis2-webapp-SNAPSHOT/services/MyWS.MyWSHttpEndpoint/; / /wsdl:port /wsdl:service So this is good, I also found that axis2 1.3 works as well. The problem I have now is a .NET client that is afraid to move forward with us using 1.5.1 knowing that someone on their end could refresh the endpoints via Visual Studio and blow up production. Yes, I agree that they should have test procedures in place...But I don't understand how this worked in axis2 1.3 and has been broken since 1.4.1, 1.5, and 1.5.1. I cannot download 1.4 to see if it is broken in that version but this is a major miss but someone. So I would like to vote for this issue to be resolved quickly and a 1.5.2 release be made. This is very unlikely. It would mean to merge the changes from the trunk to the 1.5 branch. Technically this is not a big problem, but the code that is modified is very badly designed and there are external projects that are tightly coupled to that piece of code. I already burned my fingers with this when fixing the issue in the trunk [1] and I'm not going through this again. The fix will go into 1.6 unless somebody else volunteers to merge this into the 1.5 branch. [1] http://markmail.org/message/3gy3gnzkbh5kxt4c SanjayGupta wrote: Hi, I have the same issue and very interested in finding a solution. Sanjay -Original Message- From: v2cg4ss [mailto:ssel...@datamentors.com] Sent: Monday, November 09, 2009 1:40 PM To: axis-user@ws.apache.org Subject: Re: Generated WSDL HTTPS Port not 8443 Is this in a nightly build that I can test? Will this be axis2 1.5.2? Andreas Veithen-2 wrote: On Thu, Nov 5, 2009 at 20:49, v2cg4ss ssel...@datamentors.com wrote: Thank you for the reply, is this being resolved soon. It is implemented, but the issue is not closed yet because the documentation is not up to date with the changes. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, https://localhost:8443/axis2/services/MyWS;); Scott Andreas Veithen-2 wrote: Generating the correct endpoint URIs for https is something that doesn't work properly in the available Axis2 releases. See AXIS2-4465 and related issues. Andreas -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26274176.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26287344.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Generated WSDL HTTPS Port not 8443
On Thu, Nov 5, 2009 at 20:49, v2cg4ss ssel...@datamentors.com wrote: Thank you for the reply, is this being resolved soon. It is implemented, but the issue is not closed yet because the documentation is not up to date with the changes. I have a client using .NET and they are generating their client code from the WSDL. The programmer claims that they cannot change the endpoint in the .NET code like I can with java. MyWSStub stub = new MyWSStub(ctx, https://localhost:8443/axis2/services/MyWS;); Scott Andreas Veithen-2 wrote: Generating the correct endpoint URIs for https is something that doesn't work properly in the available Axis2 releases. See AXIS2-4465 and related issues. Andreas -- View this message in context: http://old.nabble.com/Generated-WSDL-HTTPS-Port-not-8443-tp26208367p26219924.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [Axis2] with Rampart -- XMLStreamException the prefix == Already exists for namespace
On Thu, Oct 29, 2009 at 11:33, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Wed, Oct 28, 2009 at 1:31 AM, Andreas Veithen andreas.veit...@gmail.com wrote: Srini, Here is the explanation of this issue, as I see it: - When WS-Security is disabled, ADB streams the XML data directly to the wire, using an XMLStreamWriter from Woodstox (which is indeed wrapped to handle MTOM, but this is not important). No problem here because the XMLStreamWriter from Woodstox conforms to StAX and ADB in Axis2 1.5 uses the XMLStreamWriter correctly (up to a minor issue fixed in trunk). - When WS-Security is enabled, the XML can't be streamed to the wire directly because Rampart needs to post-process the response. ADB handles this by using an XMLStreamWriter implementation that will build an Axiom (see AXIS2-4413). This is the MTOMAwareOMBuilder that you see. The problem is that MTOMAwareOMBuilder is not a correct implementation of XMLStreamWriter. While the sequence of events produced by ADB is correct (otherwise it would have failed with Woodstox), MTOMAwareOMBuilder thinks that there is a collision between two namespace bindings. The code in this class at least has two issues: - writeStartElement, writeAttribute, writeNamespace and writeDefaultNamespace may all modify the namespace context (by calling getOMNamespace). This is incorrect: according to the specs, only setPrefix and setDefaultNamespace modify the namespace context of the XMLStreamWriter. ADB write element method looks like this. xmlWriter.writeStartElement(prefix, localPart, namespace); xmlWriter.writeNamespace(prefix, namespace); xmlWriter.setPrefix(prefix, namespace); does the spec specify any order? Except for the obvious constraint that writeNamespace must follow writeStartElement, the specs don't specify the order. However, they specify that the scope of the namespace binding declared by setPrefix is the current element. Therefore, if one wants to make sure that the namespace context of the XMLStreamWriter accurately reflects the namespace context in the document being written, setPrefix must be called after writeStartElement. Since ADB makes use of the namespace context of the writer to choose namespace prefixes, the order is correct and must be like that. For more details, see [1]. [1] http://people.apache.org/~veithen/axiom/devguide/ch02.html - The namespace context is not scoped. Normally, the namespace bindings declared by setPrefix and setDefaultNamespace only remain visible in the current element. This is not the case (see the usage of a simple HashMap in MTOMAwareOMBuilder and OMStreamNamespaceContext. In your case, the problem is probably caused by the second issue: MTOMAwareOMBuilder probably believes that there is a collision between a newly declared namespace binding and an existing one that actually should be out of scope. can you check this by using a response get without rampart? if so we can remove this check. thanks, Amila. Regards, Andreas On Tue, Oct 27, 2009 at 19:53, srini.maran thiruma...@yahoo.com wrote: Hi Axis User. I am getting the below error in the client code when I try to invoke the service with WS-Security Rampart. I am using Asix2-1.5 and Rampart-1.4 XMLStreamException the prefix == Already exists for namespace in “urn:com1” when WS-Security Rampart is engaged for Axis 2 web-services Attached are the error log file (stacktrace) client code. I am using XML import in the schema. I am able to successfully test the Rampart policy samples without any issue. I am getting error when I add rampart in our existing service which has complex schema. Has this error occurred due to xml import? Below is my XSD hierarchy service.wsdl -- wsdl:types xsd:import namespace=urn:chl schemaLocation=../schema/hub_channel.xsd / - in xsd:import namespace=urn:msg schemaLocation=../schema/hub_message.xsd / - out /wsdl:types hub_channel.xsd(urn:chl) imports the below scheams. xsd:import namespace=urn:com1 schemaLocation=hub_common.xsd / xsd:import namespace=urn:usr schemaLocation=hub_user.xsd / hub_message.xsd(urn:msg) import xsd:import namespace=urn:com1 schemaLocation=hub_common.xsd / Can you please help on this issue? I will really appreciate you. I have been trying for last 1 week to resolve it. I couldn’t resolve it. I searched in Axis User, people encountered the same. I don't think it's resolved. Here is the link: http://www.mail-archive.com/axis-user@ws.apache.org/msg40661.html In the forum, one of the user Richard mentioned Rampart devs would like to acknowledge the problem and maybe even fix
Re: [Axis2] with Rampart -- XMLStreamException the prefix == Already exists for namespace
Srini, Here is the explanation of this issue, as I see it: - When WS-Security is disabled, ADB streams the XML data directly to the wire, using an XMLStreamWriter from Woodstox (which is indeed wrapped to handle MTOM, but this is not important). No problem here because the XMLStreamWriter from Woodstox conforms to StAX and ADB in Axis2 1.5 uses the XMLStreamWriter correctly (up to a minor issue fixed in trunk). - When WS-Security is enabled, the XML can't be streamed to the wire directly because Rampart needs to post-process the response. ADB handles this by using an XMLStreamWriter implementation that will build an Axiom (see AXIS2-4413). This is the MTOMAwareOMBuilder that you see. The problem is that MTOMAwareOMBuilder is not a correct implementation of XMLStreamWriter. While the sequence of events produced by ADB is correct (otherwise it would have failed with Woodstox), MTOMAwareOMBuilder thinks that there is a collision between two namespace bindings. The code in this class at least has two issues: - writeStartElement, writeAttribute, writeNamespace and writeDefaultNamespace may all modify the namespace context (by calling getOMNamespace). This is incorrect: according to the specs, only setPrefix and setDefaultNamespace modify the namespace context of the XMLStreamWriter. - The namespace context is not scoped. Normally, the namespace bindings declared by setPrefix and setDefaultNamespace only remain visible in the current element. This is not the case (see the usage of a simple HashMap in MTOMAwareOMBuilder and OMStreamNamespaceContext. In your case, the problem is probably caused by the second issue: MTOMAwareOMBuilder probably believes that there is a collision between a newly declared namespace binding and an existing one that actually should be out of scope. Regards, Andreas On Tue, Oct 27, 2009 at 19:53, srini.maran thiruma...@yahoo.com wrote: Hi Axis User. I am getting the below error in the client code when I try to invoke the service with WS-Security Rampart. I am using Asix2-1.5 and Rampart-1.4 XMLStreamException the prefix == Already exists for namespace in “urn:com1” when WS-Security Rampart is engaged for Axis 2 web-services Attached are the error log file (stacktrace) client code. I am using XML import in the schema. I am able to successfully test the Rampart policy samples without any issue. I am getting error when I add rampart in our existing service which has complex schema. Has this error occurred due to xml import? Below is my XSD hierarchy service.wsdl -- wsdl:types xsd:import namespace=urn:chl schemaLocation=../schema/hub_channel.xsd / - in xsd:import namespace=urn:msg schemaLocation=../schema/hub_message.xsd / - out /wsdl:types hub_channel.xsd(urn:chl) imports the below scheams. xsd:import namespace=urn:com1 schemaLocation=hub_common.xsd / xsd:import namespace=urn:usr schemaLocation=hub_user.xsd / hub_message.xsd(urn:msg) import xsd:import namespace=urn:com1 schemaLocation=hub_common.xsd / Can you please help on this issue? I will really appreciate you. I have been trying for last 1 week to resolve it. I couldn’t resolve it. I searched in Axis User, people encountered the same. I don't think it's resolved. Here is the link: http://www.mail-archive.com/axis-user@ws.apache.org/msg40661.html In the forum, one of the user Richard mentioned Rampart devs would like to acknowledge the problem and maybe even fix it One user debugged the issue and added the below comments in the forum I debugged the code and observed that, in the serialize method of the XML node POJO (generated by WSDL2JAVA), the MTOMAwareXMLStreamWriter xmlWriter parameter gets an instance of MTOMAwareOMBuilder if WS-Security is enabled. Whereas, without WS-Security it gets an instance of org.apache.axis2.databinding.utils.writer.MTOMAwareXMLSerializer which uses MTOMXMLStreamWriter which in turn uses com.ctc.wstx.sw.SimpleNsStreamWriter to serialize the response. I also tried using AXIS 1.4 without any success. Any idea how can this problem can be solved? Is there a way to let Rampart know which serializer should be used? Am I missing any configuration details of Rampart? Thanks Srini Maran http://www.nabble.com/file/p26083056/Error1.rtf Error1.rtf http://www.nabble.com/file/p26083056/Client.rtf Client.rtf -- View this message in context: http://www.nabble.com/-Axis2--with-RampartXMLStreamException-%22the-prefix-%3D%3D%3E-Already-exists-for-namespace-tp26083056p26083056.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Problems using XPath in Axiom when namespaces are involved
Robert, My guess is that the issue is related to the fact that you are trying to define a default namespace for the XPath expression. Can you check in the Jaxen documentation if it says something about this? Note that defining a default namespace for an XPath expression is not a good idea anyway, because it will prevent you from matching elements or attributes in the null namespace. The reason is that the null namespace can only be used as default namespace (i.e. xmlns:p= is illegal). Therefore if you declare a different default namespace, you can't refer to the null namespace in your XPath expression. That is the reason why for example the XSLT specification defines the namespace context of an XPath expression as follows: the set of namespace declarations are those in scope on the element which has the attribute in which the expression occurs; [...] the default namespace (as declared by xmlns) is not part of this set Andreas On Thu, Oct 22, 2009 at 19:09, Robert Baldock robert.bald...@pfiks.com wrote: Hi - I'm having problems getting my head round the use of XPath in Axiom, especially when using namespaces. With an XML snippet like this: ?xml version=1.0 encoding=utf-16? X Y Ztest/Z /Y /X And a code snippet like this: String xpathString = /X/Y/Z; AXIOMXPath xpathExpression = new AXIOMXPath(xpathString); OMElement element = (OMElement)xpathExpression.selectSingleNode(root); I can retrieve the element from the XML without any problem. However, with XML like this: ?xml version=1.0 encoding=utf-16? X xmlns:xsi=A xmlns:xsd=B xmlns=C Y Ztest/Z /Y /X OMNamespace namespace = documentElement.getNamespace(); String prefix = namespace.getPrefix(); String uri = namespace.getNamespaceURI(); AXIOMXPath xpathExpression = new AXIOMXPath(xpathString); xpathExpression.addNamespace(prefix, uri); OMElement element = (OMElement)xpathExpression.selectSingleNode(root); I get no results. Can anyone spot why this might be? Any advice would be much appreciated. Robert
Re: AbstractMethodError in simple Rampart client
An AbstractMethodError can only occur if the dependencies at runtime are different from the dependencies at build time. The stacktrace shows that this happens somewhere inside Axiom. Since Axiom only depends on very stable APIs (Activation, JavaMail and StAX), the only possible explanation is that you have a mix of Axiom libraries from different versions. Probably the version of axiom-dom you are using is older than the version of axiom-api. Andreas On Fri, Oct 9, 2009 at 20:47, David Dearing ddear...@stottlerhenke.com wrote: I have created a simple Axis2 echo service and client and am now trying to add Rampart security, starting with a simple UsernameToken and plain text Password. The secured service is running and it rejects client calls that are missing the required SOAP header. I set up the client to add the username and password, but I get an AbstractMethodError on the client side. Am I missing a configuration step or an overlooked dependency? Any help would be greatly appreciated!! I'm using Axis2 1.5 and Rampart 1.4. The rahas-1.4 and rampart-1.4 modules *do* get deployed from the client repo. Brief code snippet: ConfigurationContext ctx = //snip: Factory.create(repo) SecureServiceStub stub = new SecureServiceStub(ctx); // configure rampart security ServiceClient sc = stub._getServiceClient(); sc.engageModule(rampart); Options options = sc.getOptions(); options.setUserName(guest); options.setPassword(pass); stub.echo(hello); Exception in thread main java.lang.AbstractMethodError org.apache.axiom.om.impl.builder.StAXBuilder.processAttributes(StAXBuilder.java:230) org.apache.axiom.om.impl.builder.StAXOMBuilder.populateOMElement(StAXOMBuilder.java:396) org.apache.axiom.om.impl.builder.StAXOMBuilder.createOMElement(StAXOMBuilder.java:425) org.apache.axiom.om.impl.builder.StAXOMBuilder.createNextOMElement(StAXOMBuilder.java:282) org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:207) org.apache.axiom.om.impl.dom.DocumentImpl.getOMDocumentElement(DocumentImpl.java:443) org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:502) org.apache.rahas.Token.init(Token.java:141) org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:388) ...
Re: unsubscribe
Please send a mail to axis-user-unsubscr...@ws.apache.org On Fri, Oct 9, 2009 at 06:10, Gudikoti, Rajesh rajesh.gudik...@logica.com wrote: Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei, die Umwelt zu schützen. / Por favor ajude a Logica a respeitar o ambiente não imprimindo este correio electrónico. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Re: hibernate and axis2
On Tue, Oct 6, 2009 at 16:20, TomazM tomaz.majerh...@arnes.si wrote: robert lazarski wrote: On Wed, Sep 30, 2009 at 9:53 AM, Andreas Veithen andreas.veit...@gmail.com wrote: I suggest you don't put all these jar's in the aar, put them in WEB-INF/lib . hibernate uses the TCCL and that won't work directly in an aar without some extra effort. It should be enough to add the following parameter to the service: parameter name=ServiceTCCL locked=falsecomposite/parameter So where to put Hibernate persistance.xml in axis2 dir structure per one service? Regards, Tomaz In the META-INF folder at the same location where your entity classes reside, i.e. depending on where you put them, in WEB-INF/classes/META-INF or the META-INF folder inside the AAR. Andreas Andreas Right. With only one end user aar and without the OP showing a need to have a hibernate session isolated to axis2, however, its probably overkill. Its possible to do spring and/or hibernate per aar, I just think it rarely makes sense. Just my 2 brazilian centavos :-) . - R
Re: Compilation Failure in Axis2 trunk
Looks like the Axiom snapshots on people.apache.org are outdated and don't include the change in r819034. You will have to build Axiom first. Andreas On Mon, Sep 28, 2009 at 11:07, Chamara Silva chamarasi...@gmail.com wrote: Hi, I got compilation failure during the building of Axis2 trunk. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[32,30] cannot find symbol symbol : class ParserInputStreamDataSource location: package org.apache.axiom.om.ds /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[109,12] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[109,49] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[159,12] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[159,49] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder Thank you, Regards, Chamara
Re: Testing REST functionality
On Sun, Sep 27, 2009 at 18:14, Martin Gainty mgai...@hotmail.com wrote:
could someone determine if checking contentType to determine RESTRequest is
sufficient?
org.apache.axis2.transport.http.HttpTransportUtils{
public static final String MEDIA_TYPE_APPLICATION_XML = application/xml;
public static final String MEDIA_TYPE_X_WWW_FORM =
application/x-www-form-urlencoded;
public static final String MEDIA_TYPE_MULTIPART_FORM_DATA =
multipart/form-data;
public static boolean isRESTRequest(String contentType) {
return contentType != null
(contentType.indexOf(HTTPConstants.MEDIA_TYPE_APPLICATION_XML) -1 ||
contentType.indexOf(HTTPConstants.MEDIA_TYPE_X_WWW_FORM)
-1 ||
contentType.indexOf(HTTPConstants.MEDIA_TYPE_MULTIPART_FORM_DATA) -1);
}
}
some other projects are mapping REST based on URL parse(and not necessarily
contentType test)
I'm not an expert, but I would say that RESTfulness is a property of
the service, not the message. This implies that one can determine
whether a request is REST or not only after dispatching to the service
(based on the URL). I don't know why in Axis2, we try to do this at
transport level.
Andreas
does REST have a spec to follow and if so is there any parsing of URL to
determine if this is a REST request?
thanks,
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire
informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
de ceci est interdite. Ce message sert à l'information seulement et n'aura
pas n'importe quel effet légalement obligatoire. Étant donné que les email
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.
Hotmail® has ever-growing storage! Don’t worry about storage limits. Check
it out.
Re:
The two requests are NOT the same. In the first request, the sql element has a namespace, while in the second one it does not. It is normal that Axis2 rejects one of them. Which of the two request is the correct one depends on the WSDL/Schema, more specifically on the setting for elementFormDefault. Andreas On Thu, Oct 1, 2009 at 08:29, Paul Fremantle pzf...@gmail.com wrote: Sriram You don't need to have the ns prefix. As long as the XML is properly formed, you can use either style. Paul On Thu, Oct 1, 2009 at 7:12 AM, sri ram pinnamaraju_sri...@yahoo.co.in wrote: Hi, As I see in Axis 2 doesn't support a format of SOAP messages which doesn't have namespace prefix.As shown below the request doesn't work ,however when substituted bya namespace prefix it does work well. SOAP-ENV:Envelope encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; SOAP-ENV:Body executeSQLQuery xmlns=http://www.kiran.com/AXL/API/7.1 sqlselect * from typeproduct/sql /executeSQLQuery /SOAP-ENV:Body /SOAP-ENV:Envelope (axis 2) expects the request message to have namespace prefix in the request . SOAP-ENV:Envelope encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; SOAP-ENV:Body ns:executeSQLQuery xmlns:ns =http://www.kiran.com/AXL/API/8.0; sqlselect * from typeproduct/sql /ns:executeSQLQuery /SOAP-ENV:Body /SOAP-ENV:Envelope Is there a way to make the axis 2 framework to allow and process the other format of request ie withoute the namespace prefix. Is this (namespace prefix ) a standard followed by all the SOAPEngines and Parsers. Can some one throw some light on it. Please reply back soon. If this kind of question is already addressed can you guys please give link to the corresponding mail. Thanks , Sriram Connect more, do more and share more with Yahoo! India Mail. Learn more. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org p...@wso2.com Oxygenating the Web Service Platform, www.wso2.com
Re: hibernate and axis2
I suggest you don't put all these jar's in the aar, put them in WEB-INF/lib . hibernate uses the TCCL and that won't work directly in an aar without some extra effort. It should be enough to add the following parameter to the service: parameter name=ServiceTCCL locked=falsecomposite/parameter Andreas
Re: unsubscribe
Please send a mail to axis-user-unsubscr...@ws.apache.org On Mon, Sep 28, 2009 at 08:45, Chamara Silva chamarasi...@gmail.com wrote:
Re: unsubscribe
Please send a mail to axis-user-unsubscr...@ws.apache.org On Mon, Sep 28, 2009 at 19:50, Sie, Yang yang@fmr.com wrote: unsubscribe
Re: unsubscribe
You need to send a mail to axis-user-unsubscr...@ws.apache.org On Thu, Sep 24, 2009 at 09:53, Pradeep Patel patelprad...@gmail.com wrote:
Re: content type for rest/pox requests
This is probably caused by the change in AXIS2-3228, which went into Axis2 1.4.
Andreas
On Tue, Sep 22, 2009 at 23:59, Alexis Midon mi...@intalio.com wrote:
Hi all,
I struggled for a while before I finally managed to invoke a service with
non-soap message. Here is why.
The following
documentation http://ws.apache.org/axis2/1_5/rest-ws.html says:
if the content type is **text/xml** and if the SOAP Action Headers are
missing, then the Message is treated as a RESTful Message. Else it is
treated as a usual SOAP Message.
However the method HTTPTransportUtils#isRESTRequest does not test the
'text/xml' content-type [1].
So my request fails with the fault below [2]. Changing the content-type to
'application/xml' solved the issue.
Either the code or the documentation needs to be adjusted.
best,
Alexis
[1]
public static boolean isRESTRequest(String contentType) {
return contentType != null
(contentType.indexOf(HTTPConstants.MEDIA_TYPE_APPLICATION_XML) -1 ||
contentType.indexOf(HTTPConstants.MEDIA_TYPE_X_WWW_FORM)
-1 ||
contentType.indexOf(HTTPConstants.MEDIA_TYPE_MULTIPART_FORM_DATA) -1);
}
[2]
?xml version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodysoapenv:Faultfaultcode/faultcodefaultstringFirst
Element must contain the local name, Envelope , but found
Receive__MessageRequest/faultstringdetailExceptionorg.apache.axis2.AxisFault:
First Element must contain the local name, Envelope , but found
Receive__MessageRequest
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:169)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element must
contain the local name, Envelope , but found Receive__MessageRequest
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:267)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:214)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:196)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:207)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:161)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.lt;init(StAXSOAPModelBuilder.java:110)
at org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:60)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:192)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:140)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:162)
... 17 more
* Closing connection #0
/Exception/detail/soapenv:Fault/soapenv:Body/soapenv:Envelope
Re: [AXIS2] A question on axis2-wsdl2code-maven-plugin
In a Maven build you should never let a plugin output generated code into src/main/java, but instead into a temporary directory under target (so that it will be removed by mvn clean). In that case it doesn't matter that axis2-wsdl2code-maven-plugin places the code in a subdirectory called src. Andreas On Tue, Sep 22, 2009 at 19:58, Indrit Selimi indritsel...@yahoo.com wrote: Dear all, I'm using the maven plugin of axis2. As a maven plugin I thought that giving an output directory of outputDirectorysrc/main/java/outputDirectory(or better nothing at all) and the right package name I could find the generated sources on my package, but I'm seeing that the plugin generates a new directory src! So, at the end I have this situation: src/main/java/src... how I can get rid of this new src directory? Which are the best practices for integrating the plugin in a maven project? BTW, a build.xml file is also created, for what is needed? Thank you very much. Indrit Plugin Configuration: plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.5/version configuration packageNameit.rcs.maps.service.providers.microsoft.webservice/packageName wsdlFilesrc/main/resources/wsdl/mappoint.wsdl/wsdlFile generateServerSidetrue/generateServerSide outputDirectorysrc/main/java/outputDirectory /configuration executions execution idwsdl/id phasegenerate-sources/phase goals goalwsdl2code/goal /goals /execution /executions /plugin
Re: Fw: High Priority ,Parallel requests throwing null pointer exception.
This is a known issue that occurs when using Axiom = 1.2.8 together with Sun's StAX implementation. See issue WSCOMMONS-489. Andreas On Thu, Sep 17, 2009 at 15:33, sri ram pinnamaraju_sri...@yahoo.co.in wrote: Hi All, I have a webservice developed in axis 2. Works fine when there are sequence of requests. However when two parallel request hit the Axis Servlet I get exception. When I send these two requests sequentially everything is holy . So ideally,nothing is wrong with the request. PFA : For Error Stack trace Can Some one help me out on this. Should I make some changes in axis2.xml Or there's an patch available for Axis2 servlet for this scenario. Thanks, Sriram Keep up with people you care about with Yahoo! India Mail. Learn how. Add whatever you love to the Yahoo! India homepage. Try now! Now, send attachments up to 25MB with Yahoo! India Mail. Learn how.
Re: Problems encountered when upgrading from 1.4.1 to 1.5
On Tue, Sep 15, 2009 at 14:49, GOOSSENS Wim w...@cipal.be wrote: Hi all, Got 2 problems when upgrading to 1.5 (deployed in tomcat 6.0.18) 1. In 1.5 , only in the war distribution, the geronimo-jta_1.1_spec-1.1.jar is included in the lib This gives me problems when getting a UserTransation (class cast exception) This problem is solved by removing geronimo-jta_1.1_spec-1.1.jar (correct javaee.jar is in the tomcat/lib) 2. Version 1.5 goes back from xerces 2.8.1 to xerces 2.6.2 - Why is this ? I get problems with the reset method not being know by 2.6.2 Is this method used by your code or is it used by Axis2? - Is it save to put xerces 2.8.1 in the lib or should i use 2.9.1 instead (1.5 seems to work with xerces 2.8.1 and 2.9.1) Regards Wim
Re: axiom related question
commons-...@ws.apache.org is better. Andreas On Mon, Sep 14, 2009 at 19:55, Dmitry Beransky dmitry.ma...@gmail.com wrote: Hi, Is this the right place to post axiom questions? Dmitry
Re: Axis2 and SOAP encoding support
See [1] for the latest status.
[1] http://markmail.org/message/zbwojf3d67nrpisg
On Mon, Sep 7, 2009 at 11:26, Mauro Molinarimauro.molin...@cardinis.com wrote:
Hello all!
Trying to do a WSDL2Java (from Axis2 1.5) to generate the client code from a
WSDL that uses SOAP Encoding, I get the following error:
org.apache.axis2.schema.SchemaCompilationException: can not find type
{http://schemas.xmlsoap.org/soap/encoding/}Array from the parent schema
name of the parent schema
Browsing the mailing list I find a message from Anne Thomas Manes sent on
2008-05-21 stating that this error is caused by a reference to an undefined
type (soapenc:Array) and can be solved by importing the soapenc namespace.
However, Anne confirms that SOAP encoding is not supported by Axis2.
On the other hand, on 2007-12-24 Amila Suriarachchi wrote here that he
added SOAP encoded support to ADB and that now people can use soap
encoding with the Axis2 as well.
Today is 2009-09-07 and it's not clear yet:
- whether Axis2 does support RPC encoded WSDLs or not
- how well it does (meaning: is it just experimental code?)
So, are any news on this subject?
--
Mauro Molinari
Software Designer Developer
E-mail: mauro.molin...@cardinis.com
Re: Problem with ns qualified attribute of a client message
Is the string element defined in the schema? Andreas On Thu, Aug 27, 2009 at 11:23, err...@free.fr wrote: The xsd tells me : xsd:complexType name=QueryParam xsd:sequence xsd:element name=name type=xsd:string/ !-- See note in EPCIS spec text regarding the value for this element -- xsd:element name=value type=xsd:anyType / /xsd:sequence /xsd:complexType What I send with axis2 generated code : paramnameeventType/name value xmlns:s23=http://www.w3.org/2001/XMLSchema-instance; xmlns:s24=http://www.w3.org/2001/XMLSchema; s23:type=s24:stringObjectEvent/value /param What I want to send to note make the server down : paramnameeventType/name valuestringObjectEvent/string/value /param Is there a difference between xsd:AnyType and xs:AnyType ? Can't I modify the xsd to fit my needs ? (like saying that value contains a string or a datetime or ... ?, as the possibilities are limitatted. I have no problem with modifiying the schema definition) Do you know how can I do that ? - Amila Suriarachchi amilasuriarach...@gmail.com a écrit : How your value element looks like element name=value type=xs:anyType/ if so what you send is not according to the schema. Then I think there is not proper solution thanks, Amila. On Thu, Aug 27, 2009 at 1:37 PM, err...@free.fr wrote: No one ? - err...@free.fr a écrit : This is why the client should send the type. Server has said it is anyType so client has to send the type as the xsi type. As you have told your server does not process the runtime type, then it may have assume it as string. thanks, Amila. Well, Amila, the server process the runtime time like this : if it's string, the client send valuestringthestringvalue/string/value it it's dateTime, the client send valuedatetimethedatetime/datetime/value There's no need of having fully qualified namespace. What makes the server send me an error is that string is fully qualified : string xmlns:xi=http:// without this, it works (I've tried with SOAPUI) What do you think ? Any possibilities to remove these fully qualified namespace attribute ? Cheers, and thanks again -- Martin -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: imcompatible issue between axis2 and weblogic 10
Amila, That is correct. You added the check for Weblogic (and Sun) in r693811 (September 2008), so Axiom 1.2.8 should actually work with Weblogic. Andreas On Wed, Aug 26, 2009 at 06:47, Amila Suriarachchiamilasuriarach...@gmail.com wrote: On Wed, Aug 26, 2009 at 10:09 AM, Hu, Mary - ITG mary...@jpmorgan.com wrote: Sorry I don’t get you. Can you provide more detail? Which Axiom fix are you talking about? What is the Axis2 version you use? I think as Andreas has mentioned this fix should be there with Axiom 1.2.8. so if you use Axis2 1.5 this should work. thanks, Amila. Thanks, Mary Hu From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] Sent: Wednesday, August 26, 2009 12:30 AM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 On Wed, Aug 26, 2009 at 2:43 AM, Andreas Veithen andreas.veit...@gmail.com wrote: Since I recently worked on improving the interoperability of Axiom with various StAX parser, I can give you a precise answer. The short answer is: none (with Axiom 1.2.8). The long answer is: - Sun's parser (when used with Axiom up to version 1.2.8) causes a concurrency issue; see WSCOMMONS-489. - Axiom 1.2.8 makes the assumption that all parsers except Woodstox, Sun and Weblogic are broken. This is wrong because only the one from IBM is broken [1]. This means that any parser other than Woodstox, Sun, Weblogic Sometimes back I tested the Axis2 with web logic. Then I had problems with the weblogic parser and when I put the that weblogic entry to Axiom it worked fine. So if you picked an Axis2 version with this Axiom fix it should work with weblogic parser. thanks, Amila. and XLXP (IBM) will not work with Axiom 1.2.8. This excludes BEA's reference implementation (which will work fine with Axiom 1.2.9). - Finally, the one from IBM (which should work with any Axiom version) is not freely available. Andreas [1] http://svn.apache.org/viewvc?rev=800141view=rev On Tue, Aug 25, 2009 at 22:40, Hu, Mary - ITGmary...@jpmorgan.com wrote: No, Weblogic parser doesn't work for axis2. I'm wondering, beside wstx stream parser, what other parser could possibly work for axiom from axix2. Mary Hu -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Tuesday, August 25, 2009 3:53 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 The probable reason for this error is that the TLD file has a DOCTYPE declaration referencing a network location. Woodstox insists on loading the referenced DTD, while for the same configuration Weblogic's parser wouldn't load the DTD. This is due to an ambiguity in the StAX specs. Assuming that this explanation is correct, you have two options: 1) Also remove Woodstox and cross fingers that Axis2 works correctly with Weblogic's parser. Chances are high, but it is not guaranteed. I'm not a Weblogic user, but maybe somebody on the list can share his experience. 2) Hack the TLDs so that they don't have a DOCTYPE declaration with a system ID referencing a network location. Not sure what Weblogic's expectations are. Maybe you can just remove the DOCTYPE declaration entirely, maybe only the system ID or maybe you need to add the DTD to the JAR and change the system ID from an absolute URL to a relative one. Andreas On Mon, Aug 24, 2009 at 23:32, Hu, Mary - ITGmary...@jpmorgan.com wrote: After removed this jar, weblogic can't parse TLD anymore: Error while parsing the Tag Library Descriptor at c: ... \war\WEB-INF\lib\struts-1.2.9-lib.jar!/META-INF/tlds/struts-tiles.tld. com.ctc.wstx.exc.WstxIOException: java.sun.com at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086) at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCacheHe lper.java:134) Mary Hu Int: 8.226.2620 Ext: 973.793.2620 -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Monday, August 24, 2009 4:54 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 Try removing geronimo-stax-api_1.0_spec-1.0.1.jar from WEB-INF/lib. Andreas On Mon, Aug 24, 2009 at 22:28, Hu, Mary - ITGmary...@jpmorgan.com wrote: In axis2 - Application Server Specific Configuration Guide, it mentions how to deploy axis2 into weblogic. However, I have seen an issue that is blocking me. I wonder anyone has a solution for it: 1. I have a WAR containing axis2 jars. 2. My application requires prefer-web-inf-classes to be set as true in weblogic.xml. 3. I got below exception: java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory
Re: imcompatible issue between axis2 and weblogic 10
The probable reason for this error is that the TLD file has a DOCTYPE declaration referencing a network location. Woodstox insists on loading the referenced DTD, while for the same configuration Weblogic's parser wouldn't load the DTD. This is due to an ambiguity in the StAX specs. Assuming that this explanation is correct, you have two options: 1) Also remove Woodstox and cross fingers that Axis2 works correctly with Weblogic's parser. Chances are high, but it is not guaranteed. I'm not a Weblogic user, but maybe somebody on the list can share his experience. 2) Hack the TLDs so that they don't have a DOCTYPE declaration with a system ID referencing a network location. Not sure what Weblogic's expectations are. Maybe you can just remove the DOCTYPE declaration entirely, maybe only the system ID or maybe you need to add the DTD to the JAR and change the system ID from an absolute URL to a relative one. Andreas On Mon, Aug 24, 2009 at 23:32, Hu, Mary - ITGmary...@jpmorgan.com wrote: After removed this jar, weblogic can't parse TLD anymore: Error while parsing the Tag Library Descriptor at c: ... \war\WEB-INF\lib\struts-1.2.9-lib.jar!/META-INF/tlds/struts-tiles.tld. com.ctc.wstx.exc.WstxIOException: java.sun.com at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086) at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCacheHe lper.java:134) Mary Hu Int: 8.226.2620 Ext: 973.793.2620 -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Monday, August 24, 2009 4:54 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 Try removing geronimo-stax-api_1.0_spec-1.0.1.jar from WEB-INF/lib. Andreas On Mon, Aug 24, 2009 at 22:28, Hu, Mary - ITGmary...@jpmorgan.com wrote: In axis2 - Application Server Specific Configuration Guide, it mentions how to deploy axis2 into weblogic. However, I have seen an issue that is blocking me. I wonder anyone has a solution for it: 1. I have a WAR containing axis2 jars. 2. My application requires prefer-web-inf-classes to be set as true in weblogic.xml. 3. I got below exception: java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:137 ) at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCach eHelper.java:124) I know it is because weblogic can't use Woodstock stream parser. But how to instruct weblogic to use Woodstock beside wrap the app into an EAR (It doesn't apply me case)? Appreciate any help. Mary Hu This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
Re: imcompatible issue between axis2 and weblogic 10
Since I recently worked on improving the interoperability of Axiom with various StAX parser, I can give you a precise answer. The short answer is: none (with Axiom 1.2.8). The long answer is: - Sun's parser (when used with Axiom up to version 1.2.8) causes a concurrency issue; see WSCOMMONS-489. - Axiom 1.2.8 makes the assumption that all parsers except Woodstox, Sun and Weblogic are broken. This is wrong because only the one from IBM is broken [1]. This means that any parser other than Woodstox, Sun, Weblogic and XLXP (IBM) will not work with Axiom 1.2.8. This excludes BEA's reference implementation (which will work fine with Axiom 1.2.9). - Finally, the one from IBM (which should work with any Axiom version) is not freely available. Andreas [1] http://svn.apache.org/viewvc?rev=800141view=rev On Tue, Aug 25, 2009 at 22:40, Hu, Mary - ITGmary...@jpmorgan.com wrote: No, Weblogic parser doesn't work for axis2. I'm wondering, beside wstx stream parser, what other parser could possibly work for axiom from axix2. Mary Hu -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Tuesday, August 25, 2009 3:53 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 The probable reason for this error is that the TLD file has a DOCTYPE declaration referencing a network location. Woodstox insists on loading the referenced DTD, while for the same configuration Weblogic's parser wouldn't load the DTD. This is due to an ambiguity in the StAX specs. Assuming that this explanation is correct, you have two options: 1) Also remove Woodstox and cross fingers that Axis2 works correctly with Weblogic's parser. Chances are high, but it is not guaranteed. I'm not a Weblogic user, but maybe somebody on the list can share his experience. 2) Hack the TLDs so that they don't have a DOCTYPE declaration with a system ID referencing a network location. Not sure what Weblogic's expectations are. Maybe you can just remove the DOCTYPE declaration entirely, maybe only the system ID or maybe you need to add the DTD to the JAR and change the system ID from an absolute URL to a relative one. Andreas On Mon, Aug 24, 2009 at 23:32, Hu, Mary - ITGmary...@jpmorgan.com wrote: After removed this jar, weblogic can't parse TLD anymore: Error while parsing the Tag Library Descriptor at c: ... \war\WEB-INF\lib\struts-1.2.9-lib.jar!/META-INF/tlds/struts-tiles.tld. com.ctc.wstx.exc.WstxIOException: java.sun.com at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086) at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCacheHe lper.java:134) Mary Hu Int: 8.226.2620 Ext: 973.793.2620 -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Monday, August 24, 2009 4:54 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 Try removing geronimo-stax-api_1.0_spec-1.0.1.jar from WEB-INF/lib. Andreas On Mon, Aug 24, 2009 at 22:28, Hu, Mary - ITGmary...@jpmorgan.com wrote: In axis2 - Application Server Specific Configuration Guide, it mentions how to deploy axis2 into weblogic. However, I have seen an issue that is blocking me. I wonder anyone has a solution for it: 1. I have a WAR containing axis2 jars. 2. My application requires prefer-web-inf-classes to be set as true in weblogic.xml. 3. I got below exception: java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:137 ) at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCach eHelper.java:124) I know it is because weblogic can't use Woodstock stream parser. But how to instruct weblogic to use Woodstock beside wrap the app into an EAR (It doesn't apply me case)? Appreciate any help. Mary Hu This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http
Re: Combining mtom and gzip compressed soap response
Håkon, Can you try to add multipart/related to the list of compressableMimeTypes? Andreas 2009/8/25 Håkon Sagehaug hakon.sageh...@bccs.uib.no: Hi Andreas, Well the problem I guess is that the response from the service is not gzipped. I run the request/response through tcpmon and the request is gzipped but not the response. In tomcat service.xml I've got this Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on compressionMinSize=2048 noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml/ The client has these option set to true org.apache.axis2.transport.http.HTTPConstants.MC_GZIP_REQUEST org.apache.axis2.transport.http.HTTPConstants.MC_GZIP_RESPONSE org.apache.axis2.transport.http.HTTPConstants.MC_ACCEPT_GZIP and on the service I've got this MessageContext inMessageContext = MessageContext.getCurrentMessageContext(); // Obtain the operation context from the request message context OperationContext operationContext = inMessageContext .getOperationContext(); // Obtain the response (outgoing) message context from the operation context MessageContext outMessageContext; outMessageContext = operationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE); outMessageContext.setProperty(HTTPConstants.MC_GZIP_RESPONSE,Boolean.TRUE); outMessageContext.setProperty(HTTPConstants.MC_ACCEPT_GZIP,Boolean.TRUE); I've got the same configuration for a service that does not have mtom enabled this works fine, but not in the service enabled. If I remove the parameter parameter name=enableMTOM locked=falsetrue/parameter from service.xml the response is gzipped. cheers, Håkon 2009/8/24 Andreas Veithen andreas.veit...@gmail.com Håkon, Could you please be a bit more precise about the problem you are encountering? Andreas 2009/8/21 Håkon Sagehaug hakon.sageh...@bccs.uib.no: Hi all, I wanted to know if it's possible to have both gzip compressed soap response that contains mtom, I got gzip response working on a non-mtom service, but not when mtom was enabled. cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
Re: Combining mtom and gzip compressed soap response
Håkon, Could you please be a bit more precise about the problem you are encountering? Andreas 2009/8/21 Håkon Sagehaug hakon.sageh...@bccs.uib.no: Hi all, I wanted to know if it's possible to have both gzip compressed soap response that contains mtom, I got gzip response working on a non-mtom service, but not when mtom was enabled. cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
Re: How to run AXIS2 fine on Tomcat behind an Apache server.
See AXIS2-3843. Andreas On Mon, Aug 24, 2009 at 12:17, frougeotfrederic.roug...@capgemini.com wrote: Hi, did you find a convenient solution ? We are experiencing the same case, and hack the wsdl file generated by axis for now, but it does not suit us very well ... pino lollo wrote: How to run AXIS2 fine on Tomcat behind an Apache server. I have problem with internet 80 or intranet 8080 wsdl invocation. Is there anyone who can show me how to do or can tell me where I am wrong? Thanks in advance. Marco 1 Adsl internet connection, 1 public ip address: 83.211.93.144, 1 router modem, 1 lan, 1 pc server (internal ip address 192.168.1.10) On the pc server there are: 1 Apache http server 2.2, 1 Tomcat 6,0. Tomcat responds port 8080, Apache http server responds to internet at port 80. I have same http applications on Apache http server that work and you can see on internet at the address: www.acgcomplementi.com I have also same web applicationes on Tomcat that respond in the lan to port 8080 and are redirected by Apache Http server on Internet: www.p2p2mpa.com and respond there on port 80. To do this I configured a virtual server on the modem router so the requests that arrive from internet at the address 83.211.93.144 and port 80 are redirected to the pc server 192.168.1.10:80, and this works. There, on the pc server, the requests on the port 80 are managed by the Apache Http server. I worked on the file httpd.conf, and I activated the proxy module with these comands: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_connect_module modules/mod_proxy_connect.so and I added also these directives: ProxyPass /p2p2mpa/ http://localhost:8080/p2p2mpa/ ProxyPass /sito/ http://localhost:8080/sito/ ProxyPass /ws_p2p2mpa/ http://localhost:8080/ws_p2p2mpa/ (/sito/ is for www.acgcomplementi.com). /p2p2mpa/ is for www.p2p2mpa.com /ws_p2p2mpa/ if for the axis2 webservice that doesn't work. Till now it is all fine. Here began the problems. I developed, using eclipse, a web application that exposes some webservices. I used axis2. I placed the war file (ws_p2p2mpa.war) in the webapps Tomcat directory. If I invoke the the wsdl file in the lan all works fine: at the address http://192.168.1.10:8080/ws_p2p2mpa/ the axis2 welcom page responds correctly. At the address http://192.168.1.10:8080/ws_p2p2mpa/services/Ws?wsdl Axis2/Tomcat answers with the right wsdl file: it has the right endpoint: - wsdl:port name=WsHttpSoap11Endpoint binding=ns:WsSoap11Binding soap:address location=http://192.168.1.10:8080/ws_p2p2mpa/services/Ws.WsHttpSoap11Endpoint/; / /wsdl:port Instead if I invoke the wsdl file from internet I have some problems: If I use this address: http://83.211.93.144/ws_p2p2mpa/ Axis2 responds, I see the Axis2 welcome page but I cannot see correctly the Axis2 wing images; if I navigate and I select a link, for example: “Services” it shows and uses this wrong address: http://192.168.1.10:8080/ws_p2p2mpa/services/listServices as it was invoked from the lan and not internet, I aspected: http://83.211.93.144/ws_p2p2mpa/services/listServices If I invoke the wsdl and I use this address http://83.211.93.144/ws_p2p2mpa/services/Ws?wsdl I see the wsdl file but it has as endpoint address the same it has if it is invoked from the lan: http://192.168.1.10:8080/ws_p2p2mpa/services/Ws.WsHttpSoap11Endpoint/ I aspected http://83.211.93.144/ws_p2p2mpa/services/Ws.WsHttpSoap11Endpoint/ Therefore I looked around to find a solution, and I found to manage the axis2.xml configuration file. I changed the file \Apache Software Foundation\Tomcat 6.0\webapps\ws_p2p2mpa\WEB-INF\conf\axis2.xml in this way: first, in the transportReceiver section I added this parameter proxyPort = 80: that is a look of the transposrtReceiver section: - transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter parameter name=proxyPort80/parameter but nothing changed. Two, I added this instruction: parameter name=httpFrontendHostUrlhttp://83.211.93.144/ws_p2p2mpa/parameter (http without s). Then I tested it but it doesn't work again: the end point address in the wsdl file doesn't changed, it is always the same, if I invoke from internet or lan the end point address it is always http://192.168.1.10:8080/ws_p2p2mpa/services/Ws.WsHttpSoap11Endpoint/ If I invoke the axis2 welcome page from internet it work fine, instead if I invoke the axis2 welcome page from the LAN now it doesn't work. I tried with acxis2 1.3 and tomacat 5.0 and apache server 2.2, then I changed and I am working now with axis2 1.41 and Tomcat 6.0. I also added in the
Re: imcompatible issue between axis2 and weblogic 10
Try removing geronimo-stax-api_1.0_spec-1.0.1.jar from WEB-INF/lib. Andreas On Mon, Aug 24, 2009 at 22:28, Hu, Mary - ITGmary...@jpmorgan.com wrote: In axis2 - Application Server Specific Configuration Guide, it mentions how to deploy axis2 into weblogic. However, I have seen an issue that is blocking me. I wonder anyone has a solution for it: 1. I have a WAR containing axis2 jars. 2. My application requires prefer-web-inf-classes to be set as true in weblogic.xml. 3. I got below exception: java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:137 ) at weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCach eHelper.java:124) I know it is because weblogic can't use Woodstock stream parser. But how to instruct weblogic to use Woodstock beside wrap the app into an EAR (It doesn't apply me case)? Appreciate any help. Mary Hu This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
Re: [Axis2] Priority of 3rd party libs
Axis2 just follows the standard Java class loading policy. See the Javadoc of ClassLoader. Andreas On Thu, Aug 20, 2009 at 08:25, Grimm, Markusgr...@juris.de wrote: Hi all, I'm a little bit confused about the behaviour of axis2, using 3rd party libs. I've got a WS with a lib folder in its aar-file where residing some libs like commons-lang, commons-io and so on. In the WEB-INF/lib folder there are some jars that axis2 brings with f.e. commons-lang, too. Suprisingly (for me) the service uses the commons-lang jar in its WEB-INF/lib and doesn't use the commons-lang in the lib-folder at runtime, instead of the .aar-file libs. So far I thought that axis2 prioritizes the auxiliary jars in the aar-file more than its basic jars ?! Can anyone explain the background story of this behaviour? Thanks, Markus
Re: Help! Error when testing Axis2 client
If you are sure that all classes/JARs are there, then it means that some classes are loaded by the wrong class loader in the class loader hierarchy. This is something that is difficult to solve on a mailing list. My recommendations: 1) Start with a fresh server + Axis2 WAR or Axis2 binary distribution, deploy the service and check if it works. 2) Try to familiarize yourself a bit more with how class loading works in Java, especially in the context of an application/Web server. This will help you to understand and debug this kind of problems. Andreas On Thu, Aug 20, 2009 at 04:40, Claraclaire_l...@yahoo.com wrote: Hi, My xmlbeans JAR is located at C:\xmlbeans-2.4.0\lib. I also placed this in my classpath (CLASSPATH environment variable) but I am still getting the below error. What could be causing this? --- On Wed, 8/19/09, Andreas Veithen andreas.veit...@gmail.com wrote: From: Andreas Veithen andreas.veit...@gmail.com Subject: Re: Help! Error when testing Axis2 client To: axis-user@ws.apache.org Date: Wednesday, August 19, 2009, 11:10 AM Which classloader is the xmlbeans JAR loaded from (i.e. where is the xmlbeans JAR located)? Idem for the TypeSystemHolder class. Andreas On Wed, Aug 19, 2009 at 11:43, Claraclaire_l...@yahoo.com wrote: Hi Andreas, Thank you for your very helpful response. You are right, my jar files from 2 different axis2 versions got mixed up. I was using axis2 v1.4 but i used axis2.jar of axis2 v1.5. The error was resolved by using axis2 v1.5. However, when I tried running my sample client code, I got the below error during runtime: [17:10:23.500] java.lang.ExceptionInInitializerError [17:10:23.500] at com.sample.LoginRequestDocument$Factory .parse(LoginRequestDocument.java:86) [17:10:23.500] at com.sample.Axis2SampleMessageR eceiverInOut.fromOM(Axis2SampleMessageReceiverInOut.java:2540) . . . [17:10:23.500] Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSyst em. Unable to load class with name schemaorg_apache_xmlbeans.system.s23B9B2646D7 77B890CFC862E67D5196A.TypeSystemHolder. Make sure the generated binary files are on the classpath. [17:10:23.500] at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBean s.java:783) [17:10:23.500] at com.sample.LoginRequestDocument.clinit (LoginRequestDocument.java:19) [17:10:23.500] ... 21 more [17:10:23.500] Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xml beans.system.s23B9B2646D777B890CFC862E67D5196A.TypeSystemHolder [17:10:23.500] at com.caucho..loader.DynamicClassLoader.loadClass(DynamicClassLo ader.java:1133) [17:10:23.500] at com.caucho.loader.DynamicClassLoader.loadClass(DynamicClassLo ader.java:1113) [17:10:23.500] at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBean s.java:769) [17:10:23.500] ... 22 more I already placed the schemaorg_apache_xml beans.system.s23B9B2646D777B890CFC862E67D5196A.TypeSystemHolder in the classpath. Is there something that I might be missing? thanks, Clara --- On Tue, 8/18/09, Andreas Veithen andreas.veit...@gmail.com wrote: From: Andreas Veithen andreas.veit...@gmail.com Subject: Re: Help! Error when testing Axis2 client To: axis-user@ws.apache.org Date: Tuesday, August 18, 2009, 2:45 AM This probably means that you have a mix of JARs from different Axis2 versions (maybe at different locations in the class loader hierarchy). Andreas
Re: Integration in Equinox-OSGi
Daniel, Actually I wanted to point you to the following document: https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/saminda/osgi_test/axis2_osgi_integration.pdf This has nothing to do with Carbon. Note that I never tested the approach described in that document myself. Andreas On Wed, Aug 19, 2009 at 09:32, Daniel Bimschasdan...@bimschas.com wrote: Andreas, thank for you answer. I suppose you wanted to point me to the carbon framework (http://wso2.org/projects/carbon) mentioned in this thread? It's a nice thing, but for me, it's simply too much. All I want is a naked Axis2 runtime running in my OSGi container. For my purposes it doesn't make sense to simply introduce another framework as this will produce an even larger distributable with features I don't need and potentially bugs and problems I don't need too, not to mention the time I've to put in to fully understand what the framework does. So, I still would be glad to hear about some easy-to-use OSGi compatible Axis2 distribution. Kind regards, Daniel Am 10.08.2009 um 19:45 schrieb Andreas Veithen: Daniel, Please have a look a the following thread: http://markmail.org/thread/3xbjzrsvxombqvkd Andreas On Mon, Aug 10, 2009 at 18:12, Daniel Bimschasdan...@bimschas.com wrote: Hi Folks! I'm trying to simply integrate Axis2 into an Eclipse Equinox OSGi container. So far I found no easy way to do that. I think the ideal way is that there was a How-To somewhere which says: install file A, B, C, ... from Axis2-src distribution and you're done. Is there a tutorial like that which I missed? Even more ideal would be an OBR (OSGi bundle repository) repository holding the main bundle and all it's dependencies, so that one could install it by running obr install when on Apache Felix or after deploying some OBR implementation into Equinox. I tried to other ways to install it, which also failed. First one was using an OSGi-Axis2 distribution from the Knopflerfish project which simply failed because of invalid bundle headers (syntax errors and missing imports). Second one was to try to install it after downloading the src-distribution of Axis2, running complete build of it with Maven and trying to install the individual packages by hand. This is very tedious as there's no easy way to find out which bundle/jar imports/exports the packages needed and so on. Is there maybe a tutorial for that? Are there any plans for a Maven target that puts all relevant packages into one directory so that OSGi users simply use all jars in it to get up and running? I would be very thankful for some help on this (somewhat tedious) problem! Kind regards, Daniel -- Daniel Bimschas Fleischhauer Straße 45 23552 Lübeck dan...@bimschas.com --
Re: Application Time out of sync from server time
Are you using virtualization? Andreas On Wed, Aug 19, 2009 at 13:20, Krystian Szczesnykrystian.szcze...@intecbilling.com wrote: -Original Message- From: Krystian Szczesny [mailto:krystian.szcze...@intecbilling.com] Sent: 19 August 2009 11:07 To: axis-user@ws.apache.org Subject: Application Time out of sync from server time Hi, I know this is not a very Axis2 specific question, but since the app is based on Axis2 I thought I would start in here. We have an application, which for every call received by Axis2, calls our system. In the call it includes the current date, which is then treated by our system as effective date of the call. Although both: Axis2 app and our system are on the same server, the java app reports a different time than server time. Depending on the environment, we have from 4 seconds behind server time to 10 seconds ahead of server time. Problem is, that we truncate the time to the nearest minute, and for few seconds during a minute, we will have a different time in our system and in the call from the java app. Could you please tell me where I should start looking for the cause of this problem? Code in the java app is extremely simple: Request comes in-convert xml to map-get connection to our system-get current time-call our system-convert returned map to xml-send response This is how we get current date: Date invokeDate = DateUtils.truncate(new Date(), Calendar.MINUTE); Where DateUtils is: org.apache.commons.lang.time.DateUtils; and Date is: java.util.Date It's not like this date is only reported wrong when we make the call out. For logging we use SLF4J with Logback, and the timestamp of the log entries is same as the new Date() in the java app code and different from the server time. Could you please point me in some direction, where I should start digging for answers? App is deployed on HP-UX, we are using: $ java -version java version 1.5.0.07 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.07-_20_mar_2007_05_31) Java HotSpot(TM) Server VM (build 1.5.0.07 jinteg:03.20.07-11:05 IA64, mixed mode) Axis2 1.4.1 All help will be appreciated, Thanks, Krystian Hi again, Just to follow up: We have conducted an experiment: changed the server time by 10 seconds into the future and the date in the java app was not affected. This is something, as the changes might have been caused by NTP process. Is there any way I could sync the date in the java app with the server? I would have always though this is done automatically... Thanks, Krystian This e-mail and any attachments are confidential and may also be legally privileged and/or copyright material of Intec Telecom Systems PLC (or its affiliated companies). If you are not an intended or authorised recipient of this e-mail or have received it in error, please delete it immediately and notify the sender by e-mail. In such a case, reading, reproducing, printing or further dissemination of this e-mail or its contents is strictly prohibited and may be unlawful. Intec Telecom Systems PLC does not represent or warrant that an attachment hereto is free from computer viruses or other defects. The opinions expressed in this e-mail and any attachments may be those of the author and are not necessarily those of Intec Telecom Systems PLC.
Re: Help! Error when testing Axis2 client
This probably means that you have a mix of JARs from different Axis2 versions (maybe at different locations in the class loader hierarchy). Andreas On Tue, Aug 18, 2009 at 11:30, Maria Claribelle M. Lotoclaire_l...@yahoo.com wrote: Hi, I am currently developing a webservice using axis2 and Resin 3.1.9. I successfully generated the .aar file, dropped it on C:\resin\webapps\axis2\WEB-INF\services. I was able to get to the axis2 happy page. However, when I tried calling my service by accessing it through the url like http://localhost:90/axis2/services/SampleWebservice/login?username=abcpassword=def, i am getting the below error in the resin console: [14:58:14.812] Resin started in 51750ms [15:00:31.500] java.lang.NoSuchMethodError: org.apache.axis2.engine.AxisEngine. init(Lorg/apache/axis2/context/ConfigurationContext;)V [15:00:31.500] at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngin e(RESTUtil.java:135) [15:00:31.500] at org.apache.axis2.transport.http.util.RESTUtil.processURLReque st(RESTUtil.java:130) [15:00:31.500] at org.apache.axis2.transport.http.AxisServlet$RestRequestProces sor.processURLRequest(AxisServlet.java:829) [15:00:31.500] at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet .java:255) [15:00:31.500] at javax.servlet.http.HttpServlet.service(HttpServlet.java:114) [15:00:31.500] at javax.servlet.http.HttpServlet.service(HttpServlet.java:91) [15:00:31.500] at com.caucho.server.dispatch.ServletFilterChain.doFilter(Servle tFilterChain.java:103) Any idea what causes this problem and how I could resolve this? thanks a lot. Clara Pia
Re: [AXIS2] Control character encoding used by axis2 server for responses
trace files for the two request/response trials are attached to this message. Best regards, Michael On Fri, Aug 14, 2009 at 7:11 PM, Andreas Veithen andreas.veit...@gmail.com wrote: Michael, Can you test this with 1.5 and if the problem persists, create a minimal AAR that reproduces the problem (so that we can debug it)? Andreas On Fri, Aug 14, 2009 at 12:27, Michael Fryarsfryar...@gmail.com wrote: Axis2 v1.4.1, running in a WAR in a tomcat 6 container. On Fri, Aug 14, 2009 at 12:20 PM, Andreas Veithen andreas.veit...@gmail.com wrote: Which version of Axis2 do you use? Andreas On Fri, Aug 14, 2009 at 11:39, Michael Fryarsfryar...@gmail.com wrote: Hello, I'm seeking some advice/help with a character encoding problem with an axis2 service (i.e. server side). When my service receives a (WS/SOAP) request with: Content-Type: text/xml; charset=UTF-8 in the HTTP header, everything works fine, any unusual charcters in the response are correctly encoded in UTF-8. But when the service receives a request with: Content-Type: text/xml; charset=ISO-8859-1 the response is inconsistent. The response is labelled as ISO-8859-1: Content-Type: text/xml; charset=ISO-8859-1 ?xml version=1.0 encoding=ISO-8859-1? but in fact the message body is still encoded in UTF-8. Should the axis2 engine automatically select and use ISO-8859-1 encoding for the response? Or is it something I need to configure? Or is it always UTF-8? I understood from a previous thread (How to change Axis2 response character encoding) that axis2 selects a a message builder based on the Content-Type header. My axis2.xml config does not contain anything specifically for text/xml : messageBuilders messageBuilder contentType=application/xml class=org.apache.axis2.builder.ApplicationXMLBuilder/ messageBuilder contentType=application/xml class=org.apache.axis2.builder.ApplicationXMLBuilder/ messageBuilder contentType=application/x-www-form-urlencoded class=org.apache.axis2.builder.XFormURLEncodedBuilder/ messageBuilder contentType=multipart/form-data class=org.apache.axis2.builder.MultipartFormDataBuilder/ /messageBuilders Is this where I need to intervene to control the response encoding? Thanks in advance for any help you can provide. Michael Fryars
Re: Greater than's not being escaped in content of element in response
Axis2 always creates XMLStreamReader/Writer objects using org.apache.axiom.om.util.StAXUtils and this class manages the factories. In version 1.2.9 of Axiom (currently under development) there is a new mechanism that allows to set properties on these factories, as described in [1]. Unfortunately this is limited to properties of type String, Integer and Boolean. This gives you two options: 1) Hack StAXUtils so that it sets P_TEXT_ESCAPER. This means that you have to create your own version of that class and repackage axiom-api-x.x.x-jar. 2) There will be some other enhancements in StAXUtils (in particular to solve AXIS2-4450), and probably these changes will provide (or may be easily extended to provide) hooks that would allow to do this type of customizations. My recommendation: If you are impatient, go for solution 1. If you need a proper solution that will be part of the next Axis2 release, wait for solution 2. Andreas [1] http://people.apache.org/~veithen/axiom/userguide/ch04.html#d0e753 On Mon, Aug 17, 2009 at 17:46, twosnacmwiesem...@bloomberg.net wrote: Hey Andreas, This seems to be what I would hijack with mine own type to do the escaping I need. http://woodstox.codehaus.org/3.2.8/javadoc/org/codehaus/stax2/XMLOutputFactory2.html#P_TEXT_ESCAPER http://woodstox.codehaus.org/3.2.8/javadoc/org/codehaus/stax2/XMLOutputFactory2.html#P_TEXT_ESCAPER I'm not clear on where to set this properties or where to get access to these factories in the whole Axis flow. Can you give me a general pointer regarding this? -- View this message in context: http://www.nabble.com/Greater-than%27s-not-being-escaped-in-content-of-element-in-response-tp24948530p25009230.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: AxisAdminServlet in .jar
That makes sense. Bundling these classes into a separate Maven artifact would indeed give users more options when assembling a custom WAR file. Please open a JIRA for this. Andreas On Tue, Aug 18, 2009 at 22:41, Asenasen.m.ase...@gmail.com wrote: Hi there- Is there a way to get the AxisAdminServlet for 1.5 release into a .jar file. The current .war distribution comes with webapp/WEB-INF/classes and there is the .class file, but I really do not want to put this into my application in which I have integrated axis. I know that I can create my own .jar, but it would be nice to have this already done as it was in 1.4.1 release, and not to be another application maintenance point, at least in my case. Thank you.
Re: Axis2 - session management - HELP!!!
Why do you need to store this data? The two operations (extracting the data from the request and preparing the response) will be executed in the context of the same method invocation, namely MessageReceiver#receive (or an equivalent method in one of the subclasses). Andreas On Mon, Aug 17, 2009 at 20:32, Ramya K Gramaramyakgr...@gmail.com wrote: I'm sorry for not being clear enough. The specific service that I need to develop needs to be able to remember the request message inorder to generate the response message. The reason being that most of the response (nearly 80%) is the same as the request, except with a few additional data coming from the db. Sample Request xml Response XML are as below: soap:envelope soap:header…/soap:header soap:body abcRequest allElements e1Req val/e1 e2 Req val /e2 e3 Req val /e3 . e20 /e20 /allElements /abcRequest /soap:body /soap:envelope Response XML: soap:envelope soap:header…/soap:header soap:body abcResponse allElements e1Req val/e1 e2 Req val /e2 e3 Req val /e3 e20New DBVal/e20 /allElements /abcResponse /soap:body /soap:envelope So the idea is that since the response format is the same and its just a few tag values that need to be updated, we are thinking of saving the request XML in the context as a Java Object. Can something like below be done in Axis2’s Skeleton? MessageContext.getOperationContext().setMyObject(“myObj”,abcRequest); Then be able to retrieve it back on the way out as below: AbcRequest abcRequest = (AbcRequest)MessageContext.getOperationContext().getMyObject(“myObj”); AllElements[] allElements = abcRequest.getAllElements(); Update required elements in the allElements array with the new DB values. Get hold of the outgoing response Java Object. Set allElements section in the response. Send the response out. Can this be done in Axis2? On Wed, Aug 12, 2009 at 2:00 PM, Andreas Veithen andreas.veit...@gmail.com wrote: To be honest, I don't really understand the idea behind your approach. Either there is something missing in your explanation, or your approach is way too complicated. Andreas On Wed, Aug 12, 2009 at 16:05, Ramya K Gramaramyakgr...@gmail.com wrote: Thanks for ur tip on the CDATA. I'll look into that and come back with any issues I may have. The other question I have is regarding storing the request xml. Where and how could that be done? I read that OperationContext and SOAPSession can be used to achieve this. But I will need some help with the API. Thanks, wsnewbie On Wed, Aug 12, 2009 at 3:32 AM, Andreas Veithen andreas.veit...@gmail.com wrote: You need to take into account that Axis2 by default doesn't preserve CDATA sections (and converts them to text nodes). You can use the approach described in [1] to change this. Andreas [1] http://people.apache.org/~veithen/synapse/faq.html On Wed, Aug 12, 2009 at 00:39, Ramya K Gramaramyakgr...@gmail.com wrote: Hello, I'm using Axis2/Java to create a web service wherein the request and response xmls are very much the same except for some additional data from the db that gets added on to the request as a response. Also, there is a lot of CDATA sections in the request that need to be sent back in the response as is without any modification. In designing this service, we've come up with the strategy of saving the incoming SOAP request.xml(in memory) somewhere so that it can be used to recreate the response + updated data from the db (stuffing in empty tags with data from db). Is this a good approach as far as Axis2 is concerned. If so what/how would be teh best place of storing the request.xml. Are there any multi-threading issues that i need to be concerned about. What would be a fool-proof and optimal approach of doing this in Axis2. From my initial research, I've found that OperationContext with SOAPSession scope can be used for this. Am I correct here? Also, since there are a lot of CDATA sections in the request and response xmls, is there anything special that needs to be done? Your feedback will be very helpful in designing my service further. Thanks, wsNewbie.
Re: autogenerated wsdl contains wrong service location
:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Quoting Andreas Veithen andreas.veit...@gmail.com: Alex, If you can't upgrade to a newer version then you will have to use the hostname parameter solution, at least for the time being. Anyway, thanks for letting us know about the WTP issue. We will have to investigate this, since it is a real showstopper. Andreas On Wed, Jul 22, 2009 at 14:25, Alexander Bruchalexander.br...@h-net.com wrote: Andreas, if you use i.e. eclipse galileo the j2ee Version. Download Axis2 1.5 Go to preferences and configure Axis2 Path. Than choose a POJO and select WebService / Create WebService. The process will fail with ClassNotFound Exceptions because i.e. if i remember right the AxisAdminServlet could not be found. After digging arround a little bit 'I recognized that some classes where moved to other Packages so calling the AxisAdminServlet from eclipse to deploy the Service was no possible anymore. Thats why axis2 does not work out of the box with eclipse includeing WTP Regards, Alex I tried to use Eclipse galille Quoting Andreas Veithen andreas.veit...@gmail.com: Alex, Do you have more info about the Eclipse problem (which tools, how to reproduce, etc.)? Andreas On Wed, Jul 22, 2009 at 14:01, Alexander Bruchalexander.br...@h-net.com wrote: Andreas, we currently use 1.4 since 1.5 was not running good together with eclipse. I remeber that some classes were moved in other packages with 1.5 but the eclipse axis2 webservice support tools still looks for the old packagenames/classnames. So upgrading to 1.5 is not possible for the current project. Regards, Alex Quoting Andreas Veithen andreas.veit...@gmail.com: Alex, It's true that one would expect that Axis2 automatically uses the hostname or address through which the request for the WSDL came in. Technically this information is available from the ServletContext. I'm wondering whether this issue has not been addressed since the 1.4 release. Would it be possible for you to test that with version 1.5? Andreas On Wed, Jul 22, 2009 at 08:52, Alexander Bruchalexander.br...@h-net.com wrote: Andreas, thank you for responding. We publish axis2 as part of the application. Setting the hostname parameter in axis2.xml could be a solution but that means if we deploy the war on a different server, we have to update the axis2.xml. My prefered way would be to let axis2 automaticaly choose the hostname of the server it is published to. So i dont have to take care to update the axis2.xml after deployment. Regards Alex Quoting Andreas Veithen andreas.veit...@gmail.com: Alex, Normally, it should be possible to specify this using the hostname parameter in axis2.xml. Regards, Andreas On Tue, Jul 21, 2009 at 15:38, Alexander Bruchalexander.br...@h-net.com wrote: Hi all, I'am using Axis2 (Version 1.4) and i have a problem with the automaticaly generated wsdl. The Wsdl generates the follwoing Part: wsdl:service name=MyService wsdl:port name=MyServiceHttpEndpoint binding=ns:MyServiceHttpBinding http:address location=http://192.168.1.30:8080/TestApp/services/MyService.MyServiceHttpEndpoint/ /wsdl:port /wsdl:service My Problem is that the http:address - location use the IP-Address of the second networkcard (eth1) instead of the first networkcard (eth0). I tried much things but did not get the wsdl to use the IP-Address from eth0. So now I would like the wsdl to use the hostname instead of the IP-Address. I hope someone can help me with this. Thank you Alex -- Hölle Hüttner AG Informationstechnologie Alexander Bruch Derendinger Str. 40 D-72072 Tübingen Telefon +49-(0)611-73425-20 Telefax +49-(0)611-73425-29 E-Mail: alexander.br...@h-net.com Hölle Hüttner AG, Tübingen HR-Gericht Stuttgart HRB-Nr. 382139 Vorstand: Peter Beck, Dr.Steffen Hüttner Aufsichtsratsvorsitzender: Prof. Dr.Dieter Mecke -- Hölle Hüttner AG Informationstechnologie Alexander Bruch Derendinger Str. 40 D-72072 Tübingen Telefon +49-(0)611-73425-20 Telefax +49-(0)611-73425-29 E-Mail: alexander.br...@h-net.com Hölle Hüttner AG, Tübingen HR-Gericht Stuttgart HRB-Nr. 382139 Vorstand: Peter Beck, Dr.Steffen Hüttner Aufsichtsratsvorsitzender: Prof. Dr.Dieter Mecke -- Hölle Hüttner AG Informationstechnologie Alexander Bruch Derendinger Str. 40 D-72072 Tübingen Telefon +49-(0)611-73425-20 Telefax +49-(0)611-73425-29 E-Mail: alexander.br...@h-net.com Hölle Hüttner AG, Tübingen HR-Gericht Stuttgart HRB-Nr. 382139 Vorstand: Peter Beck, Dr.Steffen Hüttner Aufsichtsratsvorsitzender: Prof. Dr.Dieter Mecke -- Hölle Hüttner AG Informationstechnologie Alexander Bruch Derendinger Str. 40 D-72072 Tübingen Telefon +49-(0)611-73425-20 Telefax +49-(0)611-73425-29 E-Mail
Re: Passing 2 byte arrays to web service is yielding strange results
Could be the same issue as AXIS2-4308. Martin, are you looking into this?
Andreas
On Fri, Aug 14, 2009 at 22:17, Martin Gaintymgai...@hotmail.com wrote:
cant access the aar ?
any ability to put this on a http or ftp site or display the wsdl?
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire
informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
de ceci est interdite. Ce message sert à l'information seulement et n'aura
pas n'importe quel effet légalement obligatoire. Étant donné que les email
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.
Date: Fri, 14 Aug 2009 12:27:42 -0700
From: justin.fe...@gmail.com
To: axis-user@ws.apache.org
Subject: Re: Passing 2 byte arrays to web service is yielding strange
results
Attached is the AAR file (TestWS.aar) as well as a test client
(TestClient.jar). The test client files were generated using WSDL2Java
(ADB).
-Justin
http://www.nabble.com/file/p24977228/TestClient.jar TestClient.jar
http://www.nabble.com/file/p24977228/TestWS.aar TestWS.aar
Andreas Veithen-2 wrote:
Justin,
Can you package your service in an AAR file (or any other deployable
artifact) and post a simple test client that reproduces the problem?
Andreas
On Fri, Aug 14, 2009 at 00:19, JFeistyjustin.fe...@gmail.com wrote:
Axis newbie hereI have a very simple (pojo) web service and am
serving it
using Axis2 v1.5 in Tomcat 6. I have one web method called test(). It
takes as a parameter a 'Placeholder' object. That 'Placeholder' object
has
two private byte array fields exposed with getters and setters. Here
is
the
server-side code:
public class TestWS {
public void test(Placeholder p) {
System.out.println(Placeholder.first size: +
p.getFirst().length);
System.out.println(Placeholder.second size: +
p.getSecond().length);
}
public class Placeholder {
private byte[] first = null;
private byte[] second = null;
public byte[] getFirst() {
return first;
}
public void setFirst(byte[] first) {
this.first = first;
}
public byte[] getSecond() {
return second;
}
public void setSecond(byte[] second) {
this.second = second;
}
}
I call this web method and set the Placeholder's 'first' property to a
5-byte byte array and the 'second' property to a 2-byte byte array.
The
output is very surprising:
Placeholder.first size: 5
Placeholder.second size: 5
What is going on here? Why is the second byte array the same as the
first?
Thanks,
Justin
--
View this message in context:
http://www.nabble.com/Passing-2-byte-arrays-to-web-service-is-yielding-strange-results-tp24960357p24960357.html
Sent from the Axis - User mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/Passing-2-byte-arrays-to-web-service-is-yielding-strange-results-tp24960357p24977228.html
Sent from the Axis - User mailing list archive at Nabble.com.
Windows Live™: Keep your life in sync. Check it out.
Re: [AXIS2] Control character encoding used by axis2 server for responses
Which version of Axis2 do you use? Andreas On Fri, Aug 14, 2009 at 11:39, Michael Fryarsfryar...@gmail.com wrote: Hello, I'm seeking some advice/help with a character encoding problem with an axis2 service (i.e. server side). When my service receives a (WS/SOAP) request with: Content-Type: text/xml; charset=UTF-8 in the HTTP header, everything works fine, any unusual charcters in the response are correctly encoded in UTF-8. But when the service receives a request with: Content-Type: text/xml; charset=ISO-8859-1 the response is inconsistent. The response is labelled as ISO-8859-1: Content-Type: text/xml; charset=ISO-8859-1 ?xml version=1.0 encoding=ISO-8859-1? but in fact the message body is still encoded in UTF-8. Should the axis2 engine automatically select and use ISO-8859-1 encoding for the response? Or is it something I need to configure? Or is it always UTF-8? I understood from a previous thread (How to change Axis2 response character encoding) that axis2 selects a a message builder based on the Content-Type header. My axis2.xml config does not contain anything specifically for text/xml : messageBuilders messageBuilder contentType=application/xml class=org.apache.axis2.builder.ApplicationXMLBuilder/ messageBuilder contentType=application/xml class=org.apache.axis2.builder.ApplicationXMLBuilder/ messageBuilder contentType=application/x-www-form-urlencoded class=org.apache.axis2.builder.XFormURLEncodedBuilder/ messageBuilder contentType=multipart/form-data class=org.apache.axis2.builder.MultipartFormDataBuilder/ /messageBuilders Is this where I need to intervene to control the response encoding? Thanks in advance for any help you can provide. Michael Fryars
