Problem with Polymorphic data types with ADB stubs on client side and RPC*MessageReceiver on Server side.
Hi, I have an existing spring framework based Java application where-in the services were exposed as web services using Axis 1.3. Now we are migrating the same to Axis2 1.4.1. I have used the RPC*MessageReceiver classes for my MEPs and instead of service implementation class parameter SeviceClass I am using the ServiceObjectSupplier and the SpringBeanName parameters in the services.xml file to describe my service. On the client side I am using the ADB stubs. When I encounter any polymorphic data here i.e. if the client is sending a polymorphic data type as a parameter, the RPC*MessageReceiver class is not able to de-serialize the exact derived object instead it creates an object of the base class, resulting in data loss. Actually the problem comes in the BeanUtil class's deserailize() method. A fix is already mentioned there for issues AXIS2-2055 and AXIS2-1899 to support polymorphism in POJO approach. The code expects that a type attribute should be mentioned with a value as the fully qualified class name of the actual type object whereas if we are using ADB stubs on the client side then the request XML contains the type attribute with a namespace as http://www.w3.org/2001/XMLSchema-instance and the value as just the class name, the package name is not sent. So the code mentioned here fails. I have added a workaround for the problem and am attaching the file modified along with the mail. Changes are in the BeanUtil.java file. Also a new file has been added by name BeanClassMapper.java which expects a Namespace2PackageMapping.properties file in the classpath that contains the mapping between the fully qualified java classes and the namespace qualified object name as is received in the SOAP request. Example properties file is also attached. Please suggest if the code is correct or if there is some other way of achieving the desired result. Thanks and Regards, Rahul Miglani Quark Media House. BeanUtil.java Description: BeanUtil.java BeanClassMapper.java Description: BeanClassMapper.java Namespace2PackageMapping.properties Description: Namespace2PackageMapping.properties
Which WSDL version
Hello, How to know which version of WSDL (1.1 or 2.0) is generated by Axis ? Thank You.
Re: Which WSDL version
Hi, ?wsdl generates WSDL 1.1 while ?wsdl2 generates WSDL 2.0. Thanks, Keith. On Thu, Apr 23, 2009 at 2:09 PM, Rudy rud...@gmail.com wrote: Hello, How to know which version of WSDL (1.1 or 2.0) is generated by Axis ? Thank You. -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Re: Which WSDL version
Ok thank you. 2009/4/23 keith chapman keithgchap...@gmail.com Hi, ?wsdl generates WSDL 1.1 while ?wsdl2 generates WSDL 2.0. Thanks, Keith. On Thu, Apr 23, 2009 at 2:09 PM, Rudy rud...@gmail.com wrote: Hello, How to know which version of WSDL (1.1 or 2.0) is generated by Axis ? Thank You. -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Re: Problem with Polymorphic data types with ADB stubs on client side and RPC*MessageReceiver on Server side.
Hi, it goes against the philosophy of web services to become dependent on java packages or .net assemblies or whatever. it is essential that a classname within a soap-message is NOT relied upon for communication purposes to have a special meaning within a certain framework. you would kill interoperability this way Cheers, Wolfgang --- On Thu, 4/23/09, Rahul Miglani rmigl...@quark.com wrote: From: Rahul Miglani rmigl...@quark.com Subject: Problem with Polymorphic data types with ADB stubs on client side and RPC*MessageReceiver on Server side. To: axis-dev@ws.apache.org Date: Thursday, April 23, 2009, 9:50 AM Hi, I have an existing spring framework based Java application where-in the services were exposed as web services using Axis 1.3. Now we are migrating the same to Axis2 1.4.1. I have used the RPC*MessageReceiver classes for my MEPs and instead of service implementation class parameter “SeviceClass” I am using the “ServiceObjectSupplier” and the “SpringBeanName” parameters in the services.xml file to describe my service. On the client side I am using the ADB stubs. When I encounter any polymorphic data here i.e. if the client is sending a polymorphic data type as a parameter, the RPC*MessageReceiver class is not able to de-serialize the exact derived object instead it creates an object of the base class, resulting in data loss. Actually the problem comes in the BeanUtil class’s deserailize() method. A fix is already mentioned there for issues AXIS2-2055 and AXIS2-1899 to support polymorphism in POJO approach. The code expects that a “type” attribute should be mentioned with a value as the fully qualified class name of the actual type object whereas if we are using ADB stubs on the client side then the request XML contains the “type” attribute with a namespace as http://www.w3.org/2001/XMLSchema-instance and the value as just the class name, the package name is not sent. So the code mentioned here fails. I have added a workaround for the problem and am attaching the file modified along with the mail. Changes are in the BeanUtil.java file. Also a new file has been added by name BeanClassMapper.java which expects a “Namespace2PackageMapping.properties” file in the classpath that contains the mapping between the fully qualified java classes and the namespace qualified object name as is received in the SOAP request. Example properties file is also attached. Please suggest if the code is correct or if there is some other way of achieving the desired result. Thanks and Regards, Rahul Miglani Quark Media House.
[jira] Created: (AXIS2-4321) Generated axis2.war gives AxisAdminServlet not found when trying to administer through web interface
Generated axis2.war gives AxisAdminServlet not found when trying to administer through web interface Key: AXIS2-4321 URL: https://issues.apache.org/jira/browse/AXIS2-4321 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: 1.5 Environment: Linux, Sun 1.5.0_15-b04 JVM Reporter: Dennis Sosnoski Priority: Blocker After building the axis2.war (using the build.xml in the webapp directory of the distribution) and deploying to Tomcat (5.0.28) I'm unable to access the admin functions through the http://localhost:8080/axis2/axis2-admin/ link. The localhost_log shows: 2009-04-23 03:31:02 StandardContext[/axis2]Error loading WebappClassLoader delegate: false repositories: /WEB-INF/classes/ -- Parent Classloader: StandardClassLoader delegate: true repositories: file:/extra/tools/tomcat/shared/classes/ -- Parent Classloader: StandardClassLoader delegate: true repositories: file:/extra/tools/tomcat/common/classes/ file:/extra/tools/tomcat/common/lib/ant.jar file:/extra/tools/tomcat/common/lib/naming-java.jar file:/extra/tools/tomcat/common/lib/ant-launcher.jar file:/extra/tools/tomcat/common/lib/jsp-api.jar file:/extra/tools/tomcat/common/lib/commons-dbcp-1.2.1.jar file:/extra/tools/tomcat/common/lib/jasper-compiler.jar file:/extra/tools/tomcat/common/lib/commons-pool-1.2.jar file:/extra/tools/tomcat/common/lib/naming-common.jar file:/extra/tools/tomcat/common/lib/commons-collections-3.1.jar file:/extra/tools/tomcat/common/lib/commons-el.jar file:/extra/tools/tomcat/common/lib/jasper-runtime.jar file:/extra/tools/tomcat/common/lib/naming-resources.jar file:/extra/tools/tomcat/common/lib/naming-factory.jar file:/extra/tools/tomcat/common/lib/servlet-api.jar -- Parent Classloader: sun.misc.launcher$appclassloa...@12498b5 org.apache.axis2.webapp.AxisAdminServlet java.lang.ClassNotFoundException: org.apache.axis2.webapp.AxisAdminServlet at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1340) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:964) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:687) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:144) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4320) Error when running an Axis2 client code
[ https://issues.apache.org/jira/browse/AXIS2-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701865#action_12701865 ] Maria Claribelle Loto commented on AXIS2-4320: -- Hi Guys, Anyone who have an idea about the above error please? Thank you so much in advance. Error when running an Axis2 client code --- Key: AXIS2-4320 URL: https://issues.apache.org/jira/browse/AXIS2-4320 Project: Axis 2.0 (Axis2) Issue Type: Task Environment: Windows XP, IDEA IntelliJ Reporter: Maria Claribelle Loto Hi, I was testing a client code which calls Axis2 service but I am getting the following error: org.apache.axis2.AxisFault: unknown at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at net.brokerhub.xml.webservices2_0.Axis2MarketInterfaceStub.login(Axis2MarketInterfaceStub.java:1484) at test.Axis2TestClient.login(Axis2TestClient.java:208) at test.Axis2TestClient.test(Axis2TestClient.java:49) at test.Axis2TestClient.main(Axis2TestClient.java:38) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) May i know what could possibly be causing such error? Please message me if you need more information about the codes. Your help will be much appreciated. thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Missing org.apache.axis2.transport.tcp.TCPTransportSender into Axis2 1.5 RC
Hi everybody, I found out that we are missing the org.apache.axis2.transport.tcp.TCPTransportSender class into the distribution. You can check that pretty easy. Just deploy the axis2-1.5-war in Tomcat. Before that you should go and modify the axis2\WEB-INF\conf\axis2.xml and uncomment the: transportSender name=tcp class=org.apache.axis2.transport.tcp.TCPTransportSender/ Then when you start the server you will get the following java.lang.ClassNotFoundException: org.apache.axis2.transport.tcp.TCPTransportSender: [ERROR] org.apache.axis2.transport.tcp.TCPTransportSender org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.tcp.TCPTransportSender at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:694) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:121) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:707) at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:157) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:927) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:890) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) 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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: java.lang.ClassNotFoundException: org.apache.axis2.transport.tcp.TCPTransportSender at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1232) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.apache.axis2.util.Loader.loadClass(Loader.java:261) at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:669) ... 31 more As you may guess this is because it is missing from the classpath of the WAR. I suppose axis2-transport-tcp.jar should be added. If you want me I can open a JIRA. Regards, Dobri
[jira] Updated: (AXIS2-4313) Some MTOMPolicy module improvements are not merged to Axis2 1.5 branch
[ https://issues.apache.org/jira/browse/AXIS2-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4313: - Attachment: MTOMOutHandler_setDoingMTOM.patch Attaching a fix for the optional scenario. Some MTOMPolicy module improvements are not merged to Axis2 1.5 branch -- Key: AXIS2-4313 URL: https://issues.apache.org/jira/browse/AXIS2-4313 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: mtompolicy Environment: Axis2 1.5 RC Reporter: Nandana Mihindukulasooriya Assignee: Glen Daniels Fix For: 1.5 Attachments: MTOMOutHandler_setDoingMTOM.patch, MTOMPolicy.patch Some of the improvements done on the Axis2 trunk after branching are not merged to Axis2 1.5 branch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AXIS2-4322) Cannot connect via NTLM proxy on Mac machine.
Cannot connect via NTLM proxy on Mac machine. - Key: AXIS2-4322 URL: https://issues.apache.org/jira/browse/AXIS2-4322 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Affects Versions: 1.4, 1.4.1 Environment: Apple Mac OS X 10.5, Axis2 1.4 Reporter: Sean Cote We have a web-service client application and we allow the user to connect via an authenticating proxy server. It works for basic, digest, and NTLM authentication on all platforms, except for one case: It does not work for NTLM authentication on Mac OS X 10.5. We get the following error: [ERROR] HttpMethodDirector - Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentialsorg.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials at org.apache.commons.httpclient.auth.NTLMScheme.authenticate(NTLMScheme.java:332) at org.apache.commons.httpclient.HttpMethodDirector.authenticateProxy(HttpMethodDirector.java:320) at org.apache.commons.httpclient.HttpMethodDirector.executeConnect(HttpMethodDirector.java:491) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:391) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:542) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:189) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:364) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) Why does it work for Windows and Linux, but not Macs? Please let me know if I can help in any way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM
[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker updated AXIS2-4323: - Attachment: patch_apache.txt Attached is the patch for this change. Performance Imporvement when using JAX-WS ProviderOM -- Key: AXIS2-4323 URL: https://issues.apache.org/jira/browse/AXIS2-4323 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: patch_apache.txt I am making a small change to improve performance when a JAX-WS providerOM is used by an application. Currently when a message block is represented by OM, we are expanding OM before we serialize, this change is to avoid OM Expansion and directly serialize the xml represented by OM into an Output Stream there by improving the performance and avioding un necessary expansion of OM. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM
Performance Imporvement when using JAX-WS ProviderOM -- Key: AXIS2-4323 URL: https://issues.apache.org/jira/browse/AXIS2-4323 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: patch_apache.txt I am making a small change to improve performance when a JAX-WS providerOM is used by an application. Currently when a message block is represented by OM, we are expanding OM before we serialize, this change is to avoid OM Expansion and directly serialize the xml represented by OM into an Output Stream there by improving the performance and avioding un necessary expansion of OM. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM
[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-4323. -- Resolution: Fixed Issue resolved with svn revision #767971 Performance Imporvement when using JAX-WS ProviderOM -- Key: AXIS2-4323 URL: https://issues.apache.org/jira/browse/AXIS2-4323 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: patch_apache.txt I am making a small change to improve performance when a JAX-WS providerOM is used by an application. Currently when a message block is represented by OM, we are expanding OM before we serialize, this change is to avoid OM Expansion and directly serialize the xml represented by OM into an Output Stream there by improving the performance and avioding un necessary expansion of OM. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM
[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AXIS2-4323 started by Nikhil Thaker. Performance Imporvement when using JAX-WS ProviderOM -- Key: AXIS2-4323 URL: https://issues.apache.org/jira/browse/AXIS2-4323 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: patch_apache.txt I am making a small change to improve performance when a JAX-WS providerOM is used by an application. Currently when a message block is represented by OM, we are expanding OM before we serialize, this change is to avoid OM Expansion and directly serialize the xml represented by OM into an Output Stream there by improving the performance and avioding un necessary expansion of OM. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM
[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker closed AXIS2-4323. Performance Imporvement when using JAX-WS ProviderOM -- Key: AXIS2-4323 URL: https://issues.apache.org/jira/browse/AXIS2-4323 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nikhil Thaker Assignee: Nikhil Thaker Attachments: patch_apache.txt I am making a small change to improve performance when a JAX-WS providerOM is used by an application. Currently when a message block is represented by OM, we are expanding OM before we serialize, this change is to avoid OM Expansion and directly serialize the xml represented by OM into an Output Stream there by improving the performance and avioding un necessary expansion of OM. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AXIS2-4324) setenv.sh - extended shell functionality used where /bin/sh specified
setenv.sh - extended shell functionality used where /bin/sh specified - Key: AXIS2-4324 URL: https://issues.apache.org/jira/browse/AXIS2-4324 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.4.1 Environment: SunOS 5.10 Generic sun4u sparc SUNW Reporter: Peter Barker Priority: Minor This script declares itself as #!/bin/sh, but the script uses extended functionality not present in the /bin/sh present on this operating system. The following patch appears to fix the problem: --- ../../../axis2/axis2-1.4/bin/setenv.sh 2008-03-22 10:22:22.0 +1100 +++ setenv.sh-pbfix 2009-04-24 15:52:29.0 +1000 @@ -79,7 +79,8 @@ system $COMMAND # Enable multi threading - export QIBM_MULTI_THREADED=Y + QIBM_MULTI_THREADED=Y + export QIBM_MULTI_THREADED fi # update classpath @@ -99,9 +100,9 @@ JAVA_ENDORSED_DIRS=`cygpath --path --windows $JAVA_ENDORSED_DIRS` fi -export AXIS2_HOME=$AXIS2_HOME -export JAVA_HOME=$JAVA_HOME -export AXIS2_CLASSPATH=$AXIS2_CLASSPATH +export AXIS2_HOME +export JAVA_HOME +export AXIS2_CLASSPATH echo Using AXIS2_HOME: $AXIS2_HOME -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
