[jira] [Resolved] (AXIS2-5770) ClassCastException from org.apache.axis2.saaj.SOAPElementImpl
[ https://issues.apache.org/jira/browse/AXIS2-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5770. Resolution: Fixed Fix Version/s: 1.7.8 > 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] [Resolved] (AXIS2-5001) SOAPMessage.getSOAPHeaders() return null while no headers in the soap envelope
[ https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5001. Resolution: Incomplete > SOAPMessage.getSOAPHeaders() return null while no headers in the soap envelope > -- > > Key: AXIS2-5001 > URL: https://issues.apache.org/jira/browse/AXIS2-5001 > Project: Axis2 > Issue Type: Bug > Components: saaj >Affects Versions: 1.5.4 >Reporter: Ivan > Labels: Geronimo > Attachments: AXIS2-5001.patch > > > Per Java doc, SOAPMessage.getSOAPHeaders() should throw SOAPException while > no header exists in the soap message, while it returns null in current > axis2-saaj implementation. -- 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=16262348#comment-16262348
]
Andreas Veithen commented on AXIS2-5887:
The vote for the Axis2 1.7.7 release is now open:
http://markmail.org/thread/xeczsqdkkpigy5ha.
> 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: Orders.java, getOrdersByStatus_response.xml, 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-5899) wsdl2java/xmlbeans issue on *nix
[
https://issues.apache.org/jira/browse/AXIS2-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259898#comment-16259898
]
Andreas Veithen commented on AXIS2-5899:
Note that java.io.File has a constructor that parses file: URIs.
> wsdl2java/xmlbeans issue on *nix
>
>
> Key: AXIS2-5899
> URL: https://issues.apache.org/jira/browse/AXIS2-5899
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.4.1, 1.7.6
> Environment: linux (debian/redhat)
> all axis2 versions impacted
>Reporter: Mickael Pouliquen
>Assignee: robert lazarski
>
> The wsdl2java command with xmlbeans code generation applied to a complex wsdl
> with schemas redefinitions FAILS on LINUX os but NOT on WINDOWS os:
> wsdl2java.sh -o out -d xmlbeans -or -noBuildXML -uri sample.wsdl
> ... error on *nix platforms only
> The issue was initially produced on axis2-1.4.1, reproduced on latest version
> axis2-1.7.6
> This platform specific issue comes from the method 'getFileFromURI' in
> "./modules/xmlbeans/src/org/apache/axis2/xmlbeans/CodeGenerationUtility.java":
> the method remove the prefix of the url/uri-like path param. It works on
> windows, but on unix it removes the root slash.
> private File getFileFromURI(String path) {
> if(path.startsWith("file:///")){
> path = path.substring(8);
> } else if(path.startsWith("file://")){
> path = path.substring(7);
> } else if(path.startsWith("file:/")){
> path = path.substring(6);
> }
> return new File(path);
> }
> Exemple,
> 'file:/drive:/dir1/dir2/file1' becomes 'drive:/dir1/dir2/file1' => OK
> 'file:/dir1/dir2/file1' becomes 'dir1/dir2/file1' => KO
> A fix could be:
> private File getFileFromURI(String path) {
> //on windows, will remove the 'file:' prefix and ALL slashes
> //on unix, will remove the 'file:' prefix and keep the ROOT slash
> int offset = "/".equals(File.separator) ? 1 : 0;
> if(path.startsWith("file:///")){
> path = path.substring(8-offset);
> } else if(path.startsWith("file://")){
> path = path.substring(7-offset);
> } else if(path.startsWith("file:/")){
> path = path.substring(6-offset);
> }
> return new File(path);
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5898) Axis2 uses old version of HTTPClient/HTTPComponent Java library
[ https://issues.apache.org/jira/browse/AXIS2-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5898. Resolution: Incomplete Sorry, but this issue is totally unactionable: * The issue description is about version incompatibilities but then doesn't mention the actual versions involved, neither of Axis2 nor of HTTPClient. * There is a confusion here because some of the updates seem to ignore the fact that Commons HTTPClient (aka HTTPClient 3) and HTTPClient 4 use different Java packages and therefore can't be in conflict with each other. In particular, it's not clear what the problem with SAML would be. * Axis2 1.7 depends on Commons HTTPClient 3.1, which is already the latest version from that branch. * As noted in the release notes, Axis2 1.7 has an implementation of the HTTP transport that uses HTTPClient 4, but it's optional. In that sense, the upgrade to HTTPClient 4 has already happened. > Axis2 uses old version of HTTPClient/HTTPComponent Java library > --- > > Key: AXIS2-5898 > URL: https://issues.apache.org/jira/browse/AXIS2-5898 > Project: Axis2 > Issue Type: Improvement > Environment: Matlab 2017b, on Windows Server 2012 R2 >Reporter: Marius Kist > > Hello, > for work I have to access grib2 file subsets via OPeNDAP with climate data > using Matlab. > For this task we employ the Matlab toolbox nctoolbox. > This toolbox relies on a the netCDF Java API to access container formats > (e.g. hdf5, netCDF, grib2). > The newer Versions of netCDF java use a current version of the Java library > HTTPClient. > Matlab uses (within the axis2 framework) a very old version of HTTPClient > (Applications/MATLAB_R2017b.app/java/jarext/axis2/commons-httpclient.jar). > Therefore, nctoolbox is bound to use a very old version of the netCDF Java > API, to be conform with the Matlab version of HTTPClient. > As a user this conflicting HTTPClient versions are a problem for me. > I cannot benefit from bugfixes which were done in newer versions of netCDF > Java API. > My question is: Will axis2 be upgraded to the current version of HTTPClient > in future releases ? > Best regards > Marius -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5895) JAXWSCodeGenerationEngine extension is incomplete
[
https://issues.apache.org/jira/browse/AXIS2-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5895.
Resolution: Incomplete
> JAXWSCodeGenerationEngine extension is incomplete
> -
>
> Key: AXIS2-5895
> URL: https://issues.apache.org/jira/browse/AXIS2-5895
> Project: Axis2
> Issue Type: Test
> Components: codegen
>Affects Versions: 1.7.6
> Environment: jdk 1.8
> maven 3.3.3
>Reporter: Martin Gainty
>Priority: Minor
> Fix For: 1.8.0
>
>
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing,
> * software distributed under the License is distributed on an
> * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> * KIND, either express or implied. See the License for the
> * specific language governing permissions and limitations
> * under the License.
> */
> //extension property requires an extension java class see below
> package org.apache.axis2.wsdl.codegen.jaxws;
> import java.lang.reflect.Field;
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.Iterator;
> import java.util.List;
> import java.util.Map;
> import org.apache.axiom.om.util.LogOutputStream;
> import org.apache.axis2.util.CommandLineOption;
> import org.apache.axis2.util.CommandLineOptionConstants;
> import org.apache.axis2.util.CommandLineOptionParser;
> import org.apache.axis2.wsdl.codegen.CodeGenConfiguration;
> import org.apache.axis2.wsdl.codegen.CodeGenerationException;
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> import com.sun.tools.ws.wscompile.WsimportTool;
> /**
> * The Class JAXWSCodeGenerationEngine.
> */
> public class JAXWSCodeGenerationEngine {
> private static final Log log = LogFactory
> .getLog(JAXWSCodeGenerationEngine.class);
> private CodeGenConfiguration configuration;
> private CommandLineOptionParser commandLineOptionParser;
> private String[] originalArgs;
> /**
> * Instantiates a new jAXWS code generation engine.
> *
> * @param configuration
> *the configuration
> * @param originalArgs
> *the original args
> * @throws CodeGenerationException
> * the code generation exception
> */
> public JAXWSCodeGenerationEngine(CodeGenConfiguration configuration,
> String[] originalArgs) throws CodeGenerationException {
> this.configuration = configuration;
> this.originalArgs = originalArgs;
> // loadExtensions();
> }
> /**
> * Instantiates a new jAXWS code generation engine.
> *
> * @param commandLineOptionParser
> *the command line option parser
> * @param originalArgs
> *the original args
> */
> public JAXWSCodeGenerationEngine(
> CommandLineOptionParser commandLineOptionParser,
> String[] originalArgs) {
> this.commandLineOptionParser = commandLineOptionParser;
> this.originalArgs = originalArgs;
> // loadExtensions();
> }
> /**
> * Generate.
> *
> * @throws CodeGenerationException
> * the code generation exception
> */
> public void generate() throws CodeGenerationException {
> LogOutputStream logOutputStream = new LogOutputStream(log,
> Integer.MAX_VALUE);
> com.sun.tools.ws.wscompile.WsimportTool importTool = new
> com.sun.tools.ws.wscompile.WsimportTool(logOutputStream);
> ArrayList args = new ArrayList();
> configurImportToolOptions(args);
> mergeOriginalArgs(args);
> String []array=args.toArray(new String[args.size()]);
> log.info("JAXWSCodeGenerationEngine::generate LINE 100 before
> importTool.run where importTool="+importTool);
> //if(array[0].indexOf("extension")!=-1)
> array[0]="extension=org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension";
> log.debug("JAXWSCodeGenerationEngine::generate LINE 101 before
> importTool.run where importTool(array="+array );
> boolean success = importTool.run(array);
> log.debug("JAXWSCodeGenerationEngine::generate LINE 103
> SUCESS="+success);
> if (success) {
> log.info("Code generation
[jira] [Resolved] (AXIS2-5894) API changes review for Axis2 Kernel
[ https://issues.apache.org/jira/browse/AXIS2-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5894. Resolution: Not A Bug > API changes review for Axis2 Kernel > --- > > Key: AXIS2-5894 > URL: https://issues.apache.org/jira/browse/AXIS2-5894 > Project: Axis2 > Issue Type: Test >Reporter: Andrey Ponomarenko > Attachments: Axis2-Kernel-1.png, Axis2-Kernel-2.png > > > The review of API changes for the Axis2 Kernel library since 1.0 version: > https://abi-laboratory.pro/java/tracker/timeline/axis2-kernel/ > The report is updated 3 times a week. Hope it will be helpful for users and > maintainers of the library. > The report is generated by https://github.com/lvc/japi-tracker > Thank you. > !Axis2-Kernel-2.png|API symbols timeline! > !Axis2-Kernel-1.png|API changes review! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5893) test.wsdl not found in ServiceClientTest::testWSDLWithImportsFromZIP
[
https://issues.apache.org/jira/browse/AXIS2-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5893.
Resolution: Invalid
The file is added to the ZIP here:
https://github.com/apache/axis2-java/blob/v1.7.6/modules/kernel/test-zip/assembly.xml
> test.wsdl not found in ServiceClientTest::testWSDLWithImportsFromZIP
>
>
> Key: AXIS2-5893
> URL: https://issues.apache.org/jira/browse/AXIS2-5893
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.6
> Environment: jdk 1.8
> mvn 3.3.3
> Axis2 1.8.0-SNAPSHOT
>Reporter: Martin Gainty
>Priority: Minor
> Fix For: 1.8.0
>
>
> //current algo to locate test.wsdl never locates entry in test-zip.zip
> //this will add the test.wsdl entry allowing find method to locate 'test.wsdl'
> @Test
> public void testWSDLWithImportsFromZIP() throws Exception
> {
> OnDemandLogger log = new
> OnDemandLogger(ServiceClientTest.class);
> java.io.FileInputStream in=null;
> ConfigurationContext configContext =
> ConfigurationContextFactory.createEmptyConfigurationContext();
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 45
> configContext="+configContext);
> String basedir = System.getProperty("basedir");
> if (basedir == null) basedir = ".";
> String zipName="/AXIS2-~1/modules/kernel/target/test-zip.zip";
> String
> wsdlFullName="/AXIS2-~1/modules/kernel/target/test-zip.zip!/test.wsdl";
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 49
> zipName="+zipName);
> byte buffer[] = new byte[1024];
> // Open archive file
> FileOutputStream stream = new FileOutputStream(zipName);
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 53
> stream="+stream);
> JarOutputStream out = new JarOutputStream(stream, new Manifest());
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 55
> JarOutputStream out="+out);
> File []tobeJared={new java.io.File(wsdlFullName)};
> for (int i = 0; i < tobeJared.length; i++)
> {
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 64
> tobeJared[i]="+tobeJared[i]);
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 65
> tobeJared[i].isDirectory()="+tobeJared[i].isDirectory());
> if (tobeJared[i] == null || !tobeJared[i].exists() ||
> tobeJared[i].isDirectory())
> {
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 66
> tobeJared[i] already exists tobeJared[i]="+tobeJared[i]);
> //continue; // Just in case it already exists
> }
> if(log.isDebugEnabled()) log.debug("Adding jar entry=" +
> tobeJared[i].getName());
> // Add archive entry
> JarEntry jarAdd = new JarEntry(tobeJared[i].getName());
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 63
> jarAdd="+jarAdd);
> jarAdd.setTime(tobeJared[i].lastModified());
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 65 before
> out.putNextEntry(jarAdd) out="+out+" jarAdd="+jarAdd);
> out.putNextEntry(jarAdd);
> // Write test.wsdl file to archive
> in = new java.io.FileInputStream(tobeJared[i]);
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 71
> FileInputStream in="+in);
> while (true)
> {
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 72
> buffer="+buffer);
> int nRead = in.read(buffer, 0, buffer.length);
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 76
> nRead="+nRead);
> if (nRead <= 0)
> break;
> if(log.isDebugEnabled())
> log.debug("ServiceClientTest::testWSDLWithImportsFromZIP() LINE 79 before
> out.write(buffer="+buffer);
> out.write(buffer, 0, nRead);
> }
> }
> if(in!=null) in.close();
> if(out!=null)
> {
> out.flush();
> try {
>
[jira] [Moved] (RAMPART-444) Mutliple Client cert is not working with axis2 client
[
https://issues.apache.org/jira/browse/RAMPART-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved AXIS2-5892 to RAMPART-444:
Component/s: (was: client-api)
(was: wsdl)
Key: RAMPART-444 (was: AXIS2-5892)
Project: Rampart (was: Axis2)
> Mutliple Client cert is not working with axis2 client
> --
>
> Key: RAMPART-444
> URL: https://issues.apache.org/jira/browse/RAMPART-444
> Project: Rampart
> Issue Type: Bug
>Reporter: Ashish Mandloi
>
> Hi
> We have client which connecting to soap server and they have provided us
> client certificate which we have to installed in our keystore. It was
> working fine until we have other client certificate from server. We have
> installed it in keystore and first call to webservie is working fine but for
> the second call for other user we are getting the below Exception
> {code:java}
> org.apache.axis2.AxisFault: unknown
> at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:517)
> at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> at
> com.auruspay.manager.issuer.participants.processor.credibanco.VPOSWS20SOAPStub.authorize(VPOSWS20SOAPStub.java:193)
> at
> com.auruspay.manager.issuer.participants.processor.credibanco.CredibancoCartridge.connect(CredibancoCartridge.java:109)
> at
> com.auruspay.manager.issuer.participants.processor.credibanco.PauseCredibancoProcessor.run(CredibancoParticipant.java:92)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *Here is my code *
> {code:java}
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem("/home/test/resource/",
> null);
> VPOSWS20SOAPStub serviceVPOSWS = new
> VPOSWS20SOAPStub(ctx, urlService);
> ServiceClient client =
> serviceVPOSWS._getServiceClient();
> client.engageModule("rampart");
> Options clientOptions = new Options();
>
> clientOptions.setProperty(WSSHandlerConstants.OUTFLOW_SECURITY,
> getOutflowConfiguration());
>
> clientOptions.setProperty(WSSHandlerConstants.INFLOW_SECURITY,
> getInflowConfiguration());
> //clientOptions.setUserName("client cert");
> //clientOptions.setPassword("k12345");
> clientOptions.setTo(new EndpointReference(urlService));
> //clientOptions.setTimeOutInMilliSeconds(1000);
> clientOptions.setProperty(HTTPConstants.SO_TIMEOUT,
> 1);
>
> clientOptions.setProperty(HTTPConstants.CONNECTION_TIMEOUT, 1);
> clientOptions.setManageSession(false);
>
> client.setOptions(clientOptions);
> client.setCachingOperationContext(false);
> System.out.println("URL
> :"+client.getOptions().getTo().getAddress());
> serviceVPOSWS._setServiceClient( client );
>
>
>
> System.out.println(new Date());
> reqResp = serviceVPOSWS.authorize(req);
> private Parameter getOutflowConfiguration() {
> OutflowConfiguration ofc = new OutflowConfiguration();
> ofc.setActionItems("Signature Encrypt Timestamp");
> String fileName= "COMKEYCONFIG_"+clientID+".properties";
> LOG.info(participant.getTxnLogKey() + " PROPERTIES FILE
> NAME:"+fileName);
> ofc.setSignaturePropFile(fileName);
>
> //ofc.setSignatureKeyIdentifier("X509KeyIdentifier");
> ofc.setSignatureKeyIdentifier("DirectReference") ;
> ofc.setUser("client cert");
> ofc.setPasswordCallbackClass("com.test.ClientPWCBHandler");
> ofc.setEncryptionPropFile(fileName);
> ofc.setEncryptionUser("vposwscrypto");
> ofc.setEncryptionKeyIdentifier("X509KeyIdentifier");
> LOG.info("ofc.getProperty() OUTPUTFLOW :
> "+ofc.getProperty().toString());
> return ofc.getProperty();
> }
> private Parameter getInflowConfiguration() {
> InflowConfiguration ifc = new InflowConfiguration();
> ifc.setActionItems("Signature Timestamp");
> String fileName=
[jira] [Commented] (AXIS2-5745) Changing a service name doesn't update its TypeTable struct
[
https://issues.apache.org/jira/browse/AXIS2-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178289#comment-16178289
]
Andreas Veithen commented on AXIS2-5745:
Actually you may be able to use the API introduced by AXIS2-5322 without
writing a new deployer.
> Changing a service name doesn't update its TypeTable struct
> ---
>
> Key: AXIS2-5745
> URL: https://issues.apache.org/jira/browse/AXIS2-5745
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.6.2
> Environment: Windows 8.1 x86-64, Tomcat 7.0.68 x86-64
>Reporter: Thorsten Schöning
> Attachments: WsAxis2SvcLc.java
>
>
> I have an implementation of ServiceLifeCycle in which I'm overriding startUp
> and change the name of my service in some special way to make my deployment
> easier. I'm simply implementing some kind of mandator mechanism based on
> exploded services and their unique name in the file system.
> This worked pretty fine the last years, but today I encountered that Axis2 is
> handling structures internally in which the service name is used as some
> component of a key. Those structures were built before startUp was called and
> were not updated on a changed service name. My service generated an exception
> for some reason, Axis2 tried to handle that and failed itself with a NPE,
> which made debugging pretty hard of course because the original exception was
> lost.
> The NPE was thrown in the following line 183 of RPCMessageReceiver and the
> not up to date structure was TypeTable for the service, that's why
> elementQName was null instead of a valid object. Gladly I was able to access
> that map in my ServiceLifeCycle implementation and update the generated keys
> and QNames with my new updated service name. I would have expected that if
> I'm able to change the service name, structs containing it would get updated
> automatically by Axis 2, which at least for TypeTable currently isn't the
> case.
> {CODE}
> 175Class[] exceptionTypes = method.getExceptionTypes();
> 176for (Class exceptionType : exceptionTypes){
> 177if
> (exceptionType.getName().equals(cause.getClass().getName())){
> 178// this is an bussiness logic exception so handle it
> properly
> 179String partQName =
> inMessage.getAxisService().getName() + getSimpleClassName(exceptionType);
> 180TypeTable typeTable =
> inMessage.getAxisService().getTypeTable();
> 181QName elementQName =
> typeTable.getQNamefortheType(partQName);
> 182SOAPFactory fac = getSOAPFactory(inMessage);
> 183OMElement exceptionElement =
> fac.createOMElement(elementQName);
> 184
> 185if
> (exceptionType.getName().equals(Exception.class.getName())){
> 186// this is an exception class. so create a element
> by hand and add the message
> 187 OMElement innterExceptionElement =
> fac.createOMElement(elementQName);
> 188 OMElement messageElement =
> fac.createOMElement("Message",
> inMessage.getAxisService().getTargetNamespace(), null);
> 189 messageElement.setText(cause.getMessage());
> {CODE}
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.axis2/axis2-adb/1.6.2/org/apache/axis2/rpc/receivers/RPCMessageReceiver.java/#183
> I'm currently unable to build Axis2 from src and am not sure where one would
> implement such a change, therefore can't provide patches, but instead I'll
> simply post my implemantation of the change for TypeTable in my
> ServiceLifeCycle. In my case, TypeTable contained the following data for my
> old service name "SoapAuth":
> {CODE}
> complexTypeMap HashMap (id=165)
> {java.sql={http://sql.java/xsd}SQLException,
> SoapAuthSecurityException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthSecurityException,
> java.sql.SQLException={http://sql.java/xsd}SQLException,
> logout={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}logout,
> java.io={http://io.java/xsd}FileNotFoundException,
> SoapAuthSQLException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthSQLException,
>
> cookieAbgleich={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}cookieAbgleich,
>
> SoapAuthClassNotFoundException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthClassNotFoundException,
>
> SoapAuthFileNotFoundException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthFileNotFoundException,
> java.io.IOException={http://io.java/xsd}IOException,
> SoapAuthIOException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthIOException,
>
[jira] [Commented] (AXIS2-5745) Changing a service name doesn't update its TypeTable struct
[
https://issues.apache.org/jira/browse/AXIS2-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178232#comment-16178232
]
Andreas Veithen commented on AXIS2-5745:
I think the service name should be considered immutable. For your use case you
should probably implement a custom deployer.
> Changing a service name doesn't update its TypeTable struct
> ---
>
> Key: AXIS2-5745
> URL: https://issues.apache.org/jira/browse/AXIS2-5745
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.6.2
> Environment: Windows 8.1 x86-64, Tomcat 7.0.68 x86-64
>Reporter: Thorsten Schöning
> Attachments: WsAxis2SvcLc.java
>
>
> I have an implementation of ServiceLifeCycle in which I'm overriding startUp
> and change the name of my service in some special way to make my deployment
> easier. I'm simply implementing some kind of mandator mechanism based on
> exploded services and their unique name in the file system.
> This worked pretty fine the last years, but today I encountered that Axis2 is
> handling structures internally in which the service name is used as some
> component of a key. Those structures were built before startUp was called and
> were not updated on a changed service name. My service generated an exception
> for some reason, Axis2 tried to handle that and failed itself with a NPE,
> which made debugging pretty hard of course because the original exception was
> lost.
> The NPE was thrown in the following line 183 of RPCMessageReceiver and the
> not up to date structure was TypeTable for the service, that's why
> elementQName was null instead of a valid object. Gladly I was able to access
> that map in my ServiceLifeCycle implementation and update the generated keys
> and QNames with my new updated service name. I would have expected that if
> I'm able to change the service name, structs containing it would get updated
> automatically by Axis 2, which at least for TypeTable currently isn't the
> case.
> {CODE}
> 175Class[] exceptionTypes = method.getExceptionTypes();
> 176for (Class exceptionType : exceptionTypes){
> 177if
> (exceptionType.getName().equals(cause.getClass().getName())){
> 178// this is an bussiness logic exception so handle it
> properly
> 179String partQName =
> inMessage.getAxisService().getName() + getSimpleClassName(exceptionType);
> 180TypeTable typeTable =
> inMessage.getAxisService().getTypeTable();
> 181QName elementQName =
> typeTable.getQNamefortheType(partQName);
> 182SOAPFactory fac = getSOAPFactory(inMessage);
> 183OMElement exceptionElement =
> fac.createOMElement(elementQName);
> 184
> 185if
> (exceptionType.getName().equals(Exception.class.getName())){
> 186// this is an exception class. so create a element
> by hand and add the message
> 187 OMElement innterExceptionElement =
> fac.createOMElement(elementQName);
> 188 OMElement messageElement =
> fac.createOMElement("Message",
> inMessage.getAxisService().getTargetNamespace(), null);
> 189 messageElement.setText(cause.getMessage());
> {CODE}
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.axis2/axis2-adb/1.6.2/org/apache/axis2/rpc/receivers/RPCMessageReceiver.java/#183
> I'm currently unable to build Axis2 from src and am not sure where one would
> implement such a change, therefore can't provide patches, but instead I'll
> simply post my implemantation of the change for TypeTable in my
> ServiceLifeCycle. In my case, TypeTable contained the following data for my
> old service name "SoapAuth":
> {CODE}
> complexTypeMap HashMap (id=165)
> {java.sql={http://sql.java/xsd}SQLException,
> SoapAuthSecurityException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthSecurityException,
> java.sql.SQLException={http://sql.java/xsd}SQLException,
> logout={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}logout,
> java.io={http://io.java/xsd}FileNotFoundException,
> SoapAuthSQLException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthSQLException,
>
> cookieAbgleich={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}cookieAbgleich,
>
> SoapAuthClassNotFoundException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthClassNotFoundException,
>
> SoapAuthFileNotFoundException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthFileNotFoundException,
> java.io.IOException={http://io.java/xsd}IOException,
> SoapAuthIOException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthIOException,
>
[jira] [Resolved] (AXIS2-5889) jaxws-integration test-compile needs to include target/generated-test-sources
[ https://issues.apache.org/jira/browse/AXIS2-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5889. Resolution: Duplicate Fix Version/s: (was: 1.8.0) > jaxws-integration test-compile needs to include target/generated-test-sources > -- > > Key: AXIS2-5889 > URL: https://issues.apache.org/jira/browse/AXIS2-5889 > Project: Axis2 > Issue Type: Bug > Components: jaxws >Affects Versions: 1.7.6 > Environment: jdk 1.8 > maven 3.3.3 > axis2-1.8.0-SNAPSHOT >Reporter: Martin Gainty > > > > org.codehaus.mojo > build-helper-maven-plugin > 3.0.0 > > > add-source > generate-sources > > add-source > > > > target/GENERA~1/jaxb/ASYNC_~2 > target/GENERA~1/jaxb/SAMPLE~1 > target/GENERA~1/jaxb/RPCLit > target/GENERA~1/jaxb/ASYNC_~1 > target/GENERA~1/jaxb/FAULTY~1 > target/GENERA~1/jaxb/echo > target/GENERA~1/jaxb/HEADER~1 > target/GENERA~1/jaxb/GORILL~1 > target/GENERA~1/jaxb/stock1 > target/GENERA~1/jaxb/PROCES~1 > target/GENERA~1/jaxb/RPCLIT~3 > target/GENERA~1/jaxb/JAXBSO~1 > target/GENERA~1/jaxb/FAULTS~1 > target/GENERA~1/jaxb/SAMPLE~1 > target/GENERA~1/jaxb/SAMPLE~2 > target/GENERA~1/jaxb/ADDNUM~1 > target/GENERA~1/jaxb/ADDNUM~2 > target/GENERA~1/jaxb/PROXYD~1 > target/GENERA~1/jaxb/GREETE~1 > target/GENERA~1/jaxb/rpclit > target/GENERA~1/jaxb/RPCLIT~2 > target/GENERA~1/jaxb/DOCLIT~3 > target/GENERA~1/jaxb/SOAP11 > target/GENERA~1/jaxb/DOCLIT~1 > target/GENERA~1/jaxb/DOCLIT~2 > target/GENERA~1/jaxb/stock2 > > > > > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5890) Build failure when running mvn install without clean
[ https://issues.apache.org/jira/browse/AXIS2-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5890. Resolution: Fixed Fix Version/s: 1.7.7 > 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 > Fix For: 1.7.7 > > > 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] [Created] (AXIS2-5890) Build failure when running mvn install without clean
Andreas Veithen created AXIS2-5890: -- Summary: 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] [Resolved] (AXIS2-5888) adb-tests ExtensionTest failure for wrong element
[
https://issues.apache.org/jira/browse/AXIS2-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5888.
Resolution: Invalid
> adb-tests ExtensionTest failure for wrong element
> -
>
> Key: AXIS2-5888
> URL: https://issues.apache.org/jira/browse/AXIS2-5888
> Project: Axis2
> Issue Type: Bug
> Components: adb
>Affects Versions: 1.8.0
> Environment: jdk 1.8.0
> maven 3.3.3
> Axis2-1.8.0-SNAPSHOT
>Reporter: Martin Gainty
>
> //this fixes missing currencyElement from
> SimpleExtensionTest::testPaymentAmountElementParse:
> //create the currency element
> OMElement subElement = factory.createOMElement(new
> QName("http://apache.org/axis2/schema/extension;, "currency"));
> //add subElement to element
> element.addChild(subElement);
> //now create the XMLStreamReader from element (with subelement currency)
> XMLStreamReader reader=element.getXMLStreamReader();
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-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:all-tabpanel
]
Andreas Veithen resolved AXIS2-5887.
Resolution: Fixed
Fix Version/s: 1.7.7
> 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-5874) Memory leak when trying to getInputStream() from an External Repository data through AXIS
[
https://issues.apache.org/jira/browse/AXIS2-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161923#comment-16161923
]
Andreas Veithen commented on AXIS2-5874:
AXIS2-5301 is not about leaking memory. Note that you haven't yet provided any
evidence that there is a memory leak.
> Memory leak when trying to getInputStream() from an External Repository data
> through AXIS
> -
>
> Key: AXIS2-5874
> URL: https://issues.apache.org/jira/browse/AXIS2-5874
> Project: Axis2
> Issue Type: Bug
> Components: jaxws, wsdl
>Affects Versions: 1.6.2
> Environment: Windows 2008
>Reporter: Nidhin Lazar
>Priority: Blocker
>
> We are using AXIS WS to connect and download files from an external
> repository .We are using SOAP based webservice calls download an object. The
> API returns a DataHandler object, from where we are getting the input stream.
> We have tried closing the inputstream object but even after the close call we
> can see that the memory is still holding the stream, and eventually the
> client machine is running out of memory.Any help on this would be highly
> appreciated.
> Our client code is as shown below
> URL url = new URL("http://"+host+"/ws/CntSrvc.svc?wsdl;);
> CntSrvc_Svc cService = new CntSrvc_Svc(url);
> CntSrvc cntSrvcClient = cService.getBasicHttpBindingCntSrvc(new
> MTOMFeature());
> InputStream in = null ;
> in = cntSrvcClient.download(contextIDString).getInputStream();
> // write in to a file.
> //closing the input stream
> if (in != null){
> in.close();
> }
> [Note;] Our client code runs under tomcat container, and this acts as a
> server to other services.
> [Note:]We have created a sample client without using AXIS, where our client
> connecting to external repository and download content.Here we donot see any
> memory leak.Our investigation proves that its when we use AXIS and
> getinputstream() the memory is leaking, input stream is not closing.Our
> current framework demands AXIS hence we would like to get a solution or
> workaround for this issue
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5866) Axis ignores org.apache.axis2.client.Options#getTimeOutInMilliSeconds
[
https://issues.apache.org/jira/browse/AXIS2-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5866.
Resolution: Incomplete
> Axis ignores org.apache.axis2.client.Options#getTimeOutInMilliSeconds
> -
>
> Key: AXIS2-5866
> URL: https://issues.apache.org/jira/browse/AXIS2-5866
> Project: Axis2
> Issue Type: Bug
> Components: client-api, transports
>Affects Versions: 1.7.4
> Environment: Java 8, Tomcat
>Reporter: Mykhailo Hodovaniuk
>Priority: Minor
>
> According to documentation
> https://axis.apache.org/axis2/java/core/docs/http-transport.html the timeouts
> can be defined:
> {code:java}
> For runtime configuration, it can be set as follows within the client stub:
> ...
> Options options = new Options();
> options.setProperty(HTTPConstants.SO_TIMEOUT, new
> Integer(timeOutInMilliSeconds));
> options.setProperty(HTTPConstants.CONNECTION_TIMEOUT, new
> Integer(timeOutInMilliSeconds));
> // or
> options.setTimeOutInMilliSeconds(timeOutInMilliSeconds);
> ...
> {code}
> But instead, Axis ignores this property because:
> _org.apache.axis2.transport.http.CommonsHTTPTransportSender#invoke_ has code
> {code:java}
> // set the property values only if they are not set by the user explicitly
> if (msgContext.getProperty(HTTPConstants.SO_TIMEOUT) == null) {
> msgContext.setProperty(HTTPConstants.SO_TIMEOUT, soTimeout);
> }
> if (msgContext.getProperty(HTTPConstants.CONNECTION_TIMEOUT) ==
> null) {
> msgContext.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> connectionTimeout);
> }
> {code}
> where _connectionTimeout_ and _soTimeout_ are always non null.
> At the same time
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_
> tries to define these values if they are null with timeOutInMilliSeconds.
> The problem is that
> _org.apache.axis2.transport.http.CommonsHTTPTransportSender#invoke_ is higher
> in call hirarchy so the
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_
> does not work as expected. The _SO_TIMEOUT_ and _CONNECTION_TIMEOUT_
> parameters are always defined inside
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_.
> The workaround is to define timeouts in axis2.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-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:all-tabpanel ] Andreas Veithen resolved AXIS2-5884. Resolution: Fixed Fix Version/s: 1.8.0 > 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 > Fix For: 1.8.0 > > > 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] [Resolved] (AXIS2-5882) Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream
[ https://issues.apache.org/jira/browse/AXIS2-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5882. Resolution: Invalid > Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream > --- > > Key: AXIS2-5882 > URL: https://issues.apache.org/jira/browse/AXIS2-5882 > Project: Axis2 > Issue Type: Bug > Components: jaxws >Affects Versions: 1.7.6 >Reporter: Donald Kwakkel >Priority: Critical > Labels: security > > Attackers can control the filesystem path argument to File() at > PreProcessorInputStream.java line 218, which allows them to access or modify > otherwise protected files. > Explanation: > Path manipulation errors occur when the following two conditions are met: > 1. An attacker can specify a path used in an operation on the filesystem. > 2. By specifying the resource, the attacker gains a capability that would not > otherwise be permitted. > For example, the program may give the attacker the ability to overwrite the > specified file or run with a configuration controlled by the attacker. > In this case, the attacker can specify the value that enters the program at > readLine() in PreProcessorInputStream.java at line 86, and this value is used > to access a filesystem resource at File() in PreProcessorInputStream.java at > line 218, 230, 232, 250, 253, 278. > Possible solution: Make sure the absolute filename is validated against > known/configured valid base path. > Also: > Attackers can control the filesystem path argument to File() at > WSDL20ToAxisServiceBuilder.java line 153, which allows them to access or > modify otherwise protected files. In this case, the attacker can specify the > value that enters the program at getHeaderField() in > CodeGenerationEngine.java at line 101, and this value is used to access a > filesystem resource at File() in WSDL20ToAxisServiceBuilder.java at line 153 > and 1281. -- 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-5882) Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream
[
https://issues.apache.org/jira/browse/AXIS2-5882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160467#comment-16160467
]
Andreas Veithen commented on AXIS2-5882:
AFAICS {{PreProcessorInputStream}} is used by the IDL processor to process
{{#include}} statements. This is a legitimate use of path manipulation. I don't
see how this would satisfy any of the two conditions you mentioned.
Please note that naive implementations of static code analyzers designed to
detect security issues will produce a lot of false positives like this. Please
don't create bugs unless you have confirmed that the reported "issues" are
actual security problems.
> Path Manipulation in WSDL20ToAxisServiceBuilder and PreProcessorInputStream
> ---
>
> Key: AXIS2-5882
> URL: https://issues.apache.org/jira/browse/AXIS2-5882
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
> Labels: security
>
> Attackers can control the filesystem path argument to File() at
> PreProcessorInputStream.java line 218, which allows them to access or modify
> otherwise protected files.
> Explanation:
> Path manipulation errors occur when the following two conditions are met:
> 1. An attacker can specify a path used in an operation on the filesystem.
> 2. By specifying the resource, the attacker gains a capability that would not
> otherwise be permitted.
> For example, the program may give the attacker the ability to overwrite the
> specified file or run with a configuration controlled by the attacker.
> In this case, the attacker can specify the value that enters the program at
> readLine() in PreProcessorInputStream.java at line 86, and this value is used
> to access a filesystem resource at File() in PreProcessorInputStream.java at
> line 218, 230, 232, 250, 253, 278.
> Possible solution: Make sure the absolute filename is validated against
> known/configured valid base path.
> Also:
> Attackers can control the filesystem path argument to File() at
> WSDL20ToAxisServiceBuilder.java line 153, which allows them to access or
> modify otherwise protected files. In this case, the attacker can specify the
> value that enters the program at getHeaderField() in
> CodeGenerationEngine.java at line 101, and this value is used to access a
> filesystem resource at File() in WSDL20ToAxisServiceBuilder.java at line 153
> and 1281.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-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:all-tabpanel ] Andreas Veithen updated AXIS2-5884: --- Affects Version/s: (was: 1.8.0) 1.7.6 > 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] [Resolved] (AXIS2-5883) Generation of apidocs fails on Windows.
[ https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5883. Resolution: Fixed Fix Version/s: 1.7.7 > 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 > Fix For: 1.7.7 > > 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] [Resolved] (AXIS2-5885) Generating apidocs fails with Java 8.
[
https://issues.apache.org/jira/browse/AXIS2-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5885.
Resolution: Fixed
Fix Version/s: 1.7.7
> 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.7.6
> Environment: Windows 10 x86-64, JDK 1.8
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.7.7
>
> 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] [Updated] (AXIS2-5885) Generating apidocs fails with Java 8.
[
https://issues.apache.org/jira/browse/AXIS2-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5885:
---
Affects Version/s: (was: 1.8.0)
1.7.6
> 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.7.6
> 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=16160313#comment-16160313
]
Andreas Veithen commented on AXIS2-5877:
{{XSLTTemplateProcessor}} is not security sensitive because it's only used
during code generation. Can you provide a test case or exploit that shows how
the code in {{ConvertUtils}} would be used to carry out an attack
([CVE-2010-1632|https://svn.apache.org/repos/asf/axis/axis2/java/core/security/CVE-2010-1632.pdf]
provides an example)?
> 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-5875) Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
[
https://issues.apache.org/jira/browse/AXIS2-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160293#comment-16160293
]
Andreas Veithen commented on AXIS2-5875:
bq. Additionally, no error messages are shown when I import the modules using
m2e instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is
not created in that case. So might it be a solution to remove the following
line in the pom.xml instead of dealing with the imports?
bq. {CODE}
org.eclipse.pde.ManifestBuilder
{CODE}
The PDE builders are necessary to test these plugins in Eclipse.
> Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
> --
>
> Key: AXIS2-5875
> URL: https://issues.apache.org/jira/browse/AXIS2-5875
> Project: Axis2
> Issue Type: Bug
> Components: ide plugins
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
>
> I'm working on making trunk available in my Eclipse and came across the
> following error messages about unresolved imported packages in
> axis2.eclipse.codegen.plugin and axis2.eclipse.service.plugin. After having a
> look at the associated pom.xml, it seems that a lot of libs are already
> excluded from the import. Therefore I ask myself if the ones of the error
> messages simply need to be excluded as well? If not, shouldn't the imports be
> resolved using what my Eclipse provides and the project itself? I see a lot
> of Jars in the lib folder of those projects, but none of the ones with error
> messages.
> Additionally, no error messages are shown when I import the modules using m2e
> instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is
> not created in that case. So might it be a solution to remove the following
> line in the pom.xml instead of dealing with the imports?
> {CODE}
> org.eclipse.pde.ManifestBuilder
> {CODE}
> I have no idea currently what the proper solution to this problem is, but
> have the feeling it's removing imports...
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in
> Problem
> No available bundle exports package 'javax.jms' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 91 Plug-in Problem
> No available bundle exports package 'org.apache.crimson.jaxp' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 102Plug-in Problem
> No available bundle exports package 'org.aspectj.lang.annotation'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 104
> Plug-in Problem
> No available bundle exports package 'org.aspectj.lang'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 104Plug-in Problem
> No available bundle exports package 'org.codehaus.stax2' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.joda.convert'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.connect' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.event' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.console.history'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 113Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.console'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.internal' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.internal.jline'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 112
> Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.javadoc'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 114
> Plug-in Problem
> No available bundle exports package 'sun.misc'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 116Plug-in Problem
> No available bundle exports package 'sun.reflect.annotation' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> {QUOTE}
> {QUOTE}
> No
[jira] [Updated] (AXIS2-5875) Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
[
https://issues.apache.org/jira/browse/AXIS2-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5875:
---
Affects Version/s: (was: 1.8.0)
1.7.6
> Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
> --
>
> Key: AXIS2-5875
> URL: https://issues.apache.org/jira/browse/AXIS2-5875
> Project: Axis2
> Issue Type: Bug
> Components: ide plugins
>Affects Versions: 1.7.6
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
>
> I'm working on making trunk available in my Eclipse and came across the
> following error messages about unresolved imported packages in
> axis2.eclipse.codegen.plugin and axis2.eclipse.service.plugin. After having a
> look at the associated pom.xml, it seems that a lot of libs are already
> excluded from the import. Therefore I ask myself if the ones of the error
> messages simply need to be excluded as well? If not, shouldn't the imports be
> resolved using what my Eclipse provides and the project itself? I see a lot
> of Jars in the lib folder of those projects, but none of the ones with error
> messages.
> Additionally, no error messages are shown when I import the modules using m2e
> instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is
> not created in that case. So might it be a solution to remove the following
> line in the pom.xml instead of dealing with the imports?
> {CODE}
> org.eclipse.pde.ManifestBuilder
> {CODE}
> I have no idea currently what the proper solution to this problem is, but
> have the feeling it's removing imports...
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in
> Problem
> No available bundle exports package 'javax.jms' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 91 Plug-in Problem
> No available bundle exports package 'org.apache.crimson.jaxp' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 102Plug-in Problem
> No available bundle exports package 'org.aspectj.lang.annotation'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 104
> Plug-in Problem
> No available bundle exports package 'org.aspectj.lang'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 104Plug-in Problem
> No available bundle exports package 'org.codehaus.stax2' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.joda.convert'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.connect' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.event' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.console.history'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 113Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.console'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.internal' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.internal.jline'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 112
> Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.javadoc'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 114
> Plug-in Problem
> No available bundle exports package 'sun.misc'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 116Plug-in Problem
> No available bundle exports package 'sun.reflect.annotation' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> {QUOTE}
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'
> MANIFEST.MF /axis2.eclipse.service.plugin/META-INF line 61 Plug-in
> Problem
> No available bundle exports package 'org.aspectj.lang.annotation'
> MANIFEST.MF /axis2.eclipse.service.plugin/META-INF line 72 Plug-in
> Problem
> No available bundle exports package 'org.aspectj.lang'
[jira] [Commented] (AXIS2-5875) Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
[
https://issues.apache.org/jira/browse/AXIS2-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160291#comment-16160291
]
Andreas Veithen commented on AXIS2-5875:
These errors are only present on the trunk. They are related to r1800555.
On the 1.7 there is a different error:
bq. Unsatisfied constraint: 'Import-Package: javax.xml.stream; version="1.0.0"'
> Unresolved imported packages in MANIFEST.MF of axis2.eclipse.*.plugin.
> --
>
> Key: AXIS2-5875
> URL: https://issues.apache.org/jira/browse/AXIS2-5875
> Project: Axis2
> Issue Type: Bug
> Components: ide plugins
>Affects Versions: 1.8.0
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
>
> I'm working on making trunk available in my Eclipse and came across the
> following error messages about unresolved imported packages in
> axis2.eclipse.codegen.plugin and axis2.eclipse.service.plugin. After having a
> look at the associated pom.xml, it seems that a lot of libs are already
> excluded from the import. Therefore I ask myself if the ones of the error
> messages simply need to be excluded as well? If not, shouldn't the imports be
> resolved using what my Eclipse provides and the project itself? I see a lot
> of Jars in the lib folder of those projects, but none of the ones with error
> messages.
> Additionally, no error messages are shown when I import the modules using m2e
> instead of maven-eclipse-plugin, simply because the MANIFEST.MF-Builder is
> not created in that case. So might it be a solution to remove the following
> line in the pom.xml instead of dealing with the imports?
> {CODE}
> org.eclipse.pde.ManifestBuilder
> {CODE}
> I have no idea currently what the proper solution to this problem is, but
> have the feeling it's removing imports...
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in
> Problem
> No available bundle exports package 'javax.jms' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 91 Plug-in Problem
> No available bundle exports package 'org.apache.crimson.jaxp' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 102Plug-in Problem
> No available bundle exports package 'org.aspectj.lang.annotation'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 104
> Plug-in Problem
> No available bundle exports package 'org.aspectj.lang'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 104Plug-in Problem
> No available bundle exports package 'org.codehaus.stax2' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.joda.convert'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.connect' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi.event' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.jdi' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 111Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.console.history'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 113Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.console'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package
> 'org.openjdk.tools.internal.jline.internal' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.internal.jline'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 112
> Plug-in Problem
> No available bundle exports package 'org.openjdk.tools.javadoc'
> MANIFEST.MF /axis2.eclipse.codegen.plugin/META-INF line 114
> Plug-in Problem
> No available bundle exports package 'sun.misc'MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 116Plug-in Problem
> No available bundle exports package 'sun.reflect.annotation' MANIFEST.MF
> /axis2.eclipse.codegen.plugin/META-INF line 89 Plug-in Problem
> {QUOTE}
> {QUOTE}
> No available bundle exports package 'com.google.errorprone.annotations'
> MANIFEST.MF /axis2.eclipse.service.plugin/META-INF line 61 Plug-in
> Problem
> No available bundle exports package
[jira] [Commented] (AXIS2-5874) Memory leak when trying to getInputStream() from an External Repository data through AXIS
[
https://issues.apache.org/jira/browse/AXIS2-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160281#comment-16160281
]
Andreas Veithen commented on AXIS2-5874:
* The contract of {{DataHandler}} allows multiple calls to
{{getInputStream()}}. That means that requesting the stream and closing it will
not free the memory held by the {{DataHandler}}.
* The fact that you get an {{OutOfMemoryError}} in the code that reads the MIME
part does not mean that the (presumed) leak occurs there. You will need to look
at a heap dump to determine where references to the objects involved in the
leak are held. There is no a priori reason to believe that it's Axis2's fault;
it may be a problem in your code.
* 1.6.2 is an old release that is no longer supported. You would need to
provide steps to reproduce the problem on a more recent release.
> Memory leak when trying to getInputStream() from an External Repository data
> through AXIS
> -
>
> Key: AXIS2-5874
> URL: https://issues.apache.org/jira/browse/AXIS2-5874
> Project: Axis2
> Issue Type: Bug
> Components: jaxws, wsdl
>Affects Versions: 1.6.2
> Environment: Windows 2008
>Reporter: Nidhin Lazar
>Priority: Blocker
>
> We are using AXIS WS to connect and download files from an external
> repository .We are using SOAP based webservice calls download an object. The
> API returns a DataHandler object, from where we are getting the input stream.
> We have tried closing the inputstream object but even after the close call we
> can see that the memory is still holding the stream, and eventually the
> client machine is running out of memory.Any help on this would be highly
> appreciated.
> Our client code is as shown below
> URL url = new URL("http://"+host+"/ws/CntSrvc.svc?wsdl;);
> CntSrvc_Svc cService = new CntSrvc_Svc(url);
> CntSrvc cntSrvcClient = cService.getBasicHttpBindingCntSrvc(new
> MTOMFeature());
> InputStream in = null ;
> in = cntSrvcClient.download(contextIDString).getInputStream();
> // write in to a file.
> //closing the input stream
> if (in != null){
> in.close();
> }
> [Note;] Our client code runs under tomcat container, and this acts as a
> server to other services.
> [Note:]We have created a sample client without using AXIS, where our client
> connecting to external repository and download content.Here we donot see any
> memory leak.Our investigation proves that its when we use AXIS and
> getinputstream() the memory is leaking, input stream is not closing.Our
> current framework demands AXIS hence we would like to get a solution or
> workaround for this issue
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5874) Memory leak when trying to getInputStream() from an External Repository data through AXIS
[
https://issues.apache.org/jira/browse/AXIS2-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5874:
---
Fix Version/s: (was: 1.6.2)
> Memory leak when trying to getInputStream() from an External Repository data
> through AXIS
> -
>
> Key: AXIS2-5874
> URL: https://issues.apache.org/jira/browse/AXIS2-5874
> Project: Axis2
> Issue Type: Bug
> Components: jaxws, wsdl
>Affects Versions: 1.6.2
> Environment: Windows 2008
>Reporter: Nidhin Lazar
>Priority: Blocker
>
> We are using AXIS WS to connect and download files from an external
> repository .We are using SOAP based webservice calls download an object. The
> API returns a DataHandler object, from where we are getting the input stream.
> We have tried closing the inputstream object but even after the close call we
> can see that the memory is still holding the stream, and eventually the
> client machine is running out of memory.Any help on this would be highly
> appreciated.
> Our client code is as shown below
> URL url = new URL("http://"+host+"/ws/CntSrvc.svc?wsdl;);
> CntSrvc_Svc cService = new CntSrvc_Svc(url);
> CntSrvc cntSrvcClient = cService.getBasicHttpBindingCntSrvc(new
> MTOMFeature());
> InputStream in = null ;
> in = cntSrvcClient.download(contextIDString).getInputStream();
> // write in to a file.
> //closing the input stream
> if (in != null){
> in.close();
> }
> [Note;] Our client code runs under tomcat container, and this acts as a
> server to other services.
> [Note:]We have created a sample client without using AXIS, where our client
> connecting to external repository and download content.Here we donot see any
> memory leak.Our investigation proves that its when we use AXIS and
> getinputstream() the memory is leaking, input stream is not closing.Our
> current framework demands AXIS hence we would like to get a solution or
> workaround for this issue
--
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=16160277#comment-16160277
]
Andreas Veithen commented on AXIS2-5883:
Note that {{failIfNoMatch}} should be {{false}} to make this work on Unix based
systems.
> 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] [Updated] (AXIS2-5883) Generation of apidocs fails on Windows.
[ https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5883: --- Affects Version/s: (was: 1.8.0) 1.7.6 > 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 > 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] [Updated] (AXIS2-5883) Generation of apidocs fails on Windows.
[ https://issues.apache.org/jira/browse/AXIS2-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5883: --- Priority: Minor (was: Major) > 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] [Resolved] (AXIS2-5880) Several Resource leaks
[ https://issues.apache.org/jira/browse/AXIS2-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5880. Resolution: Invalid > Several Resource leaks > -- > > Key: AXIS2-5880 > URL: https://issues.apache.org/jira/browse/AXIS2-5880 > Project: Axis2 > Issue Type: Bug > Components: jaxws >Affects Versions: 1.7.6 >Reporter: Donald Kwakkel > Attachments: unreleased resources1.png, unreleased resources2.png, > unreleased resources3.png, unreleased resources4.png, unreleased > resources5.png > > > Our code check tool found several resource leak issues. See attached picture. > Some are not real resource leaks because the objects has a finalize method, > but even then it is better to close the resource itself because it is not > defined when the GC will close them. -- 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-5880) Several Resource leaks
[
https://issues.apache.org/jira/browse/AXIS2-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160273#comment-16160273
]
Andreas Veithen commented on AXIS2-5880:
I don't know what static code analysis tool you are using, but the results it
produces are pretty much useless. Take the example of {{WarBasedWSDLLocator}}
(line 68). The method returns an {{InputSource}} with an {{InputStream}}.
Obviously that stream must be open and it is the responsibility of the caller
to close it once it has read the data. Apparently the code analysis tool is
based on the assumption that a stream opened in a method must be closed in the
same method, which is only true if the reference to that stream is not passed
back to the caller or to another method.
> Several Resource leaks
> --
>
> Key: AXIS2-5880
> URL: https://issues.apache.org/jira/browse/AXIS2-5880
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
> Attachments: unreleased resources1.png, unreleased resources2.png,
> unreleased resources3.png, unreleased resources4.png, unreleased
> resources5.png
>
>
> Our code check tool found several resource leak issues. See attached picture.
> Some are not real resource leaks because the objects has a finalize method,
> but even then it is better to close the resource itself because it is not
> defined when the GC will close them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-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:all-tabpanel
]
Andreas Veithen updated AXIS2-5876:
---
Priority: Minor (was: Major)
> 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
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.7.7
>
> 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] [Updated] (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:all-tabpanel
]
Andreas Veithen updated AXIS2-5876:
---
Affects Version/s: (was: 1.8.0)
> 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
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
> Fix For: 1.7.7
>
> 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] [Resolved] (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:all-tabpanel
]
Andreas Veithen resolved AXIS2-5876.
Resolution: Fixed
Fix Version/s: 1.7.7
> 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
> Environment: Windows 10 Pro x86-64, Eclipse Oxygen Release (4.7.0)
> x86-64
>Reporter: Thorsten Schöning
>Priority: Minor
> Fix For: 1.7.7
>
> 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] [Resolved] (AXIS2-5879) WSDL20ToAxisServiceBuilder.java:1235 & 1255 (XML External Entity Injection)
[
https://issues.apache.org/jira/browse/AXIS2-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5879.
Resolution: Invalid
This code is used by the code generator to read the WSDL supplied by the user.
If the user wishes to process a WSDL with external entities, then we should
just do that. There is no security risk here.
> WSDL20ToAxisServiceBuilder.java:1235 & 1255 (XML External Entity Injection)
> ---
>
> Key: AXIS2-5879
> URL: https://issues.apache.org/jira/browse/AXIS2-5879
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
> Labels: security
>
> XML parser configured in WSDL20ToAxisServiceBuilder.java:1235 and 1255 does
> not prevent nor limit external entities resolution. This can expose the
> parser to an XML External Entities attack.
> Proposed solution: Always disable external entities:
> {code:java}
> public static DocumentBuilderFactory createDocumentBuilderFactory() {
> DocumentBuilderFactory factory =
> DocumentBuilderFactory.newInstance();
> factory.setNamespaceAware(true);
> try {
>
> factory.setFeature("http://xml.org/sax/features/external-general-entities;,
> false);
>
> factory.setFeature("http://xml.org/sax/features/external-parameter-entities;,
> false);
> }
> catch (ParserConfigurationException e) {
> throw new IllegalStateException(e);
> }
> return factory;
> }
> {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] [Updated] (AXIS2-5879) WSDL20ToAxisServiceBuilder.java:1235 & 1255 (XML External Entity Injection)
[
https://issues.apache.org/jira/browse/AXIS2-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5879:
---
Component/s: (was: jaxws)
kernel
> WSDL20ToAxisServiceBuilder.java:1235 & 1255 (XML External Entity Injection)
> ---
>
> Key: AXIS2-5879
> URL: https://issues.apache.org/jira/browse/AXIS2-5879
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
> Labels: security
>
> XML parser configured in WSDL20ToAxisServiceBuilder.java:1235 and 1255 does
> not prevent nor limit external entities resolution. This can expose the
> parser to an XML External Entities attack.
> Proposed solution: Always disable external entities:
> {code:java}
> public static DocumentBuilderFactory createDocumentBuilderFactory() {
> DocumentBuilderFactory factory =
> DocumentBuilderFactory.newInstance();
> factory.setNamespaceAware(true);
> try {
>
> factory.setFeature("http://xml.org/sax/features/external-general-entities;,
> false);
>
> factory.setFeature("http://xml.org/sax/features/external-parameter-entities;,
> false);
> }
> catch (ParserConfigurationException e) {
> throw new IllegalStateException(e);
> }
> return factory;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5878) ValidateXMLFile.java:55 (XML External Entity Injection)
[
https://issues.apache.org/jira/browse/AXIS2-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5878.
Resolution: Invalid
This method is only used in a single place to validate XML entered by a user
into a JTextArea. There is no security risk here.
> ValidateXMLFile.java:55 (XML External Entity Injection)
> ---
>
> Key: AXIS2-5878
> URL: https://issues.apache.org/jira/browse/AXIS2-5878
> Project: Axis2
> Issue Type: Bug
> Components: ide plugins
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
> Labels: security
>
> XML parser configured in ValidateXMLFile.java:55 does not prevent nor limit
> external entities resolution. This can expose the parser to an XML External
> Entities attack.
> Proposed solution: Always disable external entities when creating a
> DocumentBuilderFactory:
> {code:java}
> public static DocumentBuilderFactory createDocumentBuilderFactory() {
> DocumentBuilderFactory factory =
> DocumentBuilderFactory.newInstance();
> factory.setNamespaceAware(true);
> try {
>
> factory.setFeature("http://xml.org/sax/features/external-general-entities;,
> false);
>
> factory.setFeature("http://xml.org/sax/features/external-parameter-entities;,
> false);
> }
> catch (ParserConfigurationException e) {
> throw new IllegalStateException(e);
> }
> return factory;
> }
> {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] [Updated] (AXIS2-5878) ValidateXMLFile.java:55 (XML External Entity Injection)
[
https://issues.apache.org/jira/browse/AXIS2-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5878:
---
Component/s: (was: jaxws)
ide plugins
> ValidateXMLFile.java:55 (XML External Entity Injection)
> ---
>
> Key: AXIS2-5878
> URL: https://issues.apache.org/jira/browse/AXIS2-5878
> Project: Axis2
> Issue Type: Bug
> Components: ide plugins
>Affects Versions: 1.7.6
>Reporter: Donald Kwakkel
>Priority: Critical
> Labels: security
>
> XML parser configured in ValidateXMLFile.java:55 does not prevent nor limit
> external entities resolution. This can expose the parser to an XML External
> Entities attack.
> Proposed solution: Always disable external entities when creating a
> DocumentBuilderFactory:
> {code:java}
> public static DocumentBuilderFactory createDocumentBuilderFactory() {
> DocumentBuilderFactory factory =
> DocumentBuilderFactory.newInstance();
> factory.setNamespaceAware(true);
> try {
>
> factory.setFeature("http://xml.org/sax/features/external-general-entities;,
> false);
>
> factory.setFeature("http://xml.org/sax/features/external-parameter-entities;,
> false);
> }
> catch (ParserConfigurationException e) {
> throw new IllegalStateException(e);
> }
> return factory;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-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:all-tabpanel
]
Andreas Veithen resolved AXIS2-5872.
Resolution: Fixed
Fix Version/s: 1.7.7
> 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
> Fix For: 1.7.7
>
> 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=16147879#comment-16147879
]
Andreas Veithen commented on AXIS2-5872:
Damn! I forgot to include your name in the commit comment.
Do you also want this fix on the 1.7 branch?
> 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] [Updated] (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:all-tabpanel
]
Andreas Veithen updated AXIS2-5872:
---
Affects Version/s: (was: 1.8.0)
1.7.6
> 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] [Resolved] (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:all-tabpanel
]
Andreas Veithen resolved AXIS2-5873.
Resolution: Fixed
> "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 ... SKIPPED
> [INFO] echo ... SKIPPED
> [INFO] webapp-tests ... SKIPPED
> [INFO]
>
[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=16145215#comment-16145215
]
Andreas Veithen commented on AXIS2-5873:
I've implemented a slightly different solution that completely eliminates Maven
property substitution and instead retrieves the relevant properties directly
from Groovy.
> "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 ... SKIPPED
>
[jira] [Updated] (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:all-tabpanel
]
Andreas Veithen updated AXIS2-5873:
---
Affects Version/s: (was: 1.8.0)
> "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 ... SKIPPED
> [INFO] echo ... SKIPPED
> [INFO] webapp-tests ... SKIPPED
> [INFO]
>
[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=16144227#comment-16144227
]
Andreas Veithen commented on AXIS2-5872:
You could add an invocation of the {{copy-resources}} goal of the
{{maven-resources-plugin}} to copy the files into a directory under {{target}}
and then add that directory to {{}}.
> 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.8.0
> 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: 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] [Updated] (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:all-tabpanel
]
Andreas Veithen updated AXIS2-5865:
---
Fix Version/s: 1.7.7
> 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-5866) Axis ignores org.apache.axis2.client.Options#getTimeOutInMilliSeconds
[
https://issues.apache.org/jira/browse/AXIS2-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143091#comment-16143091
]
Andreas Veithen commented on AXIS2-5866:
This code has significantly changed on the trunk. Can you test that with
1.8.0-SNAPSHOT?
> Axis ignores org.apache.axis2.client.Options#getTimeOutInMilliSeconds
> -
>
> Key: AXIS2-5866
> URL: https://issues.apache.org/jira/browse/AXIS2-5866
> Project: Axis2
> Issue Type: Bug
> Components: client-api, transports
>Affects Versions: 1.7.4
> Environment: Java 8, Tomcat
>Reporter: Mykhailo Hodovaniuk
>Priority: Minor
>
> According to documentation
> https://axis.apache.org/axis2/java/core/docs/http-transport.html the timeouts
> can be defined:
> {code:java}
> For runtime configuration, it can be set as follows within the client stub:
> ...
> Options options = new Options();
> options.setProperty(HTTPConstants.SO_TIMEOUT, new
> Integer(timeOutInMilliSeconds));
> options.setProperty(HTTPConstants.CONNECTION_TIMEOUT, new
> Integer(timeOutInMilliSeconds));
> // or
> options.setTimeOutInMilliSeconds(timeOutInMilliSeconds);
> ...
> {code}
> But instead, Axis ignores this property because:
> _org.apache.axis2.transport.http.CommonsHTTPTransportSender#invoke_ has code
> {code:java}
> // set the property values only if they are not set by the user explicitly
> if (msgContext.getProperty(HTTPConstants.SO_TIMEOUT) == null) {
> msgContext.setProperty(HTTPConstants.SO_TIMEOUT, soTimeout);
> }
> if (msgContext.getProperty(HTTPConstants.CONNECTION_TIMEOUT) ==
> null) {
> msgContext.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> connectionTimeout);
> }
> {code}
> where _connectionTimeout_ and _soTimeout_ are always non null.
> At the same time
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_
> tries to define these values if they are null with timeOutInMilliSeconds.
> The problem is that
> _org.apache.axis2.transport.http.CommonsHTTPTransportSender#invoke_ is higher
> in call hirarchy so the
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_
> does not work as expected. The _SO_TIMEOUT_ and _CONNECTION_TIMEOUT_
> parameters are always defined inside
> _org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl#setTimeouts_.
> The workaround is to define timeouts in axis2.xml.
--
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=16143064#comment-16143064
]
Andreas Veithen commented on AXIS2-5865:
The problem is more general: during the build we don't check that the Web app
created by the build.xml script has the expected content, i.e. the same content
as the Web app created by the Maven build (which is the reference because we
have integration tests for it).
> 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] [Resolved] (AXIS2-5867) int doent make optional
[ https://issues.apache.org/jira/browse/AXIS2-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5867. Resolution: Invalid Please note that this is a bug tracker, not a Q forum. > int doent make optional > > > Key: AXIS2-5867 > URL: https://issues.apache.org/jira/browse/AXIS2-5867 > Project: Axis2 > Issue Type: Bug > Components: jaxws >Affects Versions: 1.7.6 > Environment: axis 2 and tomcat and windows and unix as well >Reporter: Suresh kamma > > I am creating java2wsdl as web service and create method in service > add(int i, int j), I want to create int i and int j as optional , I dont > want to make mandatory. I verified and searched lot of foroums and no of > website's. it was not getting int as optional, even though, i tried with > Integer wrapper class, that one also not able to do make nillable=true in > wsdl and cant make as optional. > I am expecting below > in my service class add(int i , int j) > I want to see int i and int j as optional > > > How do i create above? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-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:all-tabpanel
]
Andreas Veithen resolved AXIS2-5793.
Resolution: Fixed
Fix Version/s: 1.7.7
> 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
> Fix For: 1.7.7
>
> 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}
> https://docs.oracle.com/javase/7/docs/api/java/io/File.html#toURL()
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5870) XMLPrettyPrinter.prettify uses OS-dependant newlines
[
https://issues.apache.org/jira/browse/AXIS2-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5870.
Resolution: Fixed
> 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
> Fix For: 1.7.7
>
> 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 following is properly applied to the XML:
> {CODE}
> xalan:indent-amount='4'
> {CODE}
> vs.
> {CODE}
> xalan:indent-amount='40'
> {CODE}
> "line-separator" has been introduced in Xalan 2.7.0, because the associated
> bug has been resolved "02/Jun/05 06:18" and 2.7.0 has been published in
> "2005-08-08 04:26". The JDK I'm using provides Xalan 2.7.0 as well, so in
> theory
[jira] [Resolved] (AXIS2-5794) Some Data Binding tests fail if pathes with spaces are used
[
https://issues.apache.org/jira/browse/AXIS2-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5794.
Resolution: Duplicate
> Some Data Binding tests fail if pathes with spaces are used
> ---
>
> Key: AXIS2-5794
> URL: https://issues.apache.org/jira/browse/AXIS2-5794
> 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: JAXBRI pom.xml.patch, JAXWS integration pom.xml.patch,
> JAXWS pom.xml.patch, JIBX pom.xml.patch, JSON pom.xml.patch, metadata
> pom.xml.patch, samples jaxws-addressbook pom.xml.patch
>
>
> There are some tests compiling Java code using Maven or ANT or such and some
> of them don't quote paths properl, so the Java compilation fails. The
> following is one example for JAXBRI:
> {CODE}
> [DEBUG] Command line options:
> [DEBUG] -d C:\Users\tschoening\Documents\Eclipse\Java Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\jaxbri\target\test-classes -classpath
> C:\Users\tschoening\Documents\Eclipse\Java Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\jaxbri\target\test-classes;C:\Users\tschoening\Documents\Eclipse\Java
> Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\jaxbri\target\classes;C:\Users\tschoening\Documents\Eclipse\Java
> Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\codegen\target\axis2-codegen-1.7.3.jar;C:\Users\tschoening\Documents\Eclipse\Java
> Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\kernel\target\axis2-kernel-1.7.3.jar;C:\Users\tschoening\.m2\repository\org\apache\ws\commons\axiom\axiom-impl\1.2.19\axiom-impl-1.2.19.jar;C:\Users\tschoening\.m2\repository\org\codehaus\woodstox\woodstox-core-asl\4.2.0\woodstox-core-asl-4.2.0.jar;C:\Users\tschoening\.m2\repository\org\codehaus\woodstox\stax2-api\3.1.1\stax2-api-3.1.1.jar;C:\Users\tschoening\.m2\repository\org\apache\geronimo\specs\geronimo-ws-metadata_2.0_spec\1.1.2\geronimo-ws-metadata_2.0_spec-1.1.2.jar;C:\Users\tschoening\.m2\repository\org\apache\geronimo\specs\geronimo-jta_1.1_spec\1.1\geronimo-jta_1.1_spec-1.1.jar;C:\Users\tschoening\.m2\repository\javax\servlet\servlet-api\2.3\servlet-api-2.3.jar;C:\Users\tschoening\.m2\repository\commons-fileupload\commons-fileupload\1.3.1\commons-fileupload-1.3.1.jar;C:\Users\tschoening\.m2\repository\wsdl4j\wsdl4j\1.6.2\wsdl4j-1.6.2.jar;C:\Users\tschoening\.m2\repository\org\apache\neethi\neethi\3.0.3\neethi-3.0.3.jar;C:\Users\tschoening\.m2\repository\org\apache\woden\woden-core\1.0M10\woden-core-1.0M10.jar;C:\Users\tschoening\.m2\repository\javax\ws\rs\jsr311-api\1.1.1\jsr311-api-1.1.1.jar;C:\Users\tschoening\Documents\Eclipse\Java
> Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\adb\target\axis2-adb-1.7.3.jar;C:\Users\tschoening\.m2\repository\org\apache\ws\commons\axiom\axiom-dom\1.2.19\axiom-dom-1.2.19.jar;C:\Users\tschoening\.m2\repository\org\apache\geronimo\specs\geronimo-activation_1.1_spec\1.0.2\geronimo-activation_1.1_spec-1.0.2.jar;C:\Users\tschoening\.m2\repository\com\sun\xml\ws\jaxws-tools\2.2.6\jaxws-tools-2.2.6.jar;C:\Users\tschoening\.m2\repository\org\apache\ws\commons\axiom\axiom-jaxb\1.2.19\axiom-jaxb-1.2.19.jar;C:\Users\tschoening\.m2\repository\org\apache\ws\commons\axiom\axiom-api\1.2.19\axiom-api-1.2.19.jar;C:\Users\tschoening\.m2\repository\jaxen\jaxen\1.1.6\jaxen-1.1.6.jar;C:\Users\tschoening\.m2\repository\org\apache\geronimo\specs\geronimo-stax-api_1.0_spec\1.0.1\geronimo-stax-api_1.0_spec-1.0.1.jar;C:\Users\tschoening\.m2\repository\org\apache\james\apache-mime4j-core\0.7.2\apache-mime4j-core-0.7.2.jar;C:\Users\tschoening\Documents\Eclipse\Java
> Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\java2wsdl\target\axis2-java2wsdl-1.7.3.jar;C:\Users\tschoening\Documents\Eclipse\Java
> Bug 2187\Libs Java
> 3rd\Apache\Axis2\1.7.3\src\modules\transport\http\target\axis2-transport-http-1.7.3.jar;C:\Users\tschoening\.m2\repository\org\apache\httpcomponents\httpcore\4.2.5\httpcore-4.2.5.jar;C:\Users\tschoening\.m2\repository\org\apache\httpcomponents\httpclient\4.2.5\httpclient-4.2.5.jar;C:\Users\tschoening\.m2\repository\commons-codec\commons-codec\1.3\commons-codec-1.3.jar;C:\Users\tschoening\.m2\repository\commons-httpclient\commons-httpclient\3.1\commons-httpclient-3.1.jar;C:\Users\tschoening\Documents\Eclipse\Java
> Bug 2187\Libs Java
>
[jira] [Updated] (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:all-tabpanel
]
Andreas Veithen updated AXIS2-5793:
---
Summary: Various tests fail when Axis2 is built using a path with spaces
(was: DBCwithReduceWSDLMemoryParmsTests fails if pathes with spaces are used)
> 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}
> https://docs.oracle.com/javase/7/docs/api/java/io/File.html#toURL()
--
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) DBCwithReduceWSDLMemoryParmsTests fails if pathes with spaces are used
[
https://issues.apache.org/jira/browse/AXIS2-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142041#comment-16142041
]
Andreas Veithen commented on AXIS2-5793:
Please note that patches need to be prepared against trunk (because all bug
fixed need to be applied to the trunk first, to avoid regressions in the next
major release) and shouldn't contain formatting changes (to avoid unnecessary
conflicts when merging them to a maintenance branch).
> DBCwithReduceWSDLMemoryParmsTests fails if pathes with spaces are used
> --
>
> 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}
> https://docs.oracle.com/javase/7/docs/api/java/io/File.html#toURL()
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5871) Cannot deploy Service by .aar on Windows
[ https://issues.apache.org/jira/browse/AXIS2-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5871. Resolution: Fixed Fix Version/s: 1.7.7 > 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 > Fix For: 1.7.7 > > > 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] [Updated] (AXIS2-5870) XMLPrettyPrinter.prettify uses OS-dependant newlines
[
https://issues.apache.org/jira/browse/AXIS2-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5870:
---
Fix Version/s: 1.7.7
> 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
> Fix For: 1.7.7
>
> 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 following is properly applied to the XML:
> {CODE}
> xalan:indent-amount='4'
> {CODE}
> vs.
> {CODE}
> xalan:indent-amount='40'
> {CODE}
> "line-separator" has been introduced in Xalan 2.7.0, because the associated
> bug has been resolved "02/Jun/05 06:18" and 2.7.0 has been published in
> "2005-08-08 04:26". The JDK I'm using provides Xalan 2.7.0 as well, so in
> theory
[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=16140709#comment-16140709
]
Andreas Veithen commented on AXIS2-5870:
Can you test this with the latest code from the 1.7 branch?
> 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 following is properly applied to the XML:
> {CODE}
> xalan:indent-amount='4'
> {CODE}
> vs.
> {CODE}
> xalan:indent-amount='40'
> {CODE}
> "line-separator" has been introduced in Xalan 2.7.0, because the associated
> bug has been resolved "02/Jun/05 06:18" and 2.7.0 has been published in
> "2005-08-08 04:26". The JDK I'm using
[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=16140570#comment-16140570
]
Andreas Veithen commented on AXIS2-5870:
This issue actually partially duplicates AXIS2-5781 and has been fixed by
r1779069 and r1779074 on the trunk, so we could just merge these two changes to
the 1.7 branch.
> 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 following is properly applied to the XML:
> {CODE}
> xalan:indent-amount='4'
> {CODE}
> vs.
> {CODE}
> xalan:indent-amount='40'
> {CODE}
> "line-separator" has been introduced in Xalan 2.7.0, because the associated
> bug has
[jira] [Resolved] (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:all-tabpanel
]
Andreas Veithen resolved AXIS2-5868.
Resolution: Fixed
Fix Version/s: 1.7.7
> 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
> Fix For: 1.7.7
>
>
> 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] [Moved] (AXIS-2923) java.lang.ExceptionInInitializerError and java.lang.NoClassDefFoundError: Could not initialize class com.xxx.cfsa.axis.XXXConfigMerlin in jboss eap 6.4
[ https://issues.apache.org/jira/browse/AXIS-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved AXIS2-5869 to AXIS-2923: -- Affects Version/s: (was: 1.6.2) Component/s: (was: wsdl) Key: AXIS-2923 (was: AXIS2-5869) Project: Axis (was: Axis2) > java.lang.ExceptionInInitializerError and java.lang.NoClassDefFoundError: > Could not initialize class com.xxx.cfsa.axis.XXXConfigMerlin in jboss eap 6.4 > --- > > Key: AXIS-2923 > URL: https://issues.apache.org/jira/browse/AXIS-2923 > Project: Axis > Issue Type: Bug >Reporter: Suresh >Priority: Critical > Original Estimate: 12h > Remaining Estimate: 12h > > Hi Sir, > We are migrating an application from websphere to Jboss eap 6.4. > Below are some jar files created for wss4j like crypto engine axis tool etc. > xxx-axis-tools.jar: XXXConfigMerlin class file is present in this jar. > xxx-configuration-3.2.2.jar > xxx-configuration-servlet-3.2.2.jar > below is the meta info from axis.jar: > Manifest-Version: 1.0 > Ant-Version: Apache Ant 1.5.3 > Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.) > Name: org/apache/axis > Implementation-Title: Apache Axis > Implementation-Version: 1.3 2244 October 5 2005 > Implementation-Vendor: Apache Web Services > server-config.wsdd: > --- > > > > > value="com.xxx.exante.bankserv.hsa.security.callback.DefinityPWCallback" /> > > > > Crypto.properties: > > org.apache.ws.security.crypto.provider=com.xxx.cfsa.axis.XXXConfigMerlin > org.apache.ws.security.crypto.merlin.keystore.type=pkcs12 > org.apache.ws.security.crypto.merlin.keystore.password= > org.apache.ws.security.crypto.merlin.file=xxx_Keystore.pkcs > we are getting below error in soap web services in jboss eap 6.4. > when we trigger the soap request for the first time below error: > > 15:37:52,485 INFO [stdout] (http-localhost/127.0.0.1:8080-1) > Configuration.bootstrap(Configuration.java:1065): fatal error initializing > Configuration: java.lang.StringIndexOutOfBoundsException: String index out of > range: -615:37:52,491 DEBUG [org.apache.axis.i18n.ProjectResourceBundle] > (http-localhost/127.0.0.1:8080-1) > org.apache.axis.i18n.resource::handleGetObject(exception00)15:37:52,492 INFO > [org.apache.axis.EXCEPTIONS] (http-localhost/127.0.0.1:8080-1) Exception:: > java.lang.ExceptionInInitializerError at > com.xxx.cfsa.axis.XXXConfigAbstractCrypto.(XXXConfigAbstractCrypto.java:51) > [xxx_axis_tools.jar:] at > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > [rt.jar:1.7.0_11] at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > [rt.jar:1.7.0_11] at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > [rt.jar:1.7.0_11] at > java.lang.reflect.Constructor.newInstance(Constructor.java:525) > [rt.jar:1.7.0_11] at > org.apache.ws.security.components.crypto.CryptoFactory.loadClass(CryptoFactory.java:117) > [wss4j.jar:] at > org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:101) > [wss4j.jar:] at > org.apache.ws.security.handler.WSHandler.loadSignatureCrypto(WSHandler.java:400) > [wss4j.jar:] at > org.apache.ws.security.handler.WSHandler.decodeSignatureParameter2(WSHandler.java:845) > [wss4j.jar:] at > org.apache.ws.axis.security.WSDoAllReceiver.invoke(WSDoAllReceiver.java:147) > [wss4j.jar:] at > org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) > [axis.jar:] at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) > [axis.jar:] at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) > [axis.jar:] at > org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) > [axis.jar:] at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) > [axis.jar:] at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) > [axis.jar:] at > org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454) > [axis.jar:] at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281) > [axis.jar:] at > org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699) > [axis.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) > [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2] at > org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) > [axis.jar:] at
[jira] [Updated] (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:all-tabpanel
]
Andreas Veithen updated AXIS2-5868:
---
Priority: Minor (was: Major)
> 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=16134434#comment-16134434
]
Andreas Veithen commented on AXIS2-5868:
I believe that piece of code is actually nonsense and should be removed. There
are two reasons:
* We synchronize on parameters anyway, so I don't understand why we would want
to replace the {{HashMap}} by a {{ConcurrentHashMap}} dynamically.
* As far as I know, {{ConcurrentModificationException}} is only thrown by
iterators created from a {{HashMap}}, but never by {{put}}.
> 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
>
> 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-5863) Possible null dereference in ServiceStub class
[
https://issues.apache.org/jira/browse/AXIS2-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118944#comment-16118944
]
Andreas Veithen commented on AXIS2-5863:
That's because I didn't apply your patch. Instead I implemented a different
solution, namely I changed the code so that _messageContext can't be null in
the first place (by simply creating the MessageContext instance earlier). That
indeed means that the piece of code you posted in the bug description remains
unchanged. Note that similar code is produced in multiple locations in the
template. I may have missed one instance. If that's the case, let me know.
> 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
> Fix For: 1.7.6
>
> 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] [Resolved] (AXIS2-5861) axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File
[ https://issues.apache.org/jira/browse/AXIS2-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5861. Resolution: Incomplete Closing this issue. Please reopen it if you can reproduce this with Axis2 1.7.5 or 1.7.6. > axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File > -- > > Key: AXIS2-5861 > URL: https://issues.apache.org/jira/browse/AXIS2-5861 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.6.2 > Environment: Windows 7 64 bit >Reporter: Robert Seletsky > > axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File > does not generate namespace "t" in vendor WSDL > https://unm.custhelp.com/cgi-bin/unm.cfg/services/soap?wsdl=typed > Wondering is Axis2 1.6.2 is supported? > Wondering if best to use axis2-wsdl2code-maven-plugin version 1.7.5 and > migrate legacy code accordingly? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5589) Allocate exception for servlet AxisServlet
[ https://issues.apache.org/jira/browse/AXIS2-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5589. Resolution: Incomplete To identify the root cause of this type of issue, you would typically enable debug logging and then look for the messages that indicate why the module failed to load. On application servers, failures to load the addressing module are most often caused by class loader issues, not by bugs in Axis2. If you find evidence that there is a bug in Axis2, please create a new ticket with all the evidence. Please note that we use JIRA as a bug tracker, not a Q forum. > Allocate exception for servlet AxisServlet > -- > > Key: AXIS2-5589 > URL: https://issues.apache.org/jira/browse/AXIS2-5589 > Project: Axis2 > Issue Type: Bug > Components: Addressing >Affects Versions: 1.6.1 > Environment: Test and infuture Production >Reporter: Santhosh > Labels: Allocate, AxisServlet, exception, for, servlet > Original Estimate: 756h > Remaining Estimate: 756h > > Hi Team, > We are facing below exception when we exposed our webservice using AXIS2.0 on > ITP webserver(HP product which runs on Tandem OS). This is the first time we > are facing this exception for this instance and Load is minimal , all of > sudden 1 of the 4 instances went into this state and all requests processed > by this instance are errored out. Before this exception occurred we were able > to see proper response and test it properly. > I have collected all required logs during the time of issue. Please drop me a > mail on "santhosh_arvapa...@infosys.com" for more details. Request you to > please look into this and provide us with your observations. > > Fri, Jun 21, 21:04:45;$Y9MV;SEVERE;StandardWrapperValve#invoke;Allocate > exception for servlet AxisServlet > org.apache.axis2.AxisFault: The system is attempting to engage a module that > is not available: addressing > at > org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:584) > at > org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(AxisConfiguration.java:705) > at > org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:831) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.engageGlobalModules(WarBasedAxisConfigurator.java:300) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:94) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:584) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:454) > at > org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1176) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1102) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:812) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) > at > com.hp.tandem.nsjsp.valves.RequestTrackerValve.invoke(RequestTrackerValve.java:73) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:401) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:243) > at > com.tandem.servlet.coyote.http11.NSJSPHttp11Processor.process(NSJSPHttp11Processor.java:133) > at > com.tandem.servlet.coyote.http11.NSJSPHttp11Processor.process(NSJSPHttp11Processor.java:101) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:218) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:196) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:431) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For
[jira] [Resolved] (AXIS2-5860) CLONE - Allocate exception for servlet AxisServlet
[ https://issues.apache.org/jira/browse/AXIS2-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5860. Resolution: Duplicate > CLONE - Allocate exception for servlet AxisServlet > -- > > Key: AXIS2-5860 > URL: https://issues.apache.org/jira/browse/AXIS2-5860 > Project: Axis2 > Issue Type: Bug > Components: Addressing >Affects Versions: 1.6.2 > Environment: Test and Production >Reporter: Ashish Sharma > Labels: Allocate, AxisConfiguration, AxisServlet, engageModule, > exception, for, servlet > Original Estimate: 336h > Remaining Estimate: 336h > > Hi Team, > We are facing below exception when we exposed our webservice using AXIS2.0 on > ITP webserver(HP product which runs on Tandem OS). There have been multiple > occurrences of this issue in Production. When the iTP Web server with 4 > instances is restarted , all of sudden 1 of the 4 instances went into this > state(corrupt) and all requests processed by this instance(Server Process) > are errored out. > I have collected all required logs during the time of issue. Please drop me a > mail on "ashish_sharm...@infosys.com" for more details. Request you to please > look into this and provide us with your observations. > > Sun, Jul 16, 21:42:57;$Z6JQ;SEVERE;StandardWrapperValve#invoke;Allocate > exception for servlet AxisServlet > org.apache.axis2.AxisFault: The system is attempting to engage a module that > is not available: addressing > at > org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:584) > at > org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(AxisConfiguration.java:705) > at > org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:831) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.engageGlobalModules(WarBasedAxisConfigurator.java:300) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:94) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:584) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:454) > at > org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1176) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1102) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:812) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) > at > com.hp.tandem.nsjsp.valves.RequestTrackerValve.invoke(RequestTrackerValve.java:73) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:401) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:243) > at > com.tandem.servlet.coyote.http11.NSJSPHttp11Processor.process(NSJSPHttp11Processor.java:133) > at > com.tandem.servlet.coyote.http11.NSJSPHttp11Processor.process(NSJSPHttp11Processor.java:101) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:218) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:196) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:431) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Thanks > Ashish Sharma -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5862) Handler / Phase Indexes incorrect?
[
https://issues.apache.org/jira/browse/AXIS2-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5862:
---
Fix Version/s: (was: 1.7.6)
> Handler / Phase Indexes incorrect?
> --
>
> Key: AXIS2-5862
> URL: https://issues.apache.org/jira/browse/AXIS2-5862
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.4
>Reporter: Jeff Thomas
>
> I believe there is a problem or rather multiple problems in the Phase/Handler
> flow indexing..but I am not 100% sure.
> In 'org.apache.axis2.engine.Phase':
> 1. During the Phase invocation:
> While cycling through the handlers, I would expect
> 'msgctx.setHandlerIndex(i+1)' but instead the phase index is incremented.
> {code:java}
> int handlersSize = handlers.size();
>
> for (int i= currentIndex; i < handlersSize; i++) {
> Handler handler = (Handler) handlers.get(i);
> InvocationResponse pi = invokeHandler(handler, msgctx);
>
> if (!pi.equals(InvocationResponse.CONTINUE)) {
> return pi;
> }
>
> // Set phase index to the next handler
> msgctx.setCurrentPhaseIndex(i+1);
> }
> {code}
> 2. During the phase 'flowComplete':
> I would expect here 'msgContext.getCurrenHandlerIndex()' and
> 'msgContext.setCurrentHandlerIndex(0)' instead.
> {code:java}
> // This will be non-zero if we failed during execution of one of the
> // handlers in this phase
> int currentHandlerIndex = msgContext.getCurrentPhaseIndex();
> if (currentHandlerIndex == 0) {
> currentHandlerIndex = handlers.size();
> } else {
> /*We need to set it to 0 so that any previous phases will execute
> all
> * of their handlers.*/
>msgContext.setCurrentPhaseIndex(0);
> }
>for (; currentHandlerIndex > 0; currentHandlerIndex--) {
> Handler handler = (Handler) handlers.get(currentHandlerIndex - 1);
> if (isDebugEnabled) {
> log.debug(msgContext.getLogIDString() + " Invoking
> flowComplete() for Handler '" +
> handler.getName() + "' in Phase '" + phaseName + "'");
> }
> handler.flowComplete(msgContext);
> }
> {code}
>This is currrently causing errors in our installation because we are
> seeing a currentPhaseIndex == 1, which forces the "currentHandlerIndex == 1";
> however the phase we are in has no handlers. This causes an
> OutOfBoundsException when it attempts to get the handler with index[0] (1-1).
> {noformat}
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:368)
> at
> java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:377)
> at org.apache.axis2.engine.Phase.flowComplete(Phase.java:361)
> {noformat}
> Unfortunately I am not sure if there even more locations where HandlerIndex
> instead of PhaseIndex probably should have been used.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5863) Possible null dereference in ServiceStub class
[
https://issues.apache.org/jira/browse/AXIS2-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5863.
Resolution: Fixed
Fix Version/s: 1.7.6
> 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
> Fix For: 1.7.6
>
> 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-5861) axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File
[ https://issues.apache.org/jira/browse/AXIS2-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097291#comment-16097291 ] Andreas Veithen commented on AXIS2-5861: Yes. > axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File > -- > > Key: AXIS2-5861 > URL: https://issues.apache.org/jira/browse/AXIS2-5861 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.6.2 > Environment: Windows 7 64 bit >Reporter: Robert Seletsky > > axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File > does not generate namespace "t" in vendor WSDL > https://unm.custhelp.com/cgi-bin/unm.cfg/services/soap?wsdl=typed > Wondering is Axis2 1.6.2 is supported? > Wondering if best to use axis2-wsdl2code-maven-plugin version 1.7.5 and > migrate legacy code accordingly? -- 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-5861) axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File
[ https://issues.apache.org/jira/browse/AXIS2-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093715#comment-16093715 ] Andreas Veithen commented on AXIS2-5861: Please confirm that the problem still exists in the latest release and provide the steps to reproduce. Since this occurs with axis2-wsdl2code-maven-plugin that would mean provide a minimal Maven project that shows the problem. > axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File > -- > > Key: AXIS2-5861 > URL: https://issues.apache.org/jira/browse/AXIS2-5861 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.6.2 > Environment: Windows 7 64 bit >Reporter: Robert Seletsky > > axis2-wsdl2code-maven-plugin version 1.6.2 improperly generates Java Stub File > does not generate namespace "t" in vendor WSDL > https://unm.custhelp.com/cgi-bin/unm.cfg/services/soap?wsdl=typed > Wondering is Axis2 1.6.2 is supported? > Wondering if best to use axis2-wsdl2code-maven-plugin version 1.7.5 and > migrate legacy code accordingly? -- 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=16071746#comment-16071746 ] Andreas Veithen commented on AXIS2-5857: Can you help us translate https://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/modules/kernel/conf/log4j.properties into an equivalent Log4j 2.x configuration? > 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] [Resolved] (AXIS2-5325) java.lang.LinkageError: loader constraint violation in interface itable initialization
[ https://issues.apache.org/jira/browse/AXIS2-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5325. Resolution: Not A Problem > java.lang.LinkageError: loader constraint violation in interface itable > initialization > -- > > Key: AXIS2-5325 > URL: https://issues.apache.org/jira/browse/AXIS2-5325 > Project: Axis2 > Issue Type: Bug > Components: om >Affects Versions: 1.6.2 > Environment: Windows 7 Enterprise Service pack 1, jboss-5.1.0.GA, > axis2-1.6.2 (exploded war), rampart-1.6.2 >Reporter: AravindPS > Labels: Axis2, LinkageError, rampart, upgrade, version > > I have a working web service project using axis2 1.5.5 and rampart 1.6.0 > deployed on JBoss. I tried to upgrade the axis2 and rampart versions to > 1.6.2. When I use the 1.6.2 related jars and try to build the code, I got > minor errors which I corrected (WSHandlerResult.getResults() now returns a > List rather than a Vector which I was using before) and then tried to deploy > this on JBoss. The service gets deployed but when I try to view the services > (http://localhost:8080/axis2/) I get an error: > - > 2012-05-21 13:43:29,177 [main] WARN > com.ipswitch.messageway.perimeter.init.MWWSLifeCycle - Not able to load > action handler, instantiating default handler > 2012-05-21 13:43:29,740 [main] INFO > org.apache.axis2.deployment.ServiceDeployer - The MessageWayWebService.aar > service, which is not valid, caused java.lang.LinkageError: loader constraint > violation in interface itable initialization: when resolving method > "org.apache.axiom.om.impl.dom.DocumentImpl.getDomConfig()Lorg/w3c/dom/DOMConfiguration;" > the class loader (instance of > org/jboss/classloader/spi/base/BaseClassLoader) of the current class, > org/apache/axiom/om/impl/dom/DocumentImpl, and the class loader (instance of > ) for interface org/w3c/dom/Document have different Class objects > for the type org/w3c/dom/DOMConfiguration used in the signature > at > org.apache.axiom.om.impl.dom.factory.OMDOMFactory.createOMDocument(OMDOMFactory.java:418) > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.createDocument(StAXOMBuilder.java:183) > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:105) > at > org.apache.axiom.om.impl.dom.factory.AbstractOMMetaFactory.internalCreateStAXOMBuilder(AbstractOMMetaFactory.java:81) > at > org.apache.axiom.om.impl.dom.factory.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:91) > at > org.apache.axiom.om.OMXMLBuilderFactory.createStAXOMBuilder(OMXMLBuilderFactory.java:92) > at > org.apache.neethi.builders.converters.OMToDOMConverter.convert(OMToDOMConverter.java:37) > at > org.apache.neethi.builders.converters.OMToDOMConverter.convert(OMToDOMConverter.java:32) > at > org.apache.neethi.builders.converters.ConverterRegistry.convert(ConverterRegistry.java:159) > at > org.apache.neethi.AssertionBuilderFactoryImpl.invokeBuilder(AssertionBuilderFactoryImpl.java:135) > at > org.apache.neethi.AssertionBuilderFactoryImpl.build(AssertionBuilderFactoryImpl.java:117) > at > org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:224) > at > org.apache.neethi.PolicyBuilder.getPolicyOperator(PolicyBuilder.java:174) > at org.apache.neethi.PolicyBuilder.getPolicy(PolicyBuilder.java:124) > at org.apache.neethi.PolicyEngine.getPolicy(PolicyEngine.java:100) > at > org.apache.ws.secpolicy11.builders.X509TokenBuilder.build(X509TokenBuilder.java:77) > at > org.apache.ws.secpolicy11.builders.X509TokenBuilder.build(X509TokenBuilder.java:35) > at > org.apache.neethi.AssertionBuilderFactoryImpl.invokeBuilder(AssertionBuilderFactoryImpl.java:138) > at > org.apache.neethi.AssertionBuilderFactoryImpl.build(AssertionBuilderFactoryImpl.java:117) > at > org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:224) > at > org.apache.neethi.PolicyBuilder.getPolicyOperator(PolicyBuilder.java:174) > at org.apache.neethi.PolicyBuilder.getPolicy(PolicyBuilder.java:124) > at org.apache.neethi.PolicyEngine.getPolicy(PolicyEngine.java:100) > at > org.apache.ws.secpolicy11.builders.InitiatorTokenBuilder.build(InitiatorTokenBuilder.java:40) > at > org.apache.ws.secpolicy11.builders.InitiatorTokenBuilder.build(InitiatorTokenBuilder.java:34) > at > org.apache.neethi.AssertionBuilderFactoryImpl.invokeBuilder(AssertionBuilderFactoryImpl.java:138) > at > org.apache.neethi.AssertionBuilderFactoryImpl.build(AssertionBuilderFactoryImpl.java:117) > at >
[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=16071604#comment-16071604 ] Andreas Veithen commented on AXIS2-5857: Ah, axis2-jibx also depends on log4j 1.2.x, but AFAICS it only uses the logging API and doesn't attempt to configure log4j, so we could use the API adapter. > 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] [Updated] (AXIS2-5857) Log4j 1.x has reached EOL
[ https://issues.apache.org/jira/browse/AXIS2-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5857: --- Priority: Minor (was: Major) > 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] [Updated] (AXIS2-5857) Log4j 1.x has reached EOL
[ https://issues.apache.org/jira/browse/AXIS2-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5857: --- Fix Version/s: (was: 1.7.6) > 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] [Resolved] (AXIS2-5856) Wrong null checker
[
https://issues.apache.org/jira/browse/AXIS2-5856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5856.
Resolution: Fixed
Fix Version/s: 1.8.0
> 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
> Fix For: 1.8.0
>
>
> 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] [Resolved] (AXIS2-5854) The service cannot be found for the endpoint reference (EPR) http://localhost:7001/casemanagement/services/casemanagement org.apache.axis2.AxisFault
[
https://issues.apache.org/jira/browse/AXIS2-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5854.
Resolution: Invalid
Axis2 1.5.4 was released in 2010 and is no longer supported. Please only report
issues for Axis2 1.7.x.
> The service cannot be found for the endpoint reference (EPR)
> http://localhost:7001/casemanagement/services/casemanagement
> org.apache.axis2.AxisFault
>
>
> Key: AXIS2-5854
> URL: https://issues.apache.org/jira/browse/AXIS2-5854
> Project: Axis2
> Issue Type: Bug
> Components: wsdl
>Reporter: Deepak
>Priority: Blocker
> Attachments: Error.jpg
>
>
> Hi Experts,
> I am facing an issue with weblogic server while accessing a webservice.
> {noformat} 2017-06-08 12:06:40,744 ERROR [org.apache.axis2.engine.AxisEngine]
> - http://10.40.6.206:7001/casemanagement/services/casemanagement>
> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
> reference (EPR) http://10.40.6.206:7001/casemanagement/services/casemanagement
>at
> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
>at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
>at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254)
>at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
>at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
>at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:751)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
>at
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
>at
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
>at
> weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
>at
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:346)
>at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
>at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
>at
> com.xxx.tools.auth.client.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:90)
>at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
>at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3436)
>at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3402)
>at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
>at
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
>at
> weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
>at
> weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2285)
>at
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2201)
>at
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
>at
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1572)
>at
> weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)
>at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
>at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) {noformat}
> Axis version: axis2-1.5.4.jar
> Weblogic: 12.1.3
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5855) The service cannot be found for the endpoint reference (EPR) http://localhost:7001/casemanagement/services/casemanagement org.apache.axis2.AxisFault
[
https://issues.apache.org/jira/browse/AXIS2-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5855.
Resolution: Duplicate
> The service cannot be found for the endpoint reference (EPR)
> http://localhost:7001/casemanagement/services/casemanagement
> org.apache.axis2.AxisFault
>
>
> Key: AXIS2-5855
> URL: https://issues.apache.org/jira/browse/AXIS2-5855
> Project: Axis2
> Issue Type: Bug
> Components: wsdl
>Reporter: Deepak
>Priority: Blocker
> Attachments: Error.jpg
>
>
> Hi Experts,
> I am facing an issue with weblogic server while accessing a webservice.
> {noformat} 2017-06-08 12:06:40,744 ERROR [org.apache.axis2.engine.AxisEngine]
> - http://localhost:7001/casecasemanagement/services/casecasemanagement>
> org.apache.axis2.AxisFault: The service cannot be found for the endpoint
> reference (EPR) http://localhost:7001/casemanagement/services/case
>at
> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:65)
>at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
>at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254)
>at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
>at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
>at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:751)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
>at
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
>at
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
>at
> weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
>at
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:346)
>at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
>at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
>at
> com.xxx.tools.auth.client.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:90)
>at
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
>at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3436)
>at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3402)
>at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
>at
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
>at
> weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
>at
> weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2285)
>at
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2201)
>at
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
>at
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1572)
>at
> weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)
>at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
>at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) {noformat}
> Axis version: axis2-1.5.4.jar
> Weblogic: 12.1.3
> It is working with other web-servers but with weblogic its throwing this
> error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-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:all-tabpanel
]
Andreas Veithen resolved AXIS2-5853.
Resolution: Fixed
Fix Version/s: 1.7.6
> 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
> Fix For: 1.7.6
>
>
> {{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] [Resolved] (AXIS2-5851) Exception in thread "main" java.lang.NumberFormatException: For input string: "1000.0"
[
https://issues.apache.org/jira/browse/AXIS2-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5851.
Resolution: Duplicate
> Exception in thread "main" java.lang.NumberFormatException: For input string:
> "1000.0"
> --
>
> Key: AXIS2-5851
> URL: https://issues.apache.org/jira/browse/AXIS2-5851
> Project: Axis2
> Issue Type: Bug
> Components: adb, databinding
>Reporter: khalithbasha
> Labels: adb, axis2, axis2_1.7.5,
> convertToStandardDecimalNotation, databinding
>
> Exception in thread "main" java.lang.NumberFormatException: For input string:
> "1000.0"
> I am facing the same issue in version 1.7.5. Kindly help me on the same..
> public void setEMPL_RCDTypeDef(int param) {
> java.lang.String totalDigitsDecimal =
> org.apache.axis2.databinding.utils.ConverterUtil.convertToStandardDecimalNotation(
> "3").toPlainString();
> if (org.apache.axis2.databinding.utils.ConverterUtil.compare(
> param, totalDigitsDecimal) < 0) {
> this.localEMPL_RCDTypeDef = param;
> } else {
> throw new java.lang.RuntimeException(
> "Input values do not follow defined XSD restrictions");
> }
> }
--
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] [Resolved] (AXIS2-5850) could not find SecureApplicationXMLBuilder
[ https://issues.apache.org/jira/browse/AXIS2-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5850. Resolution: Not A Problem SecureApplicationXMLBuilder was provided (separately from the Axis2 release) as a workaround for AXIS2-4450. For 1.7.4 that is no longer necessary and you can use ApplicationXMLBuilder instead. > could not find SecureApplicationXMLBuilder > -- > > Key: AXIS2-5850 > URL: https://issues.apache.org/jira/browse/AXIS2-5850 > Project: Axis2 > Issue Type: Bug >Reporter: Nupur > -- 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] [Resolved] (AXIS2-5849) Axis2 is creating /tmp folders in server temp directory and never cleaning it up therefore causing high disk space usage
[ https://issues.apache.org/jira/browse/AXIS2-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5849. Resolution: Invalid Please note that this is a bug tracker, not a forum. Please address questions to java-u...@axis.apache.org. > Axis2 is creating /tmp folders in server temp directory and never cleaning it > up therefore causing high disk space usage > > > Key: AXIS2-5849 > URL: https://issues.apache.org/jira/browse/AXIS2-5849 > Project: Axis2 > Issue Type: Bug > Components: jaxws, kernel, modules >Affects Versions: 1.5.5, 1.6.2 >Reporter: Priyanka Singh > > Hi, > Axis2 is creating .tmp folders and .lck files in server's temp folder and > never cleaning it up even after JVM shutdowns resulting in duplicate .tmp > folders and .lck files which causes high disk space usage. > In AXIS2-3919 we found that the files are deployed to the temp folder each > time AXIS configuration context is created and never cleaning it up. > We want to know that what all versions are affected by this issue? In > AXIS2-3919 I found that even 1.7 is affected. SP is 1.7.4 the latest release > is also affected? > In which version are you targeting this fix and when is the plan to release > it? > Thank you! -- 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] [Resolved] (AXIS2-4880) I have patches to fix poor scalability of ADB's POJO XMLStreamReader implementation
[ https://issues.apache.org/jira/browse/AXIS2-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4880. Resolution: Incomplete > I have patches to fix poor scalability of ADB's POJO XMLStreamReader > implementation > --- > > Key: AXIS2-4880 > URL: https://issues.apache.org/jira/browse/AXIS2-4880 > Project: Axis2 > Issue Type: Improvement > Components: adb >Affects Versions: 1.5.2 > Environment: Debian Lenny (x86_64), Java 1.6.0 (Sun), NetBeans, > Tomcat 6, POJO web service deployed as .aar file. >Reporter: Dan Armstrong >Assignee: Amila Chinthaka Suriarachchi > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > First, ADB's XMLStreamReader implementation becomes much slower when many > complex types exist in the TypeTable. This causes many repeated interations > through the entire map for building the ADBNamespaceContext. I have removed > the necessity of this repeated iteration by: > 1) TypeTable generates any missing prefixes when new QName is added > 2) TypeTable maintains prefix->namespace and namespace->prefix mappings > 3) ADBNamespaceContext now checks in the following order (should be > functionally equivalent to adding all complex types from TypeTable, but > without the overhead): > a) Use any added directly to our context > b) Check TypeTable mappings (This is the key addition) > c) Check parent NamespaceContext > Second, ADBNamespaceContext is fairly heavy weight in heap space. I have > minimized the heap space by: > 1) Delayed allocation of the internal ArraySet > 2) Using new AddOneNamespaceContext implementation when one and only one > QName is added to the NamespaceContext. > In our system we currently have 407 complex types in the TypeTable and were > suffering serious slowdown. We have more types to add to this system so this > problem needed to be addressed. The results of my patches to ADB in Axis > 1.5.2 are: > Times for a series of web services calls, retrieving various lengths of > heterogeneous arrays of complex types: > Before modifications: > 751.554 sec: Warm-up > 752.395 sec: Second pass > After modifications: > 138.107 sec: Warm-up > 110.705 sec: Second pass > RMI (Just for comparison): > 16.818 sec: Warm-up > 14.059 sec: Second pass > In summary, the new code is seven times as fast for our scenario with a > higher number of complex types. Where may I send the patches or may I commit > directly to your repositories? > Thank you, > Dan Armstrong > AO Industries, Inc. -- 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] [Resolved] (AXIS2-3837) Exception extracting jars into temporary directory : java.io.FileNotFoundException: C:\Program Files\jboss-4.2.2.GA\server\serveraxis\.\tmp\deploy\tmp18123axis2-exp.war\
[ https://issues.apache.org/jira/browse/AXIS2-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-3837. Resolution: Not A Problem Closing because this appears to be a problem in old JBoss versions. > Exception extracting jars into temporary directory : > java.io.FileNotFoundException: C:\Program > Files\jboss-4.2.2.GA\server\serveraxis\.\tmp\deploy\tmp18123axis2-exp.war\WEB-INF > (Accès refusé) : switching to alternate class loading mechanism > > > Key: AXIS2-3837 > URL: https://issues.apache.org/jira/browse/AXIS2-3837 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.4 > Environment: JBOSS, Eclipse >Reporter: BREMOND > > I am testing Axis2 Web Application (axis2.war) Using Standard Binary > Distribution. > When I start JBOSS server, it deploys Axis2 war. > I have the following error : Exception extracting jars into temporary > directory. > Which jar ? > Help me > 15:02:23,218 INFO [TomcatDeployer] deploy, ctxPath=/axis2, > warUrl=.../tmp/deploy/tmp18123axis2-exp.war/ > 15:02:27,265 INFO [STDOUT] [INFO] Deploying module: addressing-1.4 - > file:/C:/Program > Files/jboss-4.2.2.GA/server/serveraxis/./tmp/deploy/tmp18123axis2-exp.war/WEB-INF/modules/addressing-1.4.mar > 15:02:27,359 INFO [STDOUT] [INFO] Deploying module: metadataExchange-1.4 - > file:/C:/Program > Files/jboss-4.2.2.GA/server/serveraxis/./tmp/deploy/tmp18123axis2-exp.war/WEB-INF/modules/mex-1.4.mar > 15:02:27,406 INFO [STDOUT] [INFO] Deploying module: ping-1.4 - > file:/C:/Program > Files/jboss-4.2.2.GA/server/serveraxis/./tmp/deploy/tmp18123axis2-exp.war/WEB-INF/modules/ping-1.4.mar > 15:02:27,453 INFO [STDOUT] [INFO] Deploying module: script-1.4 - > file:/C:/Program > Files/jboss-4.2.2.GA/server/serveraxis/./tmp/deploy/tmp18123axis2-exp.war/WEB-INF/modules/scripting-1.4.mar > 15:02:27,468 INFO [STDOUT] [INFO] Deploying module: smtpfault - > file:/C:/Program > Files/jboss-4.2.2.GA/server/serveraxis/./tmp/deploy/tmp18123axis2-exp.war/WEB-INF/modules/smtpfault.mar > 15:02:27,546 INFO [STDOUT] [INFO] Deploying module: soapmonitor-1.4 - > file:/C:/Program > Files/jboss-4.2.2.GA/server/serveraxis/./tmp/deploy/tmp18123axis2-exp.war/WEB-INF/modules/soapmonitor-1.4.mar > 15:02:27,593 INFO [STDOUT] [INFO] Deploying module: metadataExchange-1.4 - > file:/C:/Program > Files/jboss-4.2.2.GA/server/serveraxis/tmp/deploy/tmp18123axis2-exp.war/WEB-INF/lib/mex-1.4.jar > 15:02:27,625 INFO [STDOUT] [WARN] Exception extracting jars into temporary > directory : java.io.FileNotFoundException: C:\Program > Files\jboss-4.2.2.GA\server\serveraxis\.\tmp\deploy\tmp18123axis2-exp.war\WEB-INF > (Accès refusé) : switching to alternate class loading mechanism > 15:02:27,640 INFO [STDOUT] [INFO] Deploying Exception Occured with > java.io.FileNotFoundException: C:\Program > Files\jboss-4.2.2.GA\server\serveraxis\.\tmp\deploy\tmp18123axis2-exp.war\WEB-INF > (Accès refusé) > java.lang.RuntimeException: java.io.FileNotFoundException: C:\Program > Files\jboss-4.2.2.GA\server\serveraxis\.\tmp\deploy\tmp18123axis2-exp.war\WEB-INF > (Accès refusé) > at org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:869) > at > org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:917) > at > org.apache.axis2.jaxws.framework.JAXWSDeployer.deployServicesInWARClassPath(JAXWSDeployer.java:100) > at > org.apache.axis2.jaxws.framework.JAXWSDeployer.init(JAXWSDeployer.java:80) > at > org.apache.axis2.deployment.DeploymentEngine.initializeDeployers(DeploymentEngine.java:928) > at > org.apache.axis2.deployment.DeploymentEngine.setConfigContext(DeploymentEngine.java:919) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.setConfigContext(WarBasedAxisConfigurator.java:350) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:76) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:511) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:431) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) > at > org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981) > at > org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4071) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4375) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790) > at >
[jira] [Resolved] (AXIS2-4863) Using axis2-1.5.2 xmlBean databinding able to send and receive a request. But axis2 is failing when processing the response with
[ https://issues.apache.org/jira/browse/AXIS2-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4863. Resolution: Incomplete > Using axis2-1.5.2 xmlBean databinding able to send and receive a request. But > axis2 is failing when processing the response with > > > Key: AXIS2-4863 > URL: https://issues.apache.org/jira/browse/AXIS2-4863 > Project: Axis2 > Issue Type: Bug > Components: Addressing >Affects Versions: 1.5.2 > Environment: this is running a client only on widnows. The server is > developed by a different provider. >Reporter: Mack Fata > Labels: xmlbean > > I am writing a web service client application using axis2-1.5.2 with xmlBeans > databinding generated classes from WSDL. > I am able to send a request and get back a response, but AXIS2 is failing > when processing the response with the following error: > org.apache.axis2.AxisFault: Must Understand check failed for header > http://www.ebxml.org/namespaces/messageHeader : MessageHeader > at > org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:97) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:165) > at > com.sabre.usg.xmlBeans.client.SessionCreateRQServiceStub.sessionCreateRQ(SessionCreateRQServiceStub.java:203) > at > com.sabre.usg.xmlBeans.client.XMLTestClient.main(XMLTestClient.java:143) > I have captured the request and response using TCP/IP Monitor, any idea why > is this failing? > Request: > > http://schemas.xmlsoap.org/soap/envelope/;> > > xmlns="http://www.ebxml.org/namespaces/messageHeader; > xmlns:axis2ns1="http://www.ebxml.org/namespaces/messageHeader; > soapenv:mustUnderstand="1" axis2ns1:version="1.0"> > > xmlns:axis2ns2="http://www.ebxml.org/namespaces/messageHeader; > axis2ns2:type="urn:x12.org:IO5:01">99 > > > xmlns:axis2ns3="http://www.ebxml.org/namespaces/messageHeader; > axis2ns3:type="urn:x12.org:IO5:01">123123 > > > ACS_Svc_Test2009-10-28-94929 > xmlns:axis2ns4="http://www.ebxml.org/namespaces/messageHeader; > axis2ns4:type="string">Session > SessionCreateRQ > > xmlns="http://schemas.xmlsoap.org/ws/2002/12/secext; > soapenv:mustUnderstand="0"> > > xx > xx > xmlns="">AAS > AA > > > > > xmlns:ns="http://www.opentravel.org/OTA/2002/11;> > > PseudoCityCode="DFW"/> > > > > > Response: > > http://schemas.xmlsoap.org/soap/envelope/;> > > xmlns:eb="http://www.ebxml.org/namespaces/messageHeader; eb:version="1.0" > soap-env:mustUnderstand="1"> > > eb:type="urn:x12.org:IO5:01">123123 > > > eb:type="urn:x12.org:IO5:01">99 > > > ACS_Svc_Test2009-10-28-94929 > eb:type="sabreXML">Session > SessionCreateRS > > > 3fb14fcb-8912-4127-9f22-ed259c3ae2b1@32 > > 2010-10-25T13:21:39 > > >
[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=15999478#comment-15999478 ] Andreas Veithen commented on AXIS2-5846: The fix is included in the 1.7.5 release to be published this week. > Local file inclusion vulnerability in SimpleHTTPServer > -- > > Key: AXIS2-5846 > URL: https://issues.apache.org/jira/browse/AXIS2-5846 > Project: Axis2 > Issue Type: Bug > Components: transports >Affects Versions: 1.6.2, 1.7.4 >Reporter: Nupur >Assignee: Andreas Veithen > Fix For: 1.7.5 > > > 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] [Resolved] (AXIS2-5620) filling of temp folder
[ https://issues.apache.org/jira/browse/AXIS2-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5620. Resolution: Duplicate > filling of temp folder > -- > > Key: AXIS2-5620 > URL: https://issues.apache.org/jira/browse/AXIS2-5620 > Project: Axis2 > Issue Type: Bug >Reporter: Bob Storey > > Trying to find help. We have an unknown process that is generating > axis2axis2.1.6.2.jar files into our \windows\temp folder > on our server. This started happening on 11 November after a server reboot. > the folder is filling up with almost a gig of files each day. File size is > consistent at 2megs. A reboot on December 1st appeared to clear out most of > the files, but it still generates. > No changes have been made to the server from what we can tell. > Thank you for any help -- 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] [Comment Edited] (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=15997484#comment-15997484 ] Andreas Veithen edited comment on AXIS2-4947 at 5/4/17 11:15 PM: - I agree for javax.activation and javax.xml.stream because these packages are provided by the JRE. javax.ws.rs on the other hand would always be provided by a bundle and have a proper version number. Anyway, that import is effectively optional and I added resolution:=optional. was (Author: veithen): I agreed for javax.activation and javax.xml.stream because these packages are provided by the JRE. javax.ws.rs on the other hand would always be provided by a bundle and have a proper version number. Anyway, that import is effectively optional and I added resolution:=optional. > [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 > Fix For: 1.7.5 > > 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-4882) AxisBindingMessage effective policy calculation adds policies in incorrect order
[ https://issues.apache.org/jira/browse/AXIS2-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997514#comment-15997514 ] Andreas Veithen commented on AXIS2-4882: This patch is missing a unit test. > AxisBindingMessage effective policy calculation adds policies in incorrect > order > > > Key: AXIS2-4882 > URL: https://issues.apache.org/jira/browse/AXIS2-4882 > Project: Axis2 > Issue Type: Bug > Components: kernel >Affects Versions: 1.6.0 >Reporter: Peter Mullins > Attachments: AxisBindingMessage.patch > > > In the calculateEffectivePolicy method in AxisBindingMessage, > PolicyComponents are added in order from the most specific to the most > general. This means that when they are combined by iterating over the list > (e.g. for use by Rampart in RampartPolicyBuilder), service-wide policies will > always override message-level ones. This order should be reversed, so that > when the policies are processed in order, more specific policies will > override more general ones. -- 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] [Updated] (AXIS2-5150) Update WSDL2Code Plug-in documentation with JiBX binding file option
[ https://issues.apache.org/jira/browse/AXIS2-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5150: --- Affects Version/s: 1.7.0 > Update WSDL2Code Plug-in documentation with JiBX binding file option > > > Key: AXIS2-5150 > URL: https://issues.apache.org/jira/browse/AXIS2-5150 > Project: Axis2 > Issue Type: Bug > Components: documentation >Affects Versions: 1.7.0 >Reporter: Mohamed Nufail > Labels: documentation > Fix For: 1.7.1 > > Attachments: AXIS2-5150.patch, AXIS2-5150.patch > > > As described AXIS2-2673 adding JiBX support to wsdl2code plugin enables to > have a new configuration option named 'jibxBindingFile' to provide the > binding definition file. So the configuration parameter table in WSDL2Code > Plug-in documentation needs to be updated with this addition. -- 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] [Resolved] (AXIS2-5150) Update WSDL2Code Plug-in documentation with JiBX binding file option
[ https://issues.apache.org/jira/browse/AXIS2-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5150. Resolution: Fixed Fix Version/s: 1.7.1 > Update WSDL2Code Plug-in documentation with JiBX binding file option > > > Key: AXIS2-5150 > URL: https://issues.apache.org/jira/browse/AXIS2-5150 > Project: Axis2 > Issue Type: Bug > Components: documentation >Affects Versions: 1.7.0 >Reporter: Mohamed Nufail > Labels: documentation > Fix For: 1.7.1 > > Attachments: AXIS2-5150.patch, AXIS2-5150.patch > > > As described AXIS2-2673 adding JiBX support to wsdl2code plugin enables to > have a new configuration option named 'jibxBindingFile' to provide the > binding definition file. So the configuration parameter table in WSDL2Code > Plug-in documentation needs to be updated with this addition. -- 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] [Updated] (AXIS2-5150) Update WSDL2Code Plug-in documentation with JiBX binding file option
[ https://issues.apache.org/jira/browse/AXIS2-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5150: --- Description: As described AXIS2-2673 adding JiBX support to wsdl2code plugin enables to have a new configuration option named 'jibxBindingFile' to provide the binding definition file. So the configuration parameter table in WSDL2Code Plug-in documentation needs to be updated with this addition. (was: As described in https://issues.apache.org/jira/browse/AXIS2-2673 adding JiBX support to wsdl2code plugin enables to have a new configuration option named 'jibxBindingFile' to provide the binding definition file. So the configuration parameter table in WSDL2Code Plug-in documentation needs to be updated with this addition.) > Update WSDL2Code Plug-in documentation with JiBX binding file option > > > Key: AXIS2-5150 > URL: https://issues.apache.org/jira/browse/AXIS2-5150 > Project: Axis2 > Issue Type: Bug > Components: documentation >Reporter: Mohamed Nufail > Labels: documentation > Attachments: AXIS2-5150.patch, AXIS2-5150.patch > > > As described AXIS2-2673 adding JiBX support to wsdl2code plugin enables to > have a new configuration option named 'jibxBindingFile' to provide the > binding definition file. So the configuration parameter table in WSDL2Code > Plug-in documentation needs to be updated with this addition. -- 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-5150) Update WSDL2Code Plug-in documentation with JiBX binding file option
[ https://issues.apache.org/jira/browse/AXIS2-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997507#comment-15997507 ] Andreas Veithen commented on AXIS2-5150: This is actually fixed by r1727171 (r1727194 on the 1.7 branch) which changed the build to generate the mojo documentation automatically from the source code. > Update WSDL2Code Plug-in documentation with JiBX binding file option > > > Key: AXIS2-5150 > URL: https://issues.apache.org/jira/browse/AXIS2-5150 > Project: Axis2 > Issue Type: Bug > Components: documentation >Reporter: Mohamed Nufail > Labels: documentation > Attachments: AXIS2-5150.patch, AXIS2-5150.patch > > > As described in https://issues.apache.org/jira/browse/AXIS2-2673 adding JiBX > support to wsdl2code plugin enables to have a new configuration option named > 'jibxBindingFile' to provide the binding definition file. So the > configuration parameter table in WSDL2Code Plug-in documentation needs to be > updated with this addition. -- 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] [Updated] (AXIS2-4505) axis2 osgi bundle should not import javax.xml.stream 1.0.0
[ https://issues.apache.org/jira/browse/AXIS2-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4505: --- Fix Version/s: (was: 1.8.0) 1.7.5 > axis2 osgi bundle should not import javax.xml.stream 1.0.0 > -- > > Key: AXIS2-4505 > URL: https://issues.apache.org/jira/browse/AXIS2-4505 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Kristoffer Peterhänsel > Fix For: 1.7.5 > > > For some reason Axis 2 bundles require version 1.0.0 of javax.xml.stream. > This is highly annoying as usually it would be provided by the JVM and hence > be version 0.0.0, and that is also what other Apache bundles require. -- 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] [Comment Edited] (AXIS2-4505) axis2 osgi bundle should not import javax.xml.stream 1.0.0
[ https://issues.apache.org/jira/browse/AXIS2-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995792#comment-15995792 ] Andreas Veithen edited comment on AXIS2-4505 at 5/4/17 9:43 PM: This was fixed by r1748021 on the trunk and r1793903 on the 1.7 branch. was (Author: veithen): This was fixed by r1748021. > axis2 osgi bundle should not import javax.xml.stream 1.0.0 > -- > > Key: AXIS2-4505 > URL: https://issues.apache.org/jira/browse/AXIS2-4505 > Project: Axis2 > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Kristoffer Peterhänsel > Fix For: 1.7.5 > > > For some reason Axis 2 bundles require version 1.0.0 of javax.xml.stream. > This is highly annoying as usually it would be provided by the JVM and hence > be version 0.0.0, and that is also what other Apache bundles require. -- 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
