[jira] [Resolved] (AXIS2-6060) [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the newest version of org.apache.axis2:axis2
[ https://issues.apache.org/jira/browse/AXIS2-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-6060. Resolution: Not A Problem > [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the > newest version of org.apache.axis2:axis2 > -- > > Key: AXIS2-6060 > URL: https://issues.apache.org/jira/browse/AXIS2-6060 > Project: Axis2 > Issue Type: Bug > Components: codegen, wsdl >Affects Versions: 1.8.0 >Reporter: Yiheng Cao >Priority: Major > > The vulnerability is present in the class > org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension of method > getNamespaceAwareDocumentBuilder() , which is responsible for getting a > DocumentBuilder object that supports namespace resolution. The vulnerable > call chain we discover is: *engage(CodeGenConfiguration > configuration)→loadAdditionalSchemas()→getNamespaceAwareDocumentBuilder().* > Given that the XML schema files stored in the > /org/apache/axis2/wsdl/codegen/schema/ which is compromised by a hacker, the > victim conducts regular process which incorporates the execution of method > engage(), resulting in an XML External Entity (XXE) Injection attack. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Comment Edited] (AXIS2-6060) [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the newest version of org.apache.axis2:axis2
[ https://issues.apache.org/jira/browse/AXIS2-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756580#comment-17756580 ] Andreas Veithen edited comment on AXIS2-6060 at 10/29/23 11:39 AM: --- Note that the schema files are loaded from the classpath. If an attacker can manipulate the classpath, then they would be able to execute arbitrary code anyway. I don't see how an attacker would achieve any kind of privilege escalation. was (Author: veithen): Note that the schema files are loaded from the classpath. If an attacker can manipulate the classpath, then they would be able to execute arbitrary code anyway. I don't see how there an attacker would achieve any kind of privilege escalation. > [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the > newest version of org.apache.axis2:axis2 > -- > > Key: AXIS2-6060 > URL: https://issues.apache.org/jira/browse/AXIS2-6060 > Project: Axis2 > Issue Type: Bug > Components: codegen, wsdl >Affects Versions: 1.8.0 >Reporter: Yiheng Cao >Priority: Major > > The vulnerability is present in the class > org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension of method > getNamespaceAwareDocumentBuilder() , which is responsible for getting a > DocumentBuilder object that supports namespace resolution. The vulnerable > call chain we discover is: *engage(CodeGenConfiguration > configuration)→loadAdditionalSchemas()→getNamespaceAwareDocumentBuilder().* > Given that the XML schema files stored in the > /org/apache/axis2/wsdl/codegen/schema/ which is compromised by a hacker, the > victim conducts regular process which incorporates the execution of method > engage(), resulting in an XML External Entity (XXE) Injection attack. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Comment Edited] (AXIS2-6060) [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the newest version of org.apache.axis2:axis2
[ https://issues.apache.org/jira/browse/AXIS2-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756580#comment-17756580 ] Andreas Veithen edited comment on AXIS2-6060 at 8/20/23 8:19 PM: - Note that the schema files are loaded from the classpath. If an attacker can manipulate the classpath, then they would be able to execute arbitrary code anyway. I don't see how there an attacker would achieve any kind of privilege escalation. was (Author: veithen): Note that the schema files are loaded from the classpath. If an attacker can manipulate the classpath, then they would be able to execute arbitrary code anyway. I don't see how there an attacher would achieve any kind of privilege escalation. > [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the > newest version of org.apache.axis2:axis2 > -- > > Key: AXIS2-6060 > URL: https://issues.apache.org/jira/browse/AXIS2-6060 > Project: Axis2 > Issue Type: Bug > Components: codegen, wsdl >Affects Versions: 1.8.0 >Reporter: Yiheng Cao >Priority: Major > > The vulnerability is present in the class > org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension of method > getNamespaceAwareDocumentBuilder() , which is responsible for getting a > DocumentBuilder object that supports namespace resolution. The vulnerable > call chain we discover is: *engage(CodeGenConfiguration > configuration)→loadAdditionalSchemas()→getNamespaceAwareDocumentBuilder().* > Given that the XML schema files stored in the > /org/apache/axis2/wsdl/codegen/schema/ which is compromised by a hacker, the > victim conducts regular process which incorporates the execution of method > engage(), resulting in an XML External Entity (XXE) Injection attack. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-6060) [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the newest version of org.apache.axis2:axis2
[ https://issues.apache.org/jira/browse/AXIS2-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756580#comment-17756580 ] Andreas Veithen commented on AXIS2-6060: Note that the schema files are loaded from the classpath. If an attacker can manipulate the classpath, then they would be able to execute arbitrary code anyway. I don't see how there an attacher would achieve any kind of privilege escalation. > [Axis2]Security Vulnerability - Action Required: XXE vulnerability in the > newest version of org.apache.axis2:axis2 > -- > > Key: AXIS2-6060 > URL: https://issues.apache.org/jira/browse/AXIS2-6060 > Project: Axis2 > Issue Type: Bug > Components: codegen, wsdl >Affects Versions: 1.8.0 >Reporter: Yiheng Cao >Priority: Major > > The vulnerability is present in the class > org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension of method > getNamespaceAwareDocumentBuilder() , which is responsible for getting a > DocumentBuilder object that supports namespace resolution. The vulnerable > call chain we discover is: *engage(CodeGenConfiguration > configuration)→loadAdditionalSchemas()→getNamespaceAwareDocumentBuilder().* > Given that the XML schema files stored in the > /org/apache/axis2/wsdl/codegen/schema/ which is compromised by a hacker, the > victim conducts regular process which incorporates the execution of method > engage(), resulting in an XML External Entity (XXE) Injection attack. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-6056) Error in DOAP file
[
https://issues.apache.org/jira/browse/AXIS2-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-6056.
Resolution: Fixed
> Error in DOAP file
> --
>
> Key: AXIS2-6056
> URL: https://issues.apache.org/jira/browse/AXIS2-6056
> Project: Axis2
> Issue Type: Bug
>Reporter: Claude Warren
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 87, col: 84] \{W002}
> Code: 0/ILLEGAL_CHARACTER in QUERY: The character violates the grammar rules
> for URIs/IRIs.
> [1]
> http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/etc/doap_Axis2.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-6056) Error in DOAP file
[
https://issues.apache.org/jira/browse/AXIS2-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739296#comment-17739296
]
Andreas Veithen commented on AXIS2-6056:
Also fixed the URL encoding issue.
> Error in DOAP file
> --
>
> Key: AXIS2-6056
> URL: https://issues.apache.org/jira/browse/AXIS2-6056
> Project: Axis2
> Issue Type: Bug
>Reporter: Claude Warren
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 87, col: 84] \{W002}
> Code: 0/ILLEGAL_CHARACTER in QUERY: The character violates the grammar rules
> for URIs/IRIs.
> [1]
> http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/etc/doap_Axis2.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-6056) Error in DOAP file
[
https://issues.apache.org/jira/browse/AXIS2-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739295#comment-17739295
]
Andreas Veithen commented on AXIS2-6056:
Updated {{project.xml}} to point to Git.
> Error in DOAP file
> --
>
> Key: AXIS2-6056
> URL: https://issues.apache.org/jira/browse/AXIS2-6056
> Project: Axis2
> Issue Type: Bug
>Reporter: Claude Warren
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 87, col: 84] \{W002}
> Code: 0/ILLEGAL_CHARACTER in QUERY: The character violates the grammar rules
> for URIs/IRIs.
> [1]
> http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/etc/doap_Axis2.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Moved] (AXIS2-6056) Error in DOAP file
[
https://issues.apache.org/jira/browse/AXIS2-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved AXIS-2951 to AXIS2-6056:
--
Component/s: (was: Documentation)
Key: AXIS2-6056 (was: AXIS-2951)
Affects Version/s: (was: 1.4)
Project: Axis2 (was: Axis)
> Error in DOAP file
> --
>
> Key: AXIS2-6056
> URL: https://issues.apache.org/jira/browse/AXIS2-6056
> Project: Axis2
> Issue Type: Bug
>Reporter: Claude Warren
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
> [line: 87, col: 84] \{W002}
> Code: 0/ILLEGAL_CHARACTER in QUERY: The character violates the grammar rules
> for URIs/IRIs.
> [1]
> http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/etc/doap_Axis2.rdf
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-6049) Generated Exceptions differ each generation
[
https://issues.apache.org/jira/browse/AXIS2-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-6049.
Fix Version/s: 1.8.3
Assignee: Andreas Veithen
Resolution: Fixed
> Generated Exceptions differ each generation
> ---
>
> Key: AXIS2-6049
> URL: https://issues.apache.org/jira/browse/AXIS2-6049
> Project: Axis2
> Issue Type: Improvement
> Components: codegen
>Affects Versions: 1.8.0
>Reporter: Stefan May
>Assignee: Andreas Veithen
>Priority: Minor
> Fix For: 1.8.3
>
>
> *Description:*
> The Java files which are generated by the AntCodegenTask for Exceptions
> differ each generation in the serialVersionUID.
> This is especially bothering if the gradle cache should be used, wich
> requires a fixed input. Also, the objects may not be deserialized again if
> the SerialVersionUID changes each time.
> *Steps to reproduce:*
> Create a WSDL with a wsdl:fault element, e.g:
> {code:java}
>
> http://schemas.xmlsoap.org/wsdl/soap/;
> xmlns:tns="http://www.example.org/;
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/;
> xmlns:xsd="http://www.w3.org/2001/XMLSchema; name="ExampleModule"
> targetNamespace="http://www.example.org/;>
>
> http://www.example.org/;>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> type="xsd:string">
>
>
>
>
>
>
>
>
>
>
>
>
>
> element="tns:getSolutionByIdFault">
>
>
>
>
>
> message="tns:getSolutionByIdFault">
>
>
>
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
> soapAction="http://www.example.org/ExampleModule/getSolutionById"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://www.example.org/"/>
>
>
> {code}
> Generate it again, the serialVersionUID changes
> *More info*
> I've checked and found the corresponding issue in the file
> [https://github.com/apache/axis-axis2-java-core/blob/master/modules/codegen/src/org/apache/axis2/wsdl/codegen/emitter/AxisServiceBasedMultiLanguageEmitter.java|https://github.com/wso2/wso2-axis2/blob/28a2220ba3a5547315347ecb97b512059070d15d/modules/codegen/src/org/apache/axis2/wsdl/codegen/emitter/AxisServiceBasedMultiLanguageEmitter.java]
> in line 1055, where the {{System.currentTimeMillis()}} is used for the
> serialVersionUID.
> A hash based on the className and the parameters would probably be better.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-6045) NPE after upgrade to 1.8.2
[ https://issues.apache.org/jira/browse/AXIS2-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606337#comment-17606337 ] Andreas Veithen commented on AXIS2-6045: What are the steps to reproduce this? > NPE after upgrade to 1.8.2 > -- > > Key: AXIS2-6045 > URL: https://issues.apache.org/jira/browse/AXIS2-6045 > Project: Axis2 > Issue Type: Bug > Components: kernel, wsdl >Affects Versions: 1.8.2 >Reporter: k >Priority: Critical > > Side effect of AXIS2-6033 which introduced this call, without checking > "definition" for null: > [https://github.com/apache/axis-axis2-java-core/blob/master/modules/kernel/src/org/apache/axis2/description/AxisService.java#L1173] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-6039) suppress prefix option not working in 1.8.0
[ https://issues.apache.org/jira/browse/AXIS2-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600529#comment-17600529 ] Andreas Veithen commented on AXIS2-6039: Can you provide steps (or a minimal test project) to reproduce this? > suppress prefix option not working in 1.8.0 > --- > > Key: AXIS2-6039 > URL: https://issues.apache.org/jira/browse/AXIS2-6039 > Project: Axis2 > Issue Type: Bug > Components: wsdl >Affects Versions: 1.8.0 > Environment: Java11 >Reporter: venkat >Priority: Major > Fix For: 1.8.3 > > > We are migrating our application to Java11 and using Axis2 1.8.0 version for > SOAP webservices. We are generating the Java classes using wsdl2java. We are > observing a prefix *ns2* is added in the response by default. We have tried > -sp option as well while generating the Java classes to suppress this prefix > but didn't get the desired result. > > 5 > > > We would like to know why the -sp option is not working and the methods to > remove the prefix to response elements -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (RAMPART-449) NoClassDefFoundError with Axis2 1.8.0
[
https://issues.apache.org/jira/browse/RAMPART-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429720#comment-17429720
]
Andreas Veithen commented on RAMPART-449:
-
[~robertlazarski] I've added you as administrator in JIRA.
The other problem we have is that Travis somehow became defunct and the build
fails with an obscure error on Github Actions, so we don't have any working
continuous integration setup.
> NoClassDefFoundError with Axis2 1.8.0
> -
>
> Key: RAMPART-449
> URL: https://issues.apache.org/jira/browse/RAMPART-449
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
>Affects Versions: 1.7.1
>Reporter: Matthias Kraaz
>Priority: Major
>
> Axis2 1.8.0 updated Axiom to 1.3 thereby breaking rampart, which uses an
> Axiom API that has been removed:
>
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/axiom/soap/impl/builder/StAXSOAPModelBuilder
> at
> org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:159)
>
> at org.apache.rampart.RampartMessageData.(RampartMessageData.java:280)
> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61)
> at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:335)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:308)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:250)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:415)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:399)
>
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>
> at org.apache.axis2.client.OperationClient.execute(OperationClient.java:150)
> at pls.soap.client.SOAPClient.sendRequest(SOAPClient.java:284)
> at pls.soap.client.SOAPClient.handleRequest(SOAPClient.java:143)
> at pls.soap.client.SOAPClient.processSendJob(SOAPClient.java:101)
> at
> pls.soap.client.SendJobProcessorImpl.processSendJob(SendJobProcessorImpl.java:10)
>
> at ls.osis.server.prot.SendJobQueue.process(SendJobQueue.java:139)
> at ls.osis.server.prot.SendJobQueue$SendJobTask.run(SendJobQueue.java:108)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
>
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ...
> 22 more
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-6013) Apache Axis2 1.8.0 seems to have DEBUG level logging enabled by default
[
https://issues.apache.org/jira/browse/AXIS2-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-6013.
Fix Version/s: 1.8.1
Resolution: Fixed
> Apache Axis2 1.8.0 seems to have DEBUG level logging enabled by default
> ---
>
> Key: AXIS2-6013
> URL: https://issues.apache.org/jira/browse/AXIS2-6013
> Project: Axis2
> Issue Type: Bug
> Components: deployment
>Affects Versions: 1.8.0
> Environment: CentOS Linux 7, Apache Tomcat 8.5.71, Axis2 1.8.0
>Reporter: Jinesh Choksi
>Assignee: Andreas Veithen
>Priority: Major
> Fix For: 1.8.1
>
>
> In v1.8.0 of the Axis2 webapp, the \webapp\WEB-INF\classes\log4j2.xml file
> has the following config by default:
>
> {noformat}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
>
> This causes a lot of log msgs to be logged into Apache Tomcat's catalina.out
> log file.
> Could the Root level be set as info and the name="org.apache.axis2" logger
> be commented or changed to info as well?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5966) Axis2 1.8.0-SNAPSHOT fix did not work for JDK 11
[ https://issues.apache.org/jira/browse/AXIS2-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5966: --- Fix Version/s: (was: 1.8.0) > Axis2 1.8.0-SNAPSHOT fix did not work for JDK 11 > > > Key: AXIS2-5966 > URL: https://issues.apache.org/jira/browse/AXIS2-5966 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.7.9 >Reporter: Suma Malsekar >Assignee: Robert Lazarski >Priority: Major > > jdk version: 11 > tomcat: 9.0.20 > axis2 version: 1.7.9 > [org.apache.axis2.deployment.ServiceDeployer] ERROR 2019-09-11 11:21:40,531 - > The ***.aar service, which is not valid, caused The following error > occurred during schema generation: Error looking for paramter names in > bytecode: unexpected end of file > org.apache.axis2.deployment.DeploymentException: The following error occurred > during schema generation: Error looking for paramter names in bytecode: > unexpected end of file > at > org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:441) > at > org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:109) > at > org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:232) > at > org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:154) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:149) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:585) > at > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:164) > at > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) > at > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) > at > org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:136) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:289) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:622) > at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:471) > at > org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1122) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1077) > at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:971) > at > org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4868) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5184) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:713) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705) > at > org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1133) > at > org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1867) > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown > Source) > at java.base/java.util.concurrent.FutureTask.run(Unknown Source) > at > org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) > at java.base/java.util.concurrent.AbstractExecutorService.submit(Unknown > Source) > at > org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1045) > at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:429) > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576) > at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) > at > org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423) > at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) > at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:929) > at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1377) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1367) > at java.base/java.util.concurrent.FutureTask.run(Unknown Source) > at > org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) >
[jira] [Updated] (AXIS2-4602) JAX-WS MTOM issue
[ https://issues.apache.org/jira/browse/AXIS2-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4602: --- Fix Version/s: (was: 1.8.0) > JAX-WS MTOM issue > - > > Key: AXIS2-4602 > URL: https://issues.apache.org/jira/browse/AXIS2-4602 > Project: Axis2 > Issue Type: Bug > Components: jaxws >Affects Versions: 1.7.0 >Reporter: Isuru Suriarachchi >Priority: Major > Attachments: jaxws-mtom-fix.txt > > > In Axis2 JAX-WS implementation, org.apache.axis2.jaxws.message.Block is > extending OMDataSourceExt. In the response messages of normal invocations, > this object is kept inside the body of the SOAPEnvelope and directly > serialized without building the OMElement. In order to handle MTOM, it uses > the JAXBAttachmentMarshaller which writes data handler objects into the > MTOMXMLStreamWriter. > MTOM works fine as far as the return OMElement is not built and directly > serialized using the OMDataSource. But if the OMElement is built by some > handler on the return path, JAXB Block is written to a ByteArrayOutputStream > and read as a ByteArray (through the getReader() method of BlockImpl). > Therefore, the OMElement which is built using this ByteArray, doesn't know > about MTOM. So, the response is given as base64 (inline). > So even though the service is MTOM enabled, if some handler (Ex: Security) > builds the body element, the binary response data is transmitted as > base64-encoded inline, instead of as a separate binary attachment (see below > - I remove most of the returned data due to its length): > --MIMEBoundaryurn_uuid_6A41A9AB6F9E3EEAB71262792774662 > Content-Type: application/xop+xml; charset=UTF-8; type="text/xml" > Content-Transfer-Encoding: binary > Content-ID: <0.urn:uuid:6a41a9ab6f9e3eeab71262792774...@apache.org> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;> > xmlns:dlwmin="urn:ca.dmf.webservices">f39/f39/f39/f39... > --MIMEBoundaryurn_uuid_6A41A9AB6F9E3EEAB71262792774662-- -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-6013) Apache Axis2 1.8.0 seems to have DEBUG level logging enabled by default
[
https://issues.apache.org/jira/browse/AXIS2-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen reassigned AXIS2-6013:
--
Assignee: Andreas Veithen
> Apache Axis2 1.8.0 seems to have DEBUG level logging enabled by default
> ---
>
> Key: AXIS2-6013
> URL: https://issues.apache.org/jira/browse/AXIS2-6013
> Project: Axis2
> Issue Type: Bug
> Components: deployment
>Affects Versions: 1.8.0
> Environment: CentOS Linux 7, Apache Tomcat 8.5.71, Axis2 1.8.0
>Reporter: Jinesh Choksi
>Assignee: Andreas Veithen
>Priority: Major
>
> In v1.8.0 of the Axis2 webapp, the \webapp\WEB-INF\classes\log4j2.xml file
> has the following config by default:
>
> {noformat}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
>
> This causes a lot of log msgs to be logged into Apache Tomcat's catalina.out
> log file.
> Could the Root level be set as info and the name="org.apache.axis2" logger
> be commented or changed to info as well?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Deleted] (AXIS-2944) [WATCH] Minari (2021) Mp4 Online Full Free
[ https://issues.apache.org/jira/browse/AXIS-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen deleted AXIS-2944: -- > [WATCH] Minari (2021) Mp4 Online Full Free > -- > > Key: AXIS-2944 > URL: https://issues.apache.org/jira/browse/AXIS-2944 > Project: Axis > Issue Type: Bug >Reporter: 123Movies >Priority: Major > > UltraHD! ++ 4K. Downloads-! JWPLayer (Filemcollection ~ stream) 'MovieS.4K ~ > Watch Minari (2021) Free Full HD Movies Online, Free Full Play, Play, Play > Full Movies Online, Watch Minari Movies Online for Free, Full Play Movies > Watch Online Free Official Partner to Watch Minari Online (2021) Full > > █ > > Watch Minari ► [Click Here|https://tinyurl.com/ramefilm] > > Download Minari ► [Click Here|https://tinyurl.com/ramefilm] > > █ > > *Watch Minari Full Movie ~ Minari Full Movie Online Free Streaming All > Subtitles* > > Watch Minari (2021) Free Full HD Movies Online, Minari Full Free, Minari, > Minari Full Movies Online, Watch Minari Movies Online Free, Minari Movies > Watch Full Online FreeMinari (2021) Full Movie Watch Online > > Minari (2021) full English Full Movie > > Film Full Minari (2021), > > Nonton Minari (2021) full English Full Movie Online > > Minari (2021) full Film Online > > Watch Minari (2021) Full English Movie > > Streaming the movie Full Minari (2021) for free > > Nonton film Minari (2021) subtitle full movie > > Watch Minari (2021) full spoiler movie > > Minari (2021) full Movie Francais > > Minari (2021) full movie download Francais > > Watch Minari (2021) full movie download > > Watch Minari (2021) full movie telugu > > Nonton Minari (2021) full movie tamildubbed download > > Minari (2021) Full Movie to watch Toy Full Movie Watch vidzi > > Minari (2021) film Full vimeo > > Watch Minari (2021) > > 01 secs ago ~ 4K-HD ~! How To Watch Minari (2021) Full Movie Online For Free? > HQ Reddit DVD-ENGLISHMinari (2021) Full Movies Watch free online Dailymotion > #Minari Google Drive / DvdRip-USA / Eng-SubsMinari! (2021) Watch Full Movies > Online Without Registering 123 Movies Online !! Minari (2021) Open ~ Load | > Watch Minari Online (2021) Full Movie Free HD.720Px | Watch Minari Online > (2021) Full HD Movie Free !! Minari (2021) with English Subtitles ready to > download, Minari (2021) 720p, 1080p, BrRip, DvdRip, Youtube, Reddit, > Multilanguage and High Quality. Download Full Movies on Openload, Netflix, > > *Nonton Minari (2021): Full_Movies* > > Nonton Minari (2021) Online 4k Quality > > Watch Minari (2021) StreamiNG HD video > > Film Full Minari (2021) > > Minari Movie Release (2021) > > Watch Free Movies Online in 2021 > > Watch Minari (2021) FullMovie Online > > Watch Minari (2021) online > > Minari (2021) full English Full Movie > > Watch Minari (2021) Full English Movie > > Watch Minari (2021) Indonesian subtitles > > Full English Movie Minari (2021), > > Minari (2021) Film Full Sub Eng > > Nonton film Minari (2021) subtitle full movie > > Watch Minari (2021) full spoiler movie > > Minari (2021) full Film Online > > Streaming the movie Full Minari (2021) for free > > Watch Minari (2021) Full Movie to download > > Watch Minari (2021) full movie telugu > > Minari (2021) full movie tamil > > Minari (2021) full movie download tamil > > Minari (2021) Complete French > > Minari (2021) Spanish subtitles > > Minari (2021) Full Norwegian film > > Minari (2021) versi NederMinari > > Minari (2021) Belgian Full film > > The artwork in the form of a series of live images that is played creates the > illusion of a moving image presented as a form of entertainment. The illusion > of a series of images produces continuous motion in the form of a video. > Films are often referred to as films or moving pictures. Film is a modern and > popular art form created for both business and entertainment purposes. > Filmmaking has now become a popular industry around the world, where feature > films are always awaited by cinemas. Films are made in two main ways. The > first is through shooting and recording techniques via a film camera. This > method is done by taking pictures or objects. The second uses traditional > animation techniques. This method is done through computer graphic animation > or CGI techniques. They can also be combined with other techniques and visual > effects. Filming usually takes a relatively long time. Besides that, they > also need a job desk each, starting from director, producer, editor, > wardrobe, visual effects and others. > > Understanding and Understanding Film / Movie > > *Watch Minari (2021) Full Movie Online for Free* > > Meanwhile, the
[jira] [Deleted] (AXIS-2942) Joker123 | Slot Joker123 | Joker Gaming | Agen Joker123 | Daftar Joker123 | Login Joker123
[ https://issues.apache.org/jira/browse/AXIS-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen deleted AXIS-2942: -- > Joker123 | Slot Joker123 | Joker Gaming | Agen Joker123 | Daftar Joker123 | > Login Joker123 > -- > > Key: AXIS-2942 > URL: https://issues.apache.org/jira/browse/AXIS-2942 > Project: Axis > Issue Type: Improvement > Environment: Joker123 >Reporter: Joker123 >Priority: Major > Labels: Daftar-Joker132, Game-Joker123, Joker123, > Login-Joker123, Situs, Situs-Joker123, Slot, daftar, joker123 > > h1. *Joker123 | Slot Joker123 | Joker Gaming | Agen Joker123 | Daftar > Joker123 | Login Joker123* > http://kingjoker.info/registrasi/; rel="noopener"> src="https://i.postimg.cc/G870x44N/daftar-joker123.gif; alt="daftar-joker123" > width="309" height="115" border="0" /> > src="https://i.postimg.cc/KjZyC2Dj/SITUS-LINK-DAFTAR-LOGIN-JOKER123-JUDI-SLOT-ONLINE.jpg; > alt="Login Joker123" width="894" height="453" /> > Jika salah satu orang mencoba untuk menemukan alasan dibalik popularitas > joker123 slot online dan kesuksesan besar yang didapatkan sebuah mesin ini > selama bertahun-tahun, maka itu benar, itu akan menjadi suatu hal yang jelas > bagaimana kesederhanaan tata tertib joker123 slot online akan menjadi review > utama yang akan kita bahas kali ini. > Dikarenakan, memainkan mesin jackpot Slot Online Joker123 bisa lebih gampang > untuk menerima koin, memasukkannya ke dalam mesin dan kemudian tekan tombol > berputar saja. Sebelum bermain, anda wajib mencari lebih-lebih dahulu variasi > permainan Slot Joker123 Terbaik yang menyerahkan dengan kemenangan terbaik > dan penawaran hadiah yang besar. > Dan pada kali ini dengan memanfaatkan kemajuan dunia teknologi yang semakin > canggih, joker123 menyediakan variasi permainan game online yang bisa kamu > mainkan dan kamu nikmati tidak hanya wajib mengguankan perangkat komputer > saja, tapi bisa juga kamu mainkan dan kamu nikmati dengan mengaplikasikan > perangkat telpon seluler yang berbasis android atau ios (iphone). > h3. *Agen Joker123 Teraman Indonesia Dengan Deposit Pulsa XL Murah* > Joker123 juga dikenal dengan tampilan yang sungguh-sungguh modern sehingga > pemain tidak akan merasa bosan saat bermain. Desain yang sungguh-sungguh > berkelas dihadirkan untuk memandu para pemain baik itu desain situs maupun > desai aplikasi mobile. > Daftar Joker123 Gaming Terpercaya Kerja Mudah > Oleh sebab itulah situs ini sungguh-sungguh dikenal dan diminati oleh banyak > orang. Secara di Indonesia situs ini telah bisa dikatakan situs yang paling > acap kali kali kali dikunjungi saat ini. > Mengapa demikian itu? Sebab di sini kami memberikan banyak bonus untuk para > new member seperti yang bisa kalian lihat di tabel di atas. Kalau hanya bonus > di atas sepertinya masih kurang untuk membikin kalian betah bermain game Slot > Daftar Slot Joker123. Masih ada lagi yang bakal buat kalian untuk terus > bermain ialah Jackpot Progessive. > Beberapa permianan yang bisa pemain mainkan hanya mengaplikasikan 1 akun juga > ada di sini memandu permainan yang ada di dalamnya. Game Slot Joker Gaming > yang saat ini sedang banyak-banyaknya membawa tema yang menarik juga. > Layanan LiveChat kami yang akan di sediakan selama 24 jam penuh tanpa henti > supaya pemain bisa berkomunikasi dengan kami kapan saja menghasilkan kenaikan > layanan yang sungguh-sungguh baik dari Agen Slot Online kami. > h2. *Joker123 Slot Online Situs Download Joker123 Terbaik* > Jadi pemain bisa dengan gampang menghubungi kami jika adanya kendala dalam > bermain. Dan bisa memberikan keluhan yang di natural sehingga akan membentuk > alur bermain yang sungguh-sungguh menyenangkan dan santai dalam bermain Game > Slot Joker123. > Dan untuk jalan mendaftar yang gampang pun bukan hanya melalu LiveChat saja > tetapi juga melewati layanan Menu Daftar Joker Slot Atau Akun Agen Sv388 > Sabung Ayam yang sudah kami sediakan untuk anda bermain di sini. > Bermain bersama kami maka anda akan seketika mendapatkan layanan terbaik dan > profesional yang sudah di miliki oleh staff Joker123 tetapi di sini kemudahan > pertama pastinya ada dalam langkah meregistrasikan akun Joker123 Gaming > secara khusus dahulu. > h3. *Daftar Joker123 Terbaru Indonesia Kemudahan Login Joker123* > Slot Online Joker123 Gaming Terpercaya yang di mana kini ini sudah banyak > sekali permainan yang ada di dalamnya juga anda bisa memainkan game slot > joker yang ada di dalamnya. > Permainan slot joker juga sudah menguasai pasaran game judi online yang di > mana akan membawakan keuntungan tersendiri untuk pemain yang mau memainkan > game slot joker hal yang demikian di dalam Web Joker123. > Pengalaman setiap-setiap orang yang bermain game online di
[jira] [Deleted] (AXIS-2943) Joker123 | Slot Joker123 | Joker Gaming | Agen Joker123 | Daftar Joker123 | Login Joker123
[ https://issues.apache.org/jira/browse/AXIS-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen deleted AXIS-2943: -- > Joker123 | Slot Joker123 | Joker Gaming | Agen Joker123 | Daftar Joker123 | > Login Joker123 > -- > > Key: AXIS-2943 > URL: https://issues.apache.org/jira/browse/AXIS-2943 > Project: Axis > Issue Type: Improvement > Environment: Joker123 >Reporter: Joker123 >Priority: Major > Labels: Agen-Joker123, Daftar-Joker123, Download, Game-Joker123, > Joker-123, Joker123, Login-Joker123, Situs-Joker123 > > h1. *Joker123 | Slot Joker123 | Joker Gaming | Agen Joker123 | Daftar > Joker123 | Login Joker123* > http://kingjoker.me/registrasi/; rel="noopener"> src="https://i.postimg.cc/G870x44N/daftar-joker123.gif; alt="daftar-joker123" > width="309" height="115" border="0" /> > src="https://i.postimg.cc/KjZyC2Dj/SITUS-LINK-DAFTAR-LOGIN-JOKER123-JUDI-SLOT-ONLINE.jpg; > alt="Login Joker123" width="894" height="453" /> > Jika salah satu orang mencoba untuk menemukan alasan dibalik popularitas > joker123 slot online dan kesuksesan besar yang didapatkan sebuah mesin ini > selama bertahun-tahun, maka itu benar, itu akan menjadi suatu hal yang jelas > bagaimana kesederhanaan tata tertib joker123 slot online akan menjadi review > utama yang akan kita bahas kali ini. > Dikarenakan, memainkan mesin jackpot Slot Online Joker123 bisa lebih gampang > untuk menerima koin, memasukkannya ke dalam mesin dan kemudian tekan tombol > berputar saja. Sebelum bermain, anda wajib mencari lebih-lebih dahulu variasi > permainan Slot Joker123 Terbaik yang menyerahkan dengan kemenangan terbaik > dan penawaran hadiah yang besar. > Dan pada kali ini dengan memanfaatkan kemajuan dunia teknologi yang semakin > canggih, joker123 menyediakan variasi permainan game online yang bisa kamu > mainkan dan kamu nikmati tidak hanya wajib mengguankan perangkat komputer > saja, tapi bisa juga kamu mainkan dan kamu nikmati dengan mengaplikasikan > perangkat telpon seluler yang berbasis android atau ios (iphone). > h3. *Agen Joker123 Terpercaya Indonesia Deposit Pulsa XL* > Joker123 juga dikenal dengan tampilan yang sungguh-sungguh modern sehingga > pemain tidak akan merasa bosan saat bermain. Desain yang sungguh-sungguh > berkelas dihadirkan untuk memandu para pemain baik itu desain situs maupun > desai aplikasi mobile. > Daftar Joker123 Gaming Terpercaya Kerja Mudah > Oleh sebab itulah situs ini sungguh-sungguh dikenal dan diminati oleh banyak > orang. Secara di Indonesia situs ini telah bisa dikatakan situs yang paling > acap kali kali kali dikunjungi saat ini. > Mengapa demikian itu? Sebab di sini kami memberikan banyak bonus untuk para > new member seperti yang bisa kalian lihat di tabel di atas. Kalau hanya bonus > di atas sepertinya masih kurang untuk membikin kalian betah bermain game Slot > Daftar Slot Joker123. Masih ada lagi yang bakal buat kalian untuk terus > bermain ialah Jackpot Progessive. > Beberapa permianan yang bisa pemain mainkan hanya mengaplikasikan 1 akun juga > ada di sini memandu permainan yang ada di dalamnya. Game Slot Joker Gaming > yang saat ini sedang banyak-banyaknya membawa tema yang menarik juga. > Layanan LiveChat kami yang akan di sediakan selama 24 jam penuh tanpa henti > supaya pemain bisa berkomunikasi dengan kami kapan saja menghasilkan kenaikan > layanan yang sungguh-sungguh baik dari Agen Slot Online kami. > h2. *Joker123 Slot Online Situs Download Joker 123 Teraman* > Jadi pemain bisa dengan gampang menghubungi kami jika adanya kendala dalam > bermain. Dan bisa memberikan keluhan yang di natural sehingga akan membentuk > alur bermain yang sungguh-sungguh menyenangkan dan santai dalam bermain Game > Slot Joker123. > Dan untuk jalan mendaftar yang gampang pun bukan hanya melalu LiveChat saja > tetapi juga melewati layanan Menu Daftar Joker Slot Atau Akun Agen Sv388 > Sabung Ayam yang sudah kami sediakan untuk anda bermain di sini. > Bermain bersama kami maka anda akan seketika mendapatkan layanan terbaik dan > profesional yang sudah di miliki oleh staff Joker123 tetapi di sini kemudahan > pertama pastinya ada dalam langkah meregistrasikan akun Joker123 Gaming > secara khusus dahulu. > Slot Online Joker123 Gaming Terpercaya yang di mana kini ini sudah banyak > sekali permainan yang ada di dalamnya juga anda bisa memainkan game slot > joker yang ada di dalamnya. > h3. *Daftar Joker123 Teraman Serta Login Joker123 Terbaru* > Permainan slot joker juga sudah menguasai pasaran game judi online yang di > mana akan membawakan keuntungan tersendiri untuk pemain yang mau memainkan > game slot joker hal yang demikian di dalam Web Joker123. > Pengalaman setiap-setiap orang yang bermain game online di Web Slot
[jira] [Deleted] (AXIS-2941) Situs Slot Deposit Pulsa Tanpa Potongan 20 Ribu 24 Jam
[ https://issues.apache.org/jira/browse/AXIS-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen deleted AXIS-2941: -- > Situs Slot Deposit Pulsa Tanpa Potongan 20 Ribu 24 Jam > --- > > Key: AXIS-2941 > URL: https://issues.apache.org/jira/browse/AXIS-2941 > Project: Axis > Issue Type: New Feature > Environment: Slot Online Deposit Pulsa Tanpa Potongan 2021 >Reporter: Deposit Pulsa Tanpa Potongan >Priority: Major > Labels: SlotDepositPulsa, SlotPulsaTelkomsel10rbTanpaPotongan, > depositpulsatanpapotongan, depositpulsatanpapotongan2021 > > h1. *Situs Slot Deposit Pulsa Tanpa Potongan 20 Ribu 24 Jam* > h1. > *[DAFTAR SEKARANG DISINI|http://citrahijau.com/?ref=citra88]* > Citra88 merupakan situs slot deposit pulsa tanpa potongan 20 ribu yang online > 24 jam setiap hari. Kami menyediakan beragam jenis permainan slot online > pulsa yang dapat anda mainkan setiap hari melalui seluler anda. Tanpa perlu > bingung mencari di internet lagi tempat bermain scater yang bermutu dan > berkualitas. Di Citra88 anda bisa memainakn segala jenis permainan slot pulsa > menggunakan 1 user id. Berikut adalah Daftar Slot Online Pulsa Tanpa Potongan > yang kami sediakan untuk anda : > * Pragmatic > * Habanero > * Isoftbet > * Playstar > * Microgaming > * Spadegaming > * CQ9 > h2. *FASILITAS SLOT DEPOSIT PULSA TANPA POTONGAN TERPERCAYA* > h2. > Sebagai agen judi slot deposit pulsa terpercaya, sudah sepantasnya jika > deposit menggunakan pulsa tidak di kenakan potongan. Hanya di situs citra88 > yang bisa [deposit pulsa tanpa > potongan|https://sites.google.com/view/slot-deposit-pulsa-citra88/home] dan > menadapatkan bonus deposit pulsa 10% setiap harinya. Selain itu masih banyak > lagi fasilitas dan pelayanan lainnya yang bisa anda dapatkan jika main di > situs kami. Banyak Fasilitas lainnya yang bisa anda temukan di sini seperti, > layanan live chat 24 jam, deposit pulsa tanpa potongan 24 jam, dan juga > costumer service yang sangat ramah dan sopan. > h3. *DAFTAR SITUS JUDI SLOT PULSA TERPERCAYA 2021* > h3. > Citra88 merupakan daftar situs judi slot online terkemuka dan berkualitas > dengan win rate 90%. Slot online merupakan permainan populer yang banyak di > gemari karena serunya memutar spin untuk mendapatkan freespin. Selain itu, > Banyak sekali jackpot yang tersedia dalam permainan slot online, sehingga > menambah keseruan saat anda memainkan nya melalui PC ataupun menggunakan > versi Mobile. Banyak faktor yang membuat orang-orang memilih situs slot > online, salah satunya seperti: Pelayanan, Jaminan Pembayaran, Bonus yang di > begikan, serta kenyamanan yang di berikan saat bermain. > Poin-poin penting tersebut dapat anda coba rasakan di situs Citra88 yang di > kenal Daftar Slot Online terpercaya 2020. Melalui handphone, anda langsung > dapat mengakses website kami yang telah di sesuaikan Responsive mobile anda. > Tanpa perlu download aplikasi, melalui handphone versi android dan iOS, anda > dapat memainkan slot online yang ada di situs kami. Kami menggunakan server > pilihan yang mungkin tidak akan anda temukan lag, lemot, atau jaringan error. > Selama sehari 24 jam, anda akan dilayani dengan customer service yang baik > dan sopan melalui livechat ataupun whatsapp. > h4. *Situs Deposit Pulsa Tanpa Potongan 24 Jam* > h4. > Kami beroperasi Mulai dari 00.00 hingga 12.00 dan 12.00 hingga 00.00 wib > setiap hari. Anda dapat melakukan deposit pulsa tanpa potongan 24 jam setiap > hari. Dengan itu juga kami siap melayani anda sepenuh hati tanpa henti. Semua > permainan yang kami sediakan bisa di mainkan kapan saja dan di mana saja > tanpa khawatir tidak dapat memainkannya. > Costumer service kami akan membereskan permasalahan anda seperti proses > deposit, proses withdraw atau melakukan register akun. Kami adalah situs yang > bernama Citra88 atau biasa di sebut situs judi online deposit pulsa tanpa > potongan. Operator pulsa 24 jam kami sediakan di sini seperti: Telkomsel, > [XL|https://sites.google.com/view/slot-pulsa-xl-tanpa-potongan/home], Axis, > Smartfren, Indosat. Sebagai situs deposit pulsa terpercaya, tentunya kami > telah mempersiapakn diri untuk melayani anda 24 jam. > h5. *CARA DAFTAR AKUN DEPOSIT PULSA TANPA POTONGAN* > h5. > Untuk menjadi pemain di situs deposit pulsa cepat tanpa potongan, siapkan > terlebih dahulu informasi pribadi dan beberapa data penting lainnya seperti: > Nama Lengkap : > Email : > Mata Uang : > Nomor Handphone : > Username : > Password : > Jenis Bank : > Nomor Rekening : > Untuk Langkah selanjutnya anda perlu memahami cara deposit. Untuk informasi > lebih lanjut, anda bisa menghubungi kami melalui kontak yang telah kami > sediakan. > Bagaimana jika saya tidak memiliki Rekening? > Tenang saja, kami juga menyediakan
[jira] [Deleted] (AXIS-2940) SLOT DEPOSIT PULSA BONUS NEW MEMBER 100% TANPA POTONGAN 396CLUB AGEN SITUS JUDI ONLINE TERPERCAYA
[ https://issues.apache.org/jira/browse/AXIS-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen deleted AXIS-2940: -- > SLOT DEPOSIT PULSA BONUS NEW MEMBER 100% TANPA POTONGAN 396CLUB AGEN SITUS > JUDI ONLINE TERPERCAYA > - > > Key: AXIS-2940 > URL: https://issues.apache.org/jira/browse/AXIS-2940 > Project: Axis > Issue Type: New Feature > Environment: Slot deposit pulsa xl, axis dan telkomsel Indonesia > terpercaya dari situs agen judi slot online 396club dan dapatkan kesempatan > hadiah putaran gratis !! fraeebet/freespin slots dari game slot online > pilihan terbaik 396club https://396indo.com >Reporter: SLOT DEPOSIT PULSA BONUS NEW MEMBER 100% SLOT PULSA XL > AXIS TELKOMSEL INDONESIA TANPA POTONGAN >Priority: Major > Labels: SlotDepositPulsa, SlotPulsaTelkomsel, agenslot, > bandarslot, judislot, situsslot, slotbonus, slotindonesia, slotonline, > slotpulsa, slotpulsaaxis, slotpulsaxl > Original Estimate: 504h > Remaining Estimate: 504h > > h1. *SLOT DEPOSIT PULSA BONUS NEW MEMBER 100% TANPA POTONGAN 396CLUB AGEN > SITUS JUDI ONLINE TERPERCAYA* > h2. *Slot deposit pulsa xl, axis dan telkomsel Indonesia terpercaya dari > situs agen judi slot online 396club dan dapatkan kesempatan hadiah putaran > gratis !! fraeebet/freespin slots dari game slot online pilihan terbaik > 396club.* > > > [!https://1.bp.blogspot.com/-stGOGy8CwOs/YAZgmsFJ8EI/AbU/wqJ2cQL4-KUr_U7oShLMHiFVmgm0Js2iQCLcBGAsYHQ/w640-h400/Screenshot_44.png|width=640,height=400!|https://www.396indo.com/] > > > [!https://1.bp.blogspot.com/-Kvaf0ZKk8QM/X_JzZnMcqPI/AFI/y2gGp7H4b-IuQ9UWNRr14rBxu9ZHImT8ACLcBGAsYHQ/w320-h126/registernowgif.gif|width=320,height=126!|https://www.396indo.com/register] > > > [!https://1.bp.blogspot.com/-tC2H9NB07Ec/X_JzRCRf0bI/AFE/wzddh0cgKAYbLt0zriFHjuxvO69ykovCgCLcBGAsYHQ/w320-h90/Gambar-GIF-Order-via-WhatsApp.gif|width=320,height=90!|https://api.whatsapp.com/send?phone=+639270327213] > h3. Berbagai Slot Online Di 396CLUB Slot Deposit Pulsa XL > > Pada suatu waktu, kasino online didukung oleh satu penyedia perangkat lunak. > Dengan perkembangan perangkat lunak game, segera dimungkinkan untuk > menggabungkan game terbaik dari penyedia game yang berbeda dalam satu > platform. Sekarang pengaturan ini sudah menjadi kebiasaan. Kasino online > 396CLUB Slot Deposit Pulsa XL hanya dioperasikan oleh Microgaming selama > beberapa dekade. Baru-baru ini telah menyediakan penyedia perangkat lunak > lain dan memberikan para pemainnya berbagai permainan slot baru yang menarik. > Artikel ini memilih dua yang terbaik. > > 7 Sins berasal dari portofolio Play 'n Go. 243 cara untuk memenangkan slot > online adalah yang terbaik dalam godaan. Kesombongan, keserakahan, nafsu, iri > hati, keserakahan, murka dan kemalasan telah digambarkan sebagai sirene yang > menggoda yang menunjukkan perilaku berdosa mereka dalam memenangkan animasi. > Simbol bayaran rendah adalah permainan kartu yang cocok. 7 adalah simbol > liar. Ini juga muncul sebagai Double 7 saat bertindak sebagai dua simbol liar > di samping satu sama lain. Kemudian dapat menghasilkan kombinasi lebih dari > lima simbol. Simbol liar memberikan pembayaran baris tertinggi. > > Penghargaan kotak emas menyebarkan pembayaran dan memicu tujuh putaran > gratis. Dalam setiap putaran bebas hanya satu dosa yang muncul. Pengganda > pembayaran meningkat dengan setiap putaran 1x. Fitur Kesempatan Kedua dipicu > saat Anda mendaratkan hanya dua simbol pencar di gulungan. Anda harus memilih > salah satu dosa di layar kedua. Jika Anda beruntung dia akan mengungkapkan > simbol pencar ketiga dan mengaktifkan putaran gratis. Jika tidak, Anda > mendapatkan kompensasi hingga 15x jumlah taruhan. > > 2 Juta SM berasal dari penyedia perangkat lunak CQ9. Salah satu atraksi slot > Betsoft adalah karya seni 3D berupa simbol dan animasi. Zaman prasejarah > diciptakan oleh simbol-simbol seperti gadis gua, harimau bergigi pedang, > Stonehenge, roda, pentungan, dan lukisan dinding. Simbol api memicu fitur > putaran gratis. Anda dapat memenangkan putaran gratis ekstra melalui fitur > ini. 2 Million BC menawarkan dua game bonus di layar kedua. Yang pertama > disebut fitur Sabre Attack yang dipicu oleh simbol biji pohon ek. Anda harus > membantu manusia gua membidik dan menembak harimau. Jika Anda mengalahkannya > maka Anda akan mendapatkan kredit bonus. Simbol berlian membuka fitur bonus > kedua. Kali ini Anda memberi tahu manusia gua bagaimana dia harus mencuri > berlian dari harimau gigi pedang. > > >
[jira] [Resolved] (AXIS2-5988) axis wsdl namespace prefixes are changing in the response
[ https://issues.apache.org/jira/browse/AXIS2-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5988. Resolution: Not A Bug Namespace prefixes are arbitrary and Axis2 (or Axiom; I don't remember where they are generated) doesn't make any guarantee that they are deterministic. If you have code that relies on a specific namespace prefix being used, then that code is incorrect (It doesn't conform to XML specifications) and needs to be fixed. > axis wsdl namespace prefixes are changing in the response > - > > Key: AXIS2-5988 > URL: https://issues.apache.org/jira/browse/AXIS2-5988 > Project: Axis2 > Issue Type: Bug > Components: wsdl >Reporter: Sivaramakrishnan Raghavan >Priority: Major > > ax25 namespace prefix got changed to ax21 prefix.. we would like to know the > axis2 behavior causing this: > Our system was sending a soap response like this until now: > http://com.service/xsd;> xmlns:ax25="http://service.com/xsd; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:type="ax25:Result"> > TEST > > Now after deploying to a new environment, It got changed to: > http://com.service/xsd;> xmlns:ax21="http://service.com/xsd; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:type="ax21:Result"> > TEST > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5993) Upgrade logging to log4j v2.x
[ https://issues.apache.org/jira/browse/AXIS2-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5993: --- Fix Version/s: (was: 1.7.9) 1.8.0 > Upgrade logging to log4j v2.x > - > > Key: AXIS2-5993 > URL: https://issues.apache.org/jira/browse/AXIS2-5993 > Project: Axis2 > Issue Type: Improvement > Components: client-api >Affects Versions: 1.7.9 > Environment: Tomcat >Reporter: Gregory Knott >Assignee: Robert Lazarski >Priority: Major > Fix For: 1.8.0 > > > [https://nvd.nist.gov/vuln/detail/CVE-2019-17571] > This vulnerability prompts us to upgrade to a v2 version of log4j since all > v1 versions are end of support. However all versions of axis2 still use v1 > log4j. > If axis2 is not updated, then we will need to move to another web service > container. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5994) Update woodstox-core-asl to woodstox-core
[
https://issues.apache.org/jira/browse/AXIS2-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5994.
Fix Version/s: 1.8.0
Resolution: Fixed
Axis2 doesn't depend directly on Woodstox. The dependency on Woodstox comes in
via {{axiom-impl}}. Axiom 1.3 already depends on Woodstox 6, so this will be
fixed in Axis2 1.8.
> Update woodstox-core-asl to woodstox-core
> -
>
> Key: AXIS2-5994
> URL: https://issues.apache.org/jira/browse/AXIS2-5994
> Project: Axis2
> Issue Type: New Feature
>Reporter: Davy
>Priority: Major
> Fix For: 1.8.0
>
>
> The current woodstox version used has been renamed after 4.x and continues as
> woodstox-core. The reason this update is relevant is because this way axis2
> can use the stax2-api version 4.x (currently 3.x), which is necessary for
> axis2 to be compatible with some important libraries like the newer jackson
> versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5995) Invalid char in xml namespace prefix
[
https://issues.apache.org/jira/browse/AXIS2-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253422#comment-17253422
]
Andreas Veithen commented on AXIS2-5995:
This appears to be a problem in XMLBeans: XMLBEANS-436. As mentioned in that
issue, at the XMLBeans level, a possible workaround is to set suggested
prefixes on the {{XmlOptions}}. The question is then whether it's possible to
set {{XmlOptions}} in Axis2.
> Invalid char in xml namespace prefix
>
>
> Key: AXIS2-5995
> URL: https://issues.apache.org/jira/browse/AXIS2-5995
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.9
>Reporter: William Buch
>Priority: Blocker
> Attachments: 12.21.2020.axis.logs.txt
>
>
> When upgrading from Axis2 1.5.1 to Axis2 1.7.9, xmlbeans based XML is
> creating a namespace with invalid characters in them. Please see sample
> below. I am not sure how to resolve this and looking for any pointers. In
> debugging I cannot find the place where the xmlns:x / = is being added or why
> it would add it like this.
>
> {{ xmlns:x / ="http://www.ACORD.org/standards/PC_Surety/ACORD1.10.0/xml/;> :ItemIdInfo> :OtherIdTypeCd>UserId :OtherId>NBVQA670
> :OtherIdTypeCd>ProfileId :OtherId>Min
> :OtherIdTypeCd>ApplicationId :OtherId>NBV
> :OtherIdTypeCd>UseContractorSearch :OtherId>true
>
> }}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Reopened] (AXIS-2295) problem with http proxy parameters caching mechanism
[
https://issues.apache.org/jira/browse/AXIS-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen reopened AXIS-2295:
---
I had to roll back this change because it causes
{{test.wsdl.multithread.MultithreadTestCase}} to fail.
> problem with http proxy parameters caching mechanism
>
>
> Key: AXIS-2295
> URL: https://issues.apache.org/jira/browse/AXIS-2295
> Project: Axis
> Issue Type: Bug
> Components: Basic Architecture
> Environment: weblogic 8.1 and Windows XP
>Reporter: Renaud SAULAY
>Assignee: Robert Lazarski
>Priority: Minor
> Attachments: DefaultHTTPTransportClientProperties.java,
> TransportClientPropertiesFactory.java
>
>
> The JVM http proxy parameters are read only once when calling a webservice :
> if you make a first Call.invoke(...) the JVM proxy parameters are read and
> cached, but on other calls of method invoke() those JVM http proxy
> parameters are not read again, which can be disturbing since
> one may need to change these parameters and they will not be taken into
> account unless the application server is restarted.
> See classes :
>org.apache.axis.components.net.DefaultSocketFactory; (lines 97, 102, 116)
>org.apache.axis.components.net.TransportClientPropertiesFactory (method
> create)
>rg.apache.axis.components.net.DefaultHTTPTransportClientProperties (all
> methods)
> I hope i have been precise enough on this bug description.
> If not, do not hesitate to email me
> Thank you for your help
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5979) Error while printing the SOAP Message Response (In)
[
https://issues.apache.org/jira/browse/AXIS2-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5979.
Resolution: Not A Bug
> Error while printing the SOAP Message Response (In)
>
>
> Key: AXIS2-5979
> URL: https://issues.apache.org/jira/browse/AXIS2-5979
> Project: Axis2
> Issue Type: Bug
>Reporter: kuldeep
>Priority: Major
> Labels: Axis2
>
> I had created a client stub (jar) using the Axis 2. I need to consume this
> jar into my application and like wise print the soap request and response
> whenever a soap service is invoked. How do i do that ? While surfing on
> internet i only found the below approach to print the logs. But it only print
> the request . While printing the response it throws error "
> java.lang.IllegalStateException: Can't process next node because caching is
> disabled" . Please assist ?
> ServiceContext serviceContext =
> this.proxy._getServiceClient().getServiceContext();
> boolean cacheLastOperationContext = true;
> serviceContext.setCachingOperationContext(cacheLastOperationContext);
> OperationContext lastOperationContext =
> serviceContext.getLastOperationContext();
> lastOperationContext.setComplete(true);
> if(null != lastOperationContext) {
> MessageContext outMessageContext =
> lastOperationContext.getMessageContext("Out");
> MessageContext inMessageContext =
> lastOperationContext.getMessageContext("In");
> if (outMessageContext != null)
> { System.out.println("OUT SOAP: " +
> outMessageContext.getEnvelope().toString()); }
> if (inMessageContext != null)
> { ** This below line throws the error while printing the response**
> System.out.println("IN SOAP: "+ inMessageContext.getEnvelope().toString());
> proxy.cleanup(); }
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5979) Error while printing the SOAP Message Response (In)
[
https://issues.apache.org/jira/browse/AXIS2-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042831#comment-17042831
]
Andreas Veithen commented on AXIS2-5979:
You would do that using a handler, as described in
[http://axis.apache.org/axis2/java/core/docs/modules.html.|http://axis.apache.org/axis2/java/core/docs/modules.html]
> Error while printing the SOAP Message Response (In)
>
>
> Key: AXIS2-5979
> URL: https://issues.apache.org/jira/browse/AXIS2-5979
> Project: Axis2
> Issue Type: Bug
>Reporter: kuldeep
>Priority: Major
> Labels: Axis2
>
> I had created a client stub (jar) using the Axis 2. I need to consume this
> jar into my application and like wise print the soap request and response
> whenever a soap service is invoked. How do i do that ? While surfing on
> internet i only found the below approach to print the logs. But it only print
> the request . While printing the response it throws error "
> java.lang.IllegalStateException: Can't process next node because caching is
> disabled" . Please assist ?
> ServiceContext serviceContext =
> this.proxy._getServiceClient().getServiceContext();
> boolean cacheLastOperationContext = true;
> serviceContext.setCachingOperationContext(cacheLastOperationContext);
> OperationContext lastOperationContext =
> serviceContext.getLastOperationContext();
> lastOperationContext.setComplete(true);
> if(null != lastOperationContext) {
> MessageContext outMessageContext =
> lastOperationContext.getMessageContext("Out");
> MessageContext inMessageContext =
> lastOperationContext.getMessageContext("In");
> if (outMessageContext != null)
> { System.out.println("OUT SOAP: " +
> outMessageContext.getEnvelope().toString()); }
> if (inMessageContext != null)
> { ** This below line throws the error while printing the response**
> System.out.println("IN SOAP: "+ inMessageContext.getEnvelope().toString());
> proxy.cleanup(); }
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5979) Error while printing the SOAP Message Response (In)
[
https://issues.apache.org/jira/browse/AXIS2-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042613#comment-17042613
]
Andreas Veithen commented on AXIS2-5979:
This is by design. For performance reasons, the original response XML isn't
preserved; it's consumed by the databinding when building the response object.
For the outgoing request the situation is different: the XML is generated on
the fly from the request object and therefore can be serialized any number of
times.
> Error while printing the SOAP Message Response (In)
>
>
> Key: AXIS2-5979
> URL: https://issues.apache.org/jira/browse/AXIS2-5979
> Project: Axis2
> Issue Type: Bug
>Reporter: kuldeep
>Priority: Major
> Labels: Axis2
>
> I had created a client stub (jar) using the Axis 2. I need to consume this
> jar into my application and like wise print the soap request and response
> whenever a soap service is invoked. How do i do that ? While surfing on
> internet i only found the below approach to print the logs. But it only print
> the request . While printing the response it throws error "
> java.lang.IllegalStateException: Can't process next node because caching is
> disabled" . Please assist ?
> ServiceContext serviceContext =
> this.proxy._getServiceClient().getServiceContext();
> boolean cacheLastOperationContext = true;
> serviceContext.setCachingOperationContext(cacheLastOperationContext);
> OperationContext lastOperationContext =
> serviceContext.getLastOperationContext();
> lastOperationContext.setComplete(true);
> if(null != lastOperationContext) {
> MessageContext outMessageContext =
> lastOperationContext.getMessageContext("Out");
> MessageContext inMessageContext =
> lastOperationContext.getMessageContext("In");
> if (outMessageContext != null)
> { System.out.println("OUT SOAP: " +
> outMessageContext.getEnvelope().toString()); }
> if (inMessageContext != null)
> { ** This below line throws the error while printing the response**
> System.out.println("IN SOAP: "+ inMessageContext.getEnvelope().toString());
> proxy.cleanup(); }
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5935) axis2 service did not work under jdk 11 class format
[ https://issues.apache.org/jira/browse/AXIS2-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827549#comment-16827549 ] Andreas Veithen commented on AXIS2-5935: It means that a particular class of services with code compiled for Java 11 will not work. > axis2 service did not work under jdk 11 class format > > > Key: AXIS2-5935 > URL: https://issues.apache.org/jira/browse/AXIS2-5935 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.7.8 >Reporter: Kris Chung >Priority: Blocker > > jdk version: 11 > tomcat: 9.0.12 > os: centos 6 > axis2 version: 1.7.8 > 20:06:16.797 ERROR ServiceDeployer - The axis2 service, which is not valid, > caused The following error occurred during schema generation: Error looking > for paramter names in bytecode: unexpected bytes in file > org.apache.axis2.deployment.DeploymentException: The following error occurred > during schema generation: Error looking for paramter names in bytecode: > unexpected bytes in file > at > org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:117) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:232) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:154) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:149) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:585) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:164) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:136) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:289) > ~[axis2-kernel-1.7.8.jar:1.7.8] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS-2932) Windows Server 2019
[ https://issues.apache.org/jira/browse/AXIS-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-2932. --- Resolution: Invalid Please don't create JIRAs to ask questions. Instead use the user mailing list. Anyway, this has been answered in https://markmail.org/message/mzcz74bmdlplqxvt. > Windows Server 2019 > --- > > Key: AXIS-2932 > URL: https://issues.apache.org/jira/browse/AXIS-2932 > Project: Axis > Issue Type: Wish >Reporter: mengln >Priority: Major > Fix For: 1.4 > > > Hello, I am doing an investigation. Does Windows Server 2019 support the > following products: > Apache Axis 1.4 > Is the other version supported? > Can you tell me, thank you very much. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5954) Windows Server 2019
[ https://issues.apache.org/jira/browse/AXIS2-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5954. Resolution: Invalid Please don't create JIRAs to ask questions. Instead use the user mailing list. Anyway, this has been answered in https://markmail.org/message/mzcz74bmdlplqxvt. > Windows Server 2019 > --- > > Key: AXIS2-5954 > URL: https://issues.apache.org/jira/browse/AXIS2-5954 > Project: Axis2 > Issue Type: Wish >Reporter: mengln >Priority: Major > > Does Windows Server 2019 support the following products: > Apache Axis2 1.5.1 > Apache Axis2 1.5.5 > Apache Axis2/C 1.6.0 > Apache Axis2 - ADB Codegen 1.4.1 > Is the other version supported? > .Can you tell me, thank you very much. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5952) File.mkdir() may fail and cause crash.
[ https://issues.apache.org/jira/browse/AXIS2-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5952. Resolution: Fixed Fix Version/s: 1.8.0 > File.mkdir() may fail and cause crash. > -- > > Key: AXIS2-5952 > URL: https://issues.apache.org/jira/browse/AXIS2-5952 > Project: Axis2 > Issue Type: Bug >Reporter: bd2019us >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Attachments: 1.patch > > > Locations: > (1) > modules/tool/axis2-idea-plugin/src/main/java/org/apache/axis2/tools/wizardframe/WizardFrame.java:409 > (2) > modules/tool/axis2-idea-plugin/src/main/java/org/apache/axis2/tools/bean/SrcCompiler.java:50 > The File.mkdir() method will fail if the parent directory does not exist. In > this case, since we cannot ensure the existence of parent directory and we > still need to create the directory, the File.mkdirs() should be preferred, > which is safe and without any lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (RAMPART-446) Rampart uses vulnerable version of WSS4J
[ https://issues.apache.org/jira/browse/RAMPART-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved RAMPART-446. - Resolution: Fixed Fix Version/s: 1.7.2 > Rampart uses vulnerable version of WSS4J > > > Key: RAMPART-446 > URL: https://issues.apache.org/jira/browse/RAMPART-446 > Project: Rampart > Issue Type: Bug >Affects Versions: 1.7.1 >Reporter: Christopher >Priority: Critical > Fix For: 1.7.2 > > > Apache WSS4J has some security issues that have been known since 2015. See > [https://ws.apache.org/wss4j/security_advisories.html] Both are against any > version of Apache WSS4J below version 1.6.17. Looking at the pom.xml file > for Apache Rampart on version 1.7.1, it appears that Rampart pulls down > version 1.6.16, and hence is vulnerable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5946) IDEA Plugin cannot be installed into IDEA environment
[ https://issues.apache.org/jira/browse/AXIS2-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740754#comment-16740754 ] Andreas Veithen commented on AXIS2-5946: The IDEA plugin code hasn't been updated for more than 10 years. I think it's time to remove it unless somebody steps up to maintain it. Also note that manually generating code and building archives is not a recommended practice anyway. It should be done during the build process (using the provided Maven plugins e.g.). > IDEA Plugin cannot be installed into IDEA environment > - > > Key: AXIS2-5946 > URL: https://issues.apache.org/jira/browse/AXIS2-5946 > Project: Axis2 > Issue Type: Bug > Components: ide plugins >Affects Versions: 1.7.9 > Environment: IDEA 2018.3.3, Java 8 >Reporter: Artur Linhart >Priority: Critical > > The downloaded ZIP with Axis2 Plugin cannot be installed into IDEA 2018.3.3 > After download and installation attempt from disk > (File/Settings/Plugins/Install from Disk) there comes an error "Fail to load > plugin descriptor from file axis2-idea-plugin-1.7.9.zip" and nothing is > installed. > This makes the plugin completely unusable -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5945) CVE-2014-0107 in xalan
[ https://issues.apache.org/jira/browse/AXIS2-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5945. Resolution: Fixed Fix Version/s: 1.7.10 > CVE-2014-0107 in xalan > -- > > Key: AXIS2-5945 > URL: https://issues.apache.org/jira/browse/AXIS2-5945 > Project: Axis2 > Issue Type: Bug > Components: deployment >Affects Versions: 1.7.9 >Reporter: Ranjit Vadakkan >Priority: Major > Fix For: 1.7.10 > > > BlackDuck is flagging Axis2's transitive dependency to xalan 2.7.0 as a major > vulnerability. See [https://nvd.nist.gov/vuln/detail/CVE-2014-0107] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5944) NullPointer Exception on AbstractContext.needPropertyDifferences
[
https://issues.apache.org/jira/browse/AXIS2-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727056#comment-16727056
]
Andreas Veithen commented on AXIS2-5944:
The line where the {{NullPointerException}} is thrown is:
{code:java}
ClusteringAgent clusteringAgent =
cc.getAxisConfiguration().getClusteringAgent();
{code}
{{cc}} is the {{ConfigurationContext}} and there is a null check right before,
so the only possible reason is that the {{AxisConfiguration}} is null. That
would happen after calling {{terminate}} on the {{ConfigurationContext}}.
So probably there is a bug in your application where you use a stub or
{{ServiceClient}} after destroying the {{ConfigurationContext}}.
> NullPointer Exception on AbstractContext.needPropertyDifferences
>
>
> Key: AXIS2-5944
> URL: https://issues.apache.org/jira/browse/AXIS2-5944
> Project: Axis2
> Issue Type: Bug
>Affects Versions: 1.6.2
>Reporter: Santosh Raman
>Priority: Critical
>
> In Production, we are seeing NullPointer exception being thrown randomly when
> calling an Axis2 webservice.
> From the stack trace it looks like it happens when the axis2 client is
> trying to process the response.
> The webservice calls an ESB layer and the ESB layer calls the external
> interface.The ESB layer is just a pass through.
> The stack trace is
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
> at
> org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
> at
> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:270)
> at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:194)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
> at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
> at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
> at
> curam.custom.webservices.edrs.impl.NFWSElectronicDQRecipientService.onlineQueryByID(NFWSElectronicDQRecipientService.java:175)
> at
> curam.custom.webservices.edrs.impl.NFElectronicDQUtil.invokeOnlineQueryByID(NFElectronicDQUtil.java:452)
> at
> curam.custom.nfprogramintegrity.disqualification.facade.impl.NFEPIDisqualification.getElectornicDQDetailsListBySsn(NFEPIDisqualification.java:555)
> at
> curam.custom.nfprogramintegrity.disqualification.facade.impl.NFEPIDisqualification.getDQSearchRecordsFromEDRS(NFEPIDisqualification.java:491)
> at sun.reflect.GeneratedMethodAccessor352.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at curam.util.internal.CuramSessionBean.invoke(CuramSessionBean.java:297)
>
> Thanks
> Santosh
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5943) GSON, MessageContext.isFault() NPE because getEnvelope() returns null
[
https://issues.apache.org/jira/browse/AXIS2-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724546#comment-16724546
]
Andreas Veithen commented on AXIS2-5943:
I think that the basic assumption that the Axis2 architecture makes is that any
payload always has some form of SOAP representation and the envelope should
therefore never be null. And in fact {{GsonXMLStreamReader}} appears to define
such a representation.
> GSON, MessageContext.isFault() NPE because getEnvelope() returns null
> -
>
> Key: AXIS2-5943
> URL: https://issues.apache.org/jira/browse/AXIS2-5943
> Project: Axis2
> Issue Type: Bug
>Reporter: robert lazarski
>Priority: Major
>
> As discussed on the user list, after a GSON service completes, this code in
> MessageContext throws an NPE:
> public boolean isFault() {
> return getEnvelope().hasFault();
> }
> The code I compiled myself and is running on my production systems is as
> follows, [~veithen] do you have a suggestion on a better fix?
> public boolean isFault() {
> if (getEnvelope() == null) {
> log.warn(getLogIDString() + ": WARNING " + myClassName +
> " , found null envelope, returning false");
> return false;
> }
> return getEnvelope().hasFault();
> }
>
> See user list discussion:
>
> http://mail-archives.apache.org/mod_mbox/axis-java-user/201808.mbox/%3ccabpplbvtwaa54j1rnjvhrkdtreeqq9fwzuh-ak-xnr782pm...@mail.gmail.com%3E
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5936) Soapenv namespace is not added implicitly or explicitly on Redhat
[ https://issues.apache.org/jira/browse/AXIS2-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718228#comment-16718228 ] Andreas Veithen commented on AXIS2-5936: That's a plausible theory. The OS related issue may simply be a difference in file system ordering, making it use different StAX implementations. > Soapenv namespace is not added implicitly or explicitly on Redhat > - > > Key: AXIS2-5936 > URL: https://issues.apache.org/jira/browse/AXIS2-5936 > Project: Axis2 > Issue Type: Bug > Components: adb >Affects Versions: 1.6.4, 1.7.8 >Reporter: Muhammad Hamid >Priority: Major > > Tested with Linux (Red Hat Enterprise Linux Server release 5.11 (Tikanga) > and 7.5 (Maipo)), namespace for soapenv is not being added, tried to add it > implicitly, doesn't work. > The only workaround I was able to do to fix this is to use SOAP 11 envelope, > and add it's namespace, so seems like this error is specific to SOAP 12. > Java version in Linux: jdk1.8.0_92 > Java version in Windows: jdk1.8.0.161 > p.s in windows everything works fine, I don't have to specify envelope's > version, or namespace URI. > another p.s: this issue had been there since version 1.6.2, and I believe > it's OS specific, should try it on newer redhat OS. > Update: I've tried it with Redhat 7.5 Maipo, same issue -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5936) Soapenv namespace is not added implicitly or explicitly on Redhat
[ https://issues.apache.org/jira/browse/AXIS2-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713322#comment-16713322 ] Andreas Veithen commented on AXIS2-5936: The builds of Axis2 and Axiom (including their test suites) both succeed on RHEL 7.5 with OpenJDK 1.8.0_191. If this was a general problem, I would expect this to trigger test failures. Can you provide an executable Java program (ideally as a Maven project) that reproduces the issue? > Soapenv namespace is not added implicitly or explicitly on Redhat > - > > Key: AXIS2-5936 > URL: https://issues.apache.org/jira/browse/AXIS2-5936 > Project: Axis2 > Issue Type: Bug > Components: adb >Affects Versions: 1.6.4, 1.7.8 >Reporter: Muhammad Hamid >Priority: Major > > Tested with Linux (Red Hat Enterprise Linux Server release 5.11 (Tikanga) > and 7.5 (Maipo)), namespace for soapenv is not being added, tried to add it > implicitly, doesn't work. > The only workaround I was able to do to fix this is to use SOAP 11 envelope, > and add it's namespace, so seems like this error is specific to SOAP 12. > Java version in Linux: jdk1.8.0_92 > Java version in Windows: jdk1.8.0.161 > p.s in windows everything works fine, I don't have to specify envelope's > version, or namespace URI. > another p.s: this issue had been there since version 1.6.2, and I believe > it's OS specific, should try it on newer redhat OS. > Update: I've tried it with Redhat 7.5 Maipo, same issue -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5941) version issue - Jdk 8 SOAP WS calls MEP RawXMLINOnlyMessageReceiver instead of AbstractInOutMessageReceiver
[ https://issues.apache.org/jira/browse/AXIS2-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697837#comment-16697837 ] Andreas Veithen commented on AXIS2-5941: Can you share a minimal test case to reproduce the problem? > version issue - Jdk 8 SOAP WS calls MEP RawXMLINOnlyMessageReceiver instead > of AbstractInOutMessageReceiver > --- > > Key: AXIS2-5941 > URL: https://issues.apache.org/jira/browse/AXIS2-5941 > Project: Axis2 > Issue Type: Bug >Reporter: Aparna >Priority: Major > > I have created a Java web server proxy using client's wsdl file (using > axis2). The service works fine when I use JDK 6/7. When I switch over to > JDK 8 then internally it uses reflection and tries to find out API method > with void return type and OMElement as parameter which doesn't exist in the > ServiceSkeleton. > > I have posted the same question on StackOverFlow. This is the link for more > details - > [https://stackoverflow.com/questions/53372508/version-issue-jdk-8-tomcat-8-web-service-calls-mep-rawxmlinonlymessagereceiv|https://www.google.com/url?q=https://stackoverflow.com/questions/53372508/version-issue-jdk-8-tomcat-8-web-service-calls-mep-rawxmlinonlymessagereceiv=D=hangouts=1542800419655000=AFQjCNGyxOEKZUDa8A8uHxkMdDRb1-baCg] > > For JDK8 - when I post the request xml from SoapUi, the call goes to > org.apache.axis2.receivers.*RawXMLINOnlyMessageReceiver* where it finds the > method(void) name using reflection which doesn't exist in the serviceSkeleton. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5936) Soapenv namespace is not added implicitly or explicitly on Linux Tikanga
[ https://issues.apache.org/jira/browse/AXIS2-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690614#comment-16690614 ] Andreas Veithen commented on AXIS2-5936: We would have to find a way to reproduce this issue. That's problematic because RHEL5 is really old and no cloud provider offers images for that version. Any idea? Can you at least provide a minimal test case that shows the problem? > Soapenv namespace is not added implicitly or explicitly on Linux Tikanga > > > Key: AXIS2-5936 > URL: https://issues.apache.org/jira/browse/AXIS2-5936 > Project: Axis2 > Issue Type: Bug > Components: adb >Affects Versions: 1.6.4, 1.7.8 >Reporter: Muhammad Hamid >Priority: Major > > Tested with Linux (Red Hat Enterprise Linux Server release 5.11 (Tikanga)), > namespace for soapenv is not being added, tried to add it implicitly, doesn't > work. > The only workaround I was able to do to fix this is to use SOAP 11 envelope, > and add it's namespace, so seems like this error is specific to SOAP 12. > Java version in Linux: jdk1.8.0_92 > Java version in Windows: jdk1.8.0.161 > p.s in windows everything works fine, I don't have to specify envelope's > version, or namespace URI. > another p.s: this issue had been there since version 1.6.2, and I believe > it's OS specific, should try it on newer redhat OS. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5930) CVE issues with dependency jars of axis2
[ https://issues.apache.org/jira/browse/AXIS2-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689972#comment-16689972 ] Andreas Veithen commented on AXIS2-5930: The release process for 1.7.9 has been started; see https://markmail.org/thread/2vfy7b6gswxln6sk. > CVE issues with dependency jars of axis2 > > > Key: AXIS2-5930 > URL: https://issues.apache.org/jira/browse/AXIS2-5930 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.8 >Reporter: tanishq pruthi >Priority: Major > Fix For: 1.7.9 > > > The dependent jars in axis 2 package are not updated to latest version > Due to which, some of the jars contains vulnerabilities . Some of them are > below > [mex-1.7.6-impl.jar|#l203_99ee5f563d035e3904894ea89c4550bb71ddf34b] > [axis2-kernel-1.7.6.jar|#l245_aa2e05c5dc080f7089072d17acfb9b1a50d8bda9] > [tribes-6.0.16.jar|#l321_50b300ff415ef0cf3af4f14ec03131cdcb019efa] > Dependency check tool is giving the following CVE in these jar > *[CVE-2012-5351|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-5351]* > *[CVE-2012-4418|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-4418]* > ** -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (RAMPART-445) Expired certificates in rampart project
[ https://issues.apache.org/jira/browse/RAMPART-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16680553#comment-16680553 ] Andreas Veithen commented on RAMPART-445: - There are two basic principles or best practices relevant here: * Sources should consist only of human written files. If something needs to be generated, it should be generated during the build process, not included in the sources. * Unit tests should be deterministic and not depend on the current time. Therefore the right solution here would be to generate those certificates during the build process (so that they always have a validity that covers the test execution). However, I couldn't figure out how those certificates and corresponding key material was originally generated and/or how to generate them during the build process. So the next best solution was to effectively disable validation of the expiry date. > Expired certificates in rampart project > --- > > Key: RAMPART-445 > URL: https://issues.apache.org/jira/browse/RAMPART-445 > Project: Rampart > Issue Type: Bug > Components: rampart-integration >Affects Versions: 1.6.2 >Reporter: Svetoslav ILIEV >Priority: Major > Fix For: 1.7.2 > > > We observed expired certificates in Apache Rampart project. Keystores with > expired certificates are located in: > \modules\rampart-integration\src\test\resources\rahas\rahas-sts.jks > > and > \modules\rampart-integration\src\test\resources\rahas\sec.jks > Other Rampart versions might be also affected. > Could you please renew the expired certificates? > > Best Regards, > Svetoslav ILIEV -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5938) juli-6.0.16.jar and tribes-6.0.16.jar has reached end of life.
[ https://issues.apache.org/jira/browse/AXIS2-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5938. Resolution: Duplicate See AXIS2-5930. > juli-6.0.16.jar and tribes-6.0.16.jar has reached end of life. > -- > > Key: AXIS2-5938 > URL: https://issues.apache.org/jira/browse/AXIS2-5938 > Project: Axis2 > Issue Type: Improvement > Components: adb >Affects Versions: 1.7.6 >Reporter: Raghavi >Priority: Critical > > Hi, > We are using Apache axis2 1.7.6 version. We could see that this package has > juli-6.0.16.jar and tribes-6.0.16.jar , which has reached end of life. Could > you please check and get back to us, is there any plan to upgrade these jars. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5937) End Of Life for juli-6.0.16.jar and tribes-6.0.16.jar
[ https://issues.apache.org/jira/browse/AXIS2-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5937. Resolution: Duplicate > End Of Life for juli-6.0.16.jar and tribes-6.0.16.jar > - > > Key: AXIS2-5937 > URL: https://issues.apache.org/jira/browse/AXIS2-5937 > Project: Axis2 > Issue Type: Improvement > Components: adb >Affects Versions: 1.7.6 >Reporter: Neeraj >Priority: Major > > The above mentioned jars (juli-6.0.16.jar and tribes-6.0.16.jar) have reached > end of life. Is there any plan to upgrade the affected components. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (RAMPART-445) Expired certificates in rampart project
[ https://issues.apache.org/jira/browse/RAMPART-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved RAMPART-445. - Resolution: Fixed Fix Version/s: (was: 1.6.2) 1.7.2 > Expired certificates in rampart project > --- > > Key: RAMPART-445 > URL: https://issues.apache.org/jira/browse/RAMPART-445 > Project: Rampart > Issue Type: Bug > Components: rampart-integration >Affects Versions: 1.6.2 >Reporter: Svetoslav ILIEV >Priority: Major > Fix For: 1.7.2 > > > We observed expired certificates in Apache Rampart project. Keystores with > expired certificates are located in: > \modules\rampart-integration\src\test\resources\rahas\rahas-sts.jks > > and > \modules\rampart-integration\src\test\resources\rahas\sec.jks > Other Rampart versions might be also affected. > Could you please renew the expired certificates? > > Best Regards, > Svetoslav ILIEV -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (RAMPART-445) Expired certificates in rampart project
[ https://issues.apache.org/jira/browse/RAMPART-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677259#comment-16677259 ] Andreas Veithen commented on RAMPART-445: - This was fixed by r1837550 and r1837559. > Expired certificates in rampart project > --- > > Key: RAMPART-445 > URL: https://issues.apache.org/jira/browse/RAMPART-445 > Project: Rampart > Issue Type: Bug > Components: rampart-integration >Affects Versions: 1.6.2 >Reporter: Svetoslav ILIEV >Priority: Major > Fix For: 1.6.2 > > > We observed expired certificates in Apache Rampart project. Keystores with > expired certificates are located in: > \modules\rampart-integration\src\test\resources\rahas\rahas-sts.jks > > and > \modules\rampart-integration\src\test\resources\rahas\sec.jks > Other Rampart versions might be also affected. > Could you please renew the expired certificates? > > Best Regards, > Svetoslav ILIEV -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5935) axis2 service did not work under jdk 11 class format
[ https://issues.apache.org/jira/browse/AXIS2-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669441#comment-16669441 ] Andreas Veithen commented on AXIS2-5935: We should probably rip that code out and replace it with ASM. That would imply an additional dependency, but at least we wouldn't have to maintain our own byte code reader. > axis2 service did not work under jdk 11 class format > > > Key: AXIS2-5935 > URL: https://issues.apache.org/jira/browse/AXIS2-5935 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.7.8 >Reporter: Kris Chung >Priority: Blocker > > jdk version: 11 > tomcat: 9.0.12 > os: centos 6 > axis2 version: 1.7.8 > 20:06:16.797 ERROR ServiceDeployer - The axis2 service, which is not valid, > caused The following error occurred during schema generation: Error looking > for paramter names in bytecode: unexpected bytes in file > org.apache.axis2.deployment.DeploymentException: The following error occurred > during schema generation: Error looking for paramter names in bytecode: > unexpected bytes in file > at > org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:117) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:232) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:154) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:149) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:585) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:164) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:136) > ~[axis2-kernel-1.7.8.jar:1.7.8] > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:289) > ~[axis2-kernel-1.7.8.jar:1.7.8] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5936) Soapenv namespace is not added implicitly or explicitly on Linux Tikanga
[ https://issues.apache.org/jira/browse/AXIS2-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657403#comment-16657403 ] Andreas Veithen commented on AXIS2-5936: Have you tried to update the JDK on Linux to a more recent version? > Soapenv namespace is not added implicitly or explicitly on Linux Tikanga > > > Key: AXIS2-5936 > URL: https://issues.apache.org/jira/browse/AXIS2-5936 > Project: Axis2 > Issue Type: Bug > Components: adb >Affects Versions: 1.6.4, 1.7.8 >Reporter: Muhammad Hamid >Priority: Major > > Tested with Linux (Red Hat Enterprise Linux Server release 5.11 (Tikanga)), > namespace for soapenv is not being added, tried to add it implicitly, doesn't > work. > The only workaround I was able to do to fix this is to use SOAP 11 envelope, > and add it's namespace, so seems like this error is specific to SOAP 12. > Java version in Linux: jdk1.8.0_92 > Java version in Windows: jdk1.8.0.161 > p.s in windows everything works fine, I don't have to specify envelope's > version, or namespace URI. > another p.s: this issue had been there since version 1.6.2, and I believe > it's OS specific, should try it on newer redhat OS. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5936) Soapenv namespace is not added implicitly or explicitly on Linux Tikanga
[ https://issues.apache.org/jira/browse/AXIS2-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657328#comment-16657328 ] Andreas Veithen commented on AXIS2-5936: I don't think this is related to the operating system the code is running on. Are you sure that both environments use the same JRE version? > Soapenv namespace is not added implicitly or explicitly on Linux Tikanga > > > Key: AXIS2-5936 > URL: https://issues.apache.org/jira/browse/AXIS2-5936 > Project: Axis2 > Issue Type: Bug > Components: adb >Affects Versions: 1.6.4, 1.7.8 >Reporter: Muhammad Hamid >Priority: Major > > Tested with Linux (Red Hat Enterprise Linux Server release 5.11 (Tikanga)), > namespace for soapenv is not being added, tried to add it implicitly, doesn't > work. > The only workaround I was able to do to fix this is to use SOAP 11 envelope, > and add it's namespace, so seems like this error is specific to SOAP 12. > p.s in windows everything works fine, I don't have to specify envelope's > version, or namespace URI. > another p.s: this issue had been there since version 1.6.2, and I believe > it's OS specific, should try it on newer redhat OS. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5518) adb-codegen: ADBBeanTemplate.xsl generates erroneous code resulting in javac error: 'else' without 'if'
[ https://issues.apache.org/jira/browse/AXIS2-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5518. Resolution: Incomplete > adb-codegen: ADBBeanTemplate.xsl generates erroneous code resulting in javac > error: 'else' without 'if' > --- > > Key: AXIS2-5518 > URL: https://issues.apache.org/jira/browse/AXIS2-5518 > Project: Axis2 > Issue Type: Bug > Components: adb >Affects Versions: 1.5.1 > Environment: Various Windows and Java 6 JDKs have produced this error >Reporter: William Walsh >Priority: Minor > > It appears that the code in ADBBeanTemplate.xsl at line 2837 generates the > beginning of a try block whose end and subsequent catch block, generated at > line 3552, fall after the else generated at line 2819. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5932) Axis2 behave differently in unix
[
https://issues.apache.org/jira/browse/AXIS2-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615382#comment-16615382
]
Andreas Veithen commented on AXIS2-5932:
I don't think this is related to the operating system the code is running on.
Are you sure that both environments use the same JRE version?
Also note that 1.6.4 is no longer supported. Please upgrade to the latest Axis2
version and confirm that the issue still exists.
> Axis2 behave differently in unix
>
>
> Key: AXIS2-5932
> URL: https://issues.apache.org/jira/browse/AXIS2-5932
> Project: Axis2
> Issue Type: Bug
>Affects Versions: 1.6.4
>Reporter: Muhammad Hamid
>Priority: Major
>
> I made a SOAP client using Axis2 adb, tested the web service inside eclipse,
> working fine, but, when I deployed it to unix servers in QA the request sent
> is different than the one created in windows:
> in Windows:
> {code:java}
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;>{code}
> in unix
> {code:java}
> {code}
> so I tried to explicitly add the namespace using:
> {code:java}
> env.declareNamespace("http://schemas.xmlsoap.org/soap/envelope/;,
> "soapenv");{code}
> but still, not added and I receive the following error
> javax.xml.stream.XMLStreamException: The namespace prefix "soapenv" was not
> declared.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5931) AxisFault: A message with content type application/xop+xml can only appear in a MIME multipart message
[ https://issues.apache.org/jira/browse/AXIS2-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615377#comment-16615377 ] Andreas Veithen commented on AXIS2-5931: Am I understanding this correctly: the server is actually returning a message that doesn't conform to SOAP or any related standard? > AxisFault: A message with content type application/xop+xml can only appear in > a MIME multipart message > -- > > Key: AXIS2-5931 > URL: https://issues.apache.org/jira/browse/AXIS2-5931 > Project: Axis2 > Issue Type: Improvement > Components: transports >Affects Versions: 1.7.8 >Reporter: Ralf Hauser >Priority: Major > > We are just about to upgrade our axis client from v1.6.2 to v1.7.8 ,but we get > > < can only appear in a MIME multipart message > at > org.apache.axis2.builder.MTOMBuilder.processDocument(MTOMBuilder.java:40) > at > org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:203) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:144) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:107) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:66) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:347)>> > > The third party server side is unchanged. > MTOM is not globally activated on the client-side, but we use > > options.setProperty( > org.apache.axis2.Constants.Configuration.ENABLE_MTOM, > org.apache.axis2.Constants.VALUE_TRUE); > With 2-1.6.2. this was always set. > > The server offers multiple stubs and even on stubs that do not need MTOM if > omit setting ENABLE_MTOM, this happens. > > Adding: > myConfigContext.getAxisConfiguration().addParameter(org.apache.axis2.Constants.Configuration.USE_DEFAULT_FALLBACK_BUILDER, > "true"); > > doesn't help either. > > Please document in > MTOMBuilder.processDocument(InputStream inputStream, String contentType, > MessageContext messageContext) throws AxisFault > that always throws this exception, how this can be avoided to ensure backward > compatibility > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5933) instrument RepositoryListener.findServicesInDirectory(File root) etc. with Debug statements
[
https://issues.apache.org/jira/browse/AXIS2-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615363#comment-16615363
]
Andreas Veithen commented on AXIS2-5933:
Maybe you can prepare a patch?
> instrument RepositoryListener.findServicesInDirectory(File root) etc. with
> Debug statements
> ---
>
> Key: AXIS2-5933
> URL: https://issues.apache.org/jira/browse/AXIS2-5933
> Project: Axis2
> Issue Type: Improvement
> Components: deployment
>Affects Versions: 1.7.8
> Environment: debian stretch
>Reporter: Ralf Hauser
>Priority: Major
>
> org.apache.axis2.deployment.RepositoryListener.findServicesInDirectory()
> appears to be crucial why my simple .aar in the standard services directory
> is not loaded
>
> Like AXIS2-5912 it happens when migrating from v1.6.2 and results in
> The service cannot be found for the endpoint reference
> .
> Putting
> org.apache.axis2=TRACE
> unfortunately only gives
> (ScriptModule.java:70) - script module activated
> (WarBasedAxisConfigurator.java:276) - loaded services from path:
> /usr/share/tomcat8/ws/WEB-INF
>
> Therefore I suggest that
> 1) findServicesInDirectory counts how many times "addFileToDeploy" is called
> and returns this int . Then line 276 could give a hint how many services were
> loaded
> 2) in the for (File file : files) { loop
> each file gets a debug trace with file.getAbsolutePath()
> 3) each "continue" or if-else where nothing happens gets a trace statement
> 4) same for "loadOtherDirectories"
> 5)
> [DeploymentEngine|eclipse-javadoc:%E2%98%82=%20/%3C%7BDeploymentEngine.java%E2%98%83DeploymentEngine]{color:#00}.doDeploy(){color}
> should also get a few trace statements (e.g. wsToDeploy.size())
> 6)
> [ServiceDeployer|eclipse-javadoc:%E2%98%82=%20/%3C%7BServiceDeployer.java%E2%98%83ServiceDeployer]{color:#00}.deploy({color})
> urgently needs some trace statements
> etc.
>
> I run the service in a lab environments where the services are found, in
> "integration" unfortunately not
> In both environments the modules load perfectly
> "axisConfiguration.getModules()" :
> Module 0: jaxws-1.7.8
>
> INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 1:
> ping-1.7.8
>
> INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 2:
> metadataExchange-1.7.8
>
> INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 3:
> addressing-1.7.8
>
> INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 4:
> mtompolicy-1.7.8
>
> INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 5:
> soapmonitor-1.7.8
>
> INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 6:
> script-1.7.8
>
> INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 7:
> MyWebServiceModule
> axisConfiguration.getServices() and axisConfiguration.getFaultyServices() are
> unfortunately empty.
> It would be interesting to see the "deploymentFileDataMap" field of
> WarBasedAxisConfigurator
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5930) CVE issues with dependency jars of axis2
[ https://issues.apache.org/jira/browse/AXIS2-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608194#comment-16608194 ] Andreas Veithen commented on AXIS2-5930: Yes (as indicated by the "Fix Version" field of this ticket). > CVE issues with dependency jars of axis2 > > > Key: AXIS2-5930 > URL: https://issues.apache.org/jira/browse/AXIS2-5930 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.8 >Reporter: tanishq pruthi >Priority: Major > Fix For: 1.7.9 > > > The dependent jars in axis 2 package are not updated to latest version > Due to which, some of the jars contains vulnerabilities . Some of them are > below > [mex-1.7.6-impl.jar|#l203_99ee5f563d035e3904894ea89c4550bb71ddf34b] > [axis2-kernel-1.7.6.jar|#l245_aa2e05c5dc080f7089072d17acfb9b1a50d8bda9] > [tribes-6.0.16.jar|#l321_50b300ff415ef0cf3af4f14ec03131cdcb019efa] > Dependency check tool is giving the following CVE in these jar > *[CVE-2012-5351|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-5351]* > *[CVE-2012-4418|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-4418]* > ** -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5930) CVE issues with dependency jars of axis2
[ https://issues.apache.org/jira/browse/AXIS2-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5930. Resolution: Fixed Fix Version/s: 1.7.9 > CVE issues with dependency jars of axis2 > > > Key: AXIS2-5930 > URL: https://issues.apache.org/jira/browse/AXIS2-5930 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.8 >Reporter: tanishq pruthi >Priority: Major > Fix For: 1.7.9 > > > The dependent jars in axis 2 package are not updated to latest version > Due to which, some of the jars contains vulnerabilities . Some of them are > below > [mex-1.7.6-impl.jar|#l203_99ee5f563d035e3904894ea89c4550bb71ddf34b] > [axis2-kernel-1.7.6.jar|#l245_aa2e05c5dc080f7089072d17acfb9b1a50d8bda9] > [tribes-6.0.16.jar|#l321_50b300ff415ef0cf3af4f14ec03131cdcb019efa] > Dependency check tool is giving the following CVE in these jar > *[CVE-2012-5351|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-5351]* > *[CVE-2012-4418|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-4418]* > ** -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5930) CVE issues with dependency jars of axis2
[ https://issues.apache.org/jira/browse/AXIS2-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599624#comment-16599624 ] Andreas Veithen commented on AXIS2-5930: CVE-2012-5351 and CVE-2012-4418 are related to SAML which would affect Rampart, not Axis2 itself. Probably the tool incorrectly links them to mex and axis2-kernel. Regarding the Tribes vulnerability, that dependency was updated in r1837509. > CVE issues with dependency jars of axis2 > > > Key: AXIS2-5930 > URL: https://issues.apache.org/jira/browse/AXIS2-5930 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.8 >Reporter: tanishq pruthi >Priority: Major > Fix For: 1.7.9 > > > The dependent jars in axis 2 package are not updated to latest version > Due to which, some of the jars contains vulnerabilities . Some of them are > below > [mex-1.7.6-impl.jar|#l203_99ee5f563d035e3904894ea89c4550bb71ddf34b] > [axis2-kernel-1.7.6.jar|#l245_aa2e05c5dc080f7089072d17acfb9b1a50d8bda9] > [tribes-6.0.16.jar|#l321_50b300ff415ef0cf3af4f14ec03131cdcb019efa] > Dependency check tool is giving the following CVE in these jar > *[CVE-2012-5351|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-5351]* > *[CVE-2012-4418|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-4418]* > ** -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5665) Wsdl2java is not creating class files properly
[ https://issues.apache.org/jira/browse/AXIS2-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5665. Resolution: Incomplete > Wsdl2java is not creating class files properly > -- > > Key: AXIS2-5665 > URL: https://issues.apache.org/jira/browse/AXIS2-5665 > Project: Axis2 > Issue Type: Bug > Components: jaxws, wsdl >Affects Versions: 1.2, 1.3, 1.6.0, 1.6.2 > Environment: Solaris, Bea Weblogic Server 10, >Reporter: Ankur Khetan >Priority: Critical > > Hello Support Team, > We are facing an issue from the generating classes using below wsdl2java > command. > WSDL2Java -uri FrontDesk.wsdl -ns2p > urn:fiber.abc.com:crm:frontdesk:v0=com.abc.fiber.portal.stub.co,urn:fiber.abc.com:crm:frontdesk:data:v0=com.abc.fiber.portal.stub.co.data > -d jaxbri –s > In our WSDL we have more then one operation having same request type object. > The generated Stub class have created only one toEnvelope and toOM method for > all those operations those have same request Object. Which leads to call only > one operation even if we are triggering different operation from our java > code. > Regards, > Ankur Khetan -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5805) Axis2 InterfaceImplementation generated with jaxbri binding does not compile.
[
https://issues.apache.org/jira/browse/AXIS2-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5805.
Resolution: Duplicate
> Axis2 InterfaceImplementation generated with jaxbri binding does not compile.
> -
>
> Key: AXIS2-5805
> URL: https://issues.apache.org/jira/browse/AXIS2-5805
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.3
>Reporter: Jayesh Nageshkar
>Priority: Major
> Attachments: DocumentManagementService.wsdl
>
>
> jaxbri generates binding containing toOM method with 3 parameters as follows:
> private org.apache.axiom.om.OMElement toOM(
> com.comcast.xml.commercialdocumentmanagement.services.GetFileByName
> param,
> boolean optimizeContent, javax.xml.namespace.QName elementQName)
> throws org.apache.axis2.AxisFault {
> However InterfaceImplementation generates method invocation with 2 parameters
> as follows:
> org.apache.axiom.om.OMElement omElementrequestHeader = toOM(requestHeader,
> optimizeContent(
> new javax.xml.namespace.QName(
>
> "http://xml.comcast.com/commercialdocumentmanagement/services;,
> "getFileByName")));
> The result is InterfaceImplementation does not compile when we try to build
> client jar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5919) WSDL2Java not working properly when using jaxbri and WSDL with faults
[
https://issues.apache.org/jira/browse/AXIS2-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5919.
Resolution: Fixed
Assignee: Andreas Veithen
Fix Version/s: 1.8.0
> WSDL2Java not working properly when using jaxbri and WSDL with faults
> -
>
> Key: AXIS2-5919
> URL: https://issues.apache.org/jira/browse/AXIS2-5919
> Project: Axis2
> Issue Type: Bug
> Components: codegen, databinding
>Affects Versions: 1.7.7, 1.7.8
>Reporter: Edi Obradovic
>Assignee: Andreas Veithen
>Priority: Major
> Labels: codegen, jaxbri, wsdl2java
> Fix For: 1.8.0
>
>
> We are currently unable to use newer version of Axis2 (1.7.7) because the
> Java classes generated by axis2-codegen and axis2-jaxbri have missing
> parameter errors.
> When you generate Java classes from WSDL that contains faults you get errors
> in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
> QName) in the type is not applicable for the arguments
> (TestFaultStruct, boolean)". The reason you get that is because the QName
> parameter is missing when calling toOM in faults.
> *The error happens because:*
> - all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
> (axis2-jaxbri) and they all have QName parameter defined
> - all custom faults code is generated using MessageReceiverTemplate.xsl
> (axis2-codegen) and if you look at the xsl code you can see that QName
> parameter is not there:
> {code:xml}
>
> } catch ( select="@name"/> e) {
>
> msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME," select="@localname"/>");
> org.apache.axis2.AxisFault f = createAxisFault(e);
> if (e.getFaultMessage() != null){
> f.setDetail(toOM(e.getFaultMessage(),false));
> }
> throw f;
> }
>
> {code}
>
> *How to reproduce:*
> - Download and extract axis2-1.7.7
> - Execute WSDL2Java:
> {code:java}
> java -Dfile.encoding=UTF-8 -Djavax.xml.accessExternalSchema=all -classpath
> "c:\DevStudio\axis2-1.7.7\lib\*;" org.apache.axis2.wsdl.WSDL2Java -uri
> "c:\DevStudio\axis2-1.7.7\samples\faulthandling\bank.wsdl" -o "%CD%\GEN" -d
> jaxbri -ss -g -or -p com.company.generated
> {code}
> - Compile code (eclipse/ant ...)
> {code:java}
> Buildfile: C:\TEMP\Test\GEN\build.xml
> init:
> [mkdir] Created dir: C:\TEMP\Test\GEN\build
> [mkdir] Created dir: C:\TEMP\Test\GEN\build\classes
> [mkdir] Created dir: C:\TEMP\Test\GEN\build\lib
> pre.compile.test:
> [echo] JAX-B RI Availability = true
> [echo] Stax Availability= true
> [echo] Axis2 Availability= true
> compile.src:
> [javac] C:\TEMP\Test\GEN\build.xml:47: warning: 'includeantruntime' was
> not set, defaulting to build.sysclasspat
> h=last; set to false for repeatable builds
> [javac] Compiling 12 source files to C:\TEMP\Test\GEN\build\classes
> [javac]
> C:\TEMP\Test\GEN\src\com\company\generated\BankServiceMessageReceiverInOut.java:89:
> error: no suitable m
> ethod found for toOM(AccountNotExistFault,boolean)
> [javac] f.setDetail(toOM(e.getFaultMessage(), false));
> [javac] ^
> [javac] method
> BankServiceMessageReceiverInOut.toOM(InsufficientFundFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(AccountNotExistFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(WithdrawResponse,boolean,QName) is not
> applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(Withdraw,boolean,QName) is not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac]
> C:\TEMP\Test\GEN\src\com\company\generated\BankServiceMessageReceiverInOut.java:100:
> error: no suitable
> method found for toOM(InsufficientFundFault,boolean)
> [javac] f.setDetail(toOM(e.getFaultMessage(), false));
> [javac] ^
> [javac] method
> BankServiceMessageReceiverInOut.toOM(InsufficientFundFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(AccountNotExistFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
>
[jira] [Updated] (AXIS2-5919) WSDL2Java not working properly when using jaxbri and WSDL with faults
[
https://issues.apache.org/jira/browse/AXIS2-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5919:
---
Priority: Major (was: Blocker)
> WSDL2Java not working properly when using jaxbri and WSDL with faults
> -
>
> Key: AXIS2-5919
> URL: https://issues.apache.org/jira/browse/AXIS2-5919
> Project: Axis2
> Issue Type: Bug
> Components: codegen, databinding
>Affects Versions: 1.7.7, 1.7.8
>Reporter: Edi Obradovic
>Priority: Major
> Labels: codegen, jaxbri, wsdl2java
> Fix For: 1.8.0
>
>
> We are currently unable to use newer version of Axis2 (1.7.7) because the
> Java classes generated by axis2-codegen and axis2-jaxbri have missing
> parameter errors.
> When you generate Java classes from WSDL that contains faults you get errors
> in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
> QName) in the type is not applicable for the arguments
> (TestFaultStruct, boolean)". The reason you get that is because the QName
> parameter is missing when calling toOM in faults.
> *The error happens because:*
> - all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
> (axis2-jaxbri) and they all have QName parameter defined
> - all custom faults code is generated using MessageReceiverTemplate.xsl
> (axis2-codegen) and if you look at the xsl code you can see that QName
> parameter is not there:
> {code:xml}
>
> } catch ( select="@name"/> e) {
>
> msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME," select="@localname"/>");
> org.apache.axis2.AxisFault f = createAxisFault(e);
> if (e.getFaultMessage() != null){
> f.setDetail(toOM(e.getFaultMessage(),false));
> }
> throw f;
> }
>
> {code}
>
> *How to reproduce:*
> - Download and extract axis2-1.7.7
> - Execute WSDL2Java:
> {code:java}
> java -Dfile.encoding=UTF-8 -Djavax.xml.accessExternalSchema=all -classpath
> "c:\DevStudio\axis2-1.7.7\lib\*;" org.apache.axis2.wsdl.WSDL2Java -uri
> "c:\DevStudio\axis2-1.7.7\samples\faulthandling\bank.wsdl" -o "%CD%\GEN" -d
> jaxbri -ss -g -or -p com.company.generated
> {code}
> - Compile code (eclipse/ant ...)
> {code:java}
> Buildfile: C:\TEMP\Test\GEN\build.xml
> init:
> [mkdir] Created dir: C:\TEMP\Test\GEN\build
> [mkdir] Created dir: C:\TEMP\Test\GEN\build\classes
> [mkdir] Created dir: C:\TEMP\Test\GEN\build\lib
> pre.compile.test:
> [echo] JAX-B RI Availability = true
> [echo] Stax Availability= true
> [echo] Axis2 Availability= true
> compile.src:
> [javac] C:\TEMP\Test\GEN\build.xml:47: warning: 'includeantruntime' was
> not set, defaulting to build.sysclasspat
> h=last; set to false for repeatable builds
> [javac] Compiling 12 source files to C:\TEMP\Test\GEN\build\classes
> [javac]
> C:\TEMP\Test\GEN\src\com\company\generated\BankServiceMessageReceiverInOut.java:89:
> error: no suitable m
> ethod found for toOM(AccountNotExistFault,boolean)
> [javac] f.setDetail(toOM(e.getFaultMessage(), false));
> [javac] ^
> [javac] method
> BankServiceMessageReceiverInOut.toOM(InsufficientFundFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(AccountNotExistFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(WithdrawResponse,boolean,QName) is not
> applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(Withdraw,boolean,QName) is not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac]
> C:\TEMP\Test\GEN\src\com\company\generated\BankServiceMessageReceiverInOut.java:100:
> error: no suitable
> method found for toOM(InsufficientFundFault,boolean)
> [javac] f.setDetail(toOM(e.getFaultMessage(), false));
> [javac] ^
> [javac] method
> BankServiceMessageReceiverInOut.toOM(InsufficientFundFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(AccountNotExistFault,boolean,QName) is
> not applicable
> [javac] (actual and formal argument lists differ in length)
> [javac] method
> BankServiceMessageReceiverInOut.toOM(WithdrawResponse,boolean,QName) is not
> applicable
> [javac] (actual
[jira] [Commented] (AXIS2-5928) cite the values when hitting "Transport level information does not match with SOAP Message namespace URI"
[ https://issues.apache.org/jira/browse/AXIS2-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584805#comment-16584805 ] Andreas Veithen commented on AXIS2-5928: Can you prepare a patch? > cite the values when hitting "Transport level information does not match with > SOAP Message namespace URI" > - > > Key: AXIS2-5928 > URL: https://issues.apache.org/jira/browse/AXIS2-5928 > Project: Axis2 > Issue Type: Improvement >Affects Versions: 1.6.2 >Reporter: Ralf Hauser >Priority: Major > > When running into this exception, in BuilderUtil.validateSOAPVersion() please > cite the offending values - in my case they were > > soapNamespaceURIFromTransport: [http://www.w3.org/2003/05/soap-envelope] > vs. > envelope.getNamespace().getNamespaceURI(): > http://schemas.xmlsoap.org/soap/envelope/ > > currently, I see only > SOAPProcessingException: Transport level information does not > match with SOAP Message namespace URI > at > org.apache.axis2.builder.BuilderUtil.validateSOAPVersion(BuilderUtil.java:772) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5929) REST Services URL GET json request not working
[
https://issues.apache.org/jira/browse/AXIS2-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584800#comment-16584800
]
Andreas Veithen commented on AXIS2-5929:
{{getRequestURI}} would return
{{/opencdefhirserver/services/FHIR/Binary/4295642378}}, but that doesn't look
like JSON, right?
> REST Services URL GET json request not working
> --
>
> Key: AXIS2-5929
> URL: https://issues.apache.org/jira/browse/AXIS2-5929
> Project: Axis2
> Issue Type: Improvement
> Components: json
>Affects Versions: 1.7.8
>Reporter: Marti Pamies Sola
>Priority: Minor
> Attachments: AbstractJSONOMBuilder.java,
> AbstractJSONOMBuilder.java.patch
>
>
> At a REST services, I do not receive HTTP GET requests when content-type is
> json, and parameters are at request URL path (not as Query string). Let me
> explain in detail:
> I am implementing a REST services according to [HL7
> FHIR|[http://www.hl7.org/fhir/],] that must be able to return content both on
> xml and json (depending on http header content-type), once an HTTP GET
> request is received. Keys for the information to be returned can be provided
> both directly at the request URL path or as a Query String:
> * Keys at URL path:
> {color:#505050}[http://localhost:8080/opencdefhirserver/services/FHIR/Binary/4295642378]{color}
> * Keys as Query string:
> {color:#505050}[http://localhost:8080/opencdefhirserver/services/FHIR/Binary?id4295642378|http://localhost:8080/opencdefhirserver/services/FHIR/Binary/4295642378]{color}
> Where, FHIR is my service; Binary is the axis2 operation to be executed
> (mapping to a FHIR resource); and {color:#505050}4295642378{color} the
> resource id.
> Providing keys as Query String work properly with xml and json, but providing
> key at URL path just work with xml, on json I get the following exception:
> "_No JSON message received through HTTP GET or POST"_
> I've been reviewing source code and I guess the issue comes form this
> fragment of code at AbstractJSONOMBuilder.java line 85:
>
> {code:java}
> // if ((index = requestURL.indexOf("=")) > 0) {
> jsonString = requestURL.substring(index + 1);
> reader = new StringReader(jsonString);
> } else {
> throw new AxisFault("No JSON message received through HTTP
> GET or POST");
> }
> {code}
> As it only accepts parameters as Query String, and when not provided it raise
> an exception.
> I propose the following modification, where if not Query String is provided,
> it considers full request URL as input json.
> {code:java}
> // if ((index = requestURL.indexOf("=")) > 0) {
> jsonString = requestURL.substring(index + 1);
> reader = new StringReader(jsonString);
> } else {
> /*
> * MARTI PAMIES SOLA
> * Get JSON message from request URI if not present as
> parameter.
> * To be able to response to full URL requests
> */
> HttpServletRequest httpServeltRqst
> =(HttpServletRequest)messageContext.getProperty("transport.http.servletRequest");
> String requestParam=httpServeltRqst.getRequestURI();
> if (!(requestParam.equals(""))) {
> jsonString = requestParam;
> reader = new StringReader(jsonString);
> }else {
> throw new AxisFault("No JSON message received through
> HTTP GET or POST");
> }
> }
> {code}
> I've test locally and it work for me, so I propose to include modification at
> next release. Attached is the new AbstractJSONOMBuilder.java file and also
> the svn patch.
> Hope useful.
> Thanks,
> Martí
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5518) adb-codegen: ADBBeanTemplate.xsl generates erroneous code resulting in javac error: 'else' without 'if'
[ https://issues.apache.org/jira/browse/AXIS2-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16570865#comment-16570865 ] Andreas Veithen commented on AXIS2-5518: Can you test if that issue still exists in Axis2 1.7.8? > adb-codegen: ADBBeanTemplate.xsl generates erroneous code resulting in javac > error: 'else' without 'if' > --- > > Key: AXIS2-5518 > URL: https://issues.apache.org/jira/browse/AXIS2-5518 > Project: Axis2 > Issue Type: Bug > Components: adb >Affects Versions: 1.5.1 > Environment: Various Windows and Java 6 JDKs have produced this error >Reporter: William Walsh >Priority: Minor > > It appears that the code in ADBBeanTemplate.xsl at line 2837 generates the > beginning of a try block whose end and subsequent catch block, generated at > line 3552, fall after the else generated at line 2819. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5923) Broken build in JDK1.8u172
[
https://issues.apache.org/jira/browse/AXIS2-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5923.
Resolution: Fixed
Fix Version/s: 1.7.9
> Broken build in JDK1.8u172
> --
>
> Key: AXIS2-5923
> URL: https://issues.apache.org/jira/browse/AXIS2-5923
> Project: Axis2
> Issue Type: Bug
>Reporter: Edgar Molina
>Priority: Minor
> Fix For: 1.7.9
>
>
> h1. Background
> The 1st of April 2018, Namibia changed their time zone and they don't observe
> DST anymore, they changed from _Western African Time (WAST)_ to _Central
> African Time (CAST)_, this change was rolled out in JDK 1.8u161 (Search for
> tzdata2017c
> [here|http://www.oracle.com/technetwork/java/javase/tzdata-versions-138805.html],
> and check the database in
> [wikipedia|https://en.wikipedia.org/wiki/List_of_tz_database_time_zones]).
> The Axis2 code in the ConverterUtil
> (java/org/apache/axis2/databinding/utils/ConverterUtil.java) creates a
> Calendar object which is historically aware (returns the date offsets for the
> date that is being set, in other words returns that in Feb 2007, Namibia had
> DST), then pulls the raw offset from the time zone, which returns the current
> offset (no DST) and then sets it to the calendar again.
> This discrepancy causes that the calendar is off by one hour this time of the
> year:
> {noformat}
> setting time zone to Africa/Windhoek
> testing with TimeZone Central African Time
> uses daylight time: false
> we are in daylight time: false
> testValue ==> 2007-02-15T14:54:29
> calendar ==> 2007-02-15T13:54:29+02:00 < HERE
> back ==> 2007-02-15T14:54:29.000+03:00{noformat}
> h1. Proposed Design
> We can default the test date time zone to GMT+1 as WAST used to be or to a
> different country in this TZ. It seems that this test is very outdated as
> Namibia hasn't been GMT+1 for a while and currently there is no GMT+1 that
> observes DST in the southern hemisphere.
> Therefore:
> # Update the offending test to switch from "Africa/Windhoek" to
> "Africa/Tunis" (capital of Tunisia) to fix the broken build.
> # Or refactor the ConverterUtil so it doesn't overwrites the TZ offset (this
> might be sensitive to specific JVM implementations).
> {panel:title=Build Execution}
> {noformat}
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.axis2.databinding.utils.BeanUtilTest
> [INFO] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.418
> s - in org.apache.axis2.databinding.utils.BeanUtilTest
> [INFO] Running org.apache.axis2.databinding.utils.ConverterUtilTest
> [ERROR] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 0.204 s <<< FAILURE! - in org.apache.axis2.databinding.utils.ConverterUtilTest
> [ERROR]
> testConvertToDateTime(org.apache.axis2.databinding.utils.ConverterUtilTest)
> Time elapsed: 0.027 s <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<2007-02-15T1[4]:54:29> but
> was:<2007-02-15T1[3]:54:29>
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
> at junit.framework.TestCase.assertEquals(TestCase.java:269)
> at
> org.apache.axis2.databinding.utils.ConverterUtilTest.internalTestConvertToDateTime(ConverterUtilTest.java:385)
> at
> org.apache.axis2.databinding.utils.ConverterUtilTest.testConvertToDateTime(ConverterUtilTest.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
>
[jira] [Resolved] (AXIS2-5922) the org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference
[ https://issues.apache.org/jira/browse/AXIS2-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5922. Resolution: Not A Problem > the org.apache.axis2.AxisFault: The service cannot be found for the endpoint > reference > --- > > Key: AXIS2-5922 > URL: https://issues.apache.org/jira/browse/AXIS2-5922 > Project: Axis2 > Issue Type: Bug > Environment: solaris >Reporter: Ramesh Chandra >Priority: Major > > the past few months one of our web services that was created using axis > framework randomly throws the below error-, I spent hrs in the internet but > no luck > > org.apache.axis2.AxisFault: The service cannot be found for the endpoint > reference -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5922) the org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference
[ https://issues.apache.org/jira/browse/AXIS2-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544595#comment-16544595 ] Andreas Veithen commented on AXIS2-5922: Please refer to [https://axis.apache.org/axis2/java/core/docs/app_server.html] for instructions about how to run Axis2 in WebSphere Application Server. > the org.apache.axis2.AxisFault: The service cannot be found for the endpoint > reference > --- > > Key: AXIS2-5922 > URL: https://issues.apache.org/jira/browse/AXIS2-5922 > Project: Axis2 > Issue Type: Bug > Environment: solaris >Reporter: Ramesh Chandra >Priority: Major > > the past few months one of our web services that was created using axis > framework randomly throws the below error-, I spent hrs in the internet but > no luck > > org.apache.axis2.AxisFault: The service cannot be found for the endpoint > reference -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-4833) Modules not getting loaded from classpath in Oracle WebLogic 10.x
[
https://issues.apache.org/jira/browse/AXIS2-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-4833.
Resolution: Fixed
Fix Version/s: 1.7.9
> Modules not getting loaded from classpath in Oracle WebLogic 10.x
> -
>
> Key: AXIS2-4833
> URL: https://issues.apache.org/jira/browse/AXIS2-4833
> Project: Axis2
> Issue Type: Bug
> Components: deployment
>Affects Versions: 1.5.1, 1.6.2
> Environment: JDK 1.6.0_14, Oracle WebLogic Application Server 10.3,
> Solaris SunOS 5.10
>Reporter: Joerg
>Priority: Major
> Fix For: 1.7.9
>
> Attachments: AXIS2-4833.patch, bug_4833_pic1.jpg, bug_4833_pic2.jpg
>
>
> I've tried to loading the logging-module from the classpath which did not
> work on a BEA Weblogic 10.3 (causing a NullPointerException in
> RepositoryListener, Method loadClassPathModules().
> The problem is similar to AXIS2-4258 (Fix for the WebSphere AppServer)
> because the BEA container uses a different protocol, too.
> In my case the logging module (named axis2-log-module.jar) is included within
> EAR-File and the returned URL from the ClassLoader to this resource is:
> zip:/projects/projectname/weblogic10.3/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/_appsdir_AppName_ear/jpclyk/axis2-log-module.jar!/META-INF/module.xml
> I'm not sure if this might be a problem of the BEA ClassLoader
> (weblogic.utils.classloader.ChangeAwareClassloader) but the returned Scheme
> is null, which causes a NullPointerException when checking the scheme is not
> "file".
> Code line 137: if (!moduleURI.getScheme().equals("file")).
> Regards,
> Joerg
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5924) getting timeout error to AXIS2 in websphere application server
[ https://issues.apache.org/jira/browse/AXIS2-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544179#comment-16544179 ] Andreas Veithen commented on AXIS2-5924: What version of Axis2 are you using? > getting timeout error to AXIS2 in websphere application server > -- > > Key: AXIS2-5924 > URL: https://issues.apache.org/jira/browse/AXIS2-5924 > Project: Axis2 > Issue Type: Bug > Components: jaxws, JMS transport >Reporter: Sudarshana >Priority: Major > > Hello, > we are getting timeout error in IBM SPSS CNDS which deployed in IBM Websphere > Applications server which uses AXIS2. > ERROR [JobExecutionWSClient] Exception occurred in the method > queryExecutions() > 00e4 SOAPOverHTTPS E WSWS7263E: The following exception occured: > java.net.SocketTimeoutException: Async operation timed out > 00fc AxisEngine E org.apache.axis2.engine.AxisEngine receive An error > was detected during JAXWS processing > IBM PMR team suggested to contact AXIS2 support to change timeout value. > Solution is much appreciate. > Thanks > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5915) java.lang.ArrayIndexOutOfBoundsException while doing load testing
[ https://issues.apache.org/jira/browse/AXIS2-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5915. Resolution: Cannot Reproduce Version 1.5.2 is no longer supported. I remember fixing various issues in the StAX parser support in Axiom that may cause this type of error. Please migrate to a recent Axis2 release and reopen the issue if you can still reproduce it. > java.lang.ArrayIndexOutOfBoundsException while doing load testing > - > > Key: AXIS2-5915 > URL: https://issues.apache.org/jira/browse/AXIS2-5915 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.5.2 >Reporter: manojkumar >Priority: Critical > > we have developed one soap webservice using Axis2 1.5.2 version. In this > service when multiple requests are processing at a time then a few requests > receiving below exception. > out of 1 cases around 30 cases are fail, in response we are getting below > error. > > ERROR *[org.apache.axis2.transport.http.AxisServlet] (default task-59) null: > java.lang.ArrayIndexOutOfBoundsException* > at > com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInputStream.read(XMLEntityManager.java:2973) > at > com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:335) > at > com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1756) > at > com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.arrangeCapacity(XMLEntityScanner.java:1633) > at > com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipString(XMLEntityScanner.java:1698) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$XMLDeclDriver.next(XMLDocumentScannerImpl.java:809). > > so i wan to know is there any specific reason in it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5916) java.io.IOException: CRLF expected at end of chunk: 62/60
[ https://issues.apache.org/jira/browse/AXIS2-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5916. Resolution: Incomplete There is no useful information in this bug report, apart from the fact that "CRLF expected at end of chunk" is an error message that may be produced by Apache HttpCore (which makes it likely that it's a bug in the peer). > java.io.IOException: CRLF expected at end of chunk: 62/60 > - > > Key: AXIS2-5916 > URL: https://issues.apache.org/jira/browse/AXIS2-5916 > Project: Axis2 > Issue Type: Bug > Environment: Websphere server >Reporter: Suhas SP >Priority: Major > > org.apache.axis2.AxisFault: CRLF expected at end of chunk: 62/60 > Caused by: java.io.IOException: CRLF expected at end of chunk: 62/60 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5914) httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability HTTPCLIENT-1803
[ https://issues.apache.org/jira/browse/AXIS2-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481678#comment-16481678 ] Andreas Veithen commented on AXIS2-5914: I'm working on it. > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > --- > > Key: AXIS2-5914 > URL: https://issues.apache.org/jira/browse/AXIS2-5914 > Project: Axis2 > Issue Type: Bug > Components: transports >Affects Versions: 1.7.7 >Reporter: Milko Todorov >Priority: Major > Labels: security > Fix For: 1.7.8 > > > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > According to the link above the issue is fixed with version 4.5.3. The > version used need to be adjusted in pom.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5914) httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability HTTPCLIENT-1803
[ https://issues.apache.org/jira/browse/AXIS2-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5914. Resolution: Fixed > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > --- > > Key: AXIS2-5914 > URL: https://issues.apache.org/jira/browse/AXIS2-5914 > Project: Axis2 > Issue Type: Bug > Components: transports >Affects Versions: 1.7.7 >Reporter: Milko Todorov >Priority: Major > Labels: security > Fix For: 1.7.8 > > > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > According to the link above the issue is fixed with version 4.5.3. The > version used need to be adjusted in pom.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5913) commons-httpclient-3.1 bundled in axis2-1.7.7 is exposed to vulnerability CVE-2012-5783
[ https://issues.apache.org/jira/browse/AXIS2-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5913. Resolution: Won't Do This is not fixable since commons-httpclient is no longer maintained. As indicated in the 1.7.0 release notes, it's possible to switch to HttpClient 4.x to avoid security problems. > commons-httpclient-3.1 bundled in axis2-1.7.7 is exposed to vulnerability > CVE-2012-5783 > --- > > Key: AXIS2-5913 > URL: https://issues.apache.org/jira/browse/AXIS2-5913 > Project: Axis2 > Issue Type: Bug > Components: transports >Affects Versions: 1.7.7 >Reporter: Milko Todorov >Priority: Blocker > Labels: security > > commons-httpclient-3.1 bundled in axis2-1.7.7 is exposed to vulnerability > [CVE-2012-5783|https://nvd.nist.gov/vuln/detail/CVE-2012-5783] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5914) httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability HTTPCLIENT-1803
[ https://issues.apache.org/jira/browse/AXIS2-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5914. Resolution: Fixed Fix Version/s: 1.7.8 > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > --- > > Key: AXIS2-5914 > URL: https://issues.apache.org/jira/browse/AXIS2-5914 > Project: Axis2 > Issue Type: Bug > Components: transports >Affects Versions: 1.7.7 >Reporter: Milko Todorov >Priority: Major > Labels: security > Fix For: 1.7.8 > > > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > According to the link above the issue is fixed with version 4.5.3. The > version used need to be adjusted in pom.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5914) httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability HTTPCLIENT-1803
[ https://issues.apache.org/jira/browse/AXIS2-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5914: --- Priority: Major (was: Blocker) > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > --- > > Key: AXIS2-5914 > URL: https://issues.apache.org/jira/browse/AXIS2-5914 > Project: Axis2 > Issue Type: Bug > Components: transports >Affects Versions: 1.7.7 >Reporter: Milko Todorov >Priority: Major > Labels: security > > httpclient-4.5.2 bundled in axis2-1.7.7 is exposed to vulnerability > HTTPCLIENT-1803 > According to the link above the issue is fixed with version 4.5.3. The > version used need to be adjusted in pom.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5911) Update Axis2 FAQ to include production hardening tips
[ https://issues.apache.org/jira/browse/AXIS2-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405577#comment-16405577 ] Andreas Veithen commented on AXIS2-5911: I don't understand. The error messages basically mean that the Veracode thing is too dumb to properly compile the JSPs. The only known problem is the weak default password. If we remove that and instead use container security, then it would be disabled by default. > Update Axis2 FAQ to include production hardening tips > - > > Key: AXIS2-5911 > URL: https://issues.apache.org/jira/browse/AXIS2-5911 > Project: Axis2 > Issue Type: Improvement >Reporter: robert lazarski >Assignee: robert lazarski >Priority: Major > > The axis2 mailing list is getting frequent requests for help, regarding 3rd > party penetration testing tool reports. Jira issues are also getting created. > A lot of these reports are in the localhost:8080/axis2/axis2-web section for > example. Its not mandatory to run HappyAxis.jsp in prod - arguably we should > discourage it. There are "enumeration" vulnerabilities and info leakage > issues in the axis2-web section.This whole axis2-web section is disabled in > my day job, for example. > axis2-admin is another area that will perhaps be off by default in an > upcoming release, since the current implementation uses weak passwords, see > AXIS2-5910. > 500 Exceptions are easy to create with Axis2 since it requires specific > parameters in the payload, therefore penetration testing will likely cause > them. Customized error handling via the web.xml could be recommended in the > FAQ. > Any thoughts, comments or concerns [~veithen] ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5911) Update Axis2 FAQ to include production hardening tips
[ https://issues.apache.org/jira/browse/AXIS2-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401148#comment-16401148 ] Andreas Veithen commented on AXIS2-5911: I would actually be tempted to completely remove HappyAxis.jsp. As for the weak password, an option would be to let the admin console use the standard security features provided by the servlet container. > Update Axis2 FAQ to include production hardening tips > - > > Key: AXIS2-5911 > URL: https://issues.apache.org/jira/browse/AXIS2-5911 > Project: Axis2 > Issue Type: Improvement >Reporter: robert lazarski >Assignee: robert lazarski >Priority: Major > > The axis2 mailing list is getting frequent requests for help, regarding 3rd > party penetration testing tool reports. Jira issues are also getting created. > A lot of these reports are in the localhost:8080/axis2/axis2-web section for > example. Its not mandatory to run HappyAxis.jsp in prod - arguably we should > discourage it. There are "enumeration" vulnerabilities and info leakage > issues in the axis2-web section.This whole axis2-web section is disabled in > my day job, for example. > axis2-admin is another area that will perhaps be off by default in an > upcoming release, since the current implementation uses weak passwords, see > AXIS2-5910. > 500 Exceptions are easy to create with Axis2 since it requires specific > parameters in the payload, therefore penetration testing will likely cause > them. Customized error handling via the web.xml could be recommended in the > FAQ. > Any thoughts, comments or concerns [~veithen] ? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (TRANSPORTS-57) Appel WebService SOAP RPGLE gelé
[ https://issues.apache.org/jira/browse/TRANSPORTS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved TRANSPORTS-57. --- Resolution: Invalid > Appel WebService SOAP RPGLE gelé > > > Key: TRANSPORTS-57 > URL: https://issues.apache.org/jira/browse/TRANSPORTS-57 > Project: Axis2 Transports > Issue Type: Bug > Environment: Le serveur Apache AXIS2 tourne sur un IBM i > (anciennement AS400). > Le client est un programme RPGLE qui utilise un STUB RPGLE créer à partir > d'un WSDL. > Le serveur distant hébergeant le WS est un serveur IIS. > La ligne internet entre le client et le serveur distant peut être dégradé et > parfois subir des coupures momentanées. >Reporter: SDOUGA Mehdi >Priority: Major > > Bonjour, > J'ai un soucis lorsque j'utilise Apache AXIS pour appeller des WS à partir de > STUB, ces derniers restent parfois figé en attente de réception de données. > Ce blocage est rare (environ 5% des appels) mais problématique. > *Problème* > J'ai créer un programme utilisant un STUB générer par un script IBM à partir > d'un WSDL fournie par notre prestataire. La plupart du temps, le programme > s'exécute correctement, il envoi des données au serveur de WS distant et > reçoit une réponse avant de se terminer. > Mais il arrive que mon programme "bloque" au moment de l'appel du WS, à ce > moment là selon la pile d'appel du programme il semble être en attente de > réception de donné du serveur distant. Malgrès le fait que l'on ai rajouté un > TIMEOUT lors de la génération du STUB le problème persiste et cela est très > gênant car il peut rester plusieurs jours à attendre sans erreur ni aucun > messages dans la JOBLOG. > *Informations complémentaires* > Commande de génération du STUB : > /QIBM/ProdData/OS/WebServices/V1/client/bin/wsdl2rpg.sh -t60 -o"$2" > -s"/QSYS.LIB/$3.LIB/$4.SRVPGM" -p"$5" "$1" -ma"$6" > Dernières instructions de la pile d'appel du programme : > QAXIS10X QSYSDIR readBytes_18SoapBinInputSt... > QAXIS10HT QSYSDIR getBytes__13HTTPTransportFP... > QAXIS10HT QSYSDIR readHTTPHeader__13HTTPTrans... > QAXIS10HC QSYSDIR readBytes__11HTTPChannelFPc... > QSOSRV1 QSYS recv > Merci d'avance. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5906) XML to JSON
[ https://issues.apache.org/jira/browse/AXIS2-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5906. Resolution: Not A Problem Fix Version/s: (was: nightly) Please note that this is a bug tracker. For questions, use the [java-u...@axis.apache.org|mailto:java-u...@axis.apache.org] mailing list. > XML to JSON > --- > > Key: AXIS2-5906 > URL: https://issues.apache.org/jira/browse/AXIS2-5906 > Project: Axis2 > Issue Type: Bug > Components: json >Affects Versions: 1.6.2 >Reporter: umamaheswara sarma >Priority: Major > > Hello Team, I am trying to get json response using axis2 service. It is > prefixing @ symbol in front of all attributes. But I need without symbol. > Could you please help me on this. Thanks in advance -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5904) Intermittent Rampart policy configuration missing Error
[
https://issues.apache.org/jira/browse/AXIS2-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323322#comment-16323322
]
Andreas Veithen commented on AXIS2-5904:
I think the simplest solution would be something like this:
http://svn.apache.org/viewvc?view=revision=1820941
Needs testing though.
> Intermittent Rampart policy configuration missing Error
> ---
>
> Key: AXIS2-5904
> URL: https://issues.apache.org/jira/browse/AXIS2-5904
> Project: Axis2
> Issue Type: Bug
> Components: client-api, codegen, modules, rpc
>Affects Versions: 1.7.0, 1.7.7
> Environment: Apache Tomcat 9
>Reporter: Mohamed Anis Mekki
>Priority: Critical
>
> I created a secured (sign body) Axis2 Web Service and generated .aar archive
> which I deployed to Axis2 Container (.war in Apache Tomcat). I then used
> Java2WSDL to generate a client stub. I finally created the class below that
> uses the client stub.
> In a nutshell the main method of the class calls consecutively the first then
> the second method of the service. I create a separate service stub for each
> call, using serviceStub() method and configure correctly the rampart security
> policy using getRampartConfig() method.
> {code:java}
> package tn.nat.cnss.client;
> import java.util.Properties;
> import java.rmi.RemoteException;
> import org.apache.axis2.AxisFault;
> import org.apache.axis2.context.ConfigurationContext;
> import org.apache.axis2.context.ConfigurationContextFactory;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.neethi.Policy;
> import org.apache.rampart.policy.model.CryptoConfig;
> import org.apache.rampart.policy.model.RampartConfig;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ArrayOfString;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation2;
> public class Sample2SignBodyServiceClient
> {
> private static Policy getRampartConfig()
> {
> RampartConfig rampartConfig = new RampartConfig();
> rampartConfig.setUser("clientkey");
>
> rampartConfig.setPwCbClass("tn.nat.cnss.client.PasswordCallBackHandler");
> CryptoConfig sigCrypto = new CryptoConfig();
>
> sigCrypto.setProvider("org.apache.ws.security.components.crypto.Merlin");
> Properties props = new Properties();
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.type",
> "JKS");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.file","keys/client.jks");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.password",
> "clientStorePW");
> sigCrypto.setProp(props);
> rampartConfig.setSigCryptoConfig(sigCrypto);
> Policy policy = new Policy();
> policy.addAssertion(rampartConfig);
> return policy;
> }
> private static Sample2SignBodyServiceStub serviceStub() throws AxisFault
> {
>
> org.apache.log4j.Logger.getRootLogger().setLevel(org.apache.log4j.Level.OFF);
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("client-repo",
> null);
> Sample2SignBodyServiceStub serviceStub = new
> Sample2SignBodyServiceStub(ctx,"http://localhost:8080/axis2/services/Sample2SignBodyService;);
> serviceStub._getServiceClient().engageModule("rampart");
> Policy rampartConfig = getRampartConfig();
>
> serviceStub._getServiceClient().getAxisService().getPolicySubject().attachPolicy(rampartConfig);
>
> serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(30);
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT,
> new Integer(30));
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> new Integer(30));
> return serviceStub;
> }
> public static Operation1Response operation1(String...parameters) throws
> RemoteException, AxisFault
> {
> Sample2SignBodyServiceStub serviceStub = serviceStub();
> ServiceRequestOperation1 req = new ServiceRequestOperation1();
> req.setParam1(parameters[0]);
> req.setParam2(parameters[1]);
>
[jira] [Commented] (AXIS2-5904) Intermittent Rampart policy configuration missing Error
[
https://issues.apache.org/jira/browse/AXIS2-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320880#comment-16320880
]
Andreas Veithen commented on AXIS2-5904:
The change went to the trunk, not the 1.7 branch. Note that it doesn't fix the
problem. It's just an attempt to clean up the involved code a bit, while trying
to figure out what the right fix is.
> Intermittent Rampart policy configuration missing Error
> ---
>
> Key: AXIS2-5904
> URL: https://issues.apache.org/jira/browse/AXIS2-5904
> Project: Axis2
> Issue Type: Bug
> Components: client-api, codegen, modules, rpc
>Affects Versions: 1.7.0, 1.7.7
> Environment: Apache Tomcat 9
>Reporter: Mohamed Anis Mekki
>Priority: Critical
>
> I created a secured (sign body) Axis2 Web Service and generated .aar archive
> which I deployed to Axis2 Container (.war in Apache Tomcat). I then used
> Java2WSDL to generate a client stub. I finally created the class below that
> uses the client stub.
> In a nutshell the main method of the class calls consecutively the first then
> the second method of the service. I create a separate service stub for each
> call, using serviceStub() method and configure correctly the rampart security
> policy using getRampartConfig() method.
> {code:java}
> package tn.nat.cnss.client;
> import java.util.Properties;
> import java.rmi.RemoteException;
> import org.apache.axis2.AxisFault;
> import org.apache.axis2.context.ConfigurationContext;
> import org.apache.axis2.context.ConfigurationContextFactory;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.neethi.Policy;
> import org.apache.rampart.policy.model.CryptoConfig;
> import org.apache.rampart.policy.model.RampartConfig;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ArrayOfString;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation2;
> public class Sample2SignBodyServiceClient
> {
> private static Policy getRampartConfig()
> {
> RampartConfig rampartConfig = new RampartConfig();
> rampartConfig.setUser("clientkey");
>
> rampartConfig.setPwCbClass("tn.nat.cnss.client.PasswordCallBackHandler");
> CryptoConfig sigCrypto = new CryptoConfig();
>
> sigCrypto.setProvider("org.apache.ws.security.components.crypto.Merlin");
> Properties props = new Properties();
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.type",
> "JKS");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.file","keys/client.jks");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.password",
> "clientStorePW");
> sigCrypto.setProp(props);
> rampartConfig.setSigCryptoConfig(sigCrypto);
> Policy policy = new Policy();
> policy.addAssertion(rampartConfig);
> return policy;
> }
> private static Sample2SignBodyServiceStub serviceStub() throws AxisFault
> {
>
> org.apache.log4j.Logger.getRootLogger().setLevel(org.apache.log4j.Level.OFF);
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("client-repo",
> null);
> Sample2SignBodyServiceStub serviceStub = new
> Sample2SignBodyServiceStub(ctx,"http://localhost:8080/axis2/services/Sample2SignBodyService;);
> serviceStub._getServiceClient().engageModule("rampart");
> Policy rampartConfig = getRampartConfig();
>
> serviceStub._getServiceClient().getAxisService().getPolicySubject().attachPolicy(rampartConfig);
>
> serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(30);
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT,
> new Integer(30));
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> new Integer(30));
> return serviceStub;
> }
> public static Operation1Response operation1(String...parameters) throws
> RemoteException, AxisFault
> {
> Sample2SignBodyServiceStub serviceStub = serviceStub();
> ServiceRequestOperation1 req = new ServiceRequestOperation1();
>
[jira] [Resolved] (AXIS2-5421) Axis2 Can't find ServletConfigParameter
[
https://issues.apache.org/jira/browse/AXIS2-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5421.
Resolution: Cannot Reproduce
> Axis2 Can't find ServletConfigParameter
> ---
>
> Key: AXIS2-5421
> URL: https://issues.apache.org/jira/browse/AXIS2-5421
> Project: Axis2
> Issue Type: Bug
> Components: Addressing, deployment, wsdl
>Affects Versions: 1.4
> Environment: Weblogic 12.1 , spring
>Reporter: Moe Jalali
> Labels: WSDeployment
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> I am migrating a web service to WebLogic 12.1 from WebSphere. I am getting
> the error:
> Axis2 Can't find ServletConfigParameter
> which causes
> DeploymentException: The following error occurred during schema generation:
> null
> I am using 1xis2 1.4 and spring. I have implemented the recommendations on
> the site
> http://axis.apache.org/axis2/java/core/docs/spring.html
> to resolve weblogic and axis2 jar conflicts. Addressing and Rampart modules
> engage okay. Error happens when making this call from the client
>
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("c:EdlService.ear/EdlService/WEB-INF","c:/EdlService.ear/EdlService/WEB-INF/conf/axis2.xml");
> 2012-09-13 12:58:46,112 ERROR org.apache.axis2.deployment.ServiceDeployer -
> The EdlService service, which is not valid, caused The following error
> occurred during schema generation: null
> org.apache.axis2.deployment.DeploymentException: The following error occurred
> during schema generation: null
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106)
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:110)
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:179)
> at
> org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:81)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:131)
> at
> org.apache.axis2.deployment.FileSystemConfigurator.loadServices(FileSystemConfigurator.java:147)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:82)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184)
> at
> cbp.pspo.tm.edl.ws.externalWSClientStub.CbsaEdlService.createServiceStub(CbsaEdlService.java:109)
> at
> cbp.pspo.tm.edl.ws.externalWSClientStub.CbsaEdlService.init(CbsaEdlService.java:96)
> CAUSED BY:
> Caused by: org.apache.axis2.AxisFault: Axis2 Can't find ServletConfigParameter
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> at
> org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier.getServiceObject(SpringServletContextObjectSupplier.java:86)
> ... 127 more
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5730) Make threadsafe - axis2-wsdl2code-maven-plugin
[ https://issues.apache.org/jira/browse/AXIS2-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5730. Resolution: Fixed Fix Version/s: 1.7.8 > Make threadsafe - axis2-wsdl2code-maven-plugin > --- > > Key: AXIS2-5730 > URL: https://issues.apache.org/jira/browse/AXIS2-5730 > Project: Axis2 > Issue Type: Improvement > Components: wsdl >Affects Versions: 1.6.3 >Reporter: Gary >Priority: Minor > Labels: maven > Fix For: 1.7.8 > > > Paraellel maven build presents warning that this plugin is not threadsafe. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5904) Intermittent Rampart policy configuration missing Error
[
https://issues.apache.org/jira/browse/AXIS2-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315484#comment-16315484
]
Andreas Veithen commented on AXIS2-5904:
I think the culprit is this piece of code:
https://github.com/apache/axis2-java/blob/329ac88407e73d63c1831c85a1228abc588d8f39/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java#L299
The theory is that the problem occurs when the policy is updated in the same
millisecond as the last computation of the effective policy.
> Intermittent Rampart policy configuration missing Error
> ---
>
> Key: AXIS2-5904
> URL: https://issues.apache.org/jira/browse/AXIS2-5904
> Project: Axis2
> Issue Type: Bug
> Components: client-api, codegen, modules, rpc
>Affects Versions: 1.7.0, 1.7.7
> Environment: Apache Tomcat 9
>Reporter: Mohamed Anis Mekki
>Priority: Critical
>
> I created a secured (sign body) Axis2 Web Service and generated .aar archive
> which I deployed to Axis2 Container (.war in Apache Tomcat). I then used
> Java2WSDL to generate a client stub. I finally created the class below that
> uses the client stub.
> In a nutshell the main method of the class calls consecutively the first then
> the second method of the service. I create a separate service stub for each
> call, using serviceStub() method and configure correctly the rampart security
> policy using getRampartConfig() method.
> {code:java}
> package tn.nat.cnss.client;
> import java.util.Properties;
> import java.rmi.RemoteException;
> import org.apache.axis2.AxisFault;
> import org.apache.axis2.context.ConfigurationContext;
> import org.apache.axis2.context.ConfigurationContextFactory;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.neethi.Policy;
> import org.apache.rampart.policy.model.CryptoConfig;
> import org.apache.rampart.policy.model.RampartConfig;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ArrayOfString;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation2;
> public class Sample2SignBodyServiceClient
> {
> private static Policy getRampartConfig()
> {
> RampartConfig rampartConfig = new RampartConfig();
> rampartConfig.setUser("clientkey");
>
> rampartConfig.setPwCbClass("tn.nat.cnss.client.PasswordCallBackHandler");
> CryptoConfig sigCrypto = new CryptoConfig();
>
> sigCrypto.setProvider("org.apache.ws.security.components.crypto.Merlin");
> Properties props = new Properties();
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.type",
> "JKS");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.file","keys/client.jks");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.password",
> "clientStorePW");
> sigCrypto.setProp(props);
> rampartConfig.setSigCryptoConfig(sigCrypto);
> Policy policy = new Policy();
> policy.addAssertion(rampartConfig);
> return policy;
> }
> private static Sample2SignBodyServiceStub serviceStub() throws AxisFault
> {
>
> org.apache.log4j.Logger.getRootLogger().setLevel(org.apache.log4j.Level.OFF);
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("client-repo",
> null);
> Sample2SignBodyServiceStub serviceStub = new
> Sample2SignBodyServiceStub(ctx,"http://localhost:8080/axis2/services/Sample2SignBodyService;);
> serviceStub._getServiceClient().engageModule("rampart");
> Policy rampartConfig = getRampartConfig();
>
> serviceStub._getServiceClient().getAxisService().getPolicySubject().attachPolicy(rampartConfig);
>
> serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(30);
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT,
> new Integer(30));
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> new Integer(30));
> return serviceStub;
> }
> public static Operation1Response operation1(String...parameters) throws
> RemoteException, AxisFault
> {
> Sample2SignBodyServiceStub
[jira] [Commented] (AXIS2-5904) Intermittent Rampart policy configuration missing Error
[
https://issues.apache.org/jira/browse/AXIS2-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314684#comment-16314684
]
Andreas Veithen commented on AXIS2-5904:
Can you provide a test project to reproduce the problem? Note that since the
error occurs on the client side before sending the message, you don't need to
include the service in the test project.
> Intermittent Rampart policy configuration missing Error
> ---
>
> Key: AXIS2-5904
> URL: https://issues.apache.org/jira/browse/AXIS2-5904
> Project: Axis2
> Issue Type: Bug
> Components: client-api, codegen, modules, rpc
>Affects Versions: 1.7.0, 1.7.7
> Environment: Apache Tomcat 9
>Reporter: Mohamed Anis Mekki
>Priority: Critical
>
> I created a secured (sign body) Axis2 Web Service and generated .aar archive
> which I deployed to Axis2 Container (.war in Apache Tomcat). I then used
> Java2WSDL to generate a client stub. I finally created the class below that
> uses the client stub.
> In a nutshell the main method of the class calls consecutively the first then
> the second method of the service. I create a separate service stub for each
> call, using serviceStub() method and configure correctly the rampart security
> policy using getRampartConfig() method.
> {code:java}
> package tn.nat.cnss.client;
> import java.util.Properties;
> import java.rmi.RemoteException;
> import org.apache.axis2.AxisFault;
> import org.apache.axis2.context.ConfigurationContext;
> import org.apache.axis2.context.ConfigurationContextFactory;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.neethi.Policy;
> import org.apache.rampart.policy.model.CryptoConfig;
> import org.apache.rampart.policy.model.RampartConfig;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ArrayOfString;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation1Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.Operation2Response;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation1;
> import tn.nat.cnss.client.Sample2SignBodyServiceStub.ServiceRequestOperation2;
> public class Sample2SignBodyServiceClient
> {
> private static Policy getRampartConfig()
> {
> RampartConfig rampartConfig = new RampartConfig();
> rampartConfig.setUser("clientkey");
>
> rampartConfig.setPwCbClass("tn.nat.cnss.client.PasswordCallBackHandler");
> CryptoConfig sigCrypto = new CryptoConfig();
>
> sigCrypto.setProvider("org.apache.ws.security.components.crypto.Merlin");
> Properties props = new Properties();
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.type",
> "JKS");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.file","keys/client.jks");
>
> props.setProperty("org.apache.ws.security.crypto.merlin.keystore.password",
> "clientStorePW");
> sigCrypto.setProp(props);
> rampartConfig.setSigCryptoConfig(sigCrypto);
> Policy policy = new Policy();
> policy.addAssertion(rampartConfig);
> return policy;
> }
> private static Sample2SignBodyServiceStub serviceStub() throws AxisFault
> {
>
> org.apache.log4j.Logger.getRootLogger().setLevel(org.apache.log4j.Level.OFF);
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("client-repo",
> null);
> Sample2SignBodyServiceStub serviceStub = new
> Sample2SignBodyServiceStub(ctx,"http://localhost:8080/axis2/services/Sample2SignBodyService;);
> serviceStub._getServiceClient().engageModule("rampart");
> Policy rampartConfig = getRampartConfig();
>
> serviceStub._getServiceClient().getAxisService().getPolicySubject().attachPolicy(rampartConfig);
>
> serviceStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(30);
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT,
> new Integer(30));
>
> serviceStub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> new Integer(30));
> return serviceStub;
> }
> public static Operation1Response operation1(String...parameters) throws
> RemoteException, AxisFault
> {
> Sample2SignBodyServiceStub serviceStub = serviceStub();
> ServiceRequestOperation1 req = new ServiceRequestOperation1();
>
[jira] [Resolved] (AXIS2-5681) Axis client fails when content-encoding http header is passed as empty string from soap service
[ https://issues.apache.org/jira/browse/AXIS2-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5681. Resolution: Duplicate Fix Version/s: (was: 1.6.2) > Axis client fails when content-encoding http header is passed as empty string > from soap service > --- > > Key: AXIS2-5681 > URL: https://issues.apache.org/jira/browse/AXIS2-5681 > Project: Axis2 > Issue Type: Bug > Components: Addressing, client-api, Integration, om, wsdl >Affects Versions: 1.6.2 > Environment: Windows 7, tomcat >Reporter: KRISHNA SAI MULPURI >Priority: Blocker > Original Estimate: 48h > Remaining Estimate: 48h > > Axis client fails when content-encoding http header is passed as empty string > from soap service > Content-Encoding: '' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5832) Missing Brackets in ADBBeanTemplate-bean.xsl
[
https://issues.apache.org/jira/browse/AXIS2-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5832.
Resolution: Duplicate
> Missing Brackets in ADBBeanTemplate-bean.xsl
>
>
> Key: AXIS2-5832
> URL: https://issues.apache.org/jira/browse/AXIS2-5832
> Project: Axis2
> Issue Type: Bug
> Components: adb
>Affects Versions: 1.7.2, 1.7.4
>Reporter: Phil Mueller
>
> Line 2190 of ADBBeanTemplate-bean.xsl in 1.7.2
> {code}
> if (reader.isStartElement() ||
> reader.hasText() select="$propQName"/>.equals(reader.getName()) || select="$propQName2"/>.equals(reader.getName()) ){
> {code}
> must be changed to
> {code}
> if (reader.isStartElement() ||
> reader.hasText() ( select="$propQName"/>.equals(reader.getName()) || select="$propQName2"/>.equals(reader.getName())) ){
> {code}
> Because the generated Factory.parse method in the bean-source code
> {code}
> if (reader.isStartElement()
> && new javax.xml.namespace.QName("",
> "struct").equals(reader.getName())
> || new javax.xml.namespace.QName("",
> "struct").equals(reader.getName()))
> {code}
> runs in some cases into
> {code}
> java.lang.IllegalStateException: Current state is not among the states
> START_ELEMENT , ATTRIBUTEvalid for getAttributeValue()
> at
> com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.getAttributeValue(XMLStreamReaderImpl.java:819)
> at
> ise.service.wswdx.gen.WDXDataStruct$Factory.parse(WDXDataStruct.java:692)
> {code}
> This is the code with the xsl-changes
> {code}
> if (reader.isStartElement()
> && (new javax.xml.namespace.QName("",
> "struct").equals(reader.getName())
> || new javax.xml.namespace.QName("",
> "struct").equals(reader.getName(
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5629) WS-Security for Corba Module
[ https://issues.apache.org/jira/browse/AXIS2-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5629. Resolution: Won't Fix > WS-Security for Corba Module > > > Key: AXIS2-5629 > URL: https://issues.apache.org/jira/browse/AXIS2-5629 > Project: Axis2 > Issue Type: New Feature > Components: corba >Affects Versions: 1.6.2 >Reporter: Jürgen Weber > > It should be possible to protect Corba services exposed with Axis2 Corba > module with WS-Security. > Corba module should map WS-Security to CSIV2. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5641) Support SOAP over WebSocket transport for Apache Axis2
[ https://issues.apache.org/jira/browse/AXIS2-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5641. Resolution: Won't Fix > Support SOAP over WebSocket transport for Apache Axis2 > --- > > Key: AXIS2-5641 > URL: https://issues.apache.org/jira/browse/AXIS2-5641 > Project: Axis2 > Issue Type: Improvement >Reporter: Gihan Madhusanka > Labels: gsoc2014 > > WebSocket is a technology that developed as a part of the HTML5 initiative > and getting lots of attraction from various developer communities including > Java Script, Java , .NET etc. Apache Axis2 is a popular web service framework > which is developed and maintained by ASF. Main objective of this project is > to write Axis2 transport module which supports for WebSocket protocol. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5474) DefaultSchemaGenerator : properly handle failure when a bean property has no getReadMethod()
[
https://issues.apache.org/jira/browse/AXIS2-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5474.
Resolution: Fixed
This problem was addressed in r1338183.
> DefaultSchemaGenerator : properly handle failure when a bean property has no
> getReadMethod()
>
>
> Key: AXIS2-5474
> URL: https://issues.apache.org/jira/browse/AXIS2-5474
> Project: Axis2
> Issue Type: Improvement
> Components: kernel
>Affects Versions: 1.6.2
>Reporter: Philippe Le Berre
>Priority: Trivial
> Labels: patch
> Attachments: patch.diff
>
>
> Deployment of service (aar file) might failed with :
> Caused by: org.apache.axis2.deployment.DeploymentException: The following
> error occurred during schema generation: null
> at
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:396)
> ... 35 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.generateSchema(DefaultSchemaGenerator.java:606)
> at
> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.generateSchemaTypeforNameCommon(DefaultSchemaGenerator.java:1092)
> In which the getReadMethod() is returning null for a bean property, thus to
> make it more friendly and avoid anyone loosing time on such things :
> --- DefaultSchemaGenerator.java 2013-01-08 10:09:33.0 +0100
> +++ DefaultSchemaGenerator.java.new 2013-01-08 10:09:17.0 +0100
> @@ -603,6 +603,9 @@
> String propertyName = property.getName();
> if (!property.getName().equals("class") &&
> (property.getPropertyType() != null)) {
> if ((beanExcludeInfo == null) ||
> !beanExcludeInfo.isExcludedProperty(propertyName)) {
> +if (property.getReadMethod() == null) {
> +throw new Exception("Failed property
> ("+property.getName()+") has no getReadMethod() method in Class
> ("+javaType+")");
> +}
> Type genericFieldType =
> property.getReadMethod().getGenericReturnType();
> if(genericFieldType instanceof ParameterizedType){
> ParameterizedType aType = (ParameterizedType)
> genericFieldType;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-3993) Failed on redirect from Apache
[ https://issues.apache.org/jira/browse/AXIS2-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-3993. Resolution: Not A Problem > Failed on redirect from Apache > --- > > Key: AXIS2-3993 > URL: https://issues.apache.org/jira/browse/AXIS2-3993 > Project: Axis2 > Issue Type: Bug > Components: modules > Environment: Linux >Reporter: Kenny Lee > > When the client application direct connect to weblogic server use the URL > "http://10.1.1.53:7011/axis2/services/testService; , the application respond > correct. (P.S 10.1.1.53 is the Weblogic Server IP address) > But when I change to use "http://www.abc.com/axis2/services/testService; it > return the following exception error. > The "http://www.abc.com/axis2/services/testService; was redirect from the > Apache Web service and config by httpd.conf > org.apache.axis2.AxisFault > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:89) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) > at > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528) > at > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508) > Thanks, > Kenny. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-3993) Failed on redirect from Apache
[ https://issues.apache.org/jira/browse/AXIS2-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-3993: --- Issue Type: Bug (was: Test) > Failed on redirect from Apache > --- > > Key: AXIS2-3993 > URL: https://issues.apache.org/jira/browse/AXIS2-3993 > Project: Axis2 > Issue Type: Bug > Components: modules > Environment: Linux >Reporter: Kenny Lee > > When the client application direct connect to weblogic server use the URL > "http://10.1.1.53:7011/axis2/services/testService; , the application respond > correct. (P.S 10.1.1.53 is the Weblogic Server IP address) > But when I change to use "http://www.abc.com/axis2/services/testService; it > return the following exception error. > The "http://www.abc.com/axis2/services/testService; was redirect from the > Apache Web service and config by httpd.conf > org.apache.axis2.AxisFault > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:89) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) > at > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528) > at > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508) > Thanks, > Kenny. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-4012) org.apache.xmlbeans.XmlException: Attempted read on closed stream.
[ https://issues.apache.org/jira/browse/AXIS2-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4012: --- Issue Type: Bug (was: Wish) > org.apache.xmlbeans.XmlException: Attempted read on closed stream. > --- > > Key: AXIS2-4012 > URL: https://issues.apache.org/jira/browse/AXIS2-4012 > Project: Axis2 > Issue Type: Bug > Components: client-api >Affects Versions: nightly > Environment: Linux,Jav1.4 >Reporter: Rajesh Kandhasamy > Labels: xmlbean > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > org.apache.xmlbeans.XmlException: Attempted read on closed stream. > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:847) > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) > at > org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) > > Caused by: com.ctc.wstx.exc.WstxIOException: Attempted read on closed stream. > at > com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java(Compiled Code)) > at > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java(Compiled Code)) > at > org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java(Compiled > Code)) > at > org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java(Compiled > Code)) > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843) > ... 48 more > Caused by: java.io.IOException: Attempted read on closed stream. > at > org.apache.commons.httpclient.AutoCloseInputStream.isReadAllowed(AutoCloseInputStream.java(Inlined > Compiled Code)) > at > org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java(Compiled > Code)) > at java.io.FilterInputStream.read(FilterInputStream.java(Inlined > Compiled Code)) > at java.io.PushbackInputStream.read(PushbackInputStream.java(Compiled > Code)) > at java.io.FilterInputStream.read(FilterInputStream.java(Compiled > Code)) > at com.ctc.wstx.io.UTF8Reader.loadMore(UTF8Reader.java(Compiled > Code)) > at com.ctc.wstx.io.UTF8Reader.read(UTF8Reader.java(Compiled Code)) > at com.ctc.wstx.io.MergedReader.read(MergedReader.java(Compiled > Code)) > Note: This occurs only in Load test maybe morethan 200-2000 concurrent > request, and i dont find in all the response, it appears occationally -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5441) [axis2] WSDL2JAVA with XMLBean binding does not create instance of the derived type or ignore xsi:type in the xm
[ https://issues.apache.org/jira/browse/AXIS2-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5441. Resolution: Incomplete > [axis2] WSDL2JAVA with XMLBean binding does not create instance of the > derived type or ignore xsi:type in the xm > > > Key: AXIS2-5441 > URL: https://issues.apache.org/jira/browse/AXIS2-5441 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.6.2 > Environment: Tomcat 6 and Axis 1.6.2 >Reporter: srikanth atluri > > Hi, > I think this issue was resolved long time ago, but I am seeing the same > behavior on my Axis 1.6.2 generated client. My client is ignoring the xsi > type parameters and the deserializer is not creating the polymorphic classes > based on the xsi types.. Any help will be greatly appreciated. Please note, > I am using the client to call a service which is send xsi types. Even the > requests generated by client are not passing the xsi types. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3964) WSDL20ToAxisServiceBuilder > HTTP Binding: AxisBindingMessage entry is being overwritten in corresponding AxisBindingOperation
[ https://issues.apache.org/jira/browse/AXIS2-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302813#comment-16302813 ] Andreas Veithen commented on AXIS2-3964: The patch doesn't contain any test case. Can you provide one? > WSDL20ToAxisServiceBuilder > HTTP Binding: AxisBindingMessage entry is being > overwritten in corresponding AxisBindingOperation > --- > > Key: AXIS2-3964 > URL: https://issues.apache.org/jira/browse/AXIS2-3964 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.4.1 > Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.75Ghz >Reporter: Antonio Andrade >Priority: Minor > Attachments: AXIS2-3964-trunk.patch, AXIS2-3964.patch > > Original Estimate: 4h > Remaining Estimate: 4h > > Observed Behavior: > Within WSDL20ToAxisServiceBuilder, AxisBindingOperation children are always > saved under the WSDLConstants.MESSAGE_LABEL_IN_VALUE key when the HTTP > Binding is used. Look at processHTTPBindingExtention method (around line 921). > Expected Behavior: > When using the HTTP Binding, AxisBindingMessages should be saved under the > corresponding key (should be correctly set into the corresponding > AxisBindingOperation): > - WSDLConstants.MESSAGE_LABEL_IN_VALUE whenever the message has a > WSDLConstants.WSDL_MESSAGE_DIRECTION_IN direction > - WSDLConstants.MESSAGE_LABEL_OUT_VALUE whenever the message has a > WSDLConstants.WSDL_MESSAGE_DIRECTION_OUT direction -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5902) CLONE - Making Axis2 more user friendly - client side
[ https://issues.apache.org/jira/browse/AXIS2-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5902. Resolution: Duplicate > CLONE - Making Axis2 more user friendly - client side > - > > Key: AXIS2-5902 > URL: https://issues.apache.org/jira/browse/AXIS2-5902 > Project: Axis2 > Issue Type: Improvement >Affects Versions: 1.7.0 >Reporter: Fan >Priority: Critical > > I was closely looked at some of the emails in axis user list and found > that users are facing issue when setting up Axis2 at the client side. > Specially finding the required jars for the core functionality as well > as modules such as security, reliability. Thus, I think we should have > a separate distribution for the client side with all the required > stuffs, so that user can simply downloads it and uses it. In fact, this > is not new, we have discussed this a long time ago. > With this proposal, we will be creating a single jar file or an archive > file by putting all the relevant libraries to run axis2 client and this > includes: > - Axis2 core jars > - Axis2 third party jars > - Addressing module (as a jar) > - Rampart module and related jars > - Sandesha module and related jars > - Any other useful modules and libraries > With this approach, user downloads a single file and that has everything > he needs to run axis2. He can simply turn on/off modules (addressing, > security) without having any troubles? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-4091) WSDL11ToAxisServiceBuilder + HTTP Binding: Unused/Useless global element declations are appended into WSDL's XSD documents
[ https://issues.apache.org/jira/browse/AXIS2-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299777#comment-16299777 ] Andreas Veithen commented on AXIS2-4091: I'm trying to understand the issue better. It turns out that the code in question currently has very poor test coverage; only a single low level unit test (HttpMessagesSerializationTest) fails if the generateWrapperSchema code is completely disabled. What is the end to end scenario that you are trying to make work? Could we use that to build an integration test? > WSDL11ToAxisServiceBuilder + HTTP Binding: Unused/Useless global element > declations are appended into WSDL's XSD documents > -- > > Key: AXIS2-4091 > URL: https://issues.apache.org/jira/browse/AXIS2-4091 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.4, nightly > Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.83Ghz >Reporter: Antonio Andrade >Priority: Minor > Attachments: AXIS2-4091-trunk.patch, AXIS2-4091.patch, JUnit Tests - > Before.jpg, JUnit Tests - Half of Patch.jpg > > Original Estimate: 1h > Remaining Estimate: 1h > > Observed Behavior: > 1) New XML schema global elements declarations are created and appended into > WSDL's XSD documents when they should not. This is the case of message > s already referencing global element declarations (through the > 'element' attribute of the message part). > 2) Whether a message part requires a 'wrapped' element or not can be > determine by reading the 'wrappedInput' and 'wrappedOutput' attributes of the > 'BindingOperationEntry' inner class after the message part has been analyzed > but the 'addPartToElement' method fails to properly set them for all cases > (i.e. ignores whether the message part comes from an input or output message > by ignoring the 'isOutMessage' argument received). > Expected Behavior: > 1) No XML schema global elements declarations should be added whenever > message s use the 'element' attribute (i.e. already reference > global element declarations). > 2) The 'addPartToElement' method should take into account the value of the > 'isOutMessage' argument received to set the value of the 'wrappedInput' and > 'wrappedOutput' attributes of the 'BindingOperationEntry' inner class. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5839) spring mvc axis integration
[ https://issues.apache.org/jira/browse/AXIS2-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5839. Resolution: Not A Bug > spring mvc axis integration > > > Key: AXIS2-5839 > URL: https://issues.apache.org/jira/browse/AXIS2-5839 > Project: Axis2 > Issue Type: New Feature > Components: jaxws, kernel >Affects Versions: 1.6.1 > Environment: windows, weblogic 12c >Reporter: Revathi > Fix For: 1.6.1 > > > I want to implement axis2 integration(SOAP webservice) with spring mvc using > maven. > Can you share the configuration. spring implementation code. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
