[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=16468191#comment-16468191 ] Hudson commented on AXIS2-5914: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #170 (See [https://builds.apache.org/job/axis2-1.7/170/]) AXIS2-5914: Merge r1780684 to the 1.7 branch. (veithen: rev 1831214) * (edit) axis2 * (edit) axis2/pom.xml > 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-5730) Make threadsafe - axis2-wsdl2code-maven-plugin
[ https://issues.apache.org/jira/browse/AXIS2-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317147#comment-16317147 ] Hudson commented on AXIS2-5730: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #165 (See [https://builds.apache.org/job/axis2-1.7/165/]) AXIS2-5730: Merge r1820601 to the 1.7 branch. (veithen: rev 1820603) * (edit) axis2 * (edit) axis2/modules/tool/axis2-aar-maven-plugin/src/main/java/org/apache/axis2/maven2/aar/AarMojo.java * (edit) axis2/modules/tool/axis2-aar-maven-plugin/src/main/java/org/apache/axis2/maven2/aar/DeployAarMojo.java * (edit) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/main/java/org/apache/axis2/maven2/java2wsdl/Java2WSDLMojo.java * (edit) axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/MarExplodedMojo.java * (edit) axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/MarInPlaceMojo.java * (edit) axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/MarMojo.java * (edit) axis2/modules/tool/axis2-repo-maven-plugin/src/main/java/org/apache/axis2/maven2/repo/CreateRepositoryMojo.java * (edit) axis2/modules/tool/axis2-repo-maven-plugin/src/main/java/org/apache/axis2/maven2/repo/CreateTestRepositoryMojo.java * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/WSDL2CodeMojo.java * (edit) axis2/modules/tool/simple-server-maven-plugin/src/main/java/org/apache/axis2/maven2/server/SimpleHttpServerMojo.java > 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-5730) Make threadsafe - axis2-wsdl2code-maven-plugin
[ https://issues.apache.org/jira/browse/AXIS2-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317142#comment-16317142 ] Hudson commented on AXIS2-5730: --- SUCCESS: Integrated in Jenkins build Axis2 #3890 (See [https://builds.apache.org/job/Axis2/3890/]) AXIS2-5730: Mark Maven plugins/goals thread safe. (veithen: rev 1820601) * (edit) axis2/modules/tool/axis2-aar-maven-plugin/src/main/java/org/apache/axis2/maven2/aar/AarMojo.java * (edit) axis2/modules/tool/axis2-aar-maven-plugin/src/main/java/org/apache/axis2/maven2/aar/DeployAarMojo.java * (edit) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/main/java/org/apache/axis2/maven2/java2wsdl/Java2WSDLMojo.java * (edit) axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/MarExplodedMojo.java * (edit) axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/MarInPlaceMojo.java * (edit) axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/MarMojo.java * (edit) axis2/modules/tool/axis2-repo-maven-plugin/src/main/java/org/apache/axis2/maven2/repo/CreateRepositoryMojo.java * (edit) axis2/modules/tool/axis2-repo-maven-plugin/src/main/java/org/apache/axis2/maven2/repo/CreateTestRepositoryMojo.java * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/GenerateSourcesMojo.java * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/GenerateTestSourcesMojo.java * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/WSDL2CodeMojo.java * (edit) axis2/modules/tool/axis2-xsd2java-maven-plugin/src/main/java/org/apache/axis2/maven/xsd2java/GenerateSourcesMojo.java * (edit) axis2/modules/tool/axis2-xsd2java-maven-plugin/src/main/java/org/apache/axis2/maven/xsd2java/GenerateTestSourcesMojo.java * (edit) axis2/modules/tool/simple-server-maven-plugin/src/main/java/org/apache/axis2/maven2/server/SimpleHttpServerMojo.java > 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=16315840#comment-16315840
]
Hudson commented on AXIS2-5904:
---
UNSTABLE: Integrated in Jenkins build Axis2 #3886 (See
[https://builds.apache.org/job/Axis2/3886/])
AXIS2-5904: Revert r1820513. (veithen: rev 1820516)
* (edit)
axis2/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
AXIS2-5904: Remove unused code. (veithen: rev 1820515)
* (edit)
axis2/modules/kernel/src/org/apache/axis2/description/PolicySubject.java
AXIS2-5904: Simplify the calculateEffectivePolicy and isPolicyUpdated code in
AxisBindingMessage. (veithen: rev 1820513)
* (edit)
axis2/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
> 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
[jira] [Commented] (AXIS2-5388) XMLBeans fix on the horizon
[ https://issues.apache.org/jira/browse/AXIS2-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309761#comment-16309761 ] Hudson commented on AXIS2-5388: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #164 (See [https://builds.apache.org/job/axis2-1.7/164/]) AXIS2-5388: Merge r1819265 to the 1.7 branch. (veithen: rev 1819966) * (edit) axis2 * (edit) axis2/pom.xml > XMLBeans fix on the horizon > --- > > Key: AXIS2-5388 > URL: https://issues.apache.org/jira/browse/AXIS2-5388 > Project: Axis2 > Issue Type: Improvement > Environment: Websphere 6.1 >Reporter: James Grahn >Priority: Minor > > According to #XMLBEANS-484, a probable fix for the xml bean library issues > (with Websphere) is set to deploy with version 2.5.1. > XMLBeans 2.5.1 is not yet released, but it's worth tracking. Feel free to > close this JIRA issue if it's not useful as a reminder to the project. -- 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-479) Axis2 does not deserialise abstract types correctly when receiving WSA messages
[ https://issues.apache.org/jira/browse/AXIS2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303829#comment-16303829 ] Hudson commented on AXIS2-479: -- ABORTED: Integrated in Jenkins build Axis2 #3864 (See [https://builds.apache.org/job/Axis2/3864/]) Recycle the test case for AXIS2-479 and transform it into a test case for Axiom. It is no longer relevant for Axis2 itself because XmlBeans objects are now serialized using SAX. (veithen: rev 1819279) * (edit) axis2/modules/integration/itest-build.xml * (edit) axis2/modules/integration/pom.xml * (delete) axis2/modules/integration/test-resources/xsd/type-test.xsd * (delete) axis2/modules/integration/test/org/apache/axis2/om/OMAttributeTest.java > Axis2 does not deserialise abstract types correctly when receiving WSA > messages > --- > > Key: AXIS2-479 > URL: https://issues.apache.org/jira/browse/AXIS2-479 > Project: Axis2 > Issue Type: Bug >Affects Versions: 0.94 > Environment: Suse Linux 9.3 Server, Tomcat 5.0, Axis2 0.94 >Reporter: Justin Schoeman >Assignee: Ajith Harshana Ranabahu > > When receiving WSA encoded messages containing abstract types, the created > objects are for the implementation of the abstract class, instead of the > actual type sent over the wire. > In the following example, DeviceID is an abstract type, and EANDeviceID is an > implementation of that type. The following information is obtained from the > deserialised DeviceID object (which is sent as an EANDeviceID object): > WSA: > getClass().getName(): > za.co.eskom.nrs.www.xmlvend.base._2_0.schema.impl.DeviceIDImpl > schemaType(): DeviceID@http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema > toString(): xmlns:sch="http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema"/> > XSI: > getClass().getName(): > za.co.eskom.nrs.www.xmlvend.base._2_0.schema.impl.GenericDeviceIDImpl > schemaType(): > T=GenericDeviceID@http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema > toString(): xmlns:sch="http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> > As you can see, in both cases, the correct information is contained in the > xmlbean, but for the WSA message it is deserialised incorrectly. > -justin -- 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-479) Axis2 does not deserialise abstract types correctly when receiving WSA messages
[ https://issues.apache.org/jira/browse/AXIS2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303792#comment-16303792 ] Hudson commented on AXIS2-479: -- SUCCESS: Integrated in Jenkins build axiom-trunk #2922 (See [https://builds.apache.org/job/axiom-trunk/2922/]) Recycle the test case for AXIS2-479 and transform it into a test case for Axiom. It is no longer relevant for Axis2 itself because XmlBeans objects are now serialized using SAX. (veithen: rev 1819279) * (edit) axiom/testing/axiom-testsuite/src/main/java/org/apache/axiom/ts/om/OMTestSuiteBuilder.java * (add) axiom/testing/axiom-testsuite/src/main/java/org/apache/axiom/ts/om/builder/TestCreateStAXOMBuilderFromXmlBeansPullParser.java * (add) axiom/testing/axiom-testsuite/src/main/resources/org/apache/axiom/ts/om/builder/xmlvend.xml * (add) axiom/testing/axiom-testsuite/src/main/xsd/xmlvend.xsd > Axis2 does not deserialise abstract types correctly when receiving WSA > messages > --- > > Key: AXIS2-479 > URL: https://issues.apache.org/jira/browse/AXIS2-479 > Project: Axis2 > Issue Type: Bug >Affects Versions: 0.94 > Environment: Suse Linux 9.3 Server, Tomcat 5.0, Axis2 0.94 >Reporter: Justin Schoeman >Assignee: Ajith Harshana Ranabahu > > When receiving WSA encoded messages containing abstract types, the created > objects are for the implementation of the abstract class, instead of the > actual type sent over the wire. > In the following example, DeviceID is an abstract type, and EANDeviceID is an > implementation of that type. The following information is obtained from the > deserialised DeviceID object (which is sent as an EANDeviceID object): > WSA: > getClass().getName(): > za.co.eskom.nrs.www.xmlvend.base._2_0.schema.impl.DeviceIDImpl > schemaType(): DeviceID@http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema > toString(): xmlns:sch="http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema"/> > XSI: > getClass().getName(): > za.co.eskom.nrs.www.xmlvend.base._2_0.schema.impl.GenericDeviceIDImpl > schemaType(): > T=GenericDeviceID@http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema > toString(): xmlns:sch="http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> > As you can see, in both cases, the correct information is contained in the > xmlbean, but for the WSA message it is deserialised incorrectly. > -justin -- 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-5770) ClassCastException from org.apache.axis2.saaj.SOAPElementImpl
[ https://issues.apache.org/jira/browse/AXIS2-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286930#comment-16286930 ] Hudson commented on AXIS2-5770: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #162 (See [https://builds.apache.org/job/axis2-1.7/162/]) AXIS2-5770: Merge r1817866 to the 1.7 branch. (veithen: rev 1817867) * (edit) axis2 * (edit) axis2/modules/saaj/src/org/apache/axis2/saaj/SOAPElementImpl.java > ClassCastException from org.apache.axis2.saaj.SOAPElementImpl > - > > Key: AXIS2-5770 > URL: https://issues.apache.org/jira/browse/AXIS2-5770 > Project: Axis2 > Issue Type: Bug > Components: saaj >Affects Versions: 1.7.2 > Environment: Windows 7 >Reporter: Vishwanath Washimkar > Labels: saaj > Fix For: 1.7.8 > > Attachments: SOAPTest.java > > > We have have which worked fine with Axis 1.6.2 , Axis 1.6.2 . The moment I > try to upgrade to the Axis 1.7.1 or to Axis 1.7.2 the following exception is > thrown from SOAPElementImpl > java.lang.ClassCastException: org.apache.axis2.saaj.SOAPElementImpl cannot be > cast to org.apache.axiom.om.OMElement > at > org.apache.axis2.saaj.SOAPElementImpl.addChildElement(SOAPElementImpl.java:169) > at vish.SOAPTest.addCallNode(SOAPTest.java:35) > at vish.SOAPTest.main(SOAPTest.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140) -- 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-5770) ClassCastException from org.apache.axis2.saaj.SOAPElementImpl
[ https://issues.apache.org/jira/browse/AXIS2-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286855#comment-16286855 ] Hudson commented on AXIS2-5770: --- SUCCESS: Integrated in Jenkins build Axis2 #3844 (See [https://builds.apache.org/job/Axis2/3844/]) AXIS2-5770: Fix ClassCastException in SAAJ's addChildElement method. (veithen: rev 1817866) * (edit) axis2/modules/saaj/src/org/apache/axis2/saaj/SOAPElementImpl.java > ClassCastException from org.apache.axis2.saaj.SOAPElementImpl > - > > Key: AXIS2-5770 > URL: https://issues.apache.org/jira/browse/AXIS2-5770 > Project: Axis2 > Issue Type: Bug > Components: saaj >Affects Versions: 1.7.2 > Environment: Windows 7 >Reporter: Vishwanath Washimkar > Labels: saaj > Fix For: 1.7.8 > > Attachments: SOAPTest.java > > > We have have which worked fine with Axis 1.6.2 , Axis 1.6.2 . The moment I > try to upgrade to the Axis 1.7.1 or to Axis 1.7.2 the following exception is > thrown from SOAPElementImpl > java.lang.ClassCastException: org.apache.axis2.saaj.SOAPElementImpl cannot be > cast to org.apache.axiom.om.OMElement > at > org.apache.axis2.saaj.SOAPElementImpl.addChildElement(SOAPElementImpl.java:169) > at vish.SOAPTest.addCallNode(SOAPTest.java:35) > at vish.SOAPTest.main(SOAPTest.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140) -- 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-5890) Build failure when running mvn install without clean
[ https://issues.apache.org/jira/browse/AXIS2-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177830#comment-16177830 ] Hudson commented on AXIS2-5890: --- SUCCESS: Integrated in Jenkins build Axis2 #3835 (See [https://builds.apache.org/job/Axis2/3835/]) AXIS2-5890: Fix build failure (caused by r1809385) when the apache-release profile is enabled. (veithen: rev 1809411) * (edit) axis2/modules/distribution/pom.xml > Build failure when running mvn install without clean > > > Key: AXIS2-5890 > URL: https://issues.apache.org/jira/browse/AXIS2-5890 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.6 >Reporter: Andreas Veithen >Priority: Minor > > The Maven build fails when mvn install is executed without cleaning output > directories (i.e. as opposed to mvn clean install). This is caused by a bug > in jaxb2-maven-plugin that will be fixed by > https://github.com/mojohaus/jaxb2-maven-plugin/pull/94. -- 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-5890) Build failure when running mvn install without clean
[ https://issues.apache.org/jira/browse/AXIS2-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177803#comment-16177803 ] Hudson commented on AXIS2-5890: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #145 (See [https://builds.apache.org/job/axis2-1.7/145/]) AXIS2-5890: Merge r1809384, r1809385 and r1809411 to the 1.7 branch. (veithen: rev 1809418) * (edit) axis2 * (edit) axis2/modules/distribution/pom.xml * (edit) axis2/pom.xml > Build failure when running mvn install without clean > > > Key: AXIS2-5890 > URL: https://issues.apache.org/jira/browse/AXIS2-5890 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.6 >Reporter: Andreas Veithen >Priority: Minor > > The Maven build fails when mvn install is executed without cleaning output > directories (i.e. as opposed to mvn clean install). This is caused by a bug > in jaxb2-maven-plugin that will be fixed by > https://github.com/mojohaus/jaxb2-maven-plugin/pull/94. -- 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-5890) Build failure when running mvn install without clean
[ https://issues.apache.org/jira/browse/AXIS2-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177755#comment-16177755 ] Hudson commented on AXIS2-5890: --- FAILURE: Integrated in Jenkins build Axis2 #3834 (See [https://builds.apache.org/job/Axis2/3834/]) AXIS2-5890: Always clean the directory where we unpack the distribution for testing. Files left over from a previous run interfere with the tests. (veithen: rev 1809385) * (edit) axis2/modules/distribution/pom.xml AXIS2-5890: Work around bug in jaxb2-maven-plugin. (veithen: rev 1809384) * (edit) axis2/pom.xml > Build failure when running mvn install without clean > > > Key: AXIS2-5890 > URL: https://issues.apache.org/jira/browse/AXIS2-5890 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.6 >Reporter: Andreas Veithen >Priority: Minor > > The Maven build fails when mvn install is executed without cleaning output > directories (i.e. as opposed to mvn clean install). This is caused by a bug > in jaxb2-maven-plugin that will be fixed by > https://github.com/mojohaus/jaxb2-maven-plugin/pull/94. -- 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-5887) Parsing of response ends up in a IllegalStateException (attribute type accessed in illegal event!)
[
https://issues.apache.org/jira/browse/AXIS2-5887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170952#comment-16170952
]
Hudson commented on AXIS2-5887:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #144 (See
[https://builds.apache.org/job/axis2-1.7/144/])
AXIS2-5887: Merge r1808789 (with changes) to the 1.7 branch. (veithen: rev
1808790)
* (edit) axis2
* (edit) axis2/modules/adb-codegen
* (edit)
axis2/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate-bean.xsl
* (edit) axis2/modules/adb-tests/pom.xml
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5887
* (add) axis2/modules/adb-tests/src/test/resources
* (add) axis2/modules/adb-tests/src/test/wsdl/AXIS2-5887.wsdl
> Parsing of response ends up in a IllegalStateException (attribute type
> accessed in illegal event!)
> --
>
> Key: AXIS2-5887
> URL: https://issues.apache.org/jira/browse/AXIS2-5887
> Project: Axis2
> Issue Type: Bug
> Components: codegen, wsdl
>Affects Versions: 1.7.6
> Environment: Windows 10, Java 1.8.0_131
>Reporter: Carl-Ferdinand Böhm
> Fix For: 1.7.7
>
> Attachments: getOrdersByStatus_response.xml, Orders.java, xtc_wsdl.xml
>
>
> Hello there,
> we are using AXIS2 to generate and use ServiceStubs to handle SOAP
> webservices.
> We upgraded AXIS2 from 1.6.4 to 1.7.6.
> After that we generated a new ServiceStub via WSDL2Java based on the
> following command:
> {code:java}
> wsdl2java -uri xtc_wsdl.xml -s -d adb -u -S ./
> {code}
> ([^xtc_wsdl.xml] is attached)
> If we now get the following response from the webservice, the parsing runs
> into a IllegalStateException.
> [^getOrdersByStatus_response.xml]:
> {code:xml}
>
> http://schemas.xmlsoap.org/soap/envelope/;
> xmlns:ns1="webservice/xtc/plugins/Speed4Trade/com">
>
>
>
>
>
>
> {code}
> Error:
> java.lang.IllegalStateException: attribute type accessed in illegal event!
> at
> org.apache.axiom.om.impl.common.serializer.pull.Navigator.getAttributeValue(Navigator.java:507)
> at
> org.apache.axiom.om.impl.common.serializer.pull.PullSerializer.getAttributeValue(PullSerializer.java:261)
> at
> javax.xml.stream.util.StreamReaderDelegate.getAttributeValue(StreamReaderDelegate.java:149)
> at
> com.speed4trade.plugins.xtc.webservice.Order$Factory.parse(Order.java:671)
> at
> com.speed4trade.plugins.xtc.webservice.Orders$Factory.parse(Orders.java:428)
> at
> com.speed4trade.plugins.xtc.webservice.GetOrdersByStatusResponse$Factory.parse(GetOrdersByStatusResponse.java:389)
> at
> com.speed4trade.plugins.xtc.webservice.XtcServiceStub.fromOM(XtcServiceStub.java:5906)
> ... 7 more
> I have debugged the Stub and compared it to the old one of version 1.6.4.
> I noticed here a code change caused by a change in the XSL template
> [https://github.com/apache/axis2-java/commit/26d78d25e60183c14d901139ad3cdce432e393d0]:
> ADBBeanTemplate-bean.xsl, line 2190
> This generates now this statement in the [^Orders.java]:
> {code:java}
> if ((reader.isStartElement() &&
> new javax.xml.namespace.QName("", "orders").equals(
> reader.getName())) ||
> new javax.xml.namespace.QName("", "orders").equals(
> reader.getName())) {...}
> {code}
> Is it possible that this if-statement is not correct?
> Thanks for considering my request.
--
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-5887) Parsing of response ends up in a IllegalStateException (attribute type accessed in illegal event!)
[
https://issues.apache.org/jira/browse/AXIS2-5887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170901#comment-16170901
]
Hudson commented on AXIS2-5887:
---
SUCCESS: Integrated in Jenkins build Axis2 #3833 (See
[https://builds.apache.org/job/Axis2/3833/])
AXIS2-5887: Roll back bogus change in ADBBeanTemplate-bean.xsl introduced in
r1536050. (veithen: rev 1808789)
* (edit)
axis2/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate-bean.xsl
* (edit) axis2/modules/adb-tests/pom.xml
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5887
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5887/ParseTest.java
* (add) axis2/modules/adb-tests/src/test/resources
* (add) axis2/modules/adb-tests/src/test/resources/org
* (add) axis2/modules/adb-tests/src/test/resources/org/apache
* (add) axis2/modules/adb-tests/src/test/resources/org/apache/axis2
* (add) axis2/modules/adb-tests/src/test/resources/org/apache/axis2/databinding
* (add)
axis2/modules/adb-tests/src/test/resources/org/apache/axis2/databinding/axis2_5887
* (add)
axis2/modules/adb-tests/src/test/resources/org/apache/axis2/databinding/axis2_5887/getOrdersByStatus_response.xml
* (add) axis2/modules/adb-tests/src/test/wsdl/AXIS2-5887.wsdl
> Parsing of response ends up in a IllegalStateException (attribute type
> accessed in illegal event!)
> --
>
> Key: AXIS2-5887
> URL: https://issues.apache.org/jira/browse/AXIS2-5887
> Project: Axis2
> Issue Type: Bug
> Components: codegen, wsdl
>Affects Versions: 1.7.6
> Environment: Windows 10, Java 1.8.0_131
>Reporter: Carl-Ferdinand Böhm
> Fix For: 1.7.7
>
> Attachments: getOrdersByStatus_response.xml, Orders.java, xtc_wsdl.xml
>
>
> Hello there,
> we are using AXIS2 to generate and use ServiceStubs to handle SOAP
> webservices.
> We upgraded AXIS2 from 1.6.4 to 1.7.6.
> After that we generated a new ServiceStub via WSDL2Java based on the
> following command:
> {code:java}
> wsdl2java -uri xtc_wsdl.xml -s -d adb -u -S ./
> {code}
> ([^xtc_wsdl.xml] is attached)
> If we now get the following response from the webservice, the parsing runs
> into a IllegalStateException.
> [^getOrdersByStatus_response.xml]:
> {code:xml}
>
> http://schemas.xmlsoap.org/soap/envelope/;
> xmlns:ns1="webservice/xtc/plugins/Speed4Trade/com">
>
>
>
>
>
>
> {code}
> Error:
> java.lang.IllegalStateException: attribute type accessed in illegal event!
> at
> org.apache.axiom.om.impl.common.serializer.pull.Navigator.getAttributeValue(Navigator.java:507)
> at
> org.apache.axiom.om.impl.common.serializer.pull.PullSerializer.getAttributeValue(PullSerializer.java:261)
> at
> javax.xml.stream.util.StreamReaderDelegate.getAttributeValue(StreamReaderDelegate.java:149)
> at
> com.speed4trade.plugins.xtc.webservice.Order$Factory.parse(Order.java:671)
> at
> com.speed4trade.plugins.xtc.webservice.Orders$Factory.parse(Orders.java:428)
> at
> com.speed4trade.plugins.xtc.webservice.GetOrdersByStatusResponse$Factory.parse(GetOrdersByStatusResponse.java:389)
> at
> com.speed4trade.plugins.xtc.webservice.XtcServiceStub.fromOM(XtcServiceStub.java:5906)
> ... 7 more
> I have debugged the Stub and compared it to the old one of version 1.6.4.
> I noticed here a code change caused by a change in the XSL template
> [https://github.com/apache/axis2-java/commit/26d78d25e60183c14d901139ad3cdce432e393d0]:
> ADBBeanTemplate-bean.xsl, line 2190
> This generates now this statement in the [^Orders.java]:
> {code:java}
> if ((reader.isStartElement() &&
> new javax.xml.namespace.QName("", "orders").equals(
> reader.getName())) ||
> new javax.xml.namespace.QName("", "orders").equals(
> reader.getName())) {...}
> {code}
> Is it possible that this if-statement is not correct?
> Thanks for considering my request.
--
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-5884) Change parameter "Description" to lower-case for service.xml.
[ https://issues.apache.org/jira/browse/AXIS2-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160490#comment-16160490 ] Hudson commented on AXIS2-5884: --- SUCCESS: Integrated in Jenkins build Axis2 #3829 (See [https://builds.apache.org/job/Axis2/3829/]) AXIS2-5884: Allow both 'description' and 'Description' in service.xml and module.xml files. (veithen: rev 1807970) * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/DeploymentConstants.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ModuleBuilder.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ServiceBuilder.java * (edit) axis2/modules/samples/json/src/META-INF/services.xml * (edit) axis2/src/site/xdoc/docs/axis2config.xml * (edit) axis2/systests/webapp-tests/src/test/java/org/apache/axis2/webapp/AxisAdminServletITCase.java * (edit) axis2/systests/webapp-tests/src/test/java/org/apache/axis2/webapp/AxisServletITCase.java > Change parameter "Description" to lower-case for service.xml. > - > > Key: AXIS2-5884 > URL: https://issues.apache.org/jira/browse/AXIS2-5884 > Project: Axis2 > Issue Type: Improvement > Components: deployment >Affects Versions: 1.7.6 >Reporter: Thorsten Schöning >Priority: Minor > > Because of AXIS2-5881 I had a look at my own Axis2 services and recognized > that their description is wrong and is the service name instead of what is > defined in the service.xml file. The problem was simply using "description" > instead of "Description" and the latter is documented, so I must have simply > overlooked the different spelling. > http://axis.apache.org/axis2/java/core/docs/axis2config.html#Service_Configuration > So why not change this configuration to lower case to be in-line with all > other configs in this file and with most other configs as well? > Searching through the Axis2 codebase reveals that "description" is hard coded > at some places already and I even found service.xml files in tests where > "description" is used, so are wrong in theory. The only environment where > "Description" seems to make sense is module.xml, which uses "InFlow", > "OutFlow" etc. as well. > So we can change the value of TAG_DESCRIPTION to be lower case and hard-code > something for modules or keep TAG_DESCRIPTION as it is and hard code a lower > case variant for service.xml or simply use "description" for all, which > wouldn't like that right in module.xml anymore... > What do you prefer? -- 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-5883) Generation of apidocs fails on Windows.
[ https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160401#comment-16160401 ] Hudson commented on AXIS2-5883: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #143 (See [https://builds.apache.org/job/axis2-1.7/143/]) AXIS2-5883: Merge r1807941 and r1807943 to the 1.7 branch. (veithen: rev 1807954) * (edit) axis2 * (edit) axis2/apidocs/pom.xml * (edit) axis2/pom.xml > Generation of apidocs fails on Windows. > --- > > Key: AXIS2-5883 > URL: https://issues.apache.org/jira/browse/AXIS2-5883 > Project: Axis2 > Issue Type: Bug > Components: documentation >Affects Versions: 1.7.6 > Environment: Windows 10 Pro x86-64 >Reporter: Thorsten Schöning >Priority: Minor > Attachments: MJAVADOC-469.patch > > > Generation of the project "apidocs" fails on Windows in case of spaces in > paths and because of a bug in "maven-javadoc-plugin": That plugin is writing > argument files for Javadoc, but is missing to escape backslashs in paths. > Javadoc is reading the paths from the argument file 1:1 and introduces wrong > characters, like a tab for "\t" in path which really is "...\tschoening". > This is already documented against the plugin: > https://issues.apache.org/jira/browse/MJAVADOC-469 > The attached patch is adding quotes to the command line args and working > around the problem of the maven plugin by doubling backslashes on it's own so > that the needed amount of backslashes is available in the argument file. -- 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-5883) Generation of apidocs fails on Windows.
[ https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160355#comment-16160355 ] Hudson commented on AXIS2-5883: --- SUCCESS: Integrated in Jenkins build Axis2 #3826 (See [https://builds.apache.org/job/Axis2/3826/]) AXIS2-5883: Add change missing in r1807941. (veithen: rev 1807943) * (edit) axis2/pom.xml AXIS2-5883: Fix site generation failure on Windows. Patch provided by Thorsten Schöning. (veithen: rev 1807941) * (edit) axis2/apidocs/pom.xml > Generation of apidocs fails on Windows. > --- > > Key: AXIS2-5883 > URL: https://issues.apache.org/jira/browse/AXIS2-5883 > Project: Axis2 > Issue Type: Bug > Components: documentation >Affects Versions: 1.7.6 > Environment: Windows 10 Pro x86-64 >Reporter: Thorsten Schöning >Priority: Minor > Attachments: MJAVADOC-469.patch > > > Generation of the project "apidocs" fails on Windows in case of spaces in > paths and because of a bug in "maven-javadoc-plugin": That plugin is writing > argument files for Javadoc, but is missing to escape backslashs in paths. > Javadoc is reading the paths from the argument file 1:1 and introduces wrong > characters, like a tab for "\t" in path which really is "...\tschoening". > This is already documented against the plugin: > https://issues.apache.org/jira/browse/MJAVADOC-469 > The attached patch is adding quotes to the command line args and working > around the problem of the maven plugin by doubling backslashes on it's own so > that the needed amount of backslashes is available in the argument file. -- 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-5885) Generating apidocs fails with Java 8.
[
https://issues.apache.org/jira/browse/AXIS2-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160334#comment-16160334
]
Hudson commented on AXIS2-5885:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #142 (See
[https://builds.apache.org/job/axis2-1.7/142/])
AXIS2-5885: Merge r1807837 to the 1.7 branch. (veithen: rev 1807942)
* (edit) axis2
* (edit) axis2/apidocs/pom.xml
* (edit) axis2/pom.xml
> Generating apidocs fails with Java 8.
> -
>
> Key: AXIS2-5885
> URL: https://issues.apache.org/jira/browse/AXIS2-5885
> Project: Axis2
> Issue Type: Bug
> Components: documentation
>Affects Versions: 1.8.0
> Environment: Windows 10 x86-64, JDK 1.8
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: AXIS2-5885 01.patch, AXIS2-5885 02.patch
>
>
> The project "apidocs" can not be build by default using Java 8 because of a
> lot of errors in the Javadocs and the new "javadoc" errors on those problems
> instead of warning/ignoring them. A workaround is to add
> "false" to the configuration, in that case the
> errors are turned to warnings and the build succeeds.
> Most of the errors are pretty easy, like wrong HTML etc. and one just needs
> to fix what and where "javadoc" says. But some errors are related to missing
> packages and might be a hint to classpath issues or some problems with
> available packages in the build?
> https://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
> {CODE}
> [ERROR] Exit code: 1 - C:\Users\tschoening\Documents\Eclipse\Java
> Axis2\axis2\apidocs\target\distro-javadoc-sources\org.apache.axis2.osgi-1.8.0-SNAPSHOT-sources\org\apache\axis2\extensions\osgi\util\Logger.java:4:
> error: package org.osgi.service.log does not exist
> [ERROR] import org.osgi.service.log.LogService;
> [ERROR] ^
> {CODE}
> {CODE}
> [ERROR] C:\Users\tschoening\Documents\Eclipse\Java
> Axis2\axis2\apidocs\target\distro-javadoc-sources\axis2-adb-1.8.0-SNAPSHOT-sources\org\apache\axis2\databinding\ADBDataSource.java:44:
> warning: no description for @param
> [ERROR] * @param xmlWriter
> [ERROR] ^
> {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] [Commented] (AXIS2-5877) XML External Entity Injections
[
https://issues.apache.org/jira/browse/AXIS2-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159617#comment-16159617
]
Hudson commented on AXIS2-5877:
---
SUCCESS: Integrated in Jenkins build Axis2 #3825 (See
[https://builds.apache.org/job/Axis2/3825/])
AXIS2-5877: Move XSLTTemplateProcessor to axis2-codegen because it is not used
at runtime. (veithen: rev 1807840)
* (add)
axis2/modules/codegen/src/org/apache/axis2/util/XSLTTemplateProcessor.java
* (delete)
axis2/modules/kernel/src/org/apache/axis2/util/XSLTTemplateProcessor.java
> XML External Entity Injections
> --
>
> Key: AXIS2-5877
> URL: https://issues.apache.org/jira/browse/AXIS2-5877
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
> Labels: security
> Attachments: xxe1.png, xxe2.png
>
>
> XML parser configured in ConvertUtils.java:225 does not prevent nor limit
> external entities resolution. This can expose the parser to an XML External
> Entities attack.
> Proposed fix: Enable where TransformerFactory is used always the secure
> processing feature:
> {code:java}
> public static TransformerFactory createTransformerFactory() {
> TransformerFactory factory = TransformerFactory.newInstance();
> try {
>
> factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
> }
> catch (TransformerConfigurationException e) {
> throw new IllegalStateException(e);
> }
> return factory;
> }
> {code}
> Also in XSLTTemplateProcessor.java:147 (XSLT Injection) and other locations
> where this and DocumentBuilderFactory is handled wrong. See attached
> screenshots.
--
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-5885) Generating apidocs fails with Java 8.
[
https://issues.apache.org/jira/browse/AXIS2-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159618#comment-16159618
]
Hudson commented on AXIS2-5885:
---
SUCCESS: Integrated in Jenkins build Axis2 #3825 (See
[https://builds.apache.org/job/Axis2/3825/])
AXIS2-5885: Fix site generation failure in apidocs. The problem was that the
additionalparam (with -Xdoclint:none) set by the Maven profile was overridden
in the site-javadoc execution. (veithen: rev 1807837)
* (edit) axis2/apidocs/pom.xml
* (edit) axis2/pom.xml
> Generating apidocs fails with Java 8.
> -
>
> Key: AXIS2-5885
> URL: https://issues.apache.org/jira/browse/AXIS2-5885
> Project: Axis2
> Issue Type: Bug
> Components: documentation
>Affects Versions: 1.8.0
> Environment: Windows 10 x86-64, JDK 1.8
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: AXIS2-5885 01.patch, AXIS2-5885 02.patch
>
>
> The project "apidocs" can not be build by default using Java 8 because of a
> lot of errors in the Javadocs and the new "javadoc" errors on those problems
> instead of warning/ignoring them. A workaround is to add
> "false" to the configuration, in that case the
> errors are turned to warnings and the build succeeds.
> Most of the errors are pretty easy, like wrong HTML etc. and one just needs
> to fix what and where "javadoc" says. But some errors are related to missing
> packages and might be a hint to classpath issues or some problems with
> available packages in the build?
> https://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
> {CODE}
> [ERROR] Exit code: 1 - C:\Users\tschoening\Documents\Eclipse\Java
> Axis2\axis2\apidocs\target\distro-javadoc-sources\org.apache.axis2.osgi-1.8.0-SNAPSHOT-sources\org\apache\axis2\extensions\osgi\util\Logger.java:4:
> error: package org.osgi.service.log does not exist
> [ERROR] import org.osgi.service.log.LogService;
> [ERROR] ^
> {CODE}
> {CODE}
> [ERROR] C:\Users\tschoening\Documents\Eclipse\Java
> Axis2\axis2\apidocs\target\distro-javadoc-sources\axis2-adb-1.8.0-SNAPSHOT-sources\org\apache\axis2\databinding\ADBDataSource.java:44:
> warning: no description for @param
> [ERROR] * @param xmlWriter
> [ERROR] ^
> {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] [Commented] (AXIS2-5876) axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on the Java Build Path status.tag
[
https://issues.apache.org/jira/browse/AXIS2-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159542#comment-16159542
]
Hudson commented on AXIS2-5876:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #141 (See
[https://builds.apache.org/job/axis2-1.7/141/])
AXIS2-5876: Merge r1807643 to the 1.7 branch. (veithen: rev 1807838)
* (edit) axis2
* (edit) axis2/modules/webapp/pom.xml
> axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was
> not found on the Java Build Path status.tag
>
>
> Key: AXIS2-5876
> URL: https://issues.apache.org/jira/browse/AXIS2-5876
> Project: Axis2
> Issue Type: Bug
> Components: modules
>Affects Versions: 1.7.6, 1.8.0
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
> Attachments: missing jsp-api.patch
>
>
> After importing trunk into Eclipse using maven-eclipse-plugin, I got the
> following error. This could easily be resolved by adding jsp-api to the
> pom.xml, like in the attached patch. That way the Jar is added to the
> classpath in Eclipse, provided by Maven and this resolves the error message.
> Please consider patching current trunk and 1.7, as the same problem seems to
> be present in both.
> {QUOTE}
> The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on
> the Java Build Path status.tag
> /axis2-webapp/src/main/webapp/WEB-INF/tags line 1 JSP Problem
> {QUOTE}
--
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-5876) axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on the Java Build Path status.tag
[
https://issues.apache.org/jira/browse/AXIS2-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157739#comment-16157739
]
Hudson commented on AXIS2-5876:
---
SUCCESS: Integrated in Jenkins build Axis2 #3823 (See
[https://builds.apache.org/job/Axis2/3823/])
AXIS2-5876: Add dependency on jsp-api in provided scope to make Eclipse happy.
Patch provided by Thorsten Schöning. (veithen: rev 1807643)
* (edit) axis2/modules/webapp/pom.xml
> axis2-webapp: The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was
> not found on the Java Build Path status.tag
>
>
> Key: AXIS2-5876
> URL: https://issues.apache.org/jira/browse/AXIS2-5876
> Project: Axis2
> Issue Type: Bug
> Components: modules
>Affects Versions: 1.7.6, 1.8.0
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
> Attachments: missing jsp-api.patch
>
>
> After importing trunk into Eclipse using maven-eclipse-plugin, I got the
> following error. This could easily be resolved by adding jsp-api to the
> pom.xml, like in the attached patch. That way the Jar is added to the
> classpath in Eclipse, provided by Maven and this resolves the error message.
> Please consider patching current trunk and 1.7, as the same problem seems to
> be present in both.
> {QUOTE}
> The superclass "javax.servlet.jsp.tagext.SimpleTagSupport" was not found on
> the Java Build Path status.tag
> /axis2-webapp/src/main/webapp/WEB-INF/tags line 1 JSP Problem
> {QUOTE}
--
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-5872) pom.xml for axis2-webapp is incompatible with Eclipse
[
https://issues.apache.org/jira/browse/AXIS2-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149807#comment-16149807
]
Hudson commented on AXIS2-5872:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #140 (See
[https://builds.apache.org/job/axis2-1.7/140/])
AXIS2-5872: Merge r1806719 to the 1.7 branch. (veithen: rev 1806876)
* (edit) axis2
* (edit) axis2/modules/webapp/pom.xml
> pom.xml for axis2-webapp is incompatible with Eclipse
> -
>
> Key: AXIS2-5872
> URL: https://issues.apache.org/jira/browse/AXIS2-5872
> Project: Axis2
> Issue Type: Bug
> Components: modules
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, JDK 1.8 x86-64, Eclipse Oxygen
> Release (4.7.0),
> m2e - Maven Integration for Eclipse (includes Incubating components)
> 1.8.0.20170516-2043
> m2e - slf4j over logback logging (Optional) 1.8.0.20170516-2043
> m2e connector for build-helper-maven-plugin 0.15.0.201207090124
> m2e connector for maven-remote-resources-plugin 0.0.1.201411160138
> m2e connector for the Maven Dependency Plugin 0.0.4.201409291703
> m2e-wtp - JAX-RS configurator for WTP (Optional) 1.3.2.20170517-2015
> m2e-wtp - JPA configurator for WTP (Optional) 1.3.2.20170517-2015
> m2e-wtp - JSF configurator for WTP (Optional) 1.3.2.20170517-2015
> m2e-wtp - Maven Integration for WTP 1.3.2.20170517-2015
>Reporter: Thorsten Schöning
> Attachments: axis2-webapp Eclipse compat.patch, Eclipse build path
> error axis2-webapp.png
>
>
> Im trying to get the current trunk to work in Eclipse using Maven plugins and
> following the guide on the project site by essentially checking out and
> executing "mvn -DskipTests=true install eclipse:eclipse". This works mostly,
> but one problem is the created build path for the project axis2-webapp.
> pom.xml of that project references the resource ".../kernel/conf", that
> resource is transferred to be an Eclipse source folder and the problem with
> those is that they can't be outside the current project easily. While one is
> able to link arbitrary source folders into the project, that's not what the
> Maven plugin is doing. Instead it translates the path to some absolute one
> and simply adds it as is, but Eclipse uses it as some relative path because
> by design all those source folder paths need to be relativ to the current
> project, without leaving it. Things like ".." don't work as well in the
> dialogs of Eclipse.
> The file ".classpath" of Eclipse contains the following entry and you can see
> how Eclipse uses that in the attached screenshots, it simply doesn't work.
> Removing the resource of pom.xml resolves the issue, but I guess it's there
> for some reason, you surely need the properties files of "../kernel/conf".
> {QUOTE}
> excluding="**/*.java"/>
> {QUOTE}
> So how about putting the properties files directly in the "conf" folder of
> axis2-webapp instead of referencing them? This would make Eclipse user's life
> much easier.
> While I know that copying those files is a bit bad, the only other
> alternatives are svn:externals or symlinks on file system level.
> svn:externals don't work with GitHub[1], but a lot of people seem to use your
> project mirror there, and symlinks on file system level are most likely only
> implemented in GIT/SVN-clients for Linux, not Windows. Windows-Eclipse users
> like me would need another workaround for that problem. :-) In the end, it
> doesn't look like those properties file change that often...
> Would be nice if you could fix this somehow. The only workaround I have
> currently is to remove that source folder manually and/or add the needed one
> using other Eclipse mechanisms. But I guess you would prefer as well that
> creating project files etc. works automatically as much as possible.
> [1]:
> https://help.github.com/articles/subversion-properties-supported-by-github/
--
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-5872) pom.xml for axis2-webapp is incompatible with Eclipse
[
https://issues.apache.org/jira/browse/AXIS2-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147854#comment-16147854
]
Hudson commented on AXIS2-5872:
---
SUCCESS: Integrated in Jenkins build Axis2 #3822 (See
[https://builds.apache.org/job/Axis2/3822/])
AXIS2-5872: Make the axis2-webapp POM compatible with Eclipse. (veithen: rev
1806719)
* (edit) axis2/modules/webapp/pom.xml
> pom.xml for axis2-webapp is incompatible with Eclipse
> -
>
> Key: AXIS2-5872
> URL: https://issues.apache.org/jira/browse/AXIS2-5872
> Project: Axis2
> Issue Type: Bug
> Components: modules
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, JDK 1.8 x86-64, Eclipse Oxygen
> Release (4.7.0),
> m2e - Maven Integration for Eclipse (includes Incubating components)
> 1.8.0.20170516-2043
> m2e - slf4j over logback logging (Optional) 1.8.0.20170516-2043
> m2e connector for build-helper-maven-plugin 0.15.0.201207090124
> m2e connector for maven-remote-resources-plugin 0.0.1.201411160138
> m2e connector for the Maven Dependency Plugin 0.0.4.201409291703
> m2e-wtp - JAX-RS configurator for WTP (Optional) 1.3.2.20170517-2015
> m2e-wtp - JPA configurator for WTP (Optional) 1.3.2.20170517-2015
> m2e-wtp - JSF configurator for WTP (Optional) 1.3.2.20170517-2015
> m2e-wtp - Maven Integration for WTP 1.3.2.20170517-2015
>Reporter: Thorsten Schöning
> Attachments: axis2-webapp Eclipse compat.patch, Eclipse build path
> error axis2-webapp.png
>
>
> Im trying to get the current trunk to work in Eclipse using Maven plugins and
> following the guide on the project site by essentially checking out and
> executing "mvn -DskipTests=true install eclipse:eclipse". This works mostly,
> but one problem is the created build path for the project axis2-webapp.
> pom.xml of that project references the resource ".../kernel/conf", that
> resource is transferred to be an Eclipse source folder and the problem with
> those is that they can't be outside the current project easily. While one is
> able to link arbitrary source folders into the project, that's not what the
> Maven plugin is doing. Instead it translates the path to some absolute one
> and simply adds it as is, but Eclipse uses it as some relative path because
> by design all those source folder paths need to be relativ to the current
> project, without leaving it. Things like ".." don't work as well in the
> dialogs of Eclipse.
> The file ".classpath" of Eclipse contains the following entry and you can see
> how Eclipse uses that in the attached screenshots, it simply doesn't work.
> Removing the resource of pom.xml resolves the issue, but I guess it's there
> for some reason, you surely need the properties files of "../kernel/conf".
> {QUOTE}
> excluding="**/*.java"/>
> {QUOTE}
> So how about putting the properties files directly in the "conf" folder of
> axis2-webapp instead of referencing them? This would make Eclipse user's life
> much easier.
> While I know that copying those files is a bit bad, the only other
> alternatives are svn:externals or symlinks on file system level.
> svn:externals don't work with GitHub[1], but a lot of people seem to use your
> project mirror there, and symlinks on file system level are most likely only
> implemented in GIT/SVN-clients for Linux, not Windows. Windows-Eclipse users
> like me would need another workaround for that problem. :-) In the end, it
> doesn't look like those properties file change that often...
> Would be nice if you could fix this somehow. The only workaround I have
> currently is to remove that source folder manually and/or add the needed one
> using other Eclipse mechanisms. But I guess you would prefer as well that
> creating project files etc. works automatically as much as possible.
> [1]:
> https://help.github.com/articles/subversion-properties-supported-by-github/
--
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-5873) "Apache Axis2 - Distribution" doesn't build on Windows
[
https://issues.apache.org/jira/browse/AXIS2-5873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145513#comment-16145513
]
Hudson commented on AXIS2-5873:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #139 (See
[https://builds.apache.org/job/axis2-1.7/139/])
AXIS2-5873: Merge r1806581 to the 1.7 branch. (veithen: rev 1806594)
* (edit) axis2
* (edit) axis2/modules/distribution/pom.xml
> "Apache Axis2 - Distribution" doesn't build on Windows
> --
>
> Key: AXIS2-5873
> URL: https://issues.apache.org/jira/browse/AXIS2-5873
> Project: Axis2
> Issue Type: Bug
> Components: modules
> Environment: Windows 10 Pro x86-64, JDK 1.8 x86-64
>Reporter: Thorsten Schöning
> Attachments: support Windows paths for distribution.patch
>
>
> "distribution/pom.xml" contains embedded Groovy and uses Maven build
> properties to access some paths, which resolve to some string using "\" on
> Windows. The problem is that these strings contain only one "\", which is
> valid in XML, but are forwarded to Groovy code, where those strings become
> invalid.
> {CODE}
> [INFO] --- gmavenplus-plugin:1.5:execute (check-webapp-content) @
> distribution ---
> [DEBUG] Configuring mojo
> org.codehaus.gmavenplus:gmavenplus-plugin:1.5:execute from plugin realm
> ClassRealm[plugin>org.codehaus.gmavenplus:gmavenplus-plugin:1.5, parent:
> sun.misc.Launcher$AppClassLoader@5c647e05]
> [DEBUG] Configuring mojo
> 'org.codehaus.gmavenplus:gmavenplus-plugin:1.5:execute' with
> include-project-test-dependencies configurator -->
> [DEBUG] (f) allowSystemExits = false
> [DEBUG] (f) bindPropertiesToSeparateVariables = true
> [DEBUG] (f) continueExecuting = false
> [DEBUG] (f) mojoExecution =
> org.codehaus.gmavenplus:gmavenplus-plugin:1.5:execute {execution:
> check-webapp-content}
> [DEBUG] (f) pluginArtifacts = [...]
> [DEBUG] (f) project = MavenProject:
> org.apache.axis2:distribution:1.8.0-SNAPSHOT @
> C:\Users\tschoening\Documents\Eclipse\Java
> Axis2\axis2\modules\distribution\pom.xml
> [DEBUG] (f) scripts = [import java.util.jar.*
> def jar = new JarInputStream(new
> FileInputStream("C:\Users\tschoening\.m2\repository\org\apache\axis2\axis2-webapp\1.8.0-SNAPSHOT\axis2-webapp-1.8.0-SNAPSHOT.war"))
> def expected = new HashSet()
> def entry
> while(entry = jar.nextJarEntry) {
> expected.add(entry.name)
> }
> jar.close()
> jar = new JarInputStream(new
> FileInputStream("C:\Users\tschoening\Documents\Eclipse\Java
> Axis2\axis2\modules\distribution\target/axis2-1.8.0-SNAPSHOT/dist/axis2.war"))
> while(entry = jar.nextJarEntry) {
> if (!expected.remove(entry.name)) {
> throw new Error("Unexpected entry
> in Web app: " + entry.name)
> }
> }
> if (!expected.empty) {
> throw new Error("Missing entries in
> Web app: " + expected)
> }
> jar.close()]
> [DEBUG] (f) session = org.apache.maven.execution.MavenSession@3d904e9c
> [DEBUG] (f) skipTests = false
> [DEBUG] (f) sourceEncoding = UTF-8
> [DEBUG] -- end configuration --
> [INFO] Using Groovy 2.4.4 to perform execute.
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Axis2 - Distribution FAILURE [ 49.237
> s]
> [INFO] Samples parent POM . SKIPPED
> [INFO] JAXWS - Starting from Java Example . SKIPPED
> [INFO] JAXWS Addressbook Service .. SKIPPED
> [INFO] JAXWS Calculator Service ... SKIPPED
> [INFO] JAXWS Interop Sample ... SKIPPED
> [INFO] JAXWS Samples - Echo, Ping, MTOM ... SKIPPED
> [INFO] Apache Axis2 -JAXWS Version Service SKIPPED
> [INFO] Apache Axis2 Transport-HTTPS sample SKIPPED
> [INFO] httpsService ... SKIPPED
> [INFO] httpsClient SKIPPED
> [INFO] Apache Axis2 Transport-JMS sample .. SKIPPED
> [INFO] jmsService . SKIPPED
> [INFO] databinding-tests .. SKIPPED
> [INFO] jaxbri-tests
[jira] [Commented] (AXIS2-5865) Missing JSTL files on axis2-1.7.6-bin.zip
[
https://issues.apache.org/jira/browse/AXIS2-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145405#comment-16145405
]
Hudson commented on AXIS2-5865:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #138 (See
[https://builds.apache.org/job/axis2-1.7/138/])
AXIS2-5865: Merge r1806577 to the 1.7 branch. (veithen: rev 1806591)
* (edit) axis2
* (edit) axis2/modules/distribution/src/main/assembly/bin-assembly.xml
* (edit)
axis2/modules/tool/axis2-repo-maven-plugin/src/main/java/org/apache/axis2/maven2/repo/ArchiveDeployer.java
> Missing JSTL files on axis2-1.7.6-bin.zip
> -
>
> Key: AXIS2-5865
> URL: https://issues.apache.org/jira/browse/AXIS2-5865
> Project: Axis2
> Issue Type: Bug
> Components: admin console, samples, build,site
>Affects Versions: 1.7.6
>Reporter: Danilo G. Baio
>Priority: Minor
> Fix For: 1.7.7
>
>
> From the release notes:
> {quote}The JSTL is now packaged into the Axis2 Web application. This fixes
> issues with the Admin consoles on servlet containers that don’t provide the
> JSTL.{quote}
> This was not included in axis2-1.7.6-bin.zip.
> Thank you.
--
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-5865) Missing JSTL files on axis2-1.7.6-bin.zip
[
https://issues.apache.org/jira/browse/AXIS2-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145233#comment-16145233
]
Hudson commented on AXIS2-5865:
---
UNSTABLE: Integrated in Jenkins build Axis2 #3820 (See
[https://builds.apache.org/job/Axis2/3820/])
AXIS2-5865: Fix a couple of issues that occur when building only parts of the
project (and dependencies are pulled from snapshot repositories). (veithen: rev
1806577)
* (edit) axis2/modules/distribution/src/main/assembly/bin-assembly.xml
* (edit)
axis2/modules/tool/axis2-repo-maven-plugin/src/main/java/org/apache/axis2/maven2/repo/ArchiveDeployer.java
> Missing JSTL files on axis2-1.7.6-bin.zip
> -
>
> Key: AXIS2-5865
> URL: https://issues.apache.org/jira/browse/AXIS2-5865
> Project: Axis2
> Issue Type: Bug
> Components: admin console, samples, build,site
>Affects Versions: 1.7.6
>Reporter: Danilo G. Baio
>Priority: Minor
> Fix For: 1.7.7
>
>
> From the release notes:
> {quote}The JSTL is now packaged into the Axis2 Web application. This fixes
> issues with the Admin consoles on servlet containers that don’t provide the
> JSTL.{quote}
> This was not included in axis2-1.7.6-bin.zip.
> Thank you.
--
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-5865) Missing JSTL files on axis2-1.7.6-bin.zip
[
https://issues.apache.org/jira/browse/AXIS2-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143122#comment-16143122
]
Hudson commented on AXIS2-5865:
---
SUCCESS: Integrated in Jenkins build Axis2 #3819 (See
[https://builds.apache.org/job/Axis2/3819/])
AXIS2-5865: Ensure that the Web app produced by webapp/build.xml contains the
same files as the Web app built by Maven. (veithen: rev 1806350)
* (edit) axis2/modules/distribution/pom.xml
* (edit) axis2/modules/distribution/src/main/assembly/bin-assembly.xml
* (edit) axis2/modules/webapp/pom.xml
* (edit) axis2/modules/webapp/scripts/build.xml
* (edit) axis2/systests/webapp-tests/pom.xml
> Missing JSTL files on axis2-1.7.6-bin.zip
> -
>
> Key: AXIS2-5865
> URL: https://issues.apache.org/jira/browse/AXIS2-5865
> Project: Axis2
> Issue Type: Bug
> Components: admin console, samples, build,site
>Affects Versions: 1.7.6
>Reporter: Danilo G. Baio
>Priority: Minor
> Fix For: 1.7.7
>
>
> From the release notes:
> {quote}The JSTL is now packaged into the Axis2 Web application. This fixes
> issues with the Admin consoles on servlet containers that don’t provide the
> JSTL.{quote}
> This was not included in axis2-1.7.6-bin.zip.
> Thank you.
--
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-5865) Missing JSTL files on axis2-1.7.6-bin.zip
[
https://issues.apache.org/jira/browse/AXIS2-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143098#comment-16143098
]
Hudson commented on AXIS2-5865:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #137 (See
[https://builds.apache.org/job/axis2-1.7/137/])
AXIS2-5865: Merge r1806349 and r1806350 (with changes) to the 1.7 branch.
(veithen: rev 1806353)
* (edit) axis2
* (edit) axis2/modules/distribution/pom.xml
* (edit) axis2/modules/distribution/src/main/assembly/bin-assembly.xml
* (edit) axis2/modules/fastinfoset/pom.xml
* (edit) axis2/modules/webapp/pom.xml
* (edit) axis2/modules/webapp/scripts/build.xml
* (edit) axis2/systests/webapp-tests/pom.xml
AXIS2-5865: Merge r1806344 to the 1.7 branch. (veithen: rev 1806352)
* (edit) axis2
* (edit) axis2/modules/kernel/test-resources/deployment/echo/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/invalidservice/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/module1/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/service2/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/serviceModule/build.xml
* (edit)
axis2/modules/tool/axis2-ant-plugin/src/main/java/org/apache/axis2/tool/ant/Java2WSDLTask.java
* (edit) axis2/pom.xml
> Missing JSTL files on axis2-1.7.6-bin.zip
> -
>
> Key: AXIS2-5865
> URL: https://issues.apache.org/jira/browse/AXIS2-5865
> Project: Axis2
> Issue Type: Bug
> Components: admin console, samples, build,site
>Affects Versions: 1.7.6
>Reporter: Danilo G. Baio
>Priority: Minor
> Fix For: 1.7.7
>
>
> From the release notes:
> {quote}The JSTL is now packaged into the Axis2 Web application. This fixes
> issues with the Admin consoles on servlet containers that don’t provide the
> JSTL.{quote}
> This was not included in axis2-1.7.6-bin.zip.
> Thank you.
--
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-5865) Missing JSTL files on axis2-1.7.6-bin.zip
[
https://issues.apache.org/jira/browse/AXIS2-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143070#comment-16143070
]
Hudson commented on AXIS2-5865:
---
SUCCESS: Integrated in Jenkins build Axis2 #3817 (See
[https://builds.apache.org/job/Axis2/3817/])
AXIS2-5865: Update maven-antrun-plugin. (veithen: rev 1806344)
* (edit) axis2/modules/kernel/test-resources/deployment/echo/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/invalidservice/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/module1/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/service2/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/serviceModule/build.xml
* (edit)
axis2/modules/tool/axis2-ant-plugin/src/main/java/org/apache/axis2/tool/ant/Java2WSDLTask.java
* (edit) axis2/pom.xml
> Missing JSTL files on axis2-1.7.6-bin.zip
> -
>
> Key: AXIS2-5865
> URL: https://issues.apache.org/jira/browse/AXIS2-5865
> Project: Axis2
> Issue Type: Bug
> Components: admin console, samples, build,site
>Affects Versions: 1.7.6
>Reporter: Danilo G. Baio
>Priority: Minor
>
> From the release notes:
> {quote}The JSTL is now packaged into the Axis2 Web application. This fixes
> issues with the Admin consoles on servlet containers that don’t provide the
> JSTL.{quote}
> This was not included in axis2-1.7.6-bin.zip.
> Thank you.
--
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-5793) Various tests fail when Axis2 is built using a path with spaces
[ https://issues.apache.org/jira/browse/AXIS2-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142872#comment-16142872 ] Hudson commented on AXIS2-5793: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #135 (See [https://builds.apache.org/job/axis2-1.7/135/]) AXIS2-5793: Merge r1806309 to the 1.7 branch. (veithen: rev 1806313) * (edit) axis2 * (edit) axis2/modules/jaxbri/pom.xml * (edit) axis2/modules/jibx/pom.xml * (edit) axis2/modules/json/pom.xml AXIS2-5793: Merge r1806292 to the 1.7 branch. (veithen: rev 1806311) * (edit) axis2 * (edit) axis2/modules/corba/src/org/apache/axis2/corba/deployer/CorbaDeployer.java * (edit) axis2/modules/java2wsdl/src/org/apache/ws/java2wsdl/Java2WSDLCodegenEngine.java * (edit) axis2/modules/jaxbri/src/main/java/org/apache/axis2/jaxbri/CodeGenerationUtility.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/context/sei/MessageContextService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/jaxb/string/JAXBStringService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/polymorphic/shape/tests/PolymorphicTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/provider/AddressingProviderTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/GorillaDLWProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/ProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/RPCLitSWAProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/RPCProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/soap12/SOAP12EchoService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/rpclit/enumtype/sei/Service.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/rpclit/stringarray/sei/RPCLitStringArrayService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/addnumbers/AddNumbersService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/addnumbershandler/AddNumbersHandlerService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/asyncdoclit/client/AsyncService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/doclitbare/sei/BareDocLitService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/doclitbaremin/sei/BareDocLitMinService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/doclitbarenoarg/sei/BareDocLitNoArgService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/faults/FaultyWebServiceService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/faultsservice/FaultsService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/headershandler/HeadersHandlerService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/nonwrap/sei/DocLitNonWrapService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/parallelasync/server/AsyncService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/resourceinjection/sei/ResourceInjectionService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/stringlist/sei/StringListService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/wrap/sei/DocLitWrapService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/wsgen/client/WSGenService.java * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/framework/JAXWSDeployer.java * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/framework/JAXWSServiceBuilderExtension.java * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/runtime/description/marshal/impl/PackageSetBuilder.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/catalog/MultiRedirectionCatalogTest.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/catalog/XMLCatalogTests.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/client/ClientConfigTests.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/client/ReleaseServiceTests.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/description/DescriptionTestUtils2.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/description/sample/addnumbers/AddNumbersService.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/handler/HandlerResolverTest.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/spi/ClientMetadataHandlerChainTest.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/spi/ClientMetadataTest.java * (edit)
[jira] [Commented] (AXIS2-5793) Various tests fail when Axis2 is built using a path with spaces
[
https://issues.apache.org/jira/browse/AXIS2-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142861#comment-16142861
]
Hudson commented on AXIS2-5793:
---
SUCCESS: Integrated in Jenkins build Axis2 #3814 (See
[https://builds.apache.org/job/Axis2/3814/])
AXIS2-5793: Fix AdminActions so that services can be successfully deployed to a
repository with spaces in its path. Patch provided by Thorsten Schöning.
(veithen: rev 1806305)
* (edit)
axis2/modules/webapp/src/main/java/org/apache/axis2/webapp/AdminActions.java
AXIS2-5793: Add a unit test for the Upload Service feature in the Admin
console. (veithen: rev 1806303)
* (add) axis2/systests/echo
* (add) axis2/systests/echo/pom.xml
* (add) axis2/systests/echo/services.xml
* (add) axis2/systests/echo/src
* (add) axis2/systests/echo/src/main
* (add) axis2/systests/echo/src/main/java
* (add) axis2/systests/echo/src/main/java/org
* (add) axis2/systests/echo/src/main/java/org/apache
* (add) axis2/systests/echo/src/main/java/org/apache/axis2
* (add) axis2/systests/echo/src/main/java/org/apache/axis2/echo
* (add) axis2/systests/echo/src/main/java/org/apache/axis2/echo/EchoService.java
* (edit) axis2/systests/pom.xml
* (edit) axis2/systests/webapp-tests/pom.xml
* (edit)
axis2/systests/webapp-tests/src/test/java/org/apache/axis2/webapp/AxisAdminServletITCase.java
> Various tests fail when Axis2 is built using a path with spaces
> ---
>
> Key: AXIS2-5793
> URL: https://issues.apache.org/jira/browse/AXIS2-5793
> Project: Axis2
> Issue Type: Bug
>Affects Versions: 1.7.3
> Environment: Windows 8.1 x64 Prof., Tomcat 7.0.68, JDK 1.8.0_92 x64
>Reporter: Thorsten Schöning
> Attachments: AXIS2-5793 AdminActions.patch, AXIS2-5793 all
> others.patch, DescriptionTestUtils2.java.patch,
> DescriptionTestUtils.java.patch,
> TEST-org.apache.axis2.jaxws.description.DBCwithReduceWSDLMemoryParmsTests.xml
>
>
> DBCwithReduceWSDLMemoryParmsTests fails when Axis2 is build using a path with
> spaces:
> {CODE}
>classname="org.apache.axis2.jaxws.description.DBCwithReduceWSDLMemoryParmsTests"
> name="testDBCwithReduceWSDLMemoryParms">
> type="junit.framework.AssertionFailedError:">junit.framework.AssertionFailedError:
> null
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertTrue(Assert.java:27)
> at
> org.apache.axis2.jaxws.description.DBCwithReduceWSDLMemoryParmsTests.testDBCwithReduceWSDLMemoryParms(DBCwithReduceWSDLMemoryParmsTests.java:140)
>
> {CODE}
> After enabling logging using log4j the reason is easier to find:
> {CODE}
> 2016-06-25 11:00:36,857 DEBUG
> org.apache.axis2.jaxws.util.WSDL4JWrapper.: WSDL4JWrapper(Definition,
> boolean) entry
> 2016-06-25 11:00:36,857 DEBUG
> org.apache.axis2.wsdl.util.WSDLDefinitionWrapper.:
> WSDLDefinitionWrapper(Definition,URL,boolean) entry
> 2016-06-25 11:00:36,857 DEBUG
> org.apache.axis2.wsdl.util.WSDLWrapperReloadImpl.isReloadable: Enter
> WSDLWrapperReloadImpl.isReloadable(): null
> 2016-06-25 11:00:36,857 DEBUG
> org.apache.axis2.wsdl.util.WSDLWrapperReloadImpl.getExplicitURI:
> WSDLWrapperReloadImpl.getExplicitURI(file:/C:/Users/tschoening/Documents/Eclipse/Java
> Bug 2187/Libs Java
> 3rd/Apache/Axis2/1.7.3/src/modules/metadata/test-resources/wsdl/BindingNamespaceDefaults.wsdl)
>
> 2016-06-25 11:00:36,857 DEBUG
> org.apache.axis2.wsdl.util.WSDLWrapperReloadImpl.isReloadable:
> WSDLWrapperReloadImpl.isReloaded(): [javax.wsdl.WSDLException] error
> [WSDLException: faultCode=WSDLWrapperReloadImpl : :
> java.net.URISyntaxException: Illegal character in path at index 48:
> file:/C:/Users/tschoening/Documents/Eclipse/Java Bug 2187/Libs Java
> 3rd/Apache/Axis2/1.7.3/src/modules/metadata/test-resources/wsdl/BindingNamespaceDefaults.wsdl]
> javax.wsdl.WSDLException: WSDLException: faultCode=WSDLWrapperReloadImpl : :
> java.net.URISyntaxException: Illegal character in path at index 48:
> file:/C:/Users/tschoening/Documents/Eclipse/Java Bug 2187/Libs Java
> 3rd/Apache/Axis2/1.7.3/src/modules/metadata/test-resources/wsdl/BindingNamespaceDefaults.wsdl
> at
> org.apache.axis2.wsdl.util.WSDLWrapperReloadImpl.getExplicitURI(WSDLWrapperReloadImpl.java:1382)
> {CODE}
> The problem is in DescriptionTestUtils.getWSDLURL:
> {CODE}
> wsdlURL = new File(urlString).getAbsoluteFile().toURL();
> {CODE}
> toURL is kown to fail in situations like these:
> {QUOTE}
> Deprecated. This method does not automatically escape characters that are
> illegal in URLs. It is recommended that new code convert an abstract pathname
> into a URL by first converting it into a URI, via the toURI method, and then
> converting the URI into a URL via the URI.toURL method.
> {QUOTE}
>
[jira] [Commented] (AXIS2-5793) Various tests fail when Axis2 is built using a path with spaces
[ https://issues.apache.org/jira/browse/AXIS2-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142824#comment-16142824 ] Hudson commented on AXIS2-5793: --- SUCCESS: Integrated in Jenkins build Axis2 #3813 (See [https://builds.apache.org/job/Axis2/3813/]) AXIS2-5793: Replace usages of deprecated File.getURL(). (veithen: rev 1806292) * (edit) axis2/modules/corba/src/org/apache/axis2/corba/deployer/CorbaDeployer.java * (edit) axis2/modules/java2wsdl/src/org/apache/ws/java2wsdl/Java2WSDLCodegenEngine.java * (edit) axis2/modules/jaxbri/src/main/java/org/apache/axis2/jaxbri/CodeGenerationUtility.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/context/sei/MessageContextService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/jaxb/string/JAXBStringService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/polymorphic/shape/tests/PolymorphicTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/provider/AddressingProviderTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/GorillaDLWProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/ProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/RPCLitSWAProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/RPCProxyTests.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/proxy/soap12/SOAP12EchoService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/rpclit/enumtype/sei/Service.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/rpclit/stringarray/sei/RPCLitStringArrayService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/addnumbers/AddNumbersService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/addnumbershandler/AddNumbersHandlerService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/asyncdoclit/client/AsyncService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/doclitbare/sei/BareDocLitService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/doclitbaremin/sei/BareDocLitMinService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/doclitbarenoarg/sei/BareDocLitNoArgService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/faults/FaultyWebServiceService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/faultsservice/FaultsService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/headershandler/HeadersHandlerService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/nonwrap/sei/DocLitNonWrapService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/parallelasync/server/AsyncService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/resourceinjection/sei/ResourceInjectionService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/stringlist/sei/StringListService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/wrap/sei/DocLitWrapService.java * (edit) axis2/modules/jaxws-integration/test/org/apache/axis2/jaxws/sample/wsgen/client/WSGenService.java * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/framework/JAXWSDeployer.java * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/framework/JAXWSServiceBuilderExtension.java * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/runtime/description/marshal/impl/PackageSetBuilder.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/catalog/MultiRedirectionCatalogTest.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/catalog/XMLCatalogTests.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/client/ClientConfigTests.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/client/ReleaseServiceTests.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/description/DescriptionTestUtils2.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/description/sample/addnumbers/AddNumbersService.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/handler/HandlerResolverTest.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/spi/ClientMetadataHandlerChainTest.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/spi/ClientMetadataTest.java * (edit) axis2/modules/jaxws/test/org/apache/axis2/jaxws/wsdl/schemareader/SchemaReaderTests.java * (edit) axis2/modules/jibx-codegen/src/main/java/org/apache/axis2/jibx/CodeGenerationUtility.java * (edit)
[jira] [Commented] (AXIS2-5871) Cannot deploy Service by .aar on Windows
[ https://issues.apache.org/jira/browse/AXIS2-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140945#comment-16140945 ] Hudson commented on AXIS2-5871: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #134 (See [https://builds.apache.org/job/axis2-1.7/134/]) AXIS2-5871: Merge r1806088 to the 1.7 branch. (veithen: rev 1806103) * (edit) axis2 * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ServiceDeployer.java > Cannot deploy Service by .aar on Windows > > > Key: AXIS2-5871 > URL: https://issues.apache.org/jira/browse/AXIS2-5871 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.7.6 >Reporter: Dmitry Smeliansky > > Similar to AXIS2-5778: > org.apache.axis2.deployment.ServiceDeployer.deployFromUrl uses wrong > separator for building the service name from URL -- 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-5870) XMLPrettyPrinter.prettify uses OS-dependant newlines
[
https://issues.apache.org/jira/browse/AXIS2-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140698#comment-16140698
]
Hudson commented on AXIS2-5870:
---
FAILURE: Integrated in Jenkins build axis2-1.7 #133 (See
[https://builds.apache.org/job/axis2-1.7/133/])
AXIS2-5781, AXIS2-5870: Merge r1779069 and r1779074 to the 1.7 branch.
(veithen: rev 1806081)
* (edit) axis2
* (edit)
axis2/modules/codegen/test/org/apache/axis2/wsdl/codegen/writer/SchemaWriterTest.java
* (edit)
axis2/modules/kernel/test/org/apache/axis2/description/java2wsdl/XMLSchemaTest.java
> XMLPrettyPrinter.prettify uses OS-dependant newlines
>
>
> Key: AXIS2-5870
> URL: https://issues.apache.org/jira/browse/AXIS2-5870
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, JDK 1.7.0_80
>Reporter: Thorsten Schöning
>Priority: Minor
> Attachments: AXIS2-5870 generated.xsd.patch, AXIS2-5870
> InMemory-prettify.patch, printWSDLreference.wsdl.png
>
>
> I'm building version 1.7.6 on Windows checked out using SVN by simply running
> "mvn install" and recognized that after running a successful build some WSDL
> and XSD files in my working copy have changed. TortoiseSVN is saying that the
> only differences in those files are newlines. Two things are interesting
> here: 1. It's not all WSDLs and XSDs, only very few. 2. It's not all newlines
> within the files which get changed, so the result actually is an inconsistent
> mix of Unix and Windows newlines. The changed files are the following:
> modules/codegen/test-resources/schemas/custom_schemas/generated.xsd
> modules/kernel/test-resources/wsdl/printWSDLreference.wsdl
> modules/kernel/test-resources/wsdl/testGenerateInterfaceOperationElement11_WSDL.wsdl
> modules/kernel/test-resources/wsdl/testGenerateInterfaceOperationElement_WSDL.wsdl
> I'm attaching a screenshot where you can see that the license information
> keeps it's newlines, while the XML itself is changed to get Windows newlines.
> "keeps" is actually wrong, though, because during my tests I changed the file
> to Windows newlines only, executed a build and the newlines of the license
> text only were actually changed back to be Unix style.
> So it seems that whatever is changing those files, it actively sets the
> newlines of the license text to Unix style and that of the XML to Windows
> style.
> What seems to be responsible is XMLPrettyPrinter.prettify, because all the
> files changed are going through that function, either directly or using
> XMLSchemaTest.readWSDLFromFile:
> {CODE}
> public String readWSDLFromFile(String path) throws Exception {
> File file=new File(path);
> XMLPrettyPrinter.prettify(file);//this is used to correct
> unnecessary formatting in the file
> return readFile(path);
> }
> {CODE}
> If I simply remove all the code in XMLPrettyPrinter.prettify, all changed
> files are kept as they are. That means by default they keep their Unix style
> newlines and if I change the files to have Windows style newlines they keep
> those. So it really seems that only prettify is introducing the changes I
> see. Without prettify the newlines are as placed in the file and always
> consistent.
> From my point of view running tests or such shouldn't change files under
> version control at all and it seems that most likely it isn't. Else it's
> unnecessary difficult to distinguish those changes from those one is making
> during development. So I would like to suggest to simply remove changing the
> files itself in readWSDLFromFile. It's even very unexpected that a method
> named "read" writes the file before... The applied prettify can easily work
> in memory only if really needed. The other approach would be to make sure
> that all platforms use the same consistent newlines, which is a bit difficult
> for some unknown reason...
> As prettify already relies on Xalan, the latter in theory should easily
> possible by setting the newline character to use:
> {CODE}
> transformer.setOutputProperty("{http://xml.apache.org/xalan}line-separator","\n;);
> {CODE}
> or
> {CODE}
>
> {CODE}
> https://stackoverflow.com/a/12278483/2055163
> Tried that dozen of times, but for some reason it is not working as expected,
> the newline still is Windows style for the XML. I even tried using "___" and
> such nonsense as line separator and in theory that should work as well, but
> didn't. So it seems like the statement itself is ignored for some reason OR
> there's some other thing going on after Xalan which introduces the Windows
> style newlines. Remember that removing the code in prettify fixes the
> problem, so it must be something in there. Xalan itself is working fine,
> because the
[jira] [Commented] (AXIS2-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[
https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140697#comment-16140697
]
Hudson commented on AXIS2-5781:
---
FAILURE: Integrated in Jenkins build axis2-1.7 #133 (See
[https://builds.apache.org/job/axis2-1.7/133/])
AXIS2-5781, AXIS2-5870: Merge r1779069 and r1779074 to the 1.7 branch.
(veithen: rev 1806081)
* (edit) axis2
* (edit)
axis2/modules/codegen/test/org/apache/axis2/wsdl/codegen/writer/SchemaWriterTest.java
* (edit)
axis2/modules/kernel/test/org/apache/axis2/description/java2wsdl/XMLSchemaTest.java
> Maven Build - Module: kernel - generates / modifies file under source-control
> - should build in output directory
>
>
> Key: AXIS2-5781
> URL: https://issues.apache.org/jira/browse/AXIS2-5781
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
>Reporter: Jeff Thomas
>Priority: Minor
>
> Maven Build for axis2-kernel (./modules/kernel/pom.xml).
> In the axis2-kernel Maven Module (and at in at least the axis2-integration
> module as well) test ant-scripts and unit-tests run against the
> "./test-resources" directory instead of the "./target/test-resources"
> directory.
> In the interest of Maven "compliance" the build process should not edit,
> touch or otherwise "dirty" source-code files.
> Examples:
> 1. The Ant-script "test-resources/deployment/service2/build.xml" creates
> temporary directories, generates content, and removes these temporary
> directories directly within the "test-resources" source directory.
> 2. The Unit-Test utility method 'readWSDLFromFile' in XMLSchemaTest creates a
> File reference to a file in "test-resources" and performs the following:
> {code:java}XMLPrettyPrinter.prettify(file);{code}
> This updates (dirties) the input source-file - on my windows build it changes
> the line-endings from Unix to Windows.
> The current Maven POMs already take care of copying the "test-resources"
> directory to "target/test-resources" so all of the required input files and
> ant-scripts are available there. Therefore, the POM ANT "dir" properties and
> the JUnit tests just need to be updated to use these instead of the
> source-code originals.
--
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-5868) Small logic error in axis2-kernel ParameterIncludeImpl.java
[
https://issues.apache.org/jira/browse/AXIS2-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135788#comment-16135788
]
Hudson commented on AXIS2-5868:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #132 (See
[https://builds.apache.org/job/axis2-1.7/132/])
AXIS2-5868: Merge r1805563 to the 1.7 branch. (veithen: rev 1805667)
* (edit) axis2
* (edit)
axis2/modules/kernel/src/org/apache/axis2/description/ParameterIncludeImpl.java
> Small logic error in axis2-kernel ParameterIncludeImpl.java
> ---
>
> Key: AXIS2-5868
> URL: https://issues.apache.org/jira/browse/AXIS2-5868
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.6
>Reporter: Jeff Thomas
>Priority: Minor
>
> Found small bug in the axis2-kernel ParameterIncludeImpl.java.
> The "parameters.put(param.getName(), param)" is always performed twice.
> It looks like a copy/paste mistake when moving the "put" into the try block,
> the original line was not removed and remains outside of the try block. In
> the worst-case scenario, the ConcurrentModificationException would not be
> caught as expected.
> {code:java}
> public void addParameter(Parameter param) {
> if (param != null) {
> synchronized (parameters) {
> parameters.put(param.getName(), param);
> try {
> parameters.put(param.getName(), param);
> } catch (ConcurrentModificationException cme) {
> ...
> }
> }
> {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] [Commented] (AXIS2-5868) Small logic error in axis2-kernel ParameterIncludeImpl.java
[
https://issues.apache.org/jira/browse/AXIS2-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134482#comment-16134482
]
Hudson commented on AXIS2-5868:
---
SUCCESS: Integrated in Jenkins build Axis2 #3807 (See
[https://builds.apache.org/job/Axis2/3807/])
AXIS2-5868: Revert r785716 (because ConcurrentModificationException is only
thrown by iterators produced by HashMap, not by put) and ensure that accesses
to parameters are always properly synchronized. (veithen: rev 1805563)
* (edit)
axis2/modules/kernel/src/org/apache/axis2/description/ParameterIncludeImpl.java
> Small logic error in axis2-kernel ParameterIncludeImpl.java
> ---
>
> Key: AXIS2-5868
> URL: https://issues.apache.org/jira/browse/AXIS2-5868
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.6
>Reporter: Jeff Thomas
>Priority: Minor
>
> Found small bug in the axis2-kernel ParameterIncludeImpl.java.
> The "parameters.put(param.getName(), param)" is always performed twice.
> It looks like a copy/paste mistake when moving the "put" into the try block,
> the original line was not removed and remains outside of the try block. In
> the worst-case scenario, the ConcurrentModificationException would not be
> caught as expected.
> {code:java}
> public void addParameter(Parameter param) {
> if (param != null) {
> synchronized (parameters) {
> parameters.put(param.getName(), param);
> try {
> parameters.put(param.getName(), param);
> } catch (ConcurrentModificationException cme) {
> ...
> }
> }
> {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] [Commented] (AXIS2-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[
https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115388#comment-16115388
]
Hudson commented on AXIS2-5781:
---
SUCCESS: Integrated in Jenkins build Axis2 #3805 (See
[https://builds.apache.org/job/Axis2/3805/])
AXIS2-5781: Create temporary folders under target instead of the module root
directory. (veithen: rev 1804158)
* (edit)
axis2/modules/adb-codegen/test/org/apache/axis2/schema/compile/AbstractSchemaCompilerTester.java
AXIS2-5781: Use the latest releases of axis2-aar-maven-plugin and
axis2-mar-maven-plugin; they no longer attempt to write temporary files in the
module root directory. (veithen: rev 1804157)
* (edit) axis2/pom.xml
> Maven Build - Module: kernel - generates / modifies file under source-control
> - should build in output directory
>
>
> Key: AXIS2-5781
> URL: https://issues.apache.org/jira/browse/AXIS2-5781
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
>Reporter: Jeff Thomas
>Priority: Minor
>
> Maven Build for axis2-kernel (./modules/kernel/pom.xml).
> In the axis2-kernel Maven Module (and at in at least the axis2-integration
> module as well) test ant-scripts and unit-tests run against the
> "./test-resources" directory instead of the "./target/test-resources"
> directory.
> In the interest of Maven "compliance" the build process should not edit,
> touch or otherwise "dirty" source-code files.
> Examples:
> 1. The Ant-script "test-resources/deployment/service2/build.xml" creates
> temporary directories, generates content, and removes these temporary
> directories directly within the "test-resources" source directory.
> 2. The Unit-Test utility method 'readWSDLFromFile' in XMLSchemaTest creates a
> File reference to a file in "test-resources" and performs the following:
> {code:java}XMLPrettyPrinter.prettify(file);{code}
> This updates (dirties) the input source-file - on my windows build it changes
> the line-endings from Unix to Windows.
> The current Maven POMs already take care of copying the "test-resources"
> directory to "target/test-resources" so all of the required input files and
> ant-scripts are available there. Therefore, the POM ANT "dir" properties and
> the JUnit tests just need to be updated to use these instead of the
> source-code originals.
--
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-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[
https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106476#comment-16106476
]
Hudson commented on AXIS2-5781:
---
FAILURE: Integrated in Jenkins build axis2-1.7 #125 (See
[https://builds.apache.org/job/axis2-1.7/125/])
AXIS2-5781: Merge r1787676 to the 1.7 branch. (veithen: rev 1803419)
* (edit) axis2
* (edit) axis2/modules/tool/axis2-aar-maven-plugin/pom.xml
* (edit)
axis2/modules/tool/axis2-aar-maven-plugin/src/main/java/org/apache/axis2/maven2/aar/AarMojo.java
* (edit)
axis2/modules/tool/axis2-aar-maven-plugin/src/main/java/org/apache/axis2/maven2/aar/AbstractAarMojo.java
* (edit) axis2/modules/tool/axis2-idea-plugin/pom.xml
* (edit) axis2/modules/tool/axis2-java2wsdl-maven-plugin/pom.xml
* (edit)
axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/main/java/org/apache/axis2/maven2/java2wsdl/Java2WSDLMojo.java
* (edit) axis2/modules/tool/axis2-mar-maven-plugin/pom.xml
* (edit)
axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/AbstractMarMojo.java
* (edit)
axis2/modules/tool/axis2-mar-maven-plugin/src/main/java/org/apache/axis2/maven2/mar/MarMojo.java
* (edit) axis2/modules/tool/axis2-repo-maven-plugin/pom.xml
* (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin
* (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml
* (edit) axis2/pom.xml
> Maven Build - Module: kernel - generates / modifies file under source-control
> - should build in output directory
>
>
> Key: AXIS2-5781
> URL: https://issues.apache.org/jira/browse/AXIS2-5781
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
>Reporter: Jeff Thomas
>Priority: Minor
>
> Maven Build for axis2-kernel (./modules/kernel/pom.xml).
> In the axis2-kernel Maven Module (and at in at least the axis2-integration
> module as well) test ant-scripts and unit-tests run against the
> "./test-resources" directory instead of the "./target/test-resources"
> directory.
> In the interest of Maven "compliance" the build process should not edit,
> touch or otherwise "dirty" source-code files.
> Examples:
> 1. The Ant-script "test-resources/deployment/service2/build.xml" creates
> temporary directories, generates content, and removes these temporary
> directories directly within the "test-resources" source directory.
> 2. The Unit-Test utility method 'readWSDLFromFile' in XMLSchemaTest creates a
> File reference to a file in "test-resources" and performs the following:
> {code:java}XMLPrettyPrinter.prettify(file);{code}
> This updates (dirties) the input source-file - on my windows build it changes
> the line-endings from Unix to Windows.
> The current Maven POMs already take care of copying the "test-resources"
> directory to "target/test-resources" so all of the required input files and
> ant-scripts are available there. Therefore, the POM ANT "dir" properties and
> the JUnit tests just need to be updated to use these instead of the
> source-code originals.
--
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-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[
https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106472#comment-16106472
]
Hudson commented on AXIS2-5781:
---
SUCCESS: Integrated in Jenkins build Axis2 #3803 (See
[https://builds.apache.org/job/Axis2/3803/])
AXIS2-5781: Don't write temporary files into the source tree. (veithen: rev
1803416)
* (edit) axis2/modules/kernel/test-resources/deployment/echo/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/invalidservice/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/module1/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/service2/build.xml
* (edit) axis2/modules/kernel/test-resources/deployment/serviceModule/build.xml
> Maven Build - Module: kernel - generates / modifies file under source-control
> - should build in output directory
>
>
> Key: AXIS2-5781
> URL: https://issues.apache.org/jira/browse/AXIS2-5781
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
>Reporter: Jeff Thomas
>Priority: Minor
>
> Maven Build for axis2-kernel (./modules/kernel/pom.xml).
> In the axis2-kernel Maven Module (and at in at least the axis2-integration
> module as well) test ant-scripts and unit-tests run against the
> "./test-resources" directory instead of the "./target/test-resources"
> directory.
> In the interest of Maven "compliance" the build process should not edit,
> touch or otherwise "dirty" source-code files.
> Examples:
> 1. The Ant-script "test-resources/deployment/service2/build.xml" creates
> temporary directories, generates content, and removes these temporary
> directories directly within the "test-resources" source directory.
> 2. The Unit-Test utility method 'readWSDLFromFile' in XMLSchemaTest creates a
> File reference to a file in "test-resources" and performs the following:
> {code:java}XMLPrettyPrinter.prettify(file);{code}
> This updates (dirties) the input source-file - on my windows build it changes
> the line-endings from Unix to Windows.
> The current Maven POMs already take care of copying the "test-resources"
> directory to "target/test-resources" so all of the required input files and
> ant-scripts are available there. Therefore, the POM ANT "dir" properties and
> the JUnit tests just need to be updated to use these instead of the
> source-code originals.
--
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-5863) Possible null dereference in ServiceStub class
[
https://issues.apache.org/jira/browse/AXIS2-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106454#comment-16106454
]
Hudson commented on AXIS2-5863:
---
FAILURE: Integrated in Jenkins build axis2-1.7 #124 (See
[https://builds.apache.org/job/axis2-1.7/124/])
AXIS2-5863: Merge r1803414 to the 1.7 branch. (veithen: rev 1803415)
* (edit) axis2
* (edit)
axis2/modules/codegen/src/org/apache/axis2/wsdl/template/java/InterfaceImplementationTemplate.xsl
> Possible null dereference in ServiceStub class
> --
>
> Key: AXIS2-5863
> URL: https://issues.apache.org/jira/browse/AXIS2-5863
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.5
>Reporter: Petr Dvorak
>Priority: Minor
> Labels: security
> Attachments: diff.patch
>
>
> We use Coverity Scan tool to audit our open-source code against security
> vulnerabilities. Possible NullPointerException was detected in Axis2
> generated ServiceStub class code. The issue occurs in following generated
> code:
> {code:java}
> } finally {
> if (_messageContext.getTransportOut() != null) {
> _messageContext.getTransportOut().getSender()
> .cleanup(_messageContext);
> }
> }
> {code}
> In case "_messageContext" is set to null, the if condition throws NPE. Also,
> we can see the path on how this variable value actually may become null, so
> we believe the issue is valid and null check should be present...
> Here are possible implications of the issue from the security perspective:
> http://cwe.mitre.org/data/definitions/476.html
--
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-5863) Possible null dereference in ServiceStub class
[
https://issues.apache.org/jira/browse/AXIS2-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106453#comment-16106453
]
Hudson commented on AXIS2-5863:
---
SUCCESS: Integrated in Jenkins build Axis2 #3802 (See
[https://builds.apache.org/job/Axis2/3802/])
AXIS2-5863: Prevent static code analyzers from flagging a possible null pointer
dereference in generated stubs. (veithen: rev 1803414)
* (edit)
axis2/modules/codegen/src/org/apache/axis2/wsdl/template/java/InterfaceImplementationTemplate.xsl
> Possible null dereference in ServiceStub class
> --
>
> Key: AXIS2-5863
> URL: https://issues.apache.org/jira/browse/AXIS2-5863
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.5
>Reporter: Petr Dvorak
>Priority: Minor
> Labels: security
> Attachments: diff.patch
>
>
> We use Coverity Scan tool to audit our open-source code against security
> vulnerabilities. Possible NullPointerException was detected in Axis2
> generated ServiceStub class code. The issue occurs in following generated
> code:
> {code:java}
> } finally {
> if (_messageContext.getTransportOut() != null) {
> _messageContext.getTransportOut().getSender()
> .cleanup(_messageContext);
> }
> }
> {code}
> In case "_messageContext" is set to null, the if condition throws NPE. Also,
> we can see the path on how this variable value actually may become null, so
> we believe the issue is valid and null check should be present...
> Here are possible implications of the issue from the security perspective:
> http://cwe.mitre.org/data/definitions/476.html
--
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-5857) Log4j 1.x has reached EOL
[ https://issues.apache.org/jira/browse/AXIS2-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088848#comment-16088848 ] Hudson commented on AXIS2-5857: --- SUCCESS: Integrated in Jenkins build Axis2 #3800 (See [https://builds.apache.org/job/Axis2/3800/]) AXIS2-5857: Split the codegen part of axis2-jibx into a separate module for easier dependency management. (veithen: rev 1800557) * (edit) axis2/modules/codegen/pom.xml * (edit) axis2/modules/distribution/pom.xml * (add) axis2/modules/jibx-codegen * (add) axis2/modules/jibx-codegen/pom.xml * (add) axis2/modules/jibx-codegen/src * (add) axis2/modules/jibx-codegen/src/main * (add) axis2/modules/jibx-codegen/src/main/java * (add) axis2/modules/jibx-codegen/src/main/java/org * (add) axis2/modules/jibx-codegen/src/main/java/org/apache * (add) axis2/modules/jibx-codegen/src/main/java/org/apache/axis2 * (add) axis2/modules/jibx-codegen/src/main/java/org/apache/axis2/jibx * (add) axis2/modules/jibx-codegen/src/main/java/org/apache/axis2/jibx/CodeGenerationUtility.java * (add) axis2/modules/jibx-codegen/src/main/resources * (edit) axis2/modules/jibx/pom.xml * (delete) axis2/modules/jibx/src/main/java/org/apache/axis2/jibx/CodeGenerationUtility.java * (delete) axis2/modules/jibx/src/main/resources * (edit) axis2/modules/tool/axis2-eclipse-codegen-plugin/pom.xml * (edit) axis2/pom.xml AXIS2-5857: Use the Google Java Formatter instead of Jalopy. Jalopy is no longer maintained and uses log4j 1.x which itself is end of life. (veithen: rev 1800555) * (edit) axis2 * (delete) axis2/legal/jalopy-LICENSE.txt * (edit) axis2/modules/codegen/pom.xml * (edit) axis2/modules/codegen/src/org/apache/axis2/util/PrettyPrinter.java * (edit) axis2/modules/codegen/src/org/apache/axis2/wsdl/codegen/extension/JavaPrettyPrinterExtension.java * (edit) axis2/modules/distribution/pom.xml * (edit) axis2/modules/jaxws-integration/test-resources/log4j.properties * (edit) axis2/modules/jaxws/test-resources/log4j.properties * (edit) axis2/modules/kernel/conf/log4j.properties * (edit) axis2/modules/metadata/test-resources/log4j.properties * (edit) axis2/modules/saaj/test-resources/log4j.properties * (edit) axis2/modules/samples/book/src/main/log4j.properties * (edit) axis2/modules/samples/java_first_jaxws/src/webapp/WEB-INF/classes/log4j.properties * (edit) axis2/modules/samples/jaxws-samples/src/webapp/WEB-INF/classes/log4j.properties * (edit) axis2/modules/tool/axis2-ant-plugin/src/test/resources/log4j.properties * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/test/resources/log4j.properties * (edit) axis2/pom.xml AXIS2-5857: Move PrettyPrinter to axis2-codegen. (veithen: rev 1800509) * (add) axis2/modules/codegen/src/org/apache/axis2/util * (add) axis2/modules/codegen/src/org/apache/axis2/util/PrettyPrinter.java * (delete) axis2/modules/kernel/src/org/apache/axis2/util/PrettyPrinter.java > Log4j 1.x has reached EOL > -- > > Key: AXIS2-5857 > URL: https://issues.apache.org/jira/browse/AXIS2-5857 > Project: Axis2 > Issue Type: Improvement >Affects Versions: 1.7.5 >Reporter: spoorti >Priority: Minor > > The log4j 1.x has reached EOL. Even the latest release version of Axis2 > contains the 1.x version of the log4j. > It need to be upgraded to 2.8.2 or higher since the other 2.x versions has > vulnerability reported. -- 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-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[ https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088849#comment-16088849 ] Hudson commented on AXIS2-5781: --- SUCCESS: Integrated in Jenkins build Axis2 #3800 (See [https://builds.apache.org/job/Axis2/3800/]) AXIS2-5781: Use maven-invoker-plugin to execute tests for axis2-java2wsdl-maven-plugin. (veithen: rev 1800535) * (edit) axis2/modules/tool/axis2-java2wsdl-maven-plugin/pom.xml * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1 * (edit) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/pom.xml * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main/java * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main/java/org * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main/java/org/apache * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main/java/org/apache/axis2 * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main/java/org/apache/axis2/maven2 * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main/java/org/apache/axis2/maven2/java2wsdl * (add) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/it/test1/src/main/java/org/apache/axis2/maven2/java2wsdl/test * (delete) axis2/modules/tool/axis2-java2wsdl-maven-plugin/src/test AXIS2-5781: Use maven-invoker-plugin to execute tests for axis2-aar-maven-plugin. (veithen: rev 1800534) * (edit) axis2/modules/tool/axis2-aar-maven-plugin/pom.xml * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1 * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1/pom.xml * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1/src * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1/src/main * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1/src/main/resources * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1/src/main/resources/META-INF * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1/src/main/resources/META-INF/services.xml * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test1/verify.bsh * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test2 * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test2/AdditionalDir * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test2/pom.xml * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test2/services.xml * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test2/simple.wsdl * (add) axis2/modules/tool/axis2-aar-maven-plugin/src/it/test2/verify.bsh * (delete) axis2/modules/tool/axis2-aar-maven-plugin/src/test/java * (delete) axis2/modules/tool/axis2-aar-maven-plugin/src/test/resources AXIS2-5781: Use maven-invoker-plugin to execute tests for axis2-wsdl2code-maven-plugin. (veithen: rev 1800518) * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml * (add) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/it * (add) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/it/test1 * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/it/test1/pom.xml * (add) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/it/test2 * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/it/test2/pom.xml * (delete) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/test/java * (delete) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/test/test1 * (delete) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/test/test2 * (edit) axis2/pom.xml > Maven Build - Module: kernel - generates / modifies file under source-control > - should build in output directory > > > Key: AXIS2-5781 > URL: https://issues.apache.org/jira/browse/AXIS2-5781 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.7.3 >Reporter: Jeff Thomas >Priority: Minor > > Maven Build for axis2-kernel (./modules/kernel/pom.xml). > In the axis2-kernel Maven Module (and at in at least the axis2-integration > module as well) test ant-scripts and unit-tests run against the > "./test-resources" directory instead of the "./target/test-resources" > directory. > In the interest of Maven "compliance" the build process should not edit, > touch or otherwise "dirty" source-code files. > Examples: > 1. The Ant-script "test-resources/deployment/service2/build.xml" creates > temporary directories, generates content, and removes these temporary > directories directly within the "test-resources"
[jira] [Commented] (AXIS2-2673) axis2-wsdl2code-maven-plugin + JiBX
[
https://issues.apache.org/jira/browse/AXIS2-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088847#comment-16088847
]
Hudson commented on AXIS2-2673:
---
SUCCESS: Integrated in Jenkins build Axis2 #3800 (See
[https://builds.apache.org/job/Axis2/3800/])
AXIS2-2673: Add axis2-jibx-codegen to the dependencies of
axis2-wsdl2code-maven-plugin. (veithen: rev 1800561)
* (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml
* (edit) axis2/pom.xml
> axis2-wsdl2code-maven-plugin + JiBX
> ---
>
> Key: AXIS2-2673
> URL: https://issues.apache.org/jira/browse/AXIS2-2673
> Project: Axis2
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.2
>Reporter: Antoni Jakubiak
> Labels: jibx, maven
> Fix For: 1.7.0
>
> Attachments: AXIS2-2673.patch, AXIS2-2673.patch
>
>
> I have to use maven plugin for axis and jibx - axis2-wsdl2code-maven-plugin
> version 1.2.
> It doesn't work for me. I made some changes:
> 1. pom.xml (axis2-1.2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml)
> add dependency to axis2-jibx:
>
> org.apache.axis2
> axis2-jibx
> ${version}
> It helps with "java.lang.RuntimeException: JiBX framework jars not in
> classpath" error.
> 2. WSDL2CodeMojo.java
> (modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/WSDL2CodeMojo.java)
> 2.1. add private field:
> /**
> * JiBX binding file
> *
> * @parameter expression="${axis2.wsdl2code.jibxBindingFile}"
> default-value="src/main/axis2/binding.xml"
> */
> private File jibxBindingFile;
> 2.2. modify method fillOptionMap - add code:
> if ("jibx".equals(databindingName)) {
>String tmpName =
> CommandLineOptionConstants.WSDL2JavaConstants.EXTRA_OPTIONTYPE_PREFIX
>+
> org.apache.axis2.wsdl.codegen.extension.JiBXExtension.BINDING_PATH_OPTION;
> optionMap.put( tmpName, new CommandLineOption( tmpName,
> getStringArray(jibxBindingFile.getPath(;
> }
> It helps with error "java.lang.RuntimeException: JiBX wrapped support
> requires a binding definition to be provided using the -Ebindingfile
> {file-path} parameter"
> This modifications allow me to build with maven axis2 jibx web service.
> Please add it to axis2 distribution.
> Example pom:
>
>
> 4.0.0
> org.apache.axis2.maven2
> axis2-wsdl2code-maven-plugin-test1-jibx
> 1.2-SNAPSHOT
> Test 1 of the axis2-wsdl2code-maven-plugin
>
>
>
>org.apache.axis2
>axis2-wsdl2code-maven-plugin
>1.2
>
>
>
> wsdl2code
>
>
> true
> true
> true
> true
> demo
> jibx
>
>
>
>
>
>
>
--
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-5856) Wrong null checker
[
https://issues.apache.org/jira/browse/AXIS2-5856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058115#comment-16058115
]
Hudson commented on AXIS2-5856:
---
SUCCESS: Integrated in Jenkins build Axis2 #3798 (See
[https://builds.apache.org/job/Axis2/3798/])
AXIS2-5856: Fix obvious bug in XMPPListener. (veithen: rev 1799496)
* (edit)
axis2/modules/transport/xmpp/src/org/apache/axis2/transport/xmpp/XMPPListener.java
> Wrong null checker
> --
>
> Key: AXIS2-5856
> URL: https://issues.apache.org/jira/browse/AXIS2-5856
> Project: Axis2
> Issue Type: Bug
> Components: XMPP transport
>Reporter: JC
>Priority: Trivial
>
> Hi
> In a recent GitHub snapshot, I've found a following code smell.
> Path:
> modules/transport/xmpp/src/org/apache/axis2/transport/xmpp/XMPPListener.java
> {code}
> 165 public EndpointReference[] getEPRsForService(String serviceName,
> String ip) throws AxisFault {
> 166 String domainName = serverCredentials.getDomainName() == null?
> serverCredentials.getDomainName()
> 167 : serverCredentials.getServerUrl();
> 168 return new EndpointReference[]{new
> EndpointReference(XMPPConstants.XMPP_PREFIX +
> 169 serverCredentials.getAccountName() +"@"+
> domainName +"/services/" + serviceName)};
> 170 }
> {code}
> In Line 166, serverCredentials.getDomainName() == null should be
> serverCredentials.getDomainName() != null ? This might be a trivial issue but
> wanted to report just in case.
> Thanks!
--
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-5853) Update commons fileupload to 1.3.3: Fixes CVE-2016-1000031
[
https://issues.apache.org/jira/browse/AXIS2-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053192#comment-16053192
]
Hudson commented on AXIS2-5853:
---
SUCCESS: Integrated in Jenkins build Axis2 #3797 (See
[https://builds.apache.org/job/Axis2/3797/])
AXIS2-5853: Update commons fileupload to 1.3.3. (veithen: rev 1799068)
* (edit) axis2/pom.xml
> Update commons fileupload to 1.3.3: Fixes CVE-2016-131
> --
>
> Key: AXIS2-5853
> URL: https://issues.apache.org/jira/browse/AXIS2-5853
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.5
>Reporter: Mark Symons
>
> {{org.apache.axis2:axis2-kernel}} v1.7.5 has a
> {{commons-fileupload:commons-fileupload}} v1.3.1 compile dependency
> Update {{commons-fileupload}} to v1.3.3, which addresses CVE-2016-131
> (CVE CVSS 3.0: 9.8)
> The threat was addressed in FILEUPLOAD-279
--
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-5853) Update commons fileupload to 1.3.3: Fixes CVE-2016-1000031
[
https://issues.apache.org/jira/browse/AXIS2-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053184#comment-16053184
]
Hudson commented on AXIS2-5853:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #122 (See
[https://builds.apache.org/job/axis2-1.7/122/])
AXIS2-5853: Merge r1799068 to the 1.7 branch. (veithen: rev 1799069)
* (edit) axis2
* (edit) axis2/pom.xml
> Update commons fileupload to 1.3.3: Fixes CVE-2016-131
> --
>
> Key: AXIS2-5853
> URL: https://issues.apache.org/jira/browse/AXIS2-5853
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.5
>Reporter: Mark Symons
>
> {{org.apache.axis2:axis2-kernel}} v1.7.5 has a
> {{commons-fileupload:commons-fileupload}} v1.3.1 compile dependency
> Update {{commons-fileupload}} to v1.3.3, which addresses CVE-2016-131
> (CVE CVSS 3.0: 9.8)
> The threat was addressed in FILEUPLOAD-279
--
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-3919) Temp folder being filled with files. Running out of disk space.
[ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999818#comment-15999818 ] Hudson commented on AXIS2-3919: --- SUCCESS: Integrated in Jenkins build Axis2 #3712 (See [https://builds.apache.org/job/Axis2/3712/]) AXIS2-3919: Eliminate the code duplication introduced in r619477. Also, one of the createClassLoader methods expected an array, but only ever used the first element. Fix this. (veithen: rev 1794190) * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/framework/JAXWSDeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ModuleDeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/POJODeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ServiceDeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/util/Utils.java > Temp folder being filled with files. Running out of disk space. > --- > > Key: AXIS2-3919 > URL: https://issues.apache.org/jira/browse/AXIS2-3919 > Project: Axis2 > Issue Type: Bug > Components: kernel, modules >Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3 > Environment: Windows XP, Linux >Reporter: Sujay Chauhan > > Hi > We are seeing an issue and it is holding us up from moving to production as > our production servers would run out of disk space. > This is in regards to a client that we are trying to implement using > axis2-1.4 and rampart-1.3. > We have a folder structure > clientProjectFolder > --otherFolders > -- > -- > --axis2 > --conf > --axis2.xml >--modules > --rampart1.3.mar > our axis2.xml file contains the global module > In our client code, we make use of the fileSytemConfigurator to configure the > client stub before making the call to our service. > Every time we are calling the service, files are added to the TEMP folder > (see below) > C:\TEMP\_axis2>dir > Directory of C:\TEMP\_axis2 > 07/16/2008 08:36 AM . > 07/16/2008 08:36 AM .. > 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar >1 File(s) 2,704 bytes >2 Dir(s) 103,722,340,352 bytes free > The same issue is being duplicated on our prod servers which are not windows > based but linux based. the files get put in /tmp/_axis2 folder. > Any advice on if there is a workaround for this? > Thanks, > Sujay -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
[ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999784#comment-15999784 ] Hudson commented on AXIS2-3919: --- SUCCESS: Integrated in Jenkins build Axis2 #3711 (See [https://builds.apache.org/job/Axis2/3711/]) AXIS2-3919: Remove the now unused findLibJars method. (veithen: rev 1794188) * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/util/Utils.java > Temp folder being filled with files. Running out of disk space. > --- > > Key: AXIS2-3919 > URL: https://issues.apache.org/jira/browse/AXIS2-3919 > Project: Axis2 > Issue Type: Bug > Components: kernel, modules >Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3 > Environment: Windows XP, Linux >Reporter: Sujay Chauhan > > Hi > We are seeing an issue and it is holding us up from moving to production as > our production servers would run out of disk space. > This is in regards to a client that we are trying to implement using > axis2-1.4 and rampart-1.3. > We have a folder structure > clientProjectFolder > --otherFolders > -- > -- > --axis2 > --conf > --axis2.xml >--modules > --rampart1.3.mar > our axis2.xml file contains the global module > In our client code, we make use of the fileSytemConfigurator to configure the > client stub before making the call to our service. > Every time we are calling the service, files are added to the TEMP folder > (see below) > C:\TEMP\_axis2>dir > Directory of C:\TEMP\_axis2 > 07/16/2008 08:36 AM . > 07/16/2008 08:36 AM .. > 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar >1 File(s) 2,704 bytes >2 Dir(s) 103,722,340,352 bytes free > The same issue is being duplicated on our prod servers which are not windows > based but linux based. the files get put in /tmp/_axis2 folder. > Any advice on if there is a workaround for this? > Thanks, > Sujay -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
[ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999630#comment-15999630 ] Hudson commented on AXIS2-3919: --- SUCCESS: Integrated in Jenkins build Axis2 #3710 (See [https://builds.apache.org/job/Axis2/3710/]) AXIS2-3919: Remove the alternate class loading mechanism: - It degrades performance. - There is no test coverage for it. - With r1794157 in place, in most cases, no temporary files will be created and there is no need for a fallback mechanism. (veithen: rev 1794181) * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/DeploymentClassLoader.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/util/Utils.java > Temp folder being filled with files. Running out of disk space. > --- > > Key: AXIS2-3919 > URL: https://issues.apache.org/jira/browse/AXIS2-3919 > Project: Axis2 > Issue Type: Bug > Components: kernel, modules >Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3 > Environment: Windows XP, Linux >Reporter: Sujay Chauhan > > Hi > We are seeing an issue and it is holding us up from moving to production as > our production servers would run out of disk space. > This is in regards to a client that we are trying to implement using > axis2-1.4 and rampart-1.3. > We have a folder structure > clientProjectFolder > --otherFolders > -- > -- > --axis2 > --conf > --axis2.xml >--modules > --rampart1.3.mar > our axis2.xml file contains the global module > In our client code, we make use of the fileSytemConfigurator to configure the > client stub before making the call to our service. > Every time we are calling the service, files are added to the TEMP folder > (see below) > C:\TEMP\_axis2>dir > Directory of C:\TEMP\_axis2 > 07/16/2008 08:36 AM . > 07/16/2008 08:36 AM .. > 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar >1 File(s) 2,704 bytes >2 Dir(s) 103,722,340,352 bytes free > The same issue is being duplicated on our prod servers which are not windows > based but linux based. the files get put in /tmp/_axis2 folder. > Any advice on if there is a workaround for this? > Thanks, > Sujay -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
[ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999621#comment-15999621 ] Hudson commented on AXIS2-3919: --- SUCCESS: Integrated in Jenkins build Axis2 #3709 (See [https://builds.apache.org/job/Axis2/3709/]) AXIS2-3919: Remove the extractJars argument from createClassLoader; it's always set to true. (veithen: rev 1794177) * (edit) axis2/modules/jaxws/src/org/apache/axis2/jaxws/framework/JAXWSDeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ModuleDeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/POJODeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/ServiceDeployer.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/util/Utils.java > Temp folder being filled with files. Running out of disk space. > --- > > Key: AXIS2-3919 > URL: https://issues.apache.org/jira/browse/AXIS2-3919 > Project: Axis2 > Issue Type: Bug > Components: kernel, modules >Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3 > Environment: Windows XP, Linux >Reporter: Sujay Chauhan > > Hi > We are seeing an issue and it is holding us up from moving to production as > our production servers would run out of disk space. > This is in regards to a client that we are trying to implement using > axis2-1.4 and rampart-1.3. > We have a folder structure > clientProjectFolder > --otherFolders > -- > -- > --axis2 > --conf > --axis2.xml >--modules > --rampart1.3.mar > our axis2.xml file contains the global module > In our client code, we make use of the fileSytemConfigurator to configure the > client stub before making the call to our service. > Every time we are calling the service, files are added to the TEMP folder > (see below) > C:\TEMP\_axis2>dir > Directory of C:\TEMP\_axis2 > 07/16/2008 08:36 AM . > 07/16/2008 08:36 AM .. > 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar >1 File(s) 2,704 bytes >2 Dir(s) 103,722,340,352 bytes free > The same issue is being duplicated on our prod servers which are not windows > based but linux based. the files get put in /tmp/_axis2 folder. > Any advice on if there is a workaround for this? > Thanks, > Sujay -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
[ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999557#comment-15999557 ] Hudson commented on AXIS2-3919: --- SUCCESS: Integrated in Jenkins build Axis2 #3708 (See [https://builds.apache.org/job/Axis2/3708/]) AXIS2-3919: Upgrade to Java 7. If we want to delete temporary files created by the deployer in a timely way, we need to rely on the ability to explicitly close URLClassLoader instances (at least on Windows), a feature that is only available in Java 7. (veithen: rev 1794173) * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/DeploymentEngine.java * (edit) axis2/pom.xml * (edit) axis2/src/site/markdown/release-notes/1.8.0.md > Temp folder being filled with files. Running out of disk space. > --- > > Key: AXIS2-3919 > URL: https://issues.apache.org/jira/browse/AXIS2-3919 > Project: Axis2 > Issue Type: Bug > Components: kernel, modules >Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3 > Environment: Windows XP, Linux >Reporter: Sujay Chauhan > > Hi > We are seeing an issue and it is holding us up from moving to production as > our production servers would run out of disk space. > This is in regards to a client that we are trying to implement using > axis2-1.4 and rampart-1.3. > We have a folder structure > clientProjectFolder > --otherFolders > -- > -- > --axis2 > --conf > --axis2.xml >--modules > --rampart1.3.mar > our axis2.xml file contains the global module > In our client code, we make use of the fileSytemConfigurator to configure the > client stub before making the call to our service. > Every time we are calling the service, files are added to the TEMP folder > (see below) > C:\TEMP\_axis2>dir > Directory of C:\TEMP\_axis2 > 07/16/2008 08:36 AM . > 07/16/2008 08:36 AM .. > 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar >1 File(s) 2,704 bytes >2 Dir(s) 103,722,340,352 bytes free > The same issue is being duplicated on our prod servers which are not windows > based but linux based. the files get put in /tmp/_axis2 folder. > Any advice on if there is a workaround for this? > Thanks, > Sujay -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5704) JiBX doesn't works with Jdk 1.8
[ https://issues.apache.org/jira/browse/AXIS2-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999558#comment-15999558 ] Hudson commented on AXIS2-5704: --- SUCCESS: Integrated in Jenkins build Axis2 #3708 (See [https://builds.apache.org/job/Axis2/3708/]) AXIS2-5704: Upgrade JiBX to 1.3.1. (veithen: rev 1794168) * (edit) axis2/modules/jibx/pom.xml * (edit) axis2/pom.xml > JiBX doesn't works with Jdk 1.8 > --- > > Key: AXIS2-5704 > URL: https://issues.apache.org/jira/browse/AXIS2-5704 > Project: Axis2 > Issue Type: Sub-task >Affects Versions: 1.6.3 >Reporter: Shameera Rathnayaka >Assignee: Andreas Veithen > Fix For: 1.7.0 > > > Getting following build failure, from more details check this > https://github.com/jibx/jibx/issues/3 . One option is to replace JiBX module > with JAXB which is default comes with java 8. > [INFO] --- maven-antrun-plugin:1.2:run (compile) @ axis2-jibx --- > [INFO] Executing tasks > [java] Error running binding compiler > [java] java.lang.IllegalStateException: Error loading class > java.lang.CharSequence: Error reading path java/lang/CharSequence.class for > class java.lang.CharSequence > [java] at > org.jibx.binding.classes.ClassCache$ClassCacheLocator.getClassInfo(ClassCache.java:264) > [java] at > org.jibx.binding.model.ClassHierarchyContext.accumulateInterfaces(ClassHierarchyContext.java:96) > [java] at > org.jibx.binding.model.ClassHierarchyContext.addTypedComponent(ClassHierarchyContext.java:121) > [java] at > org.jibx.binding.model.DefinitionContext.addFormat(DefinitionContext.java:469) > [java] at > org.jibx.binding.model.BindingElement.defineBaseFormat(BindingElement.java:774) > [java] at > org.jibx.binding.model.BindingElement.runValidation(BindingElement.java:793) > [java] at > org.jibx.binding.model.BindingElement.validateBinding(BindingElement.java:885) > [java] at org.jibx.binding.Utility.validateBinding(Utility.java:246) > [java] at org.jibx.binding.Utility.loadBinding(Utility.java:288) > [java] at org.jibx.binding.Utility.loadFileBinding(Utility.java:431) > [java] at org.jibx.binding.Compile.compile(Compile.java:212) > [java] at org.jibx.binding.Compile.main(Compile.java:374) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
[ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999497#comment-15999497 ] Hudson commented on AXIS2-3919: --- SUCCESS: Integrated in Jenkins build Axis2 #3707 (See [https://builds.apache.org/job/Axis2/3707/]) AXIS2-3919, AXIS2-3504: Don't copy archives to the temp directory if they are already available as files. Starting with r525695 Axis2 always copies archives (i.e. the AAR and MAR files; not only JARs embedded in those archives) to the temp directory. There were two reasons for this: 1. Avoid the performance overhead if the archive itself is embedded in another archive, such as a (non exploded) WAR file. 2. Prevent the class loader from locking the archive file (which causes problems during redeployment). 1 is only a problem if the URL of the archive isn't a file: URL. 2 is no longer a problem with Java 1.7 because URLClassLoaders can be closed explicitly. (veithen: rev 1794157) * (edit) axis2/modules/kernel/src/org/apache/axis2/deployment/util/Utils.java > Temp folder being filled with files. Running out of disk space. > --- > > Key: AXIS2-3919 > URL: https://issues.apache.org/jira/browse/AXIS2-3919 > Project: Axis2 > Issue Type: Bug > Components: kernel, modules >Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3 > Environment: Windows XP, Linux >Reporter: Sujay Chauhan > > Hi > We are seeing an issue and it is holding us up from moving to production as > our production servers would run out of disk space. > This is in regards to a client that we are trying to implement using > axis2-1.4 and rampart-1.3. > We have a folder structure > clientProjectFolder > --otherFolders > -- > -- > --axis2 > --conf > --axis2.xml >--modules > --rampart1.3.mar > our axis2.xml file contains the global module > In our client code, we make use of the fileSytemConfigurator to configure the > client stub before making the call to our service. > Every time we are calling the service, files are added to the TEMP folder > (see below) > C:\TEMP\_axis2>dir > Directory of C:\TEMP\_axis2 > 07/16/2008 08:36 AM . > 07/16/2008 08:36 AM .. > 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar >1 File(s) 2,704 bytes >2 Dir(s) 103,722,340,352 bytes free > The same issue is being duplicated on our prod servers which are not windows > based but linux based. the files get put in /tmp/_axis2 folder. > Any advice on if there is a workaround for this? > Thanks, > Sujay -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-4947) [patch] OSGi imports inappropriate for common environments
[ https://issues.apache.org/jira/browse/AXIS2-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997465#comment-15997465 ] Hudson commented on AXIS2-4947: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #115 (See [https://builds.apache.org/job/axis2-1.7/115/]) AXIS2-4947: Merge r1793728 to the 1.7 branch. (veithen: rev 1793895) * (edit) axis2 * (edit) axis2/modules/osgi-tests/pom.xml * (edit) axis2/modules/osgi-tests/src/test/java/OSGiTest.java * (edit) axis2/modules/osgi/pom.xml > [patch] OSGi imports inappropriate for common environments > -- > > Key: AXIS2-4947 > URL: https://issues.apache.org/jira/browse/AXIS2-4947 > Project: Axis2 > Issue Type: Bug >Affects Versions: nightly > Environment: E.g. GlassFish 3.1 / Felix 3.x / Java 6 >Reporter: Ancoron Luciferis > Labels: osgi > Attachments: osgi-pom.xml.patch > > > Most common environments define all package exports issued by the framework > with the system version "0.0.0". > Because Axis2 OSGi specifies the following imports with higher versions it is > not possible to use the provided OSGi bundle as is and has to be modified: > javax.ws.rs; version=1.0, > javax.activation;version="1.1", > javax.xml.stream;resolution:=optional;version="1.0" > I'll attach a patch to fix this problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-4310) Some of the versions for Import-Package headers are too restrictive
[ https://issues.apache.org/jira/browse/AXIS2-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995936#comment-15995936 ] Hudson commented on AXIS2-4310: --- SUCCESS: Integrated in Jenkins build Axis2 #3701 (See [https://builds.apache.org/job/Axis2/3701/]) AXIS2-4310: Remove the 0.0.0 version from the Import-Package for javax.xml.namespace. (veithen: rev 1793724) * (edit) axis2/modules/osgi/pom.xml > Some of the versions for Import-Package headers are too restrictive > --- > > Key: AXIS2-4310 > URL: https://issues.apache.org/jira/browse/AXIS2-4310 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.5 >Reporter: Raymond Feng > > The MF has the following Import-Package header. Some of the versions are too > restrictive: > For example: > javax.jms;version="1.1", won't be statified by > http://repo2.maven.org/maven2/org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.1.1/geronimo-jms_1.1_spec-1.1.1.jar > which exports the javax.jms without a version (default to 0.0.0). > So are the servlet apis. > The other issue is that the import version 0.0.0 can only be satified by an > export package with 0.0.0. for example, javax.xml.namespace;version="0.0.0", > cannot be supplied by an export package with version 1.0. We should remove > the 0.0.0. > Import-Package: com.ibm.wsdl.util.xml, > javax.activation;version="1.1", > javax.jms;version="1.1", > javax.jws;version="2.0", > javax.mail;version="1.4", > javax.mail.internet;version="1.4", > javax.mail.util;version="1.4", > javax.management, > javax.naming;resolution:=optional, > javax.rmi;resolution:=optional, > javax.servlet;version="2.4.0", > javax.servlet.http;version="2.4.0", > javax.transaction, > javax.wsdl, > javax.wsdl.extensions, > javax.wsdl.extensions.http, > javax.wsdl.extensions.mime, > javax.wsdl.extensions.schema, > javax.wsdl.extensions.soap, > javax.wsdl.extensions.soap12, > javax.wsdl.factory, > javax.wsdl.xml, > javax.xml.namespace;version="0.0.0", > javax.xml.parsers;resolution:=optional, > javax.xml.stream;resolution:=optional;version="1.0", > javax.xml.transform;resolution:=optional, > javax.xml.transform.dom;resolution:=optional, > javax.xml.transform.stream;resolution:=optional, > org.apache.axiom.attachments, > org.apache.axiom.attachments.impl, > org.apache.axiom.attachments.lifecycle, > org.apache.axiom.attachments.lifecycle.impl, > org.apache.axiom.attachments.utils, > org.apache.axiom.om, > org.apache.axiom.om.impl, > org.apache.axiom.om.impl.builder, > org.apache.axiom.om.impl.llom, > org.apache.axiom.om.impl.llom.factory, > org.apache.axiom.om.impl.util, > org.apache.axiom.om.util, > org.apache.axiom.soap, > org.apache.axiom.soap.impl.builder, > org.apache.axiom.soap.impl.llom.soap11, > org.apache.axiom.soap.impl.llom.soap12, > org.apache.commons.fileupload, > org.apache.commons.fileupload.disk, > org.apache.commons.fileupload.servlet, > org.apache.commons.httpclient, > org.apache.commons.httpclient.auth, > org.apache.commons.httpclient.methods, > org.apache.commons.httpclient.methods.multipart, > org.apache.commons.httpclient.params, > org.apache.commons.httpclient.protocol, > org.apache.commons.httpclient.util, > org.apache.commons.io;version="1.4", > org.apache.commons.lang;resolution:=optional, > org.apache.commons.logging, > org.apache.http;resolution:=optional, > org.apache.http.entity;resolution:=optional, > org.apache.http.impl;resolution:=optional, > org.apache.http.impl.entity;resolution:=optional, > org.apache.http.impl.io;resolution:=optional, > org.apache.http.io;resolution:=optional, > org.apache.http.message;resolution:=optional, > org.apache.http.params;resolution:=optional, > org.apache.http.protocol;resolution:=optional, > org.apache.http.util;resolution:=optional, > org.apache.neethi, > org.apache.woden;version="0.0.0", > org.apache.woden.internal;version="0.0.0", > org.apache.woden.internal.wsdl20;version="0.0.0", > org.apache.woden.internal.wsdl20.extensions;version="0.0.0", > org.apache.woden.internal.wsdl20.extensions.http;version="0.0.0", > org.apache.woden.internal.wsdl20.extensions.soap;version="0.0.0", > org.apache.woden.resolver;version="0.0.0", > org.apache.woden.schema;version="0.0.0", > org.apache.woden.types;version="0.0.0", > org.apache.woden.wsdl20;version="0.0.0", > org.apache.woden.wsdl20.enumeration;version="0.0.0", > org.apache.woden.wsdl20.extensions;version="0.0.0", > org.apache.woden.wsdl20.extensions.http;version="0.0.0", > org.apache.woden.wsdl20.extensions.rpc;version="0.0.0", > org.apache.woden.wsdl20.extensions.soap;version="0.0.0", > org.apache.woden.wsdl20.xml;version="0.0.0", > org.apache.woden.xml;version="0.0.0", > org.apache.ws.commons.schema, >
[jira] [Commented] (AXIS2-4947) [patch] OSGi imports inappropriate for common environments
[ https://issues.apache.org/jira/browse/AXIS2-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995935#comment-15995935 ] Hudson commented on AXIS2-4947: --- SUCCESS: Integrated in Jenkins build Axis2 #3701 (See [https://builds.apache.org/job/Axis2/3701/]) AXIS2-4947: Make the javax.ws.rs import optional and let BND determine the version. (veithen: rev 1793728) * (edit) axis2/modules/osgi-tests/pom.xml * (edit) axis2/modules/osgi-tests/src/test/java/OSGiTest.java * (edit) axis2/modules/osgi/pom.xml > [patch] OSGi imports inappropriate for common environments > -- > > Key: AXIS2-4947 > URL: https://issues.apache.org/jira/browse/AXIS2-4947 > Project: Axis2 > Issue Type: Bug >Affects Versions: nightly > Environment: E.g. GlassFish 3.1 / Felix 3.x / Java 6 >Reporter: Ancoron Luciferis > Labels: osgi > Attachments: osgi-pom.xml.patch > > > Most common environments define all package exports issued by the framework > with the system version "0.0.0". > Because Axis2 OSGi specifies the following imports with higher versions it is > not possible to use the provided OSGi bundle as is and has to be modified: > javax.ws.rs; version=1.0, > javax.activation;version="1.1", > javax.xml.stream;resolution:=optional;version="1.0" > I'll attach a patch to fix this problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-4310) Some of the versions for Import-Package headers are too restrictive
[ https://issues.apache.org/jira/browse/AXIS2-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995844#comment-15995844 ] Hudson commented on AXIS2-4310: --- SUCCESS: Integrated in Jenkins build Axis2 #3700 (See [https://builds.apache.org/job/Axis2/3700/]) AXIS2-4310: Remove unnecessary JMS import from OSGi bundle. (veithen: rev 1793723) * (edit) axis2/modules/osgi-tests/pom.xml * (edit) axis2/modules/osgi-tests/src/test/java/OSGiTest.java * (edit) axis2/modules/osgi/pom.xml > Some of the versions for Import-Package headers are too restrictive > --- > > Key: AXIS2-4310 > URL: https://issues.apache.org/jira/browse/AXIS2-4310 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.5 >Reporter: Raymond Feng > > The MF has the following Import-Package header. Some of the versions are too > restrictive: > For example: > javax.jms;version="1.1", won't be statified by > http://repo2.maven.org/maven2/org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.1.1/geronimo-jms_1.1_spec-1.1.1.jar > which exports the javax.jms without a version (default to 0.0.0). > So are the servlet apis. > The other issue is that the import version 0.0.0 can only be satified by an > export package with 0.0.0. for example, javax.xml.namespace;version="0.0.0", > cannot be supplied by an export package with version 1.0. We should remove > the 0.0.0. > Import-Package: com.ibm.wsdl.util.xml, > javax.activation;version="1.1", > javax.jms;version="1.1", > javax.jws;version="2.0", > javax.mail;version="1.4", > javax.mail.internet;version="1.4", > javax.mail.util;version="1.4", > javax.management, > javax.naming;resolution:=optional, > javax.rmi;resolution:=optional, > javax.servlet;version="2.4.0", > javax.servlet.http;version="2.4.0", > javax.transaction, > javax.wsdl, > javax.wsdl.extensions, > javax.wsdl.extensions.http, > javax.wsdl.extensions.mime, > javax.wsdl.extensions.schema, > javax.wsdl.extensions.soap, > javax.wsdl.extensions.soap12, > javax.wsdl.factory, > javax.wsdl.xml, > javax.xml.namespace;version="0.0.0", > javax.xml.parsers;resolution:=optional, > javax.xml.stream;resolution:=optional;version="1.0", > javax.xml.transform;resolution:=optional, > javax.xml.transform.dom;resolution:=optional, > javax.xml.transform.stream;resolution:=optional, > org.apache.axiom.attachments, > org.apache.axiom.attachments.impl, > org.apache.axiom.attachments.lifecycle, > org.apache.axiom.attachments.lifecycle.impl, > org.apache.axiom.attachments.utils, > org.apache.axiom.om, > org.apache.axiom.om.impl, > org.apache.axiom.om.impl.builder, > org.apache.axiom.om.impl.llom, > org.apache.axiom.om.impl.llom.factory, > org.apache.axiom.om.impl.util, > org.apache.axiom.om.util, > org.apache.axiom.soap, > org.apache.axiom.soap.impl.builder, > org.apache.axiom.soap.impl.llom.soap11, > org.apache.axiom.soap.impl.llom.soap12, > org.apache.commons.fileupload, > org.apache.commons.fileupload.disk, > org.apache.commons.fileupload.servlet, > org.apache.commons.httpclient, > org.apache.commons.httpclient.auth, > org.apache.commons.httpclient.methods, > org.apache.commons.httpclient.methods.multipart, > org.apache.commons.httpclient.params, > org.apache.commons.httpclient.protocol, > org.apache.commons.httpclient.util, > org.apache.commons.io;version="1.4", > org.apache.commons.lang;resolution:=optional, > org.apache.commons.logging, > org.apache.http;resolution:=optional, > org.apache.http.entity;resolution:=optional, > org.apache.http.impl;resolution:=optional, > org.apache.http.impl.entity;resolution:=optional, > org.apache.http.impl.io;resolution:=optional, > org.apache.http.io;resolution:=optional, > org.apache.http.message;resolution:=optional, > org.apache.http.params;resolution:=optional, > org.apache.http.protocol;resolution:=optional, > org.apache.http.util;resolution:=optional, > org.apache.neethi, > org.apache.woden;version="0.0.0", > org.apache.woden.internal;version="0.0.0", > org.apache.woden.internal.wsdl20;version="0.0.0", > org.apache.woden.internal.wsdl20.extensions;version="0.0.0", > org.apache.woden.internal.wsdl20.extensions.http;version="0.0.0", > org.apache.woden.internal.wsdl20.extensions.soap;version="0.0.0", > org.apache.woden.resolver;version="0.0.0", > org.apache.woden.schema;version="0.0.0", > org.apache.woden.types;version="0.0.0", > org.apache.woden.wsdl20;version="0.0.0", > org.apache.woden.wsdl20.enumeration;version="0.0.0", > org.apache.woden.wsdl20.extensions;version="0.0.0", > org.apache.woden.wsdl20.extensions.http;version="0.0.0", > org.apache.woden.wsdl20.extensions.rpc;version="0.0.0", > org.apache.woden.wsdl20.extensions.soap;version="0.0.0", > org.apache.woden.wsdl20.xml;version="0.0.0", >
[jira] [Commented] (AXIS2-5771) -Eiu option logs Unexpected value for enumeration every time
[ https://issues.apache.org/jira/browse/AXIS2-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991753#comment-15991753 ] Hudson commented on AXIS2-5771: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #114 (See [https://builds.apache.org/job/axis2-1.7/114/]) Merge the fix for AXIS2-5771 to the 1.7 branch. Note that this doesn't include the unit test because the necessary infrastructure doesn't exist in 1.7. (veithen: rev 1793419) * (edit) axis2/modules/adb-codegen * (edit) axis2/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate-bean.xsl > -Eiu option logs Unexpected value for enumeration every time > - > > Key: AXIS2-5771 > URL: https://issues.apache.org/jira/browse/AXIS2-5771 > Project: Axis2 > Issue Type: Bug > Components: adb, codegen >Affects Versions: 1.7.0, 1.7.1, 1.7.4 >Reporter: Rob Nash >Priority: Minor > Attachments: EnumExample.zip > > > Deployed Axis2 1.7.1 using generated client stubs using the -Eiu option. > Noticed in our logs the message regarding an Unexpected value for > enumeration. The api hit succeeds, and if you exclude the -Eiu option the > messages go away. But as far as I can tell they should not show up even with > the -Eiu option. I view this as related to the change in AXIS2-5273. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5771) -Eiu option logs Unexpected value for enumeration every time
[ https://issues.apache.org/jira/browse/AXIS2-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991618#comment-15991618 ] Hudson commented on AXIS2-5771: --- UNSTABLE: Integrated in Jenkins build Axis2 #3698 (See [https://builds.apache.org/job/Axis2/3698/]) AXIS2-5771: Add a unit test for the feature added in AXIS2-5848 and fix it so that it stops logging erroneous warnings. (veithen: rev 1793405) * (edit) axis2/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate-bean.xsl * (edit) axis2/modules/adb-tests/pom.xml * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/axis2_5771 * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/axis2_5771/IgnoreUnexpectedTest.java * (add) axis2/modules/adb-tests/src/test/xsd * (add) axis2/modules/adb-tests/src/test/xsd/AXIS2-5771.xsd * (edit) axis2/modules/tool/axis2-xsd2java-maven-plugin/src/main/java/org/apache/axis2/maven/xsd2java/AbstractXSD2JavaMojo.java > -Eiu option logs Unexpected value for enumeration every time > - > > Key: AXIS2-5771 > URL: https://issues.apache.org/jira/browse/AXIS2-5771 > Project: Axis2 > Issue Type: Bug > Components: adb, codegen >Affects Versions: 1.7.0, 1.7.1, 1.7.4 >Reporter: Rob Nash >Priority: Minor > Attachments: EnumExample.zip > > > Deployed Axis2 1.7.1 using generated client stubs using the -Eiu option. > Noticed in our logs the message regarding an Unexpected value for > enumeration. The api hit succeeds, and if you exclude the -Eiu option the > messages go away. But as far as I can tell they should not show up even with > the -Eiu option. I view this as related to the change in AXIS2-5273. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5848) After use -Eiu in wsdl2java.sh, factory classes for enumeration typte log warning erroneously
[
https://issues.apache.org/jira/browse/AXIS2-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991619#comment-15991619
]
Hudson commented on AXIS2-5848:
---
UNSTABLE: Integrated in Jenkins build Axis2 #3698 (See
[https://builds.apache.org/job/Axis2/3698/])
AXIS2-5771: Add a unit test for the feature added in AXIS2-5848 and fix it so
that it stops logging erroneous warnings. (veithen: rev 1793405)
* (edit)
axis2/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate-bean.xsl
* (edit) axis2/modules/adb-tests/pom.xml
* (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/axis2_5771
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/axis2_5771/IgnoreUnexpectedTest.java
* (add) axis2/modules/adb-tests/src/test/xsd
* (add) axis2/modules/adb-tests/src/test/xsd/AXIS2-5771.xsd
* (edit)
axis2/modules/tool/axis2-xsd2java-maven-plugin/src/main/java/org/apache/axis2/maven/xsd2java/AbstractXSD2JavaMojo.java
> After use -Eiu in wsdl2java.sh, factory classes for enumeration typte log
> warning erroneously
> -
>
> Key: AXIS2-5848
> URL: https://issues.apache.org/jira/browse/AXIS2-5848
> Project: Axis2
> Issue Type: Bug
> Components: adb
>Affects Versions: 1.7.4
>Reporter: Jing Teng
>
> For this schema,
> {code}
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Without -Eiu, the generated code is
> {code}
> public static class Factory {
> public static CabinType fromValue(java.lang.String value)
> throws java.lang.IllegalArgumentException {
> CabinType enumeration = (CabinType) _table_.get(value);
> // handle unexpected enumeration values properly
> if (enumeration == null) {
> throw new java.lang.IllegalArgumentException();
> }
> return enumeration;
> }
> {code}
> With -Eiu, the code is
> {code}
> public static class Factory {
> public static CabinType fromValue(java.lang.String value)
> throws java.lang.IllegalArgumentException {
> CabinType enumeration = (CabinType) _table_.get(value);
> // handle unexpected enumeration values properly
> log.warn("Unexpected value " + value +
> " for enumeration CabinType");
> return enumeration;
> }
> {code}
> Obviously the code above is wrong
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5785) Submit 'axis2-xsd2java-maven-plugin' for consideration
[ https://issues.apache.org/jira/browse/AXIS2-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991370#comment-15991370 ] Hudson commented on AXIS2-5785: --- SUCCESS: Integrated in Jenkins build Axis2 #3697 (See [https://builds.apache.org/job/Axis2/3697/]) AXIS2-5785: Add axis2-xsd2java-maven-plugin and use it in adb-tests. Based on a proposal submitted by Jeff Thomas. (veithen: rev 1793393) * (edit) axis2 * (edit) axis2/apidocs/pom.xml * (edit) axis2/modules/adb-tests/pom.xml * (delete) axis2/modules/adb-tests/sub-build.xml * (add) axis2/modules/tool/axis2-xsd2java-maven-plugin * (edit) axis2/pom.xml * (edit) axis2/src/site/xdoc/tools/index.xml > Submit 'axis2-xsd2java-maven-plugin' for consideration > -- > > Key: AXIS2-5785 > URL: https://issues.apache.org/jira/browse/AXIS2-5785 > Project: Axis2 > Issue Type: Improvement >Affects Versions: 1.7.3 >Reporter: Jeff Thomas >Priority: Minor > Attachments: axis2-xsd2java-maven-plugin.zip > > > I have created a simple maven plugin to wrap the "XSD2Java" functionality > (generation of ADB beans). > This ticket is simply to submit my project for the maven module for review / > consideration for integration into Axis2. > I tried to conform to the existing Axis2 Maven plugin setup as much as > possible. Unfortunately what is still missing in my module are unit-tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5785) Submit 'axis2-xsd2java-maven-plugin' for consideration
[ https://issues.apache.org/jira/browse/AXIS2-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990990#comment-15990990 ] Hudson commented on AXIS2-5785: --- SUCCESS: Integrated in Jenkins build Axis2 #3695 (See [https://builds.apache.org/job/Axis2/3695/]) AXIS2-5785: Extract some code from axis2-wsdl2code-maven-plugin for reuse in axis2-xsd2java-maven-plugin. (veithen: rev 1793348) * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/AbstractWSDL2CodeMojo.java * (delete) axis2/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/NamespaceURIMapping.java * (add) axis2/modules/tool/maven-shared * (add) axis2/modules/tool/maven-shared/pom.xml * (add) axis2/modules/tool/maven-shared/src * (add) axis2/modules/tool/maven-shared/src/main * (add) axis2/modules/tool/maven-shared/src/main/java * (add) axis2/modules/tool/maven-shared/src/main/java/org * (add) axis2/modules/tool/maven-shared/src/main/java/org/apache * (add) axis2/modules/tool/maven-shared/src/main/java/org/apache/axis2 * (add) axis2/modules/tool/maven-shared/src/main/java/org/apache/axis2/maven * (add) axis2/modules/tool/maven-shared/src/main/java/org/apache/axis2/maven/shared * (add) axis2/modules/tool/maven-shared/src/main/java/org/apache/axis2/maven/shared/NamespaceMapping.java * (add) axis2/modules/tool/maven-shared/src/main/java/org/apache/axis2/maven/shared/NamespaceMappingUtil.java * (edit) axis2/pom.xml > Submit 'axis2-xsd2java-maven-plugin' for consideration > -- > > Key: AXIS2-5785 > URL: https://issues.apache.org/jira/browse/AXIS2-5785 > Project: Axis2 > Issue Type: Improvement >Affects Versions: 1.7.3 >Reporter: Jeff Thomas >Priority: Minor > Attachments: axis2-xsd2java-maven-plugin.zip > > > I have created a simple maven plugin to wrap the "XSD2Java" functionality > (generation of ADB beans). > This ticket is simply to submit my project for the maven module for review / > consideration for integration into Axis2. > I tried to conform to the existing Axis2 Maven plugin setup as much as > possible. Unfortunately what is still missing in my module are unit-tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5785) Submit 'axis2-xsd2java-maven-plugin' for consideration
[ https://issues.apache.org/jira/browse/AXIS2-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990794#comment-15990794 ] Hudson commented on AXIS2-5785: --- SUCCESS: Integrated in Jenkins build Axis2 #3694 (See [https://builds.apache.org/job/Axis2/3694/]) AXIS2-5785: Move the ADB tests relying on XSD2Java to adb-tests, so that we later replace the maven-antrun-plugin execution by axis2-xsd2java-maven-plugin. (veithen: rev 1793309) * (edit) axis2/modules/adb-codegen/pom.xml * (delete) axis2/modules/adb-codegen/sub-build.xml * (delete) axis2/modules/adb-codegen/test/helper * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/ADBBeanUtil.java * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/AbstractTestCase.java * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/all * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/anytype * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/attribute * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/base64binary * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/booleantest * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/chameleon * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/choice * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/decimal * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/defaultnamespaces * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/defaultvalue * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/enumeration * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/extension * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/fix * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/group * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/innerchoice * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/innerparticleextension * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/innerparticles * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/list * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/nonamespace * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/particlemaxoccurs * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/populate * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/references * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/restriction * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/testsuite * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/union * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/union2 * (delete) axis2/modules/adb-codegen/test/org/apache/axis2/schema/unqualified * (edit) axis2/modules/adb-tests/pom.xml * (add) axis2/modules/adb-tests/src/test/java/helper * (add) axis2/modules/adb-tests/src/test/java/helper/org * (add) axis2/modules/adb-tests/src/test/java/helper/org/apache * (add) axis2/modules/adb-tests/src/test/java/helper/org/apache/axis2 * (add) axis2/modules/adb-tests/src/test/java/helper/org/apache/axis2/schema * (add) axis2/modules/adb-tests/src/test/java/helper/org/apache/axis2/schema/testsuite * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/ADBBeanUtil.java * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/AbstractTestCase.java * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/all * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/anytype * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/attribute * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/base64binary * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/booleantest * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/chameleon * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/choice * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/decimal * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/defaultnamespaces * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/defaultvalue * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/enumeration * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/extension * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/fix * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/group * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/innerchoice * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/innerparticleextension * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/schema/innerparticles * (add)
[jira] [Commented] (AXIS2-5846) Local file inclusion vulnerability in SimpleHTTPServer
[ https://issues.apache.org/jira/browse/AXIS2-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980401#comment-15980401 ] Hudson commented on AXIS2-5846: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #111 (See [https://builds.apache.org/job/axis2-1.7/111/]) AXIS2-5846: Merge r1792353 to the 1.7 branch. (veithen: rev 1792354) * (edit) axis2 * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/HTTPTransportUtils.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/HTTPWorker.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/ListingAgent.java > Local file inclusion vulnerability in SimpleHTTPServer > -- > > Key: AXIS2-5846 > URL: https://issues.apache.org/jira/browse/AXIS2-5846 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.6.2, 1.7.4 >Reporter: Nupur > > Defect CSCvd86595: Local file inclusion vulnerability in Axis2 > An defect has been raised on Present PCP 7.3 axis version > *There is a Local File Inclusion (LFI) present in the Axis2 service. It > allows the attacker to view certain files that would normally be > inaccessible. This is a violation of PSB requirement SEC-SUP-PATCH because > this is a publicly disclosed vulnerability with a patch. > *security impact: Some of the files that are accessible via this LFI contain > the username and password to the Axis2 admin interface. While the admin > interface appears to be disabled currently, if it was ever enabled or an > attacker found a way to access it, they would gain admin access to the Axis2 > system. > In addition, this vulnerability is publicly known, which makes it more likely > to be exploited by an attacker. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5846) Local file inclusion vulnerability in SimpleHTTPServer
[ https://issues.apache.org/jira/browse/AXIS2-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980384#comment-15980384 ] Hudson commented on AXIS2-5846: --- UNSTABLE: Integrated in Jenkins build Axis2 #3688 (See [https://builds.apache.org/job/Axis2/3688/]) AXIS2-5846: Fix a local file inclusion vulnerability in SimpleHTTPServer. This occurs because axis2server.sh adds the root directory of the binary distribution to the class path, and SimpleHTTPServer doesn't limit the search for XSD/WSDL files to the service class loader. This means that axis2.xml is accessible remotely via a specially crafted query string (xsd=../conf/axis2.xml). Although AxisServlet is not known to be vulnerable, this change also modifies ListingAgent to limit the search to the service class loader. (veithen: rev 1792353) * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/HTTPTransportUtils.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/HTTPWorker.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/ListingAgent.java > Local file inclusion vulnerability in SimpleHTTPServer > -- > > Key: AXIS2-5846 > URL: https://issues.apache.org/jira/browse/AXIS2-5846 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.6.2, 1.7.4 >Reporter: Nupur > > Defect CSCvd86595: Local file inclusion vulnerability in Axis2 > An defect has been raised on Present PCP 7.3 axis version > *There is a Local File Inclusion (LFI) present in the Axis2 service. It > allows the attacker to view certain files that would normally be > inaccessible. This is a violation of PSB requirement SEC-SUP-PATCH because > this is a publicly disclosed vulnerability with a patch. > *security impact: Some of the files that are accessible via this LFI contain > the username and password to the Axis2 admin interface. While the admin > interface appears to be disabled currently, if it was ever enabled or an > attacker found a way to access it, they would gain admin access to the Axis2 > system. > In addition, this vulnerability is publicly known, which makes it more likely > to be exploited by an attacker. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (RAMPART-440) update OpenSAML to 2.6.1
[ https://issues.apache.org/jira/browse/RAMPART-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973652#comment-15973652 ] Hudson commented on RAMPART-440: SUCCESS: Integrated in Jenkins build Rampart #2366 (See [https://builds.apache.org/job/Rampart/2366/]) RAMPART-440: Upgrade OpenSAML. (veithen: rev 1791842) * (edit) trunk/modules/rampart-trust/src/main/java/org/apache/rahas/RampartSAMLBootstrap.java * (edit) trunk/pom.xml > update OpenSAML to 2.6.1 > > > Key: RAMPART-440 > URL: https://issues.apache.org/jira/browse/RAMPART-440 > Project: Rampart > Issue Type: Improvement > Components: rampart-core >Affects Versions: 1.7.0 >Reporter: syed riazur rahman > Fix For: 1.8.0 > > > Rampart uses OpenSAML 2.5.1 (July 2011), which brings many outdated > dependencies. Is it possible to include the current version of openSAML? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5661) Axis2 1.6.2 @ Websphere 8.5 emits NumberFormatException intermittently.
[
https://issues.apache.org/jira/browse/AXIS2-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973642#comment-15973642
]
Hudson commented on AXIS2-5661:
---
SUCCESS: Integrated in Jenkins build Axis2 #3687 (See
[https://builds.apache.org/job/Axis2/3687/])
AXIS2-5661: Ignore empty values for the http.proxyPort system property.
(veithen: rev 1791838)
* (edit)
axis2/modules/transport/http-hc3/src/main/java/org/apache/axis2/transport/http/impl/httpclient3/HTTPProxyConfigurator.java
* (edit)
axis2/modules/transport/http/src/org/apache/axis2/transport/http/impl/httpclient4/HTTPProxyConfigurator.java
> Axis2 1.6.2 @ Websphere 8.5 emits NumberFormatException intermittently.
> ---
>
> Key: AXIS2-5661
> URL: https://issues.apache.org/jira/browse/AXIS2-5661
> Project: Axis2
> Issue Type: Improvement
> Components: transports
>Affects Versions: 1.6.2
> Environment: Websphere 8.5 on Linux
>Reporter: ARUNKUMAR NOHWAR
> Labels: easyfix, patch
> Attachments: AXIS-5661.patch
>
>
> Recently we upgraded from[Axis2-1.4.1 on Websphere-7.0] to [Axis2-1.6.2 on
> Websphere-8.5]. And the same application code start giving an intermittent
> exception. The stacktrace of the exception can be found at the end of the
> description.
> Analysis -
> The creation of these system properties is the root cause of the issue.
> http.proxyHost and http.proxyPort
> These system porperties are created with non-null but empty string "" values.
> We find that our application has no logic to create these properties. These
> properties probably created by a 3rd party library or websphere server.
> Workaround -
> We write a code to remove these system properties (System.clearProperty())
> just before the flow goes to Axis2 part of the application.
> We cannot write this code during application startup as these properties are
> created intermittently when the application is running for few days and the
> exception appears again.
> Recommendations -
> In this axis code
> packageorg.apache.axis2.transport.http.util
> class HTTPProxyConfigurationUtil
> method configure(MessageContext messageContext,
> HttpClient httpClient,
> HostConfiguration config)
> the exception appears at the following line of code -
> String port = System.getProperty(HTTP_PROXY_PORT);
> if(port != null) {
> proxyPort = Integer.parseInt(port);
> }
> This is because the non-null but empty-string ("") valued key
> HTTP_PROXY_PORT, results in NumberFormatException.
> Can we please add an empty-string value check in the "if" condition ?
> Adding further thse empty-string valued keys, both host and port, might
> overwrite the correct values built from axis2.xml. Hence we can apply the
> same checks to both of the system properties - host and port - if conditions.
> StackTrace -
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at java.lang.reflect.Method.invoke(Method.java:611)
> …….
> at
> com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
> at
> com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
> at
> com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862)
> Caused by: java.lang.NumberFormatException: For input string: ""
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:59)
> at java.lang.Integer.parseInt(Integer.java:481)
> at java.lang.Integer.parseInt(Integer.java:510)
> at
> org.apache.axis2.transport.http.util.HTTPProxyConfigurationUtil.configure(HTTPProxyConfigurationUtil.java:154)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.getHostConfiguration(AbstractHTTPSender.java:294)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:591)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
> at
> org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404)
> at
>
[jira] [Commented] (AXIS2-5841) module archive name error when loading repository from url
[
https://issues.apache.org/jira/browse/AXIS2-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944752#comment-15944752
]
Hudson commented on AXIS2-5841:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #110 (See
[https://builds.apache.org/job/axis2-1.7/110/])
AXIS2-5841: Merge r1789029 to the 1.7 branch. (veithen: rev 1789058)
* (edit)
axis2/modules/kernel/src/org/apache/axis2/deployment/ModuleDeployer.java
> module archive name error when loading repository from url
> --
>
> Key: AXIS2-5841
> URL: https://issues.apache.org/jira/browse/AXIS2-5841
> Project: Axis2
> Issue Type: Bug
> Components: deployment
>Affects Versions: 1.7.4
>Reporter: Pieter @ DHL
>Priority: Minor
>
> Hi,
> I'm trying to deploy an axis 2 webservice on an embedded jetty server using
> spring boot (1.5.1), but axis can't deploy any of the modules when I start
> the application.
> I bootstrap the axis servlet with spring boot as follows:
> {code}
> @Bean
> public ServletRegistrationBean axisServletRegistration() {
> // in order for the axis servlet to work as expected we need to tweak
> the default axis settings (axis.xml)
> // axis assumes that the axis servlet is mapped to "/*" in the
> "axis2" context of the container
> // but in this case the axis servlet is mapped to "/axis2/*" in the
> root context of the container
> // contextRoot -> /(instead of axis2)
> // servicePath -> axis2/services (instead of services)
> ServletRegistrationBean servletRegistrationBean = new
> ServletRegistrationBean(new AxisServlet(), "/axis2/*");
> servletRegistrationBean.setName("AxisServlet");
> servletRegistrationBean.setOrder(1);
> servletRegistrationBean.setLoadOnStartup(1);
> servletRegistrationBean.getInitParameters().put(PARAM_AXIS2_XML_URL,
> Resources.getResource("axis2/conf/axis2.xml").toString());
>
> servletRegistrationBean.getInitParameters().put(PARAM_AXIS2_REPOSITORY_URL,
> Resources.getResource("axis2/").toString());
> return servletRegistrationBean;
> }
> {code}
> The axis2 folder on my classpath looks like this:
> * axis2
> ** conf
> *** axis2.xml
> ** modules
> *** addressing-1.7.4.mar
> *** axis2-jaxws-mar-1.7.4.mar
> *** mex-1.7.4.mar
> *** modules.list
> *** mtompolicy-1.7.4.mar
> *** ping-1.7.4.mar
> *** scripting-1.7.4.mar
> *** soapmonitor-1.7.4.mar*services
> *** services.list
> *** version-1.7.4.aar
> When I start the application I get the following exception:
> {code}
> ERROR 2017-03-09 16:32:40,259 [main] o.a.axis2.deployment.ModuleDeployer: The
> mtompolicy-1.7.4.mar module, which is not valid, caused For input string:
> "mar"
> java.lang.NumberFormatException: For input string: "mar"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.apache.axis2.description.Version.(Version.java:78)
> at
> org.apache.axis2.description.AxisModule.setArchiveName(AxisModule.java:171)
> at
> org.apache.axis2.deployment.ModuleDeployer.deoloyFromUrl(ModuleDeployer.java:207)
> at
> org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:120)
> 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.DeploymentEngine.loadRepositoryFromURL(DeploymentEngine.java:303)
> at
> org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:212)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
> at
> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:620)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:471)
> at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:637)
> at
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:421)
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:744)
> at
> org.springframework.boot.context.embedded.jetty.JettyEmbeddedWebAppContext$JettyEmbeddedServletHandler.deferredInitialize(JettyEmbeddedWebAppContext.java:46)
> at
>
[jira] [Commented] (AXIS2-5841) module archive name error when loading repository from url
[
https://issues.apache.org/jira/browse/AXIS2-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944318#comment-15944318
]
Hudson commented on AXIS2-5841:
---
SUCCESS: Integrated in Jenkins build Axis2 #3682 (See
[https://builds.apache.org/job/Axis2/3682/])
AXIS2-5841: Fix module file name parsing for repositories loaded from URL.
(veithen: rev 1789029)
* (edit)
axis2/modules/kernel/src/org/apache/axis2/deployment/ModuleDeployer.java
> module archive name error when loading repository from url
> --
>
> Key: AXIS2-5841
> URL: https://issues.apache.org/jira/browse/AXIS2-5841
> Project: Axis2
> Issue Type: Bug
> Components: deployment
>Affects Versions: 1.7.4
>Reporter: Pieter @ DHL
>Priority: Minor
>
> Hi,
> I'm trying to deploy an axis 2 webservice on an embedded jetty server using
> spring boot (1.5.1), but axis can't deploy any of the modules when I start
> the application.
> I bootstrap the axis servlet with spring boot as follows:
> {code}
> @Bean
> public ServletRegistrationBean axisServletRegistration() {
> // in order for the axis servlet to work as expected we need to tweak
> the default axis settings (axis.xml)
> // axis assumes that the axis servlet is mapped to "/*" in the
> "axis2" context of the container
> // but in this case the axis servlet is mapped to "/axis2/*" in the
> root context of the container
> // contextRoot -> /(instead of axis2)
> // servicePath -> axis2/services (instead of services)
> ServletRegistrationBean servletRegistrationBean = new
> ServletRegistrationBean(new AxisServlet(), "/axis2/*");
> servletRegistrationBean.setName("AxisServlet");
> servletRegistrationBean.setOrder(1);
> servletRegistrationBean.setLoadOnStartup(1);
> servletRegistrationBean.getInitParameters().put(PARAM_AXIS2_XML_URL,
> Resources.getResource("axis2/conf/axis2.xml").toString());
>
> servletRegistrationBean.getInitParameters().put(PARAM_AXIS2_REPOSITORY_URL,
> Resources.getResource("axis2/").toString());
> return servletRegistrationBean;
> }
> {code}
> The axis2 folder on my classpath looks like this:
> * axis2
> ** conf
> *** axis2.xml
> ** modules
> *** addressing-1.7.4.mar
> *** axis2-jaxws-mar-1.7.4.mar
> *** mex-1.7.4.mar
> *** modules.list
> *** mtompolicy-1.7.4.mar
> *** ping-1.7.4.mar
> *** scripting-1.7.4.mar
> *** soapmonitor-1.7.4.mar*services
> *** services.list
> *** version-1.7.4.aar
> When I start the application I get the following exception:
> {code}
> ERROR 2017-03-09 16:32:40,259 [main] o.a.axis2.deployment.ModuleDeployer: The
> mtompolicy-1.7.4.mar module, which is not valid, caused For input string:
> "mar"
> java.lang.NumberFormatException: For input string: "mar"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.apache.axis2.description.Version.(Version.java:78)
> at
> org.apache.axis2.description.AxisModule.setArchiveName(AxisModule.java:171)
> at
> org.apache.axis2.deployment.ModuleDeployer.deoloyFromUrl(ModuleDeployer.java:207)
> at
> org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:120)
> 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.DeploymentEngine.loadRepositoryFromURL(DeploymentEngine.java:303)
> at
> org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:212)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
> at
> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:620)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:471)
> at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:637)
> at
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:421)
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:744)
> at
> org.springframework.boot.context.embedded.jetty.JettyEmbeddedWebAppContext$JettyEmbeddedServletHandler.deferredInitialize(JettyEmbeddedWebAppContext.java:46)
> at
>
[jira] (RAMPART-423) STS implementation may lead to performance reduction
Title: Message Title Hudson commented on RAMPART-423 Re: STS implementation may lead to performance reduction SUCCESS: Integrated in Jenkins build Rampart #2352 (See https://builds.apache.org/job/Rampart/2352/) RAMPART-423: Improve the efficiency of SimpleTokenStore. Based on a patch provided by Boris Dushanov. (veithen: rev 1781007) (edit) trunk (edit) trunk/modules/rampart-trust/src/main/java/org/apache/rahas/SimpleTokenStore.java Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (RAMPART-339) Sample 09 for rampart policy samples -(different security policies to secure request and response messages with policy attachments)
Title: Message Title Hudson commented on RAMPART-339 Re: Sample 09 for rampart policy samples -(different security policies to secure request and response messages with policy attachments) SUCCESS: Integrated in Jenkins build Rampart #2351 (See https://builds.apache.org/job/Rampart/2351/) RAMPART-339: Add sample 09 with different security policies for request and response. Based on a patch provided by Hasini Gunasinghe. (veithen: rev 1780940) (edit) trunk (edit) trunk/modules/rampart-samples/policy/build.xml (add) trunk/modules/rampart-samples/policy/sample09 (edit) trunk/modules/rampart-samples/src/test/java/org/apache/rampart/samples/runner/SampleTest.java (add) trunk/src/site/resources/samples/msgs/req09.xml (add) trunk/src/site/resources/samples/msgs/res09.xml Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (RAMPART-287) Supporting Tokens Not Encrypted When Protection Order is Encrypt Before Signing
Title: Message Title Hudson commented on RAMPART-287 Re: Supporting Tokens Not Encrypted When Protection Order is Encrypt Before Signing SUCCESS: Integrated in Jenkins build Rampart #2350 (See https://builds.apache.org/job/Rampart/2350/) Revert r1780826 (patch for RAMPART-287); this was supposed to go to a branch, not the trunk. (veithen: rev 1780829) (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/AsymmetricBindingBuilder.java (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/BindingBuilder.java Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (RAMPART-287) Supporting Tokens Not Encrypted When Protection Order is Encrypt Before Signing
Title: Message Title Hudson commented on RAMPART-287 Re: Supporting Tokens Not Encrypted When Protection Order is Encrypt Before Signing SUCCESS: Integrated in Jenkins build Rampart #2349 (See https://builds.apache.org/job/Rampart/2349/) RAMPART-287: Apply patch provided by Suresh Attanayake. (veithen: rev 1780826) (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/AsymmetricBindingBuilder.java (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/BindingBuilder.java Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (RAMPART-331) Unreachable code in org.apache.rahas.STSMessageReceiver.invokeBusinessLogic() - "dispatcher" is never null at end of try
Title: Message Title Hudson commented on RAMPART-331 Re: Unreachable code in org.apache.rahas.STSMessageReceiver.invokeBusinessLogic() - "dispatcher" is never null at end of try SUCCESS: Integrated in Jenkins build Rampart #2348 (See https://builds.apache.org/job/Rampart/2348/) RAMPART-331 : Remove unreachable code. Patch provided by David Tonhofer. (veithen: rev 1780787) (edit) trunk/modules/rampart-trust/src/main/java/org/apache/rahas/STSMessageReceiver.java Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] [Commented] (RAMPART-417) Support for transport binding Kerberos v5 authentication
[ https://issues.apache.org/jira/browse/RAMPART-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15844227#comment-15844227 ] Hudson commented on RAMPART-417: SUCCESS: Integrated in Jenkins build Rampart #2344 (See [https://builds.apache.org/job/Rampart/2344/]) RAMPART-417, RAMPART-433: Add Kerberos support. Based on patches provided by Detelin Yordanov and Boris Dushanov. (veithen: rev 1780752) * (edit) trunk * (edit) trunk/modules/rampart-core/pom.xml * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/RampartEngine.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/BindingBuilder.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/TransportBindingBuilder.java * (add) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/builders/KerberosConfigBuilder.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/builders/RampartConfigBuilder.java * (add) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/model/KerberosConfig.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/model/RampartConfig.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/util/RampartUtil.java * (edit) trunk/modules/rampart-core/src/main/resources/META-INF/services/org.apache.neethi.builders.AssertionBuilder * (edit) trunk/modules/rampart-core/src/main/resources/org/apache/rampart/errors.properties * (add) trunk/modules/rampart-core/src/test/java/org/apache/rampart/policy * (add) trunk/modules/rampart-core/src/test/resources/org/apache/rampart/policy * (edit) trunk/modules/rampart-integration/pom.xml * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/KerberosDelegationService.java * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/KerberosDelegationServiceValidator.java * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/RampartKerberosTest.java * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/util * (add) trunk/modules/rampart-integration/src/test/resources/kerberos * (add) trunk/modules/rampart-integration/src/test/resources/rampart/kerberos * (edit) trunk/modules/rampart-policy/pom.xml * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/Constants.java * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/SP11Constants.java * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/SP12Constants.java * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/SPConstants.java * (add) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/model/KerberosToken.java * (add) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy11/builders/KerberosTokenBuilder.java * (add) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy12/builders/KerberosTokenBuilder.java * (edit) trunk/modules/rampart-policy/src/main/resources/META-INF/services/org.apache.neethi.builders.AssertionBuilder * (add) trunk/modules/rampart-policy/src/test * (edit) trunk/pom.xml > Support for transport binding Kerberos v5 authentication > > > Key: RAMPART-417 > URL: https://issues.apache.org/jira/browse/RAMPART-417 > Project: Rampart > Issue Type: New Feature > Components: rampart-core >Affects Versions: 1.6.2 >Reporter: Detelin Yordanov >Assignee: Andreas Veithen > Labels: Patch > Fix For: 1.7.1 > > Attachments: ImportService.wsdl, rampart_kerberos.patch > > > While other web services runtimes (Metro, CXF, WCF) provide some level of > support for Kerberos authentication, Rampart is lacking such at the moment. > There are two basic mechanisms for bringing Kerberos authentication to web > services: > 1. Kerberos authentication over secure transport - transport-level security > (https) with Kerberos token attached as supporting token > 2. Kerberos authentication using symmetric binding - Kerberos session key is > used for message protection and Kerberos token - for client authentication > My team developed a Rampart extension that provides support for Kerberos > authentication over secure transport (1) and we are willing to contribute > this to the community. This support requires Kerberos enhancements released > with wss4j 1.6.16 and can work with both Java 1.6 and 1.7. We have tested > this for interoperability with Apache DS and Active Directory Kerberos > servers. This support can also be used to develop an Axis2 client for a MS > .NET web service that uses > [KerberosOverTransport|http://msdn.microsoft.com/en-us/library/aa751836%28v=vs.110%29.asp] > security policy - for this an extension in Axis2
[jira] [Commented] (RAMPART-433) Support for Kerberos v5 delegated authentication
[ https://issues.apache.org/jira/browse/RAMPART-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15844226#comment-15844226 ] Hudson commented on RAMPART-433: SUCCESS: Integrated in Jenkins build Rampart #2344 (See [https://builds.apache.org/job/Rampart/2344/]) RAMPART-417, RAMPART-433: Add Kerberos support. Based on patches provided by Detelin Yordanov and Boris Dushanov. (veithen: rev 1780752) * (edit) trunk * (edit) trunk/modules/rampart-core/pom.xml * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/RampartEngine.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/BindingBuilder.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/builder/TransportBindingBuilder.java * (add) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/builders/KerberosConfigBuilder.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/builders/RampartConfigBuilder.java * (add) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/model/KerberosConfig.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/model/RampartConfig.java * (edit) trunk/modules/rampart-core/src/main/java/org/apache/rampart/util/RampartUtil.java * (edit) trunk/modules/rampart-core/src/main/resources/META-INF/services/org.apache.neethi.builders.AssertionBuilder * (edit) trunk/modules/rampart-core/src/main/resources/org/apache/rampart/errors.properties * (add) trunk/modules/rampart-core/src/test/java/org/apache/rampart/policy * (add) trunk/modules/rampart-core/src/test/resources/org/apache/rampart/policy * (edit) trunk/modules/rampart-integration/pom.xml * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/KerberosDelegationService.java * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/KerberosDelegationServiceValidator.java * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/RampartKerberosTest.java * (add) trunk/modules/rampart-integration/src/test/java/org/apache/rampart/util * (add) trunk/modules/rampart-integration/src/test/resources/kerberos * (add) trunk/modules/rampart-integration/src/test/resources/rampart/kerberos * (edit) trunk/modules/rampart-policy/pom.xml * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/Constants.java * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/SP11Constants.java * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/SP12Constants.java * (edit) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/SPConstants.java * (add) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy/model/KerberosToken.java * (add) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy11/builders/KerberosTokenBuilder.java * (add) trunk/modules/rampart-policy/src/main/java/org/apache/ws/secpolicy12/builders/KerberosTokenBuilder.java * (edit) trunk/modules/rampart-policy/src/main/resources/META-INF/services/org.apache.neethi.builders.AssertionBuilder * (add) trunk/modules/rampart-policy/src/test * (edit) trunk/pom.xml > Support for Kerberos v5 delegated authentication > > > Key: RAMPART-433 > URL: https://issues.apache.org/jira/browse/RAMPART-433 > Project: Rampart > Issue Type: New Feature > Components: rampart-core >Affects Versions: 1.6.2 >Reporter: Boris Dushanov > Labels: Patch > Fix For: 1.8.0 > > Attachments: alice.keytab, bob.keytab, > rampart_kerberos_delegation_with_keytab_instructions.patch > > > This support is based on the Kerberos v5 enhancement provided in RAMPART-417. > Kerberos delegation is supported in wss4j since 1.6.17 so this feature > requires upgrade from 1.6.16 to 1.6.17.The upgrade is smooth and requires no > changes. > The changes in rampart uses the wss4j capabilities.Rampart's kerberos > configuration is enhanced with two new settings - one for requesting a > kerberos delegation credential and one for setting such. When the latter is > set, rampart requests a Kerberos security token on behalf of the user for > which the credentials are. > The provided implementation also includes a corresponding integration test. > ApacheDS 2.0 is required as 1.5.7 seems to have issues when delegation is > requested.Because of that, the existing kerberos tests are also made to work > with the newer ApacheDS version. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-2037) Improvement in json support for Axis2
[ https://issues.apache.org/jira/browse/AXIS2-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833695#comment-15833695 ] Hudson commented on AXIS2-2037: --- SUCCESS: Integrated in Jenkins build Axis2 #3656 (See [https://builds.apache.org/job/Axis2/3656/]) AXIS2-2037: Using a non standard content type (application/json/badgerfish) is already a questionable choice, but at least it should be spec compliant (which is not the case because of the second slash). Use application/json+badgerfish instead. (veithen: rev 1779844) * (edit) axis2/modules/json/test-repository/json/axis2.xml * (edit) axis2/modules/json/test/org/apache/axis2/json/JSONIntegrationTest.java * (edit) axis2/modules/json/test/org/apache/axis2/json/JSONTestConstants.java > Improvement in json support for Axis2 > - > > Key: AXIS2-2037 > URL: https://issues.apache.org/jira/browse/AXIS2-2037 > Project: Axis2 > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Isuru Eranga Suriarachchi >Assignee: Thilina Gunarathne > Fix For: 1.2 > > Attachments: latest_patch.txt, patch.txt, patch.txt > > > There are 2 major json conventions available as Badgerfish and Mapped. So far > Axis2 supported only Badgerfish. It is bit inconvenient for the javascript > users to use Badgerfish formatted json strings. Mapped convention is a good > solution for this matter. So in this patch I have implemented support for > Mapped convention as well. Here I have used 2 different JSONBuilders and the > default one is using Mapped convention. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5052) Unable to send compressed message!!
[
https://issues.apache.org/jira/browse/AXIS2-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828906#comment-15828906
]
Hudson commented on AXIS2-5052:
---
SUCCESS: Integrated in Jenkins build Axis2 #3650 (See
[https://builds.apache.org/job/Axis2/3650/])
Streamline the GZIP request compression handling in the HTTP transport:
- Move shared code to HTTPSender.
- Have a single place to decide whether GZIP is enabled or not.
- Allow GZIP compression even if chunking is disabled (AXIS2-5052).
- Use Axiom's Blob API to store the request content when chunking is disabled.
(veithen: rev 1779387)
* (edit)
axis2/modules/transport/http-hc3/src/main/java/org/apache/axis2/transport/http/impl/httpclient3/RequestImpl.java
* (edit)
axis2/modules/transport/http/src/org/apache/axis2/transport/http/AxisRequestEntity.java
* (edit)
axis2/modules/transport/http/src/org/apache/axis2/transport/http/HTTPSender.java
* (edit)
axis2/modules/transport/http/src/org/apache/axis2/transport/http/impl/httpclient4/RequestImpl.java
> Unable to send compressed message!!
> ---
>
> Key: AXIS2-5052
> URL: https://issues.apache.org/jira/browse/AXIS2-5052
> Project: Axis2
> Issue Type: Bug
> Components: client-api
>Affects Versions: 1.5.4
> Environment: Windows xp,
>Reporter: anil bondalapati
> Labels: gzip
>
> Hi,
> I have two webservices deployed on two different servers. (service1 and
> service2)
> From my client program I have enabled the GZIP format on the request for the
> serviceClient.
> When I make a call to the service1, the message is compressed and sent to the
> server and everything looks good.
> After some time I made a call to the service2 and the request xml is sent in
> compressed format and looks fine.
> But Now if I sent the message to the service1, it is in clear text and not
> using the compressed format.
> Am I missing any options on the ServiceClient. Please let me know if you have
> faced this problem.
> Here is the code I am using:
> ! mp;n! bsp;HttpMethodRetryHandler retry_handler = new
> DefaultHttpMethodRetryHandler(0, false);
> HttpClientParams params = new HttpClientParams();
> params.setParameter(HttpMethodParams.RETRY_HANDLER,
> retry_handler);
> options.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, new
> org.apache.commons.httpclient.HttpClient(params, manager));
> options.setProperty(HTTPConstants.MC_GZIP_REQUEST, true);
> options.setProperty(HTTPConstants.MC_ACCEPT_GZIP, true);
> options.setProperty(HTTPConstants.MC_GZIP_RESPONSE, true);
> &! nbsp;!
> options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, true);
>
> options.setTimeOutInMilliSeconds(wsTimeOutInMilliSeconds);
> options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> wsTimeOutInMilliSeconds);
> options.setCallTransportCleanup(true);
> Any help is greatly appreciated.
> Thanks
> Anil.
> After debugging the source code I Have found that in AxisRequestEntity.java
> at line # 80, the condition is also looking for CHUNKED flag. Is this a must
> if you want to enable gzip on request?
> if (gzip != null && JavaUtils.isTrueExplicitly(gzip) && chunked) {
> outStream = new GZIPOutputStream(outStream);
> }
> I have another question:
> THis is the code where I create an instance of the sub.
> *SERVICE 1*
> {code}
> /**
> * Returns (new or existing) reference to Web Service TransactionManager.
> * @return TransactionManager
> */
> public TransactionManagerStub
> getTransactionManagerStub(TransactionManagerStub stub, boolean retry, boolean
> compressMessage) throws Exception
> {
> if (stub == null)
> {
> try
> {
> String url = Gateway.getProperty("application",
> "TransactionWSUrl", "");
> String user = Gateway.getProperty("application",
> "WebserviceUser", "");
> String password = Gateway.getProperty("application",
> "WebservicePasswd", "");
> int wsTimeOutInMilliSeconds =
> Integer.parseInt(Gateway.getProperty("application",
> "wsTimeOutInMilliSeconds", ""));
> if (logger.isDebugEnabled())
> logger.debug(url);
> stub = new TransactionManagerStub(url);
> ServiceClient sc = stub._getServiceClient();
> sc.cleanup();
> // Set security options
> org.apache.axis2.client.Options options = sc.getOptions();
> options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
> loadPolicy(AXIS2_RAMPART_POLICY));
>
[jira] [Commented] (AXIS2-4021) AbstractHTTPSender: changes to the isAllowRetry flag have no effect
[ https://issues.apache.org/jira/browse/AXIS2-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826877#comment-15826877 ] Hudson commented on AXIS2-4021: --- UNSTABLE: Integrated in Jenkins build Axis2 #3648 (See [https://builds.apache.org/job/Axis2/3648/]) Clean up the mess related to how we maintain the isAllowedRetry flag. This should also fix AXIS2-4021. (veithen: rev 1779253) * (edit) axis2/modules/transport/http-hc3/src/main/java/org/apache/axis2/transport/http/impl/httpclient3/HTTPSenderImpl.java * (edit) axis2/modules/transport/http-hc3/src/main/java/org/apache/axis2/transport/http/impl/httpclient3/RequestImpl.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/AbstractHTTPSender.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/AxisRequestEntity.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/HTTPSender.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/impl/httpclient4/HTTPSenderImpl.java * (edit) axis2/modules/transport/http/src/org/apache/axis2/transport/http/impl/httpclient4/RequestImpl.java > AbstractHTTPSender: changes to the isAllowRetry flag have no effect > --- > > Key: AXIS2-4021 > URL: https://issues.apache.org/jira/browse/AXIS2-4021 > Project: Axis2 > Issue Type: Bug > Components: transports >Affects Versions: 1.4.1 > Environment: bug independent of environment >Reporter: Uwe Kylau > > The class org.apache.axis2.transport.http.AbstractHTTPSender contains a > boolean flag isAllowedRetry, initally set to false. > In class HTTPSender this flag is propagated to the AxisRequestEntity used by > the PostMethod (or PutMethod). > However, this is done BEFORE executeMethod(...) is called on > AbstractHTTPSender. > Part of executeMethod(...) is to retrieve the HostConfiguration, which in > turn includes processing the authentication information. > Now, the problem is that isAllowedRetry might change in > setAuthenticationInfo(...), but this change is NEVER propagated to the > AxisRequestEntity. > AxisRequestEntity does not even allow to change parameters once it has been > created. > Thanks in advance for fixing. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[
https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824506#comment-15824506
]
Hudson commented on AXIS2-5781:
---
SUCCESS: Integrated in Jenkins build Axis2 #3643 (See
[https://builds.apache.org/job/Axis2/3643/])
AXIS2-5781: Don't let SchemaWriterTest overwrite files in the source tree.
(veithen: rev 1779074)
* (edit)
axis2/modules/codegen/test/org/apache/axis2/wsdl/codegen/writer/SchemaWriterTest.java
> Maven Build - Module: kernel - generates / modifies file under source-control
> - should build in output directory
>
>
> Key: AXIS2-5781
> URL: https://issues.apache.org/jira/browse/AXIS2-5781
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
>Reporter: Jeff Thomas
>Priority: Minor
>
> Maven Build for axis2-kernel (./modules/kernel/pom.xml).
> In the axis2-kernel Maven Module (and at in at least the axis2-integration
> module as well) test ant-scripts and unit-tests run against the
> "./test-resources" directory instead of the "./target/test-resources"
> directory.
> In the interest of Maven "compliance" the build process should not edit,
> touch or otherwise "dirty" source-code files.
> Examples:
> 1. The Ant-script "test-resources/deployment/service2/build.xml" creates
> temporary directories, generates content, and removes these temporary
> directories directly within the "test-resources" source directory.
> 2. The Unit-Test utility method 'readWSDLFromFile' in XMLSchemaTest creates a
> File reference to a file in "test-resources" and performs the following:
> {code:java}XMLPrettyPrinter.prettify(file);{code}
> This updates (dirties) the input source-file - on my windows build it changes
> the line-endings from Unix to Windows.
> The current Maven POMs already take care of copying the "test-resources"
> directory to "target/test-resources" so all of the required input files and
> ant-scripts are available there. Therefore, the POM ANT "dir" properties and
> the JUnit tests just need to be updated to use these instead of the
> source-code originals.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[
https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824418#comment-15824418
]
Hudson commented on AXIS2-5781:
---
SUCCESS: Integrated in Jenkins build Axis2 #3642 (See
[https://builds.apache.org/job/Axis2/3642/])
AXIS2-5781: Don't overwrite files in the source tree. (veithen: rev 1779069)
* (edit)
axis2/modules/kernel/test/org/apache/axis2/description/java2wsdl/XMLSchemaTest.java
> Maven Build - Module: kernel - generates / modifies file under source-control
> - should build in output directory
>
>
> Key: AXIS2-5781
> URL: https://issues.apache.org/jira/browse/AXIS2-5781
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
>Reporter: Jeff Thomas
>Priority: Minor
>
> Maven Build for axis2-kernel (./modules/kernel/pom.xml).
> In the axis2-kernel Maven Module (and at in at least the axis2-integration
> module as well) test ant-scripts and unit-tests run against the
> "./test-resources" directory instead of the "./target/test-resources"
> directory.
> In the interest of Maven "compliance" the build process should not edit,
> touch or otherwise "dirty" source-code files.
> Examples:
> 1. The Ant-script "test-resources/deployment/service2/build.xml" creates
> temporary directories, generates content, and removes these temporary
> directories directly within the "test-resources" source directory.
> 2. The Unit-Test utility method 'readWSDLFromFile' in XMLSchemaTest creates a
> File reference to a file in "test-resources" and performs the following:
> {code:java}XMLPrettyPrinter.prettify(file);{code}
> This updates (dirties) the input source-file - on my windows build it changes
> the line-endings from Unix to Windows.
> The current Maven POMs already take care of copying the "test-resources"
> directory to "target/test-resources" so all of the required input files and
> ant-scripts are available there. Therefore, the POM ANT "dir" properties and
> the JUnit tests just need to be updated to use these instead of the
> source-code originals.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5828) Current Documentation is not mobile Friendly
[ https://issues.apache.org/jira/browse/AXIS2-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816524#comment-15816524 ] Hudson commented on AXIS2-5828: --- SUCCESS: Integrated in Jenkins build Axis2 #3624 (See [https://builds.apache.org/job/Axis2/3624/]) AXIS2-5828: Update the versions of the parent POM, maven-site-plugin and maven-fluido-skin. (veithen: rev 1778204) * (edit) axis2/pom.xml * (edit) axis2/src/site/site.xml > Current Documentation is not mobile Friendly > - > > Key: AXIS2-5828 > URL: https://issues.apache.org/jira/browse/AXIS2-5828 > Project: Axis2 > Issue Type: Improvement > Components: documentation >Affects Versions: 1.7.4 >Reporter: Vanjikumaran Sivajothy >Assignee: Andreas Veithen >Priority: Trivial > Fix For: 1.7.5 > > Attachments: MobileFriendly.patch, Screen Shot 2017-01-04 at 2.35.00 > PM.png > > > Current Documentation is not mobile Friendly due the current > maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5828) Current Documentation is not mobile Friendly
[ https://issues.apache.org/jira/browse/AXIS2-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816406#comment-15816406 ] Hudson commented on AXIS2-5828: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #100 (See [https://builds.apache.org/job/axis2-1.7/100/]) AXIS2-5828: Merge r1778204 to the 1.7 branch. (veithen: rev 1778205) * (edit) axis2 * (edit) axis2/pom.xml * (edit) axis2/src/site/site.xml > Current Documentation is not mobile Friendly > - > > Key: AXIS2-5828 > URL: https://issues.apache.org/jira/browse/AXIS2-5828 > Project: Axis2 > Issue Type: Improvement > Components: documentation >Affects Versions: 1.7.4 >Reporter: Vanjikumaran Sivajothy >Assignee: Andreas Veithen >Priority: Trivial > Fix For: 1.7.5 > > Attachments: MobileFriendly.patch, Screen Shot 2017-01-04 at 2.35.00 > PM.png > > > Current Documentation is not mobile Friendly due the current > maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5827) axis2-wsdl2code-maven-plugin shouldn't use Log4j
[
https://issues.apache.org/jira/browse/AXIS2-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799522#comment-15799522
]
Hudson commented on AXIS2-5827:
---
SUCCESS: Integrated in Jenkins build Axis2 #3623 (See
[https://builds.apache.org/job/Axis2/3623/])
Modify the Maven plugins so that they use SLF4J instead of Commons Logging. The
SLF4J API is supported by recent Maven versions and the -X option is honored
for log messages sent via that API.
This also eliminates the warning message about missing log4j configuration
generated by the axis2-wsdl2code-maven-plugin described in AXIS2-5827 and
caused by the change introduced in AXIS2-5364. (veithen: rev 1777379)
* (edit) axis2/modules/tool/axis2-aar-maven-plugin/pom.xml
* (edit) axis2/modules/tool/axis2-java2wsdl-maven-plugin/pom.xml
* (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml
* (edit) axis2/modules/tool/simple-server-maven-plugin/pom.xml
* (edit) axis2/pom.xml
> axis2-wsdl2code-maven-plugin shouldn't use Log4j
>
>
> Key: AXIS2-5827
> URL: https://issues.apache.org/jira/browse/AXIS2-5827
> Project: Axis2
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.7.4
>Reporter: Petr Dvorak
>Assignee: Andreas Veithen
>Priority: Minor
>
> I am using axis2-wsdl2code-maven-plugin to generate my SOAP service client.
> The plugin itself works correctly and it generates a correct SOAP client, but
> I get following warning in console with every build:
> {code}
> log4j:WARN No appenders could be found for logger
> (org.apache.axiom.locator.DefaultOMMetaFactoryLocator).
> log4j:WARN Please initialize the log4j system properly.
> {code}
> I know I need to configure Log4j properties, but I haven't found any
> documentation / help on how to do this for {{axis2-wsdl2code-maven-plugin}}...
> This is my {{pom.xml}} file:
> {code:xml}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> powerauth-java-client-axis
> 0.13.0
> powerauth-java-client-axis
> PowerAuth 2.0 Service Client - Axis
>
> io.getlime.security
> powerauth-parent
> 0.13.0
> ../pom.xml
>
>
>
> org.apache.axis2
> axis2
> 1.6.3
>
>
> org.apache.axis2
> axis2-adb
> 1.6.3
>
>
> org.apache.axis2
> axis2-transport-http
> 1.6.3
>
>
> org.apache.axis2
> axis2-transport-local
> 1.6.3
>
>
> org.apache.ws.commons.axiom
> axiom-api
> 1.2.20
>
>
> org.apache.ws.commons.axiom
> axiom-impl
> 1.2.20
>
>
> org.apache.ws.security
> wss4j
> 1.6.19
>
>
> wsdl4j
> wsdl4j
>
>
>
>
>
>
> org.apache.axis2
> axis2-wsdl2code-maven-plugin
> 1.6.4
>
>
>
> wsdl2code
>
>
>
> io.getlime.powerauth.soap
>
> ${basedir}/src/main/resources/soap/wsdl/service.wsdl
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5364) WSDL2Code Maven plug-in should format generated codes.
[ https://issues.apache.org/jira/browse/AXIS2-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799521#comment-15799521 ] Hudson commented on AXIS2-5364: --- SUCCESS: Integrated in Jenkins build Axis2 #3623 (See [https://builds.apache.org/job/Axis2/3623/]) Modify the Maven plugins so that they use SLF4J instead of Commons Logging. The SLF4J API is supported by recent Maven versions and the -X option is honored for log messages sent via that API. This also eliminates the warning message about missing log4j configuration generated by the axis2-wsdl2code-maven-plugin described in AXIS2-5827 and caused by the change introduced in AXIS2-5364. (veithen: rev 1777379) * (edit) axis2/modules/tool/axis2-aar-maven-plugin/pom.xml * (edit) axis2/modules/tool/axis2-java2wsdl-maven-plugin/pom.xml * (edit) axis2/modules/tool/axis2-wsdl2code-maven-plugin/pom.xml * (edit) axis2/modules/tool/simple-server-maven-plugin/pom.xml * (edit) axis2/pom.xml > WSDL2Code Maven plug-in should format generated codes. > --- > > Key: AXIS2-5364 > URL: https://issues.apache.org/jira/browse/AXIS2-5364 > Project: Axis2 > Issue Type: Improvement > Components: Tools >Affects Versions: 1.5.6, 1.6.2 >Reporter: Sagara Gunathunga >Assignee: Sagara Gunathunga > Fix For: 1.6.3, 1.7.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5824) [Transport][JMS] Change thrown exception
[
https://issues.apache.org/jira/browse/AXIS2-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761638#comment-15761638
]
Hudson commented on AXIS2-5824:
---
SUCCESS: Integrated in Jenkins build Axis2 #3612 (See
[https://builds.apache.org/job/Axis2/3612/])
AXIS2-5824: Avoid misleading JMS lookup exception referring to
dynamic(Queues|Topics). (veithen: rev 1775102)
* (edit)
axis2/modules/transport/jms/src/main/java/org/apache/axis2/transport/jms/JMSUtils.java
> [Transport][JMS] Change thrown exception
>
>
> Key: AXIS2-5824
> URL: https://issues.apache.org/jira/browse/AXIS2-5824
> Project: Axis2
> Issue Type: Improvement
> Components: JMS transport
>Affects Versions: 1.7.4
>Reporter: Ziborov Egor
>Priority: Trivial
>
> When we tries to lookup some destination for example "my.loc.dest" and it
> doesn't exist than we handle exception with message:
> While trying to lookup 'dynamicQueues.local.rmk.access.SMKtoRMK.dq' didn't
> find subcontext 'dynamicQueues'. Resolved '' (for Weblogic)
> I'd offer to change JMSUtils.lookupDestination from:
> {code:java}
> public static Destination lookupDestination(Context context, String
> destinationName,
> String destinationType)
> throws NamingException {
> if (destinationName == null) {
> return null;
> }
> try {
> return JMSUtils.lookup(context, Destination.class,
> destinationName);
> } catch (NameNotFoundException e) {
> try {
> return JMSUtils.lookup(context, Destination.class,
>
> (JMSConstants.DESTINATION_TYPE_TOPIC.equalsIgnoreCase(destinationType) ?
> "dynamicTopics/" : "dynamicQueues/") +
> destinationName);
> } catch (NamingException x) {
> log.warn("Cannot locate destination : " + destinationName);
> throw x;
> }
> } catch (NamingException e) {
> log.warn("Cannot locate destination : " + destinationName, e);
> throw e;
> }
> }
> {code}
> to:
> {code:java}
> public static Destination lookupDestination(Context context, String
> destinationName,
> String destinationType)
> throws NamingException {
> if (destinationName == null) {
> return null;
> }
> try {
> return JMSUtils.lookup(context, Destination.class,
> destinationName);
> } catch (NameNotFoundException e) {
> try {
> return JMSUtils.lookup(context, Destination.class,
>
> (JMSConstants.DESTINATION_TYPE_TOPIC.equalsIgnoreCase(destinationType) ?
> "dynamicTopics/" : "dynamicQueues/") +
> destinationName);
> } catch (NamingException x) {
> log.warn("Cannot locate destination : " + destinationName);
> throw e;
> }
> } catch (NamingException e) {
> log.warn("Cannot locate destination : " + destinationName, e);
> throw e;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5824) [Transport][JMS] Change thrown exception
[
https://issues.apache.org/jira/browse/AXIS2-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761499#comment-15761499
]
Hudson commented on AXIS2-5824:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #95 (See
[https://builds.apache.org/job/axis2-1.7/95/])
AXIS2-5824: Merge r1775102 to the 1.7 branch. (veithen: rev 1775104)
* (edit) axis2
* (edit)
axis2/modules/transport/jms/src/main/java/org/apache/axis2/transport/jms/JMSUtils.java
> [Transport][JMS] Change thrown exception
>
>
> Key: AXIS2-5824
> URL: https://issues.apache.org/jira/browse/AXIS2-5824
> Project: Axis2
> Issue Type: Improvement
> Components: JMS transport
>Affects Versions: 1.7.4
>Reporter: Ziborov Egor
>Priority: Trivial
>
> When we tries to lookup some destination for example "my.loc.dest" and it
> doesn't exist than we handle exception with message:
> While trying to lookup 'dynamicQueues.local.rmk.access.SMKtoRMK.dq' didn't
> find subcontext 'dynamicQueues'. Resolved '' (for Weblogic)
> I'd offer to change JMSUtils.lookupDestination from:
> {code:java}
> public static Destination lookupDestination(Context context, String
> destinationName,
> String destinationType)
> throws NamingException {
> if (destinationName == null) {
> return null;
> }
> try {
> return JMSUtils.lookup(context, Destination.class,
> destinationName);
> } catch (NameNotFoundException e) {
> try {
> return JMSUtils.lookup(context, Destination.class,
>
> (JMSConstants.DESTINATION_TYPE_TOPIC.equalsIgnoreCase(destinationType) ?
> "dynamicTopics/" : "dynamicQueues/") +
> destinationName);
> } catch (NamingException x) {
> log.warn("Cannot locate destination : " + destinationName);
> throw x;
> }
> } catch (NamingException e) {
> log.warn("Cannot locate destination : " + destinationName, e);
> throw e;
> }
> }
> {code}
> to:
> {code:java}
> public static Destination lookupDestination(Context context, String
> destinationName,
> String destinationType)
> throws NamingException {
> if (destinationName == null) {
> return null;
> }
> try {
> return JMSUtils.lookup(context, Destination.class,
> destinationName);
> } catch (NameNotFoundException e) {
> try {
> return JMSUtils.lookup(context, Destination.class,
>
> (JMSConstants.DESTINATION_TYPE_TOPIC.equalsIgnoreCase(destinationType) ?
> "dynamicTopics/" : "dynamicQueues/") +
> destinationName);
> } catch (NamingException x) {
> log.warn("Cannot locate destination : " + destinationName);
> throw e;
> }
> } catch (NamingException e) {
> log.warn("Cannot locate destination : " + destinationName, e);
> throw e;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5825) [Axis2][Tibco] Correct usage of JMS API to create MessageConsumer
[
https://issues.apache.org/jira/browse/AXIS2-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761500#comment-15761500
]
Hudson commented on AXIS2-5825:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #95 (See
[https://builds.apache.org/job/axis2-1.7/95/])
AXIS2-5825: Merge r1775081 to the 1.7 branch. (veithen: rev 1775103)
* (edit) axis2
* (edit) axis2/modules/transport/jms/pom.xml
* (edit)
axis2/modules/transport/jms/src/main/java/org/apache/axis2/transport/jms/JMSUtils.java
* (add)
axis2/modules/transport/jms/src/test/java/org/apache/axis2/transport/jms/JMSUtilsTest.java
> [Axis2][Tibco] Correct usage of JMS API to create MessageConsumer
> -
>
> Key: AXIS2-5825
> URL: https://issues.apache.org/jira/browse/AXIS2-5825
> Project: Axis2
> Issue Type: Bug
> Components: JMS transport
>Affects Versions: 1.7.4
>Reporter: Ziborov Egor
>Priority: Minor
>
> When we tried to work with Tibco ESB we handle ClassCastException:
> {noformat}
> java.lang.ClassCastException: com.tibco.tibjms.TibjmsxSessionImp cannot be
> cast to javax.jms.QueueSession
> at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:434)
> {noformat}
> Currently Axis2 logic based on correlation Queue (as destination) <->
> QueueSession (as a session) and the same for the topics. But it's not
> correct. Offer rewrite method createConsumer(Session, Destination, String) to:
> {code:java}
> public static MessageConsumer createConsumer(Session session, Destination
> dest, String messageSelector) throws JMSException {
> return (dest instanceof Queue ?
> createQueueConsumer(session, (Queue)dest, messageSelector) :
> createTopicConsumer(session, (Topic) dest, messageSelector));
> }
> public static MessageConsumer createQueueConsumer(Session session, Queue
> queue, String messageSelector) throws JMSException {
> return (session instanceof QueueSession) ?
> ((QueueSession)session).createReceiver(queue,
> messageSelector) :
> session.createConsumer(queue, messageSelector);
> }
> public static MessageConsumer createTopicConsumer(Session session, Topic
> topic, String messageSelector) throws JMSException {
> return (session instanceof TopicSession) ?
> ((TopicSession)session).createSubscriber(topic,
> messageSelector, false) :
> session.createConsumer(topic, messageSelector);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5825) [Axis2][Tibco] Correct usage of JMS API to create MessageConsumer
[
https://issues.apache.org/jira/browse/AXIS2-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761247#comment-15761247
]
Hudson commented on AXIS2-5825:
---
SUCCESS: Integrated in Jenkins build Axis2 #3610 (See
[https://builds.apache.org/job/Axis2/3610/])
AXIS2-5825: Correctly handle JMS session instances that implement Session, but
not QueueSession or TopicSession. (veithen: rev 1775081)
* (edit) axis2/modules/transport/jms/pom.xml
* (edit)
axis2/modules/transport/jms/src/main/java/org/apache/axis2/transport/jms/JMSUtils.java
* (add)
axis2/modules/transport/jms/src/test/java/org/apache/axis2/transport/jms/JMSUtilsTest.java
> [Axis2][Tibco] Correct usage of JMS API to create MessageConsumer
> -
>
> Key: AXIS2-5825
> URL: https://issues.apache.org/jira/browse/AXIS2-5825
> Project: Axis2
> Issue Type: Bug
> Components: JMS transport
>Affects Versions: 1.7.4
>Reporter: Ziborov Egor
>Priority: Minor
>
> When we tried to work with Tibco ESB we handle ClassCastException:
> {noformat}
> java.lang.ClassCastException: com.tibco.tibjms.TibjmsxSessionImp cannot be
> cast to javax.jms.QueueSession
> at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:434)
> {noformat}
> Currently Axis2 logic based on correlation Queue (as destination) <->
> QueueSession (as a session) and the same for the topics. But it's not
> correct. Offer rewrite method createConsumer(Session, Destination, String) to:
> {code:java}
> public static MessageConsumer createConsumer(Session session, Destination
> dest, String messageSelector) throws JMSException {
> return (dest instanceof Queue ?
> createQueueConsumer(session, (Queue)dest, messageSelector) :
> createTopicConsumer(session, (Topic) dest, messageSelector));
> }
> public static MessageConsumer createQueueConsumer(Session session, Queue
> queue, String messageSelector) throws JMSException {
> return (session instanceof QueueSession) ?
> ((QueueSession)session).createReceiver(queue,
> messageSelector) :
> session.createConsumer(queue, messageSelector);
> }
> public static MessageConsumer createTopicConsumer(Session session, Topic
> topic, String messageSelector) throws JMSException {
> return (session instanceof TopicSession) ?
> ((TopicSession)session).createSubscriber(topic,
> messageSelector, false) :
> session.createConsumer(topic, messageSelector);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5809) Axis2 does not properly return http connection to connection pool when using http client 4
[
https://issues.apache.org/jira/browse/AXIS2-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580777#comment-15580777
]
Hudson commented on AXIS2-5809:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #90 (See
[https://builds.apache.org/job/axis2-1.7/90/])
AXIS2-5809: Merge r1765193 to the 1.7 branch. (veithen: rev 1765194)
* (edit) axis2
* (edit)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/EchoServiceImpl.java
* (edit)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/ServiceTest.java
* (edit)
axis2/modules/transport/http/src/org/apache/axis2/transport/http/impl/httpclient4
* (edit)
axis2/modules/transport/http/src/org/apache/axis2/transport/http/impl/httpclient4/HTTPClient4TransportSender.java
> Axis2 does not properly return http connection to connection pool when using
> http client 4
> --
>
> Key: AXIS2-5809
> URL: https://issues.apache.org/jira/browse/AXIS2-5809
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.7.3
> Environment: Ubuntu 16.04, OpenJDK 7
>Reporter: Christian H.
>Priority: Critical
> Fix For: 1.7.4
>
>
> When using HTTP Client 4 with a generated WSDL-Client the HTTP connections
> are not returned properly to underlying connection pool. The HTTP connections
> are still allocated, when new requests are made. This ends up in waiting for
> HTTP connections from pool, but no connections are available anymore.
> The connections should be returned to pool as stated in the Apache HTTP
> Client 4 documentation (2.3.1):
> https://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html
> Here is some example code to reproduce the problem. The BLZServiceStub is a
> generated WSDL client (wsdl2java) of the following service:
> http://www.thomas-bayer.com/axis2/services/BLZService?wsdl . But the problem
> is independent of the used service.
> {code:title=TestRunner.java}
> package com.thomas_bayer.blz;
> import java.rmi.RemoteException;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.http.client.HttpClient;
> import org.apache.http.impl.client.DefaultHttpClient;
> import org.apache.http.impl.conn.PoolingClientConnectionManager;
> import org.apache.http.params.BasicHttpParams;
> import org.apache.http.params.CoreConnectionPNames;
> import org.apache.http.params.HttpParams;
> public class TestRunner {
> private static final int timeoutMillis = 5000;
> private static final int maxConnections = 2;
>
> private static final String[] BLZs = new String[] {
> "1203", "1207"
> };
>
> public static void main(String[] args) throws RemoteException {
> BLZServiceStub blzService = new BLZServiceStub();
>
> blzService._getServiceClient().getServiceContext().getConfigurationContext().setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
> buildHttpClient());
> for(int i = 0; i <= maxConnections; i++) {
> BLZServiceStub.GetBankType getBankType = new
> BLZServiceStub.GetBankType();
> getBankType.setBlz(BLZs[i % BLZs.length]);
> BLZServiceStub.GetBank getBank = new BLZServiceStub.GetBank();
> getBank.setGetBank(getBankType);
>
> System.out.println("Querying for bank (iteration: " + i + ")");
> BLZServiceStub.GetBankResponse response = blzService.getBank(getBank);
> System.out.println("Bank queried");
>
> System.out.println("Result: " +
> response.getGetBankResponse().getDetails().getBezeichnung());
> }
> }
> protected static HttpClient buildHttpClient() {
> final PoolingClientConnectionManager conmgr = new
> PoolingClientConnectionManager();
> conmgr.setDefaultMaxPerRoute(maxConnections);
> conmgr.setMaxTotal(maxConnections);
>
> final HttpParams params = new BasicHttpParams();
> params.setLongParameter(CoreConnectionPNames.CONNECTION_TIMEOUT,
> timeoutMillis);
> params.setLongParameter(CoreConnectionPNames.SO_TIMEOUT, timeoutMillis);
>
> return new DefaultHttpClient(conmgr, params);
> }
> }
> {code}
> Running this code will produce the following output:
> {noformat}
> Querying for bank (iteration: 0)
> Bank queried
> Result: Deutsche Kreditbank Berlin
> Querying for bank (iteration: 1)
> Bank queried
> Result: Deutsche Bank Ld Brandenburg
> Querying for bank (iteration: 2)
> Sep 27, 2016 8:32:43 AM
> org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl sendViaPost
> INFORMATION: Unable to sendViaPost to
> url[http://www.thomas-bayer.com/axis2/services/BLZService]
> org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for
> connection from pool
> at
>
[jira] [Commented] (AXIS2-5809) Axis2 does not properly return http connection to connection pool when using http client 4
[
https://issues.apache.org/jira/browse/AXIS2-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580712#comment-15580712
]
Hudson commented on AXIS2-5809:
---
SUCCESS: Integrated in Jenkins build Axis2 #3601 (See
[https://builds.apache.org/job/Axis2/3601/])
AXIS2-5809: Ensure that connections are properly released. (veithen: rev
1765193)
* (edit)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/EchoServiceImpl.java
* (edit)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/ServiceTest.java
* (edit)
axis2/modules/transport/http/src/org/apache/axis2/transport/http/impl/httpclient4/HTTPClient4TransportSender.java
> Axis2 does not properly return http connection to connection pool when using
> http client 4
> --
>
> Key: AXIS2-5809
> URL: https://issues.apache.org/jira/browse/AXIS2-5809
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.7.3
> Environment: Ubuntu 16.04, OpenJDK 7
>Reporter: Christian H.
>Priority: Critical
>
> When using HTTP Client 4 with a generated WSDL-Client the HTTP connections
> are not returned properly to underlying connection pool. The HTTP connections
> are still allocated, when new requests are made. This ends up in waiting for
> HTTP connections from pool, but no connections are available anymore.
> The connections should be returned to pool as stated in the Apache HTTP
> Client 4 documentation (2.3.1):
> https://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html
> Here is some example code to reproduce the problem. The BLZServiceStub is a
> generated WSDL client (wsdl2java) of the following service:
> http://www.thomas-bayer.com/axis2/services/BLZService?wsdl . But the problem
> is independent of the used service.
> {code:title=TestRunner.java}
> package com.thomas_bayer.blz;
> import java.rmi.RemoteException;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.http.client.HttpClient;
> import org.apache.http.impl.client.DefaultHttpClient;
> import org.apache.http.impl.conn.PoolingClientConnectionManager;
> import org.apache.http.params.BasicHttpParams;
> import org.apache.http.params.CoreConnectionPNames;
> import org.apache.http.params.HttpParams;
> public class TestRunner {
> private static final int timeoutMillis = 5000;
> private static final int maxConnections = 2;
>
> private static final String[] BLZs = new String[] {
> "1203", "1207"
> };
>
> public static void main(String[] args) throws RemoteException {
> BLZServiceStub blzService = new BLZServiceStub();
>
> blzService._getServiceClient().getServiceContext().getConfigurationContext().setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
> buildHttpClient());
> for(int i = 0; i <= maxConnections; i++) {
> BLZServiceStub.GetBankType getBankType = new
> BLZServiceStub.GetBankType();
> getBankType.setBlz(BLZs[i % BLZs.length]);
> BLZServiceStub.GetBank getBank = new BLZServiceStub.GetBank();
> getBank.setGetBank(getBankType);
>
> System.out.println("Querying for bank (iteration: " + i + ")");
> BLZServiceStub.GetBankResponse response = blzService.getBank(getBank);
> System.out.println("Bank queried");
>
> System.out.println("Result: " +
> response.getGetBankResponse().getDetails().getBezeichnung());
> }
> }
> protected static HttpClient buildHttpClient() {
> final PoolingClientConnectionManager conmgr = new
> PoolingClientConnectionManager();
> conmgr.setDefaultMaxPerRoute(maxConnections);
> conmgr.setMaxTotal(maxConnections);
>
> final HttpParams params = new BasicHttpParams();
> params.setLongParameter(CoreConnectionPNames.CONNECTION_TIMEOUT,
> timeoutMillis);
> params.setLongParameter(CoreConnectionPNames.SO_TIMEOUT, timeoutMillis);
>
> return new DefaultHttpClient(conmgr, params);
> }
> }
> {code}
> Running this code will produce the following output:
> {noformat}
> Querying for bank (iteration: 0)
> Bank queried
> Result: Deutsche Kreditbank Berlin
> Querying for bank (iteration: 1)
> Bank queried
> Result: Deutsche Bank Ld Brandenburg
> Querying for bank (iteration: 2)
> Sep 27, 2016 8:32:43 AM
> org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl sendViaPost
> INFORMATION: Unable to sendViaPost to
> url[http://www.thomas-bayer.com/axis2/services/BLZService]
> org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for
> connection from pool
> at
> org.apache.http.impl.conn.PoolingClientConnectionManager.leaseConnection(PoolingClientConnectionManager.java:232)
> at
>
[jira] [Commented] (AXIS2-5809) Axis2 does not properly return http connection to connection pool when using http client 4
[
https://issues.apache.org/jira/browse/AXIS2-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580640#comment-15580640
]
Hudson commented on AXIS2-5809:
---
FAILURE: Integrated in Jenkins build axis2-1.7 #89 (See
[https://builds.apache.org/job/axis2-1.7/89/])
AXIS2-5809: Merge r1765188 (with changes) to the 1.7 so that we can reproduce
the problem. (veithen: rev 1765189)
* (edit) axis2
* (edit)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/ServiceTest.java
* (edit)
axis2/modules/testutils/src/main/java/org/apache/axis2/testutils/Axis2Server.java
> Axis2 does not properly return http connection to connection pool when using
> http client 4
> --
>
> Key: AXIS2-5809
> URL: https://issues.apache.org/jira/browse/AXIS2-5809
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.7.3
> Environment: Ubuntu 16.04, OpenJDK 7
>Reporter: Christian H.
>Priority: Critical
>
> When using HTTP Client 4 with a generated WSDL-Client the HTTP connections
> are not returned properly to underlying connection pool. The HTTP connections
> are still allocated, when new requests are made. This ends up in waiting for
> HTTP connections from pool, but no connections are available anymore.
> The connections should be returned to pool as stated in the Apache HTTP
> Client 4 documentation (2.3.1):
> https://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html
> Here is some example code to reproduce the problem. The BLZServiceStub is a
> generated WSDL client (wsdl2java) of the following service:
> http://www.thomas-bayer.com/axis2/services/BLZService?wsdl . But the problem
> is independent of the used service.
> {code:title=TestRunner.java}
> package com.thomas_bayer.blz;
> import java.rmi.RemoteException;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.http.client.HttpClient;
> import org.apache.http.impl.client.DefaultHttpClient;
> import org.apache.http.impl.conn.PoolingClientConnectionManager;
> import org.apache.http.params.BasicHttpParams;
> import org.apache.http.params.CoreConnectionPNames;
> import org.apache.http.params.HttpParams;
> public class TestRunner {
> private static final int timeoutMillis = 5000;
> private static final int maxConnections = 2;
>
> private static final String[] BLZs = new String[] {
> "1203", "1207"
> };
>
> public static void main(String[] args) throws RemoteException {
> BLZServiceStub blzService = new BLZServiceStub();
>
> blzService._getServiceClient().getServiceContext().getConfigurationContext().setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
> buildHttpClient());
> for(int i = 0; i <= maxConnections; i++) {
> BLZServiceStub.GetBankType getBankType = new
> BLZServiceStub.GetBankType();
> getBankType.setBlz(BLZs[i % BLZs.length]);
> BLZServiceStub.GetBank getBank = new BLZServiceStub.GetBank();
> getBank.setGetBank(getBankType);
>
> System.out.println("Querying for bank (iteration: " + i + ")");
> BLZServiceStub.GetBankResponse response = blzService.getBank(getBank);
> System.out.println("Bank queried");
>
> System.out.println("Result: " +
> response.getGetBankResponse().getDetails().getBezeichnung());
> }
> }
> protected static HttpClient buildHttpClient() {
> final PoolingClientConnectionManager conmgr = new
> PoolingClientConnectionManager();
> conmgr.setDefaultMaxPerRoute(maxConnections);
> conmgr.setMaxTotal(maxConnections);
>
> final HttpParams params = new BasicHttpParams();
> params.setLongParameter(CoreConnectionPNames.CONNECTION_TIMEOUT,
> timeoutMillis);
> params.setLongParameter(CoreConnectionPNames.SO_TIMEOUT, timeoutMillis);
>
> return new DefaultHttpClient(conmgr, params);
> }
> }
> {code}
> Running this code will produce the following output:
> {noformat}
> Querying for bank (iteration: 0)
> Bank queried
> Result: Deutsche Kreditbank Berlin
> Querying for bank (iteration: 1)
> Bank queried
> Result: Deutsche Bank Ld Brandenburg
> Querying for bank (iteration: 2)
> Sep 27, 2016 8:32:43 AM
> org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl sendViaPost
> INFORMATION: Unable to sendViaPost to
> url[http://www.thomas-bayer.com/axis2/services/BLZService]
> org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for
> connection from pool
> at
> org.apache.http.impl.conn.PoolingClientConnectionManager.leaseConnection(PoolingClientConnectionManager.java:232)
> at
> org.apache.http.impl.conn.PoolingClientConnectionManager$1.getConnection(PoolingClientConnectionManager.java:199)
> at
>
[jira] [Commented] (AXIS2-5809) Axis2 does not properly return http connection to connection pool when using http client 4
[
https://issues.apache.org/jira/browse/AXIS2-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580562#comment-15580562
]
Hudson commented on AXIS2-5809:
---
FAILURE: Integrated in Jenkins build Axis2 #3600 (See
[https://builds.apache.org/job/Axis2/3600/])
AXIS2-5809: Use the custom axis2.xml config on the client as well. (veithen:
rev 1765188)
* (edit)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/ServiceTest.java
* (edit)
axis2/modules/testutils/src/main/java/org/apache/axis2/testutils/Axis2Server.java
Add test case for the scenario described in AXIS2-5809 and AXIS2-5811.
(veithen: rev 1765183)
* (edit) axis2/modules/adb-tests/pom.xml
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/EchoServiceImpl.java
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/ServiceTest.java
* (add) axis2/modules/adb-tests/src/test/repo
* (add) axis2/modules/adb-tests/src/test/repo/AXIS2-5809
* (add) axis2/modules/adb-tests/src/test/repo/AXIS2-5809/axis2.xml
* (add) axis2/modules/adb-tests/src/test/wsdl/AXIS2-5809.wsdl
* (add) axis2/modules/adb-tests/src/test/xslt/AXIS2-5809.xsl
> Axis2 does not properly return http connection to connection pool when using
> http client 4
> --
>
> Key: AXIS2-5809
> URL: https://issues.apache.org/jira/browse/AXIS2-5809
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.7.3
> Environment: Ubuntu 16.04, OpenJDK 7
>Reporter: Christian H.
>Priority: Critical
>
> When using HTTP Client 4 with a generated WSDL-Client the HTTP connections
> are not returned properly to underlying connection pool. The HTTP connections
> are still allocated, when new requests are made. This ends up in waiting for
> HTTP connections from pool, but no connections are available anymore.
> The connections should be returned to pool as stated in the Apache HTTP
> Client 4 documentation (2.3.1):
> https://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html
> Here is some example code to reproduce the problem. The BLZServiceStub is a
> generated WSDL client (wsdl2java) of the following service:
> http://www.thomas-bayer.com/axis2/services/BLZService?wsdl . But the problem
> is independent of the used service.
> {code:title=TestRunner.java}
> package com.thomas_bayer.blz;
> import java.rmi.RemoteException;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.http.client.HttpClient;
> import org.apache.http.impl.client.DefaultHttpClient;
> import org.apache.http.impl.conn.PoolingClientConnectionManager;
> import org.apache.http.params.BasicHttpParams;
> import org.apache.http.params.CoreConnectionPNames;
> import org.apache.http.params.HttpParams;
> public class TestRunner {
> private static final int timeoutMillis = 5000;
> private static final int maxConnections = 2;
>
> private static final String[] BLZs = new String[] {
> "1203", "1207"
> };
>
> public static void main(String[] args) throws RemoteException {
> BLZServiceStub blzService = new BLZServiceStub();
>
> blzService._getServiceClient().getServiceContext().getConfigurationContext().setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
> buildHttpClient());
> for(int i = 0; i <= maxConnections; i++) {
> BLZServiceStub.GetBankType getBankType = new
> BLZServiceStub.GetBankType();
> getBankType.setBlz(BLZs[i % BLZs.length]);
> BLZServiceStub.GetBank getBank = new BLZServiceStub.GetBank();
> getBank.setGetBank(getBankType);
>
> System.out.println("Querying for bank (iteration: " + i + ")");
> BLZServiceStub.GetBankResponse response = blzService.getBank(getBank);
> System.out.println("Bank queried");
>
> System.out.println("Result: " +
> response.getGetBankResponse().getDetails().getBezeichnung());
> }
> }
> protected static HttpClient buildHttpClient() {
> final PoolingClientConnectionManager conmgr = new
> PoolingClientConnectionManager();
> conmgr.setDefaultMaxPerRoute(maxConnections);
> conmgr.setMaxTotal(maxConnections);
>
> final HttpParams params = new BasicHttpParams();
> params.setLongParameter(CoreConnectionPNames.CONNECTION_TIMEOUT,
> timeoutMillis);
> params.setLongParameter(CoreConnectionPNames.SO_TIMEOUT, timeoutMillis);
>
> return new DefaultHttpClient(conmgr, params);
> }
> }
> {code}
> Running this code will produce the following output:
> {noformat}
> Querying for bank (iteration: 0)
> Bank queried
> Result: Deutsche Kreditbank Berlin
> Querying for bank (iteration: 1)
> Bank queried
>
[jira] [Commented] (AXIS2-5811) org.apache.axis2.AxisFault: Timeout waiting for connection from pool
[ https://issues.apache.org/jira/browse/AXIS2-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580561#comment-15580561 ] Hudson commented on AXIS2-5811: --- FAILURE: Integrated in Jenkins build Axis2 #3600 (See [https://builds.apache.org/job/Axis2/3600/]) Add test case for the scenario described in AXIS2-5809 and AXIS2-5811. (veithen: rev 1765183) * (edit) axis2/modules/adb-tests/pom.xml * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809 * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/EchoServiceImpl.java * (add) axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809/ServiceTest.java * (add) axis2/modules/adb-tests/src/test/repo * (add) axis2/modules/adb-tests/src/test/repo/AXIS2-5809 * (add) axis2/modules/adb-tests/src/test/repo/AXIS2-5809/axis2.xml * (add) axis2/modules/adb-tests/src/test/wsdl/AXIS2-5809.wsdl * (add) axis2/modules/adb-tests/src/test/xslt/AXIS2-5809.xsl > org.apache.axis2.AxisFault: Timeout waiting for connection from pool > > > Key: AXIS2-5811 > URL: https://issues.apache.org/jira/browse/AXIS2-5811 > Project: Axis2 > Issue Type: Bug > Components: TCP transport >Affects Versions: 1.7.3 >Reporter: Claudio Degioanni >Priority: Critical > Attachments: axis2_HttpClient4.xml, clean_log.log > > > Using Axis library 1.7.3 with HttpClient 4.4.1, after 200 request the library > throw a TimeoutException from connection pool: > Caused by: org.apache.axis2.AxisFault: Timeout waiting for connection from > pool > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) > ~[axis2-kernel-1.7.3.jar:1.7.3] > at > org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl.sendViaPost(HTTPSenderImpl.java:242) > ~[axis2-transport-http-1.7.3.jar:1.7.3] > at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:121) > ~[axis2-transport-http-1.7.3.jar:1.7.3] > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:403) > ~[axis2-transport-http-1.7.3.jar:1.7.3] > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:234) > ~[axis2-transport-http-1.7.3.jar:1.7.3] > at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:431) > ~[axis2-kernel-1.7.3.jar:1.7.3] > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:399) > ~[axis2-kernel-1.7.3.jar:1.7.3] > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225) > ~[axis2-kernel-1.7.3.jar:1.7.3] > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:150) > ~[axis2-kernel-1.7.3.jar:1.7.3] > > Caused by: org.apache.http.conn.ConnectionPoolTimeoutException: Timeout > waiting for connection from pool > at > org.apache.http.impl.conn.PoolingClientConnectionManager.leaseConnection(PoolingClientConnectionManager.java:226) > ~[httpclient-4.4.1.jar:4.4.1] > at > org.apache.http.impl.conn.PoolingClientConnectionManager$1.getConnection(PoolingClientConnectionManager.java:195) > ~[httpclient-4.4.1.jar:4.4.1] > at > org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:423) > ~[httpclient-4.4.1.jar:4.4.1] > at > org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:882) > ~[httpclient-4.4.1.jar:4.4.1] > at > org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71) > ~[httpclient-4.4.1.jar:4.4.1] > at > org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) > ~[httpclient-4.4.1.jar:4.4.1] > at > org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl.executeMethod(HTTPSenderImpl.java:873) > ~[axis2-transport-http-1.7.3.jar:1.7.3] > at > org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl.sendViaPost(HTTPSenderImpl.java:238) > ~[axis2-transport-http-1.7.3.jar:1.7.3] > ... 15 common frames omitted > I think che connection pool used by library don't work correctly, stuck the > connections to 200 ??? > Steps To reproduce: > 1 Generate client for windows web service like > (http://www.webservicex.com/globalweather.asmx) > 2 Configure axis2 to use HTTPClient4TransportSender > 3 Make 200 web service request -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5809) Axis2 does not properly return http connection to connection pool when using http client 4
[
https://issues.apache.org/jira/browse/AXIS2-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580541#comment-15580541
]
Hudson commented on AXIS2-5809:
---
SUCCESS: Integrated in Jenkins build axis2-1.7 #88 (See
[https://builds.apache.org/job/axis2-1.7/88/])
AXIS2-5809: Merge r1765183 to the 1.7 branch. (veithen: rev 1765187)
* (edit) axis2
* (edit) axis2/modules/adb-tests/pom.xml
* (add)
axis2/modules/adb-tests/src/test/java/org/apache/axis2/databinding/axis2_5809
* (add) axis2/modules/adb-tests/src/test/repo
* (add) axis2/modules/adb-tests/src/test/wsdl/AXIS2-5809.wsdl
* (add) axis2/modules/adb-tests/src/test/xslt/AXIS2-5809.xsl
> Axis2 does not properly return http connection to connection pool when using
> http client 4
> --
>
> Key: AXIS2-5809
> URL: https://issues.apache.org/jira/browse/AXIS2-5809
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.7.3
> Environment: Ubuntu 16.04, OpenJDK 7
>Reporter: Christian H.
>Priority: Critical
>
> When using HTTP Client 4 with a generated WSDL-Client the HTTP connections
> are not returned properly to underlying connection pool. The HTTP connections
> are still allocated, when new requests are made. This ends up in waiting for
> HTTP connections from pool, but no connections are available anymore.
> The connections should be returned to pool as stated in the Apache HTTP
> Client 4 documentation (2.3.1):
> https://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html
> Here is some example code to reproduce the problem. The BLZServiceStub is a
> generated WSDL client (wsdl2java) of the following service:
> http://www.thomas-bayer.com/axis2/services/BLZService?wsdl . But the problem
> is independent of the used service.
> {code:title=TestRunner.java}
> package com.thomas_bayer.blz;
> import java.rmi.RemoteException;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.http.client.HttpClient;
> import org.apache.http.impl.client.DefaultHttpClient;
> import org.apache.http.impl.conn.PoolingClientConnectionManager;
> import org.apache.http.params.BasicHttpParams;
> import org.apache.http.params.CoreConnectionPNames;
> import org.apache.http.params.HttpParams;
> public class TestRunner {
> private static final int timeoutMillis = 5000;
> private static final int maxConnections = 2;
>
> private static final String[] BLZs = new String[] {
> "1203", "1207"
> };
>
> public static void main(String[] args) throws RemoteException {
> BLZServiceStub blzService = new BLZServiceStub();
>
> blzService._getServiceClient().getServiceContext().getConfigurationContext().setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
> buildHttpClient());
> for(int i = 0; i <= maxConnections; i++) {
> BLZServiceStub.GetBankType getBankType = new
> BLZServiceStub.GetBankType();
> getBankType.setBlz(BLZs[i % BLZs.length]);
> BLZServiceStub.GetBank getBank = new BLZServiceStub.GetBank();
> getBank.setGetBank(getBankType);
>
> System.out.println("Querying for bank (iteration: " + i + ")");
> BLZServiceStub.GetBankResponse response = blzService.getBank(getBank);
> System.out.println("Bank queried");
>
> System.out.println("Result: " +
> response.getGetBankResponse().getDetails().getBezeichnung());
> }
> }
> protected static HttpClient buildHttpClient() {
> final PoolingClientConnectionManager conmgr = new
> PoolingClientConnectionManager();
> conmgr.setDefaultMaxPerRoute(maxConnections);
> conmgr.setMaxTotal(maxConnections);
>
> final HttpParams params = new BasicHttpParams();
> params.setLongParameter(CoreConnectionPNames.CONNECTION_TIMEOUT,
> timeoutMillis);
> params.setLongParameter(CoreConnectionPNames.SO_TIMEOUT, timeoutMillis);
>
> return new DefaultHttpClient(conmgr, params);
> }
> }
> {code}
> Running this code will produce the following output:
> {noformat}
> Querying for bank (iteration: 0)
> Bank queried
> Result: Deutsche Kreditbank Berlin
> Querying for bank (iteration: 1)
> Bank queried
> Result: Deutsche Bank Ld Brandenburg
> Querying for bank (iteration: 2)
> Sep 27, 2016 8:32:43 AM
> org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl sendViaPost
> INFORMATION: Unable to sendViaPost to
> url[http://www.thomas-bayer.com/axis2/services/BLZService]
> org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for
> connection from pool
> at
> org.apache.http.impl.conn.PoolingClientConnectionManager.leaseConnection(PoolingClientConnectionManager.java:232)
> at
> org.apache.http.impl.conn.PoolingClientConnectionManager$1.getConnection(PoolingClientConnectionManager.java:199)
[jira] [Commented] (AXIS2-5816) Missing files on axis2-1.7.3-bin.zip
[ https://issues.apache.org/jira/browse/AXIS2-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580047#comment-15580047 ] Hudson commented on AXIS2-5816: --- SUCCESS: Integrated in Jenkins build axis2-1.7 #87 (See [https://builds.apache.org/job/axis2-1.7/87/]) AXIS2-5816: Merge r1765132 to the 1.7 branch. (veithen: rev 1765150) * (edit) axis2 * (edit) axis2/modules/distribution/src/main/assembly/bin-assembly.xml > Missing files on axis2-1.7.3-bin.zip > > > Key: AXIS2-5816 > URL: https://issues.apache.org/jira/browse/AXIS2-5816 > Project: Axis2 > Issue Type: Bug > Components: samples, build,site >Affects Versions: 1.7.3 >Reporter: Danilo G. Baio >Priority: Minor > > Hi. > Just for reporting. > # axis2-1.7.2-bin.zip > $ find axis2-1.7.2/webapp/axis2-web > axis2-1.7.2/webapp/axis2-web > axis2-1.7.2/webapp/axis2-web/ActivateService.jsp > axis2-1.7.2/webapp/axis2-web/admin.jsp > axis2-1.7.2/webapp/axis2-web/css > axis2-1.7.2/webapp/axis2-web/css/axis-style.css > axis2-1.7.2/webapp/axis2-web/deleteService.jsp > axis2-1.7.2/webapp/axis2-web/disengage.jsp > axis2-1.7.2/webapp/axis2-web/EngageToServiceGroup.jsp > axis2-1.7.2/webapp/axis2-web/engagingglobally.jsp > axis2-1.7.2/webapp/axis2-web/engagingtoanoperation.jsp > axis2-1.7.2/webapp/axis2-web/engagingtoaservice.jsp > axis2-1.7.2/webapp/axis2-web/Error > axis2-1.7.2/webapp/axis2-web/Error/AuthError.html > axis2-1.7.2/webapp/axis2-web/Error/error404.jsp > axis2-1.7.2/webapp/axis2-web/Error/error500.jsp > axis2-1.7.2/webapp/axis2-web/Error/GenError.html > axis2-1.7.2/webapp/axis2-web/error.jsp > axis2-1.7.2/webapp/axis2-web/errorModule.jsp > axis2-1.7.2/webapp/axis2-web/globalModules.jsp > axis2-1.7.2/webapp/axis2-web/HappyAxis.jsp > axis2-1.7.2/webapp/axis2-web/images > axis2-1.7.2/webapp/axis2-web/images/asf-logo.gif > axis2-1.7.2/webapp/axis2-web/images/axis.gif > axis2-1.7.2/webapp/axis2-web/images/axis.jpg > axis2-1.7.2/webapp/axis2-web/images/axis_l.jpg > axis2-1.7.2/webapp/axis2-web/InActivateService.jsp > axis2-1.7.2/webapp/axis2-web/include > axis2-1.7.2/webapp/axis2-web/include/adminfooter.inc > axis2-1.7.2/webapp/axis2-web/include/adminfooter.jsp > axis2-1.7.2/webapp/axis2-web/include/adminheader.inc > axis2-1.7.2/webapp/axis2-web/include/adminheader.jsp > axis2-1.7.2/webapp/axis2-web/include/footer.inc > axis2-1.7.2/webapp/axis2-web/include/header.inc > axis2-1.7.2/webapp/axis2-web/include/httpbase.jsp > axis2-1.7.2/webapp/axis2-web/include/link-footer.inc > axis2-1.7.2/webapp/axis2-web/include/link-footer.jsp > axis2-1.7.2/webapp/axis2-web/index.jsp > axis2-1.7.2/webapp/axis2-web/LeftFrame.jsp > axis2-1.7.2/webapp/axis2-web/listFaultyService.jsp > axis2-1.7.2/webapp/axis2-web/listGroupService.jsp > axis2-1.7.2/webapp/axis2-web/listModules.jsp > axis2-1.7.2/webapp/axis2-web/listService.jsp > axis2-1.7.2/webapp/axis2-web/ListServiceGroup.jsp > axis2-1.7.2/webapp/axis2-web/listServices.jsp > axis2-1.7.2/webapp/axis2-web/listSingleService.jsp > axis2-1.7.2/webapp/axis2-web/Login.jsp > axis2-1.7.2/webapp/axis2-web/MainFrame.jsp > axis2-1.7.2/webapp/axis2-web/SelectService.jsp > axis2-1.7.2/webapp/axis2-web/ServiceParaEdit.jsp > axis2-1.7.2/webapp/axis2-web/TopFrame.jsp > axis2-1.7.2/webapp/axis2-web/upload.jsp > axis2-1.7.2/webapp/axis2-web/ViewContexts.jsp > axis2-1.7.2/webapp/axis2-web/ViewGlobalHandlers.jsp > axis2-1.7.2/webapp/axis2-web/viewphases.jsp > axis2-1.7.2/webapp/axis2-web/viewServiceContext.jsp > axis2-1.7.2/webapp/axis2-web/viewServiceGroupContext.jsp > axis2-1.7.2/webapp/axis2-web/ViewServiceHandlers.jsp > # axis2-1.7.3-bin.zip > $ find axis2-1.7.3/webapp/axis2-web > axis2-1.7.3/webapp/axis2-web > axis2-1.7.3/webapp/axis2-web/css > axis2-1.7.3/webapp/axis2-web/css/axis-style.css > axis2-1.7.3/webapp/axis2-web/Error > axis2-1.7.3/webapp/axis2-web/Error/AuthError.html > axis2-1.7.3/webapp/axis2-web/Error/error404.jsp > axis2-1.7.3/webapp/axis2-web/Error/error500.jsp > axis2-1.7.3/webapp/axis2-web/Error/GenError.html > axis2-1.7.3/webapp/axis2-web/error.jsp > axis2-1.7.3/webapp/axis2-web/HappyAxis.jsp > axis2-1.7.3/webapp/axis2-web/images > axis2-1.7.3/webapp/axis2-web/images/asf-logo.gif > axis2-1.7.3/webapp/axis2-web/images/axis.gif > axis2-1.7.3/webapp/axis2-web/images/axis.jpg > axis2-1.7.3/webapp/axis2-web/images/axis_l.jpg > axis2-1.7.3/webapp/axis2-web/index.jsp > axis2-1.7.3/webapp/axis2-web/listFaultyService.jsp > axis2-1.7.3/webapp/axis2-web/listGroupService.jsp > axis2-1.7.3/webapp/axis2-web/listServices.jsp > axis2-1.7.3/webapp/axis2-web/MainFrame.jsp > # axis2-1.7.3-war.zip > On the .war file, the directory "webapp/axis2-web/include" is present under > "WEB-INF/include" with other new stuff. > $ find axis2-1.7.3_war/WEB-INF -type d > axis2-1.7.3_war/WEB-INF > axis2-1.7.3_war/WEB-INF/classes > axis2-1.7.3_war/WEB-INF/classes/META-INF >
[jira] [Commented] (AXIS2-5816) Missing files on axis2-1.7.3-bin.zip
[ https://issues.apache.org/jira/browse/AXIS2-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15579782#comment-15579782 ] Hudson commented on AXIS2-5816: --- SUCCESS: Integrated in Jenkins build Axis2 #3598 (See [https://builds.apache.org/job/Axis2/3598/]) AXIS2-5816: Make sure that the webapp in the binary distribution contains all necessary files. (veithen: rev 1765132) * (edit) axis2/modules/distribution/src/main/assembly/bin-assembly.xml > Missing files on axis2-1.7.3-bin.zip > > > Key: AXIS2-5816 > URL: https://issues.apache.org/jira/browse/AXIS2-5816 > Project: Axis2 > Issue Type: Bug > Components: samples, build,site >Affects Versions: 1.7.3 >Reporter: Danilo G. Baio >Priority: Minor > > Hi. > Just for reporting. > # axis2-1.7.2-bin.zip > $ find axis2-1.7.2/webapp/axis2-web > axis2-1.7.2/webapp/axis2-web > axis2-1.7.2/webapp/axis2-web/ActivateService.jsp > axis2-1.7.2/webapp/axis2-web/admin.jsp > axis2-1.7.2/webapp/axis2-web/css > axis2-1.7.2/webapp/axis2-web/css/axis-style.css > axis2-1.7.2/webapp/axis2-web/deleteService.jsp > axis2-1.7.2/webapp/axis2-web/disengage.jsp > axis2-1.7.2/webapp/axis2-web/EngageToServiceGroup.jsp > axis2-1.7.2/webapp/axis2-web/engagingglobally.jsp > axis2-1.7.2/webapp/axis2-web/engagingtoanoperation.jsp > axis2-1.7.2/webapp/axis2-web/engagingtoaservice.jsp > axis2-1.7.2/webapp/axis2-web/Error > axis2-1.7.2/webapp/axis2-web/Error/AuthError.html > axis2-1.7.2/webapp/axis2-web/Error/error404.jsp > axis2-1.7.2/webapp/axis2-web/Error/error500.jsp > axis2-1.7.2/webapp/axis2-web/Error/GenError.html > axis2-1.7.2/webapp/axis2-web/error.jsp > axis2-1.7.2/webapp/axis2-web/errorModule.jsp > axis2-1.7.2/webapp/axis2-web/globalModules.jsp > axis2-1.7.2/webapp/axis2-web/HappyAxis.jsp > axis2-1.7.2/webapp/axis2-web/images > axis2-1.7.2/webapp/axis2-web/images/asf-logo.gif > axis2-1.7.2/webapp/axis2-web/images/axis.gif > axis2-1.7.2/webapp/axis2-web/images/axis.jpg > axis2-1.7.2/webapp/axis2-web/images/axis_l.jpg > axis2-1.7.2/webapp/axis2-web/InActivateService.jsp > axis2-1.7.2/webapp/axis2-web/include > axis2-1.7.2/webapp/axis2-web/include/adminfooter.inc > axis2-1.7.2/webapp/axis2-web/include/adminfooter.jsp > axis2-1.7.2/webapp/axis2-web/include/adminheader.inc > axis2-1.7.2/webapp/axis2-web/include/adminheader.jsp > axis2-1.7.2/webapp/axis2-web/include/footer.inc > axis2-1.7.2/webapp/axis2-web/include/header.inc > axis2-1.7.2/webapp/axis2-web/include/httpbase.jsp > axis2-1.7.2/webapp/axis2-web/include/link-footer.inc > axis2-1.7.2/webapp/axis2-web/include/link-footer.jsp > axis2-1.7.2/webapp/axis2-web/index.jsp > axis2-1.7.2/webapp/axis2-web/LeftFrame.jsp > axis2-1.7.2/webapp/axis2-web/listFaultyService.jsp > axis2-1.7.2/webapp/axis2-web/listGroupService.jsp > axis2-1.7.2/webapp/axis2-web/listModules.jsp > axis2-1.7.2/webapp/axis2-web/listService.jsp > axis2-1.7.2/webapp/axis2-web/ListServiceGroup.jsp > axis2-1.7.2/webapp/axis2-web/listServices.jsp > axis2-1.7.2/webapp/axis2-web/listSingleService.jsp > axis2-1.7.2/webapp/axis2-web/Login.jsp > axis2-1.7.2/webapp/axis2-web/MainFrame.jsp > axis2-1.7.2/webapp/axis2-web/SelectService.jsp > axis2-1.7.2/webapp/axis2-web/ServiceParaEdit.jsp > axis2-1.7.2/webapp/axis2-web/TopFrame.jsp > axis2-1.7.2/webapp/axis2-web/upload.jsp > axis2-1.7.2/webapp/axis2-web/ViewContexts.jsp > axis2-1.7.2/webapp/axis2-web/ViewGlobalHandlers.jsp > axis2-1.7.2/webapp/axis2-web/viewphases.jsp > axis2-1.7.2/webapp/axis2-web/viewServiceContext.jsp > axis2-1.7.2/webapp/axis2-web/viewServiceGroupContext.jsp > axis2-1.7.2/webapp/axis2-web/ViewServiceHandlers.jsp > # axis2-1.7.3-bin.zip > $ find axis2-1.7.3/webapp/axis2-web > axis2-1.7.3/webapp/axis2-web > axis2-1.7.3/webapp/axis2-web/css > axis2-1.7.3/webapp/axis2-web/css/axis-style.css > axis2-1.7.3/webapp/axis2-web/Error > axis2-1.7.3/webapp/axis2-web/Error/AuthError.html > axis2-1.7.3/webapp/axis2-web/Error/error404.jsp > axis2-1.7.3/webapp/axis2-web/Error/error500.jsp > axis2-1.7.3/webapp/axis2-web/Error/GenError.html > axis2-1.7.3/webapp/axis2-web/error.jsp > axis2-1.7.3/webapp/axis2-web/HappyAxis.jsp > axis2-1.7.3/webapp/axis2-web/images > axis2-1.7.3/webapp/axis2-web/images/asf-logo.gif > axis2-1.7.3/webapp/axis2-web/images/axis.gif > axis2-1.7.3/webapp/axis2-web/images/axis.jpg > axis2-1.7.3/webapp/axis2-web/images/axis_l.jpg > axis2-1.7.3/webapp/axis2-web/index.jsp > axis2-1.7.3/webapp/axis2-web/listFaultyService.jsp > axis2-1.7.3/webapp/axis2-web/listGroupService.jsp > axis2-1.7.3/webapp/axis2-web/listServices.jsp > axis2-1.7.3/webapp/axis2-web/MainFrame.jsp > # axis2-1.7.3-war.zip > On the .war file, the directory "webapp/axis2-web/include" is present under > "WEB-INF/include" with other new stuff. > $ find axis2-1.7.3_war/WEB-INF -type d > axis2-1.7.3_war/WEB-INF > axis2-1.7.3_war/WEB-INF/classes >
