[jira] [Created] (AXIS2-5895) JAXWSCodeGenerationEngine extension is incomplete
Martin Gainty created AXIS2-5895:
Summary: 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 completed");
}
}
/**
* Merge original args.
*
* @param args
*the args
*/
private void mergeOriginalArgs(ArrayList args) {
Map allOptions = commandLineOptionParser
.getAllOptions();
List axisOptionList = new ArrayList();
List originalArgsOps = new ArrayList(
[jira] [Created] (AXIS2-5893) test.wsdl not found in ServiceClientTest::testWSDLWithImportsFromZIP
Martin Gainty created AXIS2-5893:
Summary: 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 {
out.close();
}
catch(java.io.IOException ioe) {
log.error("ServiceClientTest::testWSDLWithImportsFromZIP LINE 105 out.close()
throws IOException messsage="+ioe.getMessage()); }
}
if(stream!=null)
{
stream.flush();
stream.close();
}
if(log.isDebugEnabled())
[jira] [Created] (AXIS2-5889) jaxws-integration test-compile needs to include target/generated-test-sources
Martin Gainty created AXIS2-5889: Summary: 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 Fix For: 1.8.0 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] [Created] (AXIS2-5888) adb-tests ExtensionTest failure for wrong element
Martin Gainty created AXIS2-5888:
Summary: 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] [Created] (AXIS2-5830) Failed to execute goal com.github.veithen.phos:enforcer-maven-plugin:0.1.0:enforce (default) on project axiom-impl:
Martin Gainty created AXIS2-5830:
Summary: Failed to execute goal
com.github.veithen.phos:enforcer-maven-plugin:0.1.0:enforce (default) on
project axiom-impl:
Key: AXIS2-5830
URL: https://issues.apache.org/jira/browse/AXIS2-5830
Project: Axis2
Issue Type: Bug
Components: Integration
Affects Versions: 1.7.4
Environment: JDK 1.8
AXIOM 1.3.0
Axis 1.8
Reporter: Martin Gainty
[ERROR] Failed to execute goal
com.github.veithen.phos:enforcer-maven-plugin:0.1.0:enforce (default) on
project axiom-impl: Package cycle detected. Classes involved:
[ERROR] org.apache.axiom.om.impl.intf.AxiomAttribute ->
org.apache.axiom.core.CoreNSAwareAttribute
Here is AxiomAttribute.java:
/*
* 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.
*/
package org.apache.axiom.om.impl.mixin;
import org.apache.axiom.core.CoreModelException;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.impl.common.AxiomExceptionTranslator;
import org.apache.axiom.om.impl.common.AxiomSemantics;
import org.apache.axiom.om.impl.common.NSUtil;
import org.apache.axiom.om.impl.intf.AxiomAttribute;
import org.apache.axiom.om.impl.intf.AxiomElement;
public class AxiomAttributeSupport {
public AxiomAttributeSupport() {}
public AxiomElement omElement = null;
public AxiomElement coreGetOwnerElement() { return this.omElement; }
public AxiomElement getOwner() { return
(AxiomElement)coreGetOwnerElement(); }
public final void beforeSetLocalName() { if(this.localName!=null)
this.localName="localName"; }
public OMNamespace ns=null;
public String localName="localName";
public boolean decl=true;
public void internalSetNamespace(OMNamespace ns_param)
{
ns=org.apache.axiom.om.impl.common.NSUtil.handleNamespace(
(AxiomElement)getOwner(),
(OMNamespace)ns_param,
(boolean)true,
(boolean)decl);
}
public final void setNamespace(org.apache.axiom.om.OMNamespace namespace,
boolean decl) {
this.ns=namespace;
internalSetNamespace(org.apache.axiom.om.impl.common.NSUtil.handleNamespace((AxiomElement)getOwner(),
namespace, true, decl));
}
public final void setOMNamespace(OMNamespace omNamespace) {
this.ns=omNamespace;
internalSetNamespace(omNamespace);
}
public Object coreCharacterData = null;
public String coreGetCharacterData() { return
this.coreCharacterData.toString(); }
public final String getAttributeValue() {
return coreGetCharacterData();
}
public String value="value";
public org.apache.axiom.om.impl.common.AxiomSemantics axiomSemantics
=null;
public void coreSetCharacterData(String s,
org.apache.axiom.om.impl.common.AxiomSemantics axiomSemantics)
{
this.value =s;
this.axiomSemantics = axiomSemantics;
}
public final void setAttributeValue(String value)
{
coreSetCharacterData(value, AxiomSemantics.INSTANCE);
}
public String attributeType="ELEMENT";
public String coreGetType() { return this.attributeType; }
public String coreSetType(String s) { this.attributeType = s; return s;
}
public final String getAttributeType() {
return coreGetType();
}
public final void setAttributeType(String type) {
coreSetType(type);
}
public final void build() {
// TODO
}
}
//where does org.apache.axiom.om.impl.intf.AxiomAttribute contain
org.apache.axiom.core.CoreNSAwareAttribute?
until this plugin is fixed I will be disabling this plugin and using
maven-enforcer-plugin instead here is the plugin link:
http://maven.apache.org/enforcer/maven-enforcer-plugin/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5819) classpath issue on itest-build.xml for java tasks
Martin Gainty created AXIS2-5819: Summary: classpath issue on itest-build.xml for java tasks Key: AXIS2-5819 URL: https://issues.apache.org/jira/browse/AXIS2-5819 Project: Axis2 Issue Type: Bug Components: Integration Affects Versions: 1.7.4 Environment: JDK1 8.0_45 ANT 1.9.2 MAVEN 3.2.5 Reporter: Martin Gainty select any Running codegen RPC WSDLs - take 1 old classpath declaration threw exception but above classpath/pathelement works in ant 1.9.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5818) Axis-2.1.7.3 AddressingFinalServiceTest TC missing org/apache/http/util/Args
Martin Gainty created AXIS2-5818: Summary: Axis-2.1.7.3 AddressingFinalServiceTest TC missing org/apache/http/util/Args Key: AXIS2-5818 URL: https://issues.apache.org/jira/browse/AXIS2-5818 Project: Axis2 Issue Type: Bug Components: Integration Affects Versions: 1.7.3 Environment: JDK 1.8 MVN 3.25 Axis2-1.7.3 Reporter: Martin Gainty Priority: Minor Running org.apache.axis2.addressing.AddressingFinalServiceTest Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 48.82 sec <<< FAILURE! testUsingAddressingRequired(org.apache.axis2.addressing.AddressingFinalServiceTest) Time elapsed: 0.434 sec <<< ERROR! java.lang.NoClassDefFoundError: org/apache/http/util/Args at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.apache.http.conn.scheme.Scheme.(Scheme.java:91) at org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl.getHttpClient(HTTPSenderImpl.java:836) at org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl.sendViaPost(HTTPSenderImpl.java:200) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:121) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:403) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:234) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:431) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:399) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:150) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:533) at org.apache.axis2.addressing.AddressingFinalServiceTest.testUsingAddressingRequired(AddressingFinalServiceTest.java:273) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5817) org.apache.axis2.builder.UnknownContentBuilderTest error
[
https://issues.apache.org/jira/browse/AXIS2-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15632893#comment-15632893
]
Martin Gainty commented on AXIS2-5817:
--
NP as mime_message.txt was not included in that distro i deleted
UnknownContentBuilderTest.java and UnknownContentBuilderTest.class TC and
surefire ran to completion
> org.apache.axis2.builder.UnknownContentBuilderTest error
>
>
> Key: AXIS2-5817
> URL: https://issues.apache.org/jira/browse/AXIS2-5817
> Project: Axis2
> Issue Type: Bug
> Components: Integration
>Affects Versions: 1.5.6
> Environment: jdk 1.8
>Reporter: Martin Gainty
>Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> org.apache.axis2.builder.UnknownContentBuilderTest testNoBuilder test
> File file = getTestResourceFile("mime_message.txt");
> MIMEBuilder mimeBuilder = new MIMEBuilder();
> FileInputStream fis = new FileInputStream(file);
> ConfigurationContext configContext = null;
> try {
> String path=file.getAbsolutePath();
>
> configContext=ConfigurationContextFactory.createDefaultConfigurationContext(path);
> }
> catch(Exception excp) {
> System.out.println("UnknownContentBuilderTest::testNoBuilder LINE 81 throws
> Exception mssage="+excp.getMessage()); }
> where mime-message.txt contains:
> MIMEBoundary258DE2D105298B756D
> content-type:text/plain; charset=ISO-8859-1; format=flowed
> content-transfer-encoding:binary
> content-id:<0.15b50ef49317518...@apache.org>
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope;>
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing;>http://localhost:8070/axis2/services/MTOMService/mtomSample xmlns:x="http://example.org/mtom/data;> href="cid:1.BBFC8D48A21258EBBD@apache.org"
> xmlns:xop="http://www.w3.org/2004/08/xop/include;> href="cid:2.CB365E36E21BD6491A@apache.org"
> xmlns:xop="http://www.w3.org/2004/08/xop/include;>
> MIMEBoundary258DE2D105298B756D
> content-id:<11.bbfc8d48a21258e...@apache.org>
> content-type:text/csv;name="test.csv"
> content-transfer-encoding:binary
> saminda saminda saminda saminda saminda saminda saminda saminda saminda
> saminda saminda saminda saminda saminda saminda saminda saminda saminda
> saminda saminda
> there is no axisconfig element inside message.txt so Exception is thrown:
>
> type="org.apache.axis2.deployment.DeploymentException">org.apache.axis2.deployment.DeploymentException:
>
> The system was looking for the axisconfig element,
> but it found
> C:\Axis\axis-2.1.5\modules\integration\test-resources\mime_message.txt
> at
> org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:177)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createBasicConfigurationContext(ConfigurationContextFactory.java:427)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createDefaultConfigurationContext(ConfigurationContextFactory.java:409)
> at
> org.apache.axis2.builder.UnknownContentBuilderTest.testNoBuilder(UnknownContentBuilderTest.java:77)
> disable testNoBuilder test to stop UnknownContentBuilderTest from failing
> OR sub in axis2.xml that contains element
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5817) org.apache.axis2.builder.UnknownContentBuilderTest error
Martin Gainty created AXIS2-5817:
Summary: org.apache.axis2.builder.UnknownContentBuilderTest error
Key: AXIS2-5817
URL: https://issues.apache.org/jira/browse/AXIS2-5817
Project: Axis2
Issue Type: Bug
Components: Integration
Affects Versions: 1.5.6
Environment: jdk 1.8
Reporter: Martin Gainty
Priority: Minor
org.apache.axis2.builder.UnknownContentBuilderTest testNoBuilder test
File file = getTestResourceFile("mime_message.txt");
MIMEBuilder mimeBuilder = new MIMEBuilder();
FileInputStream fis = new FileInputStream(file);
ConfigurationContext configContext = null;
try {
String path=file.getAbsolutePath();
configContext=ConfigurationContextFactory.createDefaultConfigurationContext(path);
}
catch(Exception excp) {
System.out.println("UnknownContentBuilderTest::testNoBuilder LINE 81 throws
Exception mssage="+excp.getMessage()); }
where mime-message.txt contains:
MIMEBoundary258DE2D105298B756D
content-type:text/plain; charset=ISO-8859-1; format=flowed
content-transfer-encoding:binary
content-id:<0.15b50ef49317518...@apache.org>
http://www.w3.org/2003/05/soap-envelope;>http://schemas.xmlsoap.org/ws/2004/08/addressing;>http://localhost:8070/axis2/services/MTOMService/mtomSamplehttp://example.org/mtom/data;>http://www.w3.org/2004/08/xop/include;>http://www.w3.org/2004/08/xop/include;>
MIMEBoundary258DE2D105298B756D
content-id:<11.bbfc8d48a21258e...@apache.org>
content-type:text/csv;name="test.csv"
content-transfer-encoding:binary
saminda saminda saminda saminda saminda saminda saminda saminda saminda saminda
saminda saminda saminda saminda saminda saminda saminda saminda saminda saminda
there is no axisconfig element inside message.txt so Exception is thrown:
org.apache.axis2.deployment.DeploymentException:
The system was looking for the axisconfig element,
but it found
C:\Axis\axis-2.1.5\modules\integration\test-resources\mime_message.txt
at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:177)
at
org.apache.axis2.context.ConfigurationContextFactory.createBasicConfigurationContext(ConfigurationContextFactory.java:427)
at
org.apache.axis2.context.ConfigurationContextFactory.createDefaultConfigurationContext(ConfigurationContextFactory.java:409)
at
org.apache.axis2.builder.UnknownContentBuilderTest.testNoBuilder(UnknownContentBuilderTest.java:77)
disable testNoBuilder test to stop UnknownContentBuilderTest from failing
OR sub in axis2.xml that contains element
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5815) test-resources\SwA-enabled-axis2.xml has incorrect XML
Martin Gainty created AXIS2-5815: Summary: test-resources\SwA-enabled-axis2.xml has incorrect XML Key: AXIS2-5815 URL: https://issues.apache.org/jira/browse/AXIS2-5815 Project: Axis2 Issue Type: Bug Components: Integration Affects Versions: 1.5.6 Environment: jdk 1.8 maven 3.25 Reporter: Martin Gainty Priority: Minor integration/test-resources/SwA-enabled-axis2.xml integration/test-resources/SwA-fileCache-enabled-axis2.xml BOTH have incorrect FaultFlow declaration: 123 456 789 123 456 789 please correct end tag to -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5814) org.test.headershandler.HeadersHandlerResponse missing
Martin Gainty created AXIS2-5814: Summary: org.test.headershandler.HeadersHandlerResponse missing Key: AXIS2-5814 URL: https://issues.apache.org/jira/browse/AXIS2-5814 Project: Axis2 Issue Type: Bug Components: Integration, jaxws Affects Versions: 1.5.2 Environment: Java(TM) SE Runtime Environment (build 1.8.0_40-b26) AXIS2-1.5 Reporter: Martin Gainty Priority: Minor axis-2 jaxws-integration wont compile due to missing java class import org.test.headershandler.HeadersHandlerResponse; Please advise location of HeadersHandlerResponse.java -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS-2905) Insecure certificate validation CVE-2014-3596
[ https://issues.apache.org/jira/browse/AXIS-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15521741#comment-15521741 ] Martin Gainty commented on AXIS-2905: - doesnt compile with JDK 1.8.0_40-b26 Warning: Binary file .\javax\security\cert\X509Certificate contains javax.security.cert.X509Certificate public abstract java.security.Principal getSubjectDN(); suggest backing out patch or reverting to previous version asap > Insecure certificate validation CVE-2014-3596 > - > > Key: AXIS-2905 > URL: https://issues.apache.org/jira/browse/AXIS-2905 > Project: Axis > Issue Type: Bug >Affects Versions: 1.4 >Reporter: David Jorm > Attachments: CVE-2014-3596.patch > > > It was found that the fix for CVE-2012-5784 was incomplete. The code added to > check that the server hostname matches the domain name in the subject's CN > field was flawed. This can be exploited by a Man-in-the-middle (MITM) attack > where the attacker can spoof a valid certificate using a specially crafted > subject. > For more details, see: > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-3596 > https://access.redhat.com/solutions/1164433 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5798) AxisService.wsdl
Martin Gainty created AXIS2-5798: Summary: AxisService.wsdl https://issues.apache.org/jira/browse/AXIS2-5798 Project: Axis2 Issue Type: Bug Components: jaxws Affects Versions: 1.7.3 Environment: mvn 3.25 Axis2 1.7.3 JDK 1.8 Reporter: Martin Gainty ./target/test-resources/wsdl/imports/binding/EchoService.wsdl contains: http://tempuri.org/bindings; location="EchoBindings.wsdl" /> BUT wsdl:import EchoBindings.wsdl resolves to root (modules/kernel) instead of ./target/test-resources/wsdl/imports/binding/EchoBindings.wsdl -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5752) Building with mvn install -Dmaven.test.skip=true failes
[
https://issues.apache.org/jira/browse/AXIS2-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210561#comment-15210561
]
Martin Gainty commented on AXIS2-5752:
--
maven-antrun-pluginwhere org.apache.maven.plugin.antrun.AntRunMojo.java tasks
attribute contains this deprecation warning:
/**
* The XML for the Ant task. You can add anything you can add between
target and /target in a build.xml.
* @deprecated Use target instead
*/
@Parameter
private PlexusConfiguration tasks;
/**
* The XML for the Ant target. You can add anything you can add between
target and /target in a build.xml.
*
* @since 1.5
*/
@Parameter
private PlexusConfiguration target;
> Building with mvn install -Dmaven.test.skip=true failes
> ---
>
> Key: AXIS2-5752
> URL: https://issues.apache.org/jira/browse/AXIS2-5752
> Project: Axis2
> Issue Type: Bug
>Affects Versions: 1.7.1
> Environment: Windows 7 / SP1, mvn, JDK 1.7
>Reporter: Josef Stadelmann
> Labels: build, maven, test
>
> Just wanted to build one more time axis2 from the trunk, with
> -Dmaven.test.skip=true
> That worked well for me in the past as I started to not run all the tests as
> they seldom where running and where too often the cause for a abort of the
> build.
> Now even with -Dmaven.test.skip=true it failed. The reason is a missing file
> which is not generated if tests are skipped.
>
>
> maven-antrun-plugin
>
>
>
> run
>
> test
>
>
>
>
> classname="org.apache.ws.java2wsdl.Java2WSDL"
> classpathref="maven.test.classpath" fork="true" failonerror="true">
>
> value="${project.build.directory}/java2wsdl" />
>
>
>
> value="org.apache.axis2.description.CalculatorService" />
>
> value="[org.apache.axis2.description,http://www.example.org/calculator]; />
>
> value="http://www.example.org/calculator-service; />
>
>
>
>
>
>
>
> The file p2n.wsdl is missing as it will be not generated if
> -Dmaven.test.skip=true is selected.
> Why is that file not generated when I just intend to not have tests?
>
> Josef
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS-2913) SAXException when running webservice which is apparently random
[ https://issues.apache.org/jira/browse/AXIS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15171796#comment-15171796 ] Martin Gainty commented on AXIS-2913: - Jerry.. get a RPC test client do the same 1000 iteration test https://www.google.com/?gws_rd=ssl#q=XML-RPC+client+test if that is the case we can then use OS specific utility to open up RPC Port Configuration https://www.google.com/search?q=Confgure+RPC+ports=Confgure+RPC+ports=chrome..69i57j0l5.6712j0j7=chrome_sm=93=UTF-8#q=%22Configure+RPC+port%22 > SAXException when running webservice which is apparently random > --- > > Key: AXIS-2913 > URL: https://issues.apache.org/jira/browse/AXIS-2913 > Project: Axis > Issue Type: Bug > Components: Serialization/Deserialization >Affects Versions: 1.4 >Reporter: Jerry Lee >Priority: Critical > > Hi, we have a proxy servlet in web project which use axis 1.4 client to call > web services. In our web page, we use a javascript loop to call the servlet, > it will call the servlet infinitely until the service call failed. > If we open multiple web page the service call will failed randomly.The > frequency is about one failed call with 1000 success calls. > And we have rule out the possibility of multithreading problem by adding > concurrent code. > Also we defined our own deserializers and serializers for > ServiceContainerImpl bean > org.xml.sax.SAXException: Invalid element in > com.ibm.javart.services.ServiceContainerImpl - sapSalesPersonNumber > at > org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258) > at > org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035) > at > org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) > at > org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) > at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) > at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) > at org.apache.axis.client.Call.invoke(Call.java:2467) > at org.apache.axis.client.Call.invoke(Call.java:2366) > at org.apache.axis.client.Call.invoke(Call.java:1812) > at com.ibm.javart.services.WebProxy.invoke(WebProxy.java:199) > at com.ibm.javart.services.WebProxy.ezeInvoke(WebProxy.java:134) > at > com.ibm.javart.services.RestServiceDelegate.invokeService(RestServiceDelegate.java:455) > at > com.ibm.javart.services.RestServiceDelegate.invokeSoapService(RestServiceDelegate.java:529) > at > com.ibm.javart.services.ProxyEventHandler.soapServiceCall(ProxyEventHandler.java:401) > at > com.ibm.javart.services.ProxyEventHandler.runProxy(ProxyEventHandler.java:140) > at > com.ibm.javart.services.ProxyEventHandler.runProxy(ProxyEventHandler.java:90) > at > com.ibm.javart.services.RestServiceServlet.doHttp(RestServiceServlet.java:178) > at > com.ibm.javart.services.RestServiceServlet.doPost(RestServiceServlet.java:104) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > com.ibm.javart.util.gzip.CompressionFilter.doFilter(CompressionFilter.java:75) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at > com.googlecode.psiprobe.Tomcat70AgentValve.invoke(Tomcat70AgentValve.java:38) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:947) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200) > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at
[jira] [Created] (AXIS2-5711) commons-fileupload versions 1.0 - 1.2.2 are subject to CVE-2013-0248
Martin Gainty created AXIS2-5711: Summary: commons-fileupload versions 1.0 - 1.2.2 are subject to CVE-2013-0248 Key: AXIS2-5711 URL: https://issues.apache.org/jira/browse/AXIS2-5711 Project: Axis2 Issue Type: Bug Components: Integration Affects Versions: 1.6.2 Environment: all environments Reporter: Martin Gainty modules/parent/pom.xml requires 1.3 version of commons-fileupload !-- commons-fileupload versions 1.0 - 1.2.2 are subject to CVE-2013-0248 -- !-- commons.fileupload.version1.2/commons.fileupload.version -- commons.fileupload.version1.3/commons.fileupload.version modules/fastinfoset/pom.xml requires 1.3 commons-fileupload dependency groupIdcommons-fileupload/groupId artifactIdcommons-fileupload/artifactId version1.3/version !-- commons-fileupload versions 1.0 - 1.2.2 are subject to CVE-2013-0248 -- /dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS-2592) Generated Client WSDL is not valid
[ https://issues.apache.org/jira/browse/AXIS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276900#comment-14276900 ] Martin Gainty commented on AXIS-2592: - definition of element xs:key name=element xs:selector xpath=xs:element/ xs:field xpath=@name/ /xs:key xs:key name=attribute xs:selector xpath=xs:attribute/ xs:field xpath=@name/ /xs:key xs:key name=type xs:selector xpath=xs:complexType|xs:simpleType/ xs:field xpath=@name/ /xs:key xs:key name=group xs:selector xpath=xs:group/ xs:field xpath=@name/ /xs:key xs:key name=attributeGroup xs:selector xpath=xs:attributeGroup/ xs:field xpath=@name/ /xs:key xs:key name=notation xs:selector xpath=xs:notation/ xs:field xpath=@name/ /xs:key xs:key name=identityConstraint xs:selector xpath=.//xs:key|.//xs:unique|.//xs:keyref/ xs:field xpath=@name/ /xs:key /xs:element reference: http://www.w3.org/TR/xmlschema-1/ 1)why would any of the elements require identityConstraint? 2) wsdl:part name=getActiveVesselReturn type=tns1:string/ where xmlns:tns1=http://schemas.xmlsoap.org/soap/encoding/; Why is this specification incorrect? Please explain why XMLSpy is correct in its parsing and Axis is incorrect in its WSDL Generation Generated Client WSDL is not valid -- Key: AXIS-2592 URL: https://issues.apache.org/jira/browse/AXIS-2592 Project: Axis Issue Type: Bug Affects Versions: 1.2.1 Environment: Windows XP, Java 1.5 and Eclipse 3.2.1 Sun JavaCAPS Reporter: Raghu Kodumuri Fix For: 1.2.1 Attachments: ProjectStatistics.wsdl, ProjectStatistics1.wsdl WSDL clinet that has been generated using Axis 1.2.1 and generated wsdl can not be validated by XMP SPY or Eclipse Wsdl validator. Here are the errors: XML SPY : File C:\slbProjects\IntroSpection\ProjectStatisticsNew\ProjectStatistics.wsdl is not valid. The selector './/xs:key|.//xs:unique|.//xs:keyref' of identity constraint 'xsd:identityConstraint' must evaluate to a target node set. Error location: wsdl:definitions / wsdl:types / schema Details cvc-identity-constraint.1: The selector './/xs:key|.//xs:unique|.//xs:keyref' of identity constraint 'xsd:identityConstraint' must evaluate to a target node set. Eclipse Validator: 1. ComplexType declared in schema are not visible in wsdl part type. Actual Error:The part 'getActiveVesselReturn' has an invalid value 'string' defined for its type. Type declarations must refer to valid values defined in a schema. 2. Complains xmlns datatype are not in schema: Error: The part 'getActiveVesselReturn' has an invalid value 'string' defined for its type. Type declarations must refer to valid values defined in a schema. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (TRANSPORTS-55) Improper Resource Shutdown or Release in BaseUtils.java 246
[ https://issues.apache.org/jira/browse/TRANSPORTS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14271480#comment-14271480 ] Martin Gainty commented on TRANSPORTS-55: - 25 years ago I worked in a Lab so if Elaine Benes consumed PoppySeed roll then took a test to indicate Opiates and tested positive then this test would be registered as False Positive In software terms a False positive is registered when a result that indicates a given condition has been fulfilled, when it actually has not been fulfilled. so in your case if: 1)the JVM has a lock on the CL while another client is attempting to update the resource acquired by that CL..which is always true 2)critical sections are safe for multiple threads loading different classes generally implemented with synchronized will not allow other clients to update resources in the critical section until you exit the critical section 3)you invoked java.lang.ClassLoader's static method registerAsParallelCapable(). This registration indicates that all instances of your custom class loader are multithread safe. 4)Check that all class loader classes that this custom class loader extends also invoke the registerAsParallelCapable() method in their class initializers. Ensure that they are multithread safe for concurrent class loading. if these steps have been followed there would not be a false positive..it would be a good idea for both of us to implement a testcase which would demonstrate mitigation for this vulnerability. Jeff Williams coded this for OWASP back in 2007: https://owasp-esapi-java.googlecode.com/svn-history/r1236/branches/1.4/src/main/java/org/owasp/esapi/reference/DefaultSecurityConfiguration.java starting the container with folder location of resources which must be protected with java -Dorg.owasp.esapi.resources=C:\temp\resources -jar ContainerBootstrap.jar Does this answer your question? Martin Improper Resource Shutdown or Release in BaseUtils.java 246 --- Key: TRANSPORTS-55 URL: https://issues.apache.org/jira/browse/TRANSPORTS-55 Project: Axis2 Transports Issue Type: Bug Components: Base Affects Versions: 1.0.0 Reporter: David Camilo Espitia Manrique Labels: security Fix For: 1.0.0 Original Estimate: 24h Remaining Estimate: 24h We are currently using Axis2-transport-base 1.0.0 and the veracode analysis found a bug in this class BaseUtils.java line 246: Type: Improper Resource Shutdown or Release Description: The application fails to release (or incorrectly releases) a system resource before it is made available for re-use. This condition often occurs with resources such as database connections or file handles. Most unreleased resource issues result in general software reliability problems, but if an attacker can intentionally trigger a resource leak, it may be possible to launch a denial of service attack by depleting the resource pool. Recommendations: When a resource is created or allocated, the developer is responsible for properly releasing the resource as well as accounting for all potential paths of expiration or invalidation. Ensure that all code paths properly release resources -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (TRANSPORTS-55) Improper Resource Shutdown or Release in BaseUtils.java 246
[ https://issues.apache.org/jira/browse/TRANSPORTS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270279#comment-14270279 ] Martin Gainty commented on TRANSPORTS-55: - Parroting the cl-mt guide from Java registerAsParallelCapable() should be called after classloader is created in a static initalizer: If you have a custom class loader with a risk of deadlocking, with the Java SE 7 release, you can avoid deadlocks by following these rules: Ensure that your custom class loader is multithread safe for concurrent class loading. a. Decide upon an internal locking scheme. For example, java.lang.ClassLoader uses a locking scheme based on the requested class name. b. Remove all synchronization on the class loader object lock alone. c. Ensure that critical sections are safe for multiple threads loading different classes. In your custom class loader's static initializer, invoke java.lang.ClassLoader's static method registerAsParallelCapable(). This registration indicates that all instances of your custom class loader are multithread safe. Check that all class loader classes that this custom class loader extends also invoke the registerAsParallelCapable() method in their class initializers. Ensure that they are multithread safe for concurrent class loading. If your custom class loader overrides only findClass(String), you do not need further changes. This is the recommended mechanism to create a custom class loader. http://stackoverflow.com/questions/18640996/java-deadlock-in-classloaders http://docs.oracle.com/javase/7/docs/technotes/guides/lang/cl-mt.html do you want to implement this (so any resource acquired by CL is at least thread-safe)? Saludos Cordiales, Martín Improper Resource Shutdown or Release in BaseUtils.java 246 --- Key: TRANSPORTS-55 URL: https://issues.apache.org/jira/browse/TRANSPORTS-55 Project: Axis2 Transports Issue Type: Bug Components: Base Affects Versions: 1.0.0 Reporter: David Camilo Espitia Manrique Labels: security Fix For: 1.0.0 Original Estimate: 24h Remaining Estimate: 24h We are currently using Axis2-transport-base 1.0.0 and the veracode analysis found a bug in this class BaseUtils.java line 246: Type: Improper Resource Shutdown or Release Description: The application fails to release (or incorrectly releases) a system resource before it is made available for re-use. This condition often occurs with resources such as database connections or file handles. Most unreleased resource issues result in general software reliability problems, but if an attacker can intentionally trigger a resource leak, it may be possible to launch a denial of service attack by depleting the resource pool. Recommendations: When a resource is created or allocated, the developer is responsible for properly releasing the resource as well as accounting for all potential paths of expiration or invalidation. Ensure that all code paths properly release resources -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS-2296) Get the following exception when web service call is made by client : java.lang.NoSuchMethodException: org.apache.axis.encoding.ser.ArrayDeserializerFactory.create(java.
[
https://issues.apache.org/jira/browse/AXIS-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251778#comment-14251778
]
Martin Gainty commented on AXIS-2296:
-
ArrayDeserializerFactory donated by IBM has no such method ..calling this will
always fubar your installation
/*
* Copyright 2001-2004 The Apache Software Foundation.
*
* Licensed 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.
*/
package org.apache.axis.encoding.ser;
import javax.xml.namespace.QName;
/**
* DeserializerFactory for arrays
*
* @author Rich Scheuerle sc...@us.ibm.com
*/
public class ArrayDeserializerFactory extends BaseDeserializerFactory {
private QName componentXmlType;
public ArrayDeserializerFactory() {
super(ArrayDeserializer.class);
}
/**
* Constructor
* @param componentXmlType the desired component type for this deser
* this is the namespace from your XML
*/
public ArrayDeserializerFactory(QName componentXmlType) {
super(ArrayDeserializer.class);
this.componentXmlType = componentXmlType;
}
/**
* getDeserializerAs() is overloaded here in order to set the default
* item type on the ArrayDeserializers we create.
*
* @param mechanismType
* @return
*/
public javax.xml.rpc.encoding.Deserializer getDeserializerAs(String
mechanismType) {
ArrayDeserializer dser = (ArrayDeserializer)
super.getDeserializerAs(mechanismType);
dser.defaultItemType = componentXmlType;
return dser;
}
public void setComponentType(QName componentType) {
componentXmlType = componentType;
}
}
2.1.6 BaseDeserializerFactory has NO acommodation for ArrayDeserializerFactory
in 2.1.6+ so this wont work in Axis 2.1.6+
I would remove all Axis libraries from CLASSPATH and $TOMCAT_HOME\lib and
regenerate AxisService and client stubs
with Axis2-1.6+
OR
if you can find a backup copy of axis-1.3 then use axis-1.3 libraries
exclusively
do NOT mix Axis1.3 and Axis2-1.6 libraries in CLASSPATH or $TOMCAT_HOME/lib
Axis2-1.6 has been re-architected and will not support Axis-1.3 code so making
sure your CLASSPATH contains
ONLY axis2-1.6 would be your best solution
Nota Bene: //org.apache.axis.wsdl.toJava.JavaDeployWriter detects []
if (javaType.endsWith([])) { //end your java types with [] will elect
SimpleListDeserializerFactory
if (SchemaUtils.isListWithItemType(type.getNode())) {
serializerFactory =
org.apache.axis.encoding.ser.SimpleListSerializerFactory;
deserializerFactory =
org.apache.axis.encoding.ser.SimpleListDeserializerFactory;
} else {
serializerFactory =
org.apache.axis.encoding.ser.ArraySerializerFactory;
deserializerFactory =
org.apache.axis.encoding.ser.ArrayDeserializerFactory;
innerType = type.getComponentType();
}
Keep us apprised
Martin-
Get the following exception when web service call is made by client :
java.lang.NoSuchMethodException:
org.apache.axis.encoding.ser.ArrayDeserializerFactory.create(java.lang.Class,
javax.xml.namespace.QName)
---
Key: AXIS-2296
URL: https://issues.apache.org/jira/browse/AXIS-2296
Project: Axis
Issue Type: Bug
Components: Basic Architecture, Deployment / Registries,
Serialization/Deserialization, WSDL processing
Environment: Web service is hosted on Unix box on tomcat written in
Java
Reporter: Vinita Joshi
Priority: Critical
When the webservice called WorkflowService is called by the client the
following exception is thrown,
DEBUG: 08 Nov 2005 19:18:10,356 at
org.apache.axis.i18n.ProjectResourceBundle.handleGetObject(ProjectResourceBundle.java:72)
org.apache.axis.i18n.resource::handleGetObject(exception00)
DEBUG: 08 Nov 2005 19:18:10,359 at
org.apache.axis.encoding.ser.BaseDeserializerFactory.createFactory(BaseDeserializerFactory.java:210)
Exception:
[jira] [Commented] (AXIS-2316) Connection reset when called again and again
[
https://issues.apache.org/jira/browse/AXIS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131498#comment-14131498
]
Martin Gainty commented on AXIS-2316:
-
straight from Axis doc:
Two timeout instances exist in the transport level, Socket timeout
and Connection timeout. These can be configured either at deployment
or run time. If configuring at deployment time, the user has to add the
following lines in axis2.xml.
For Socket timeout:
parameter name=SO_TIMEOUTsome_integer_value/parameter
For Connection timeout:
parameter name=CONNECTION_TIMEOUTsome_integer_value/parameter
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);
Connection reset when called again and again
Key: AXIS-2316
URL: https://issues.apache.org/jira/browse/AXIS-2316
Project: Axis
Issue Type: Bug
Components: Basic Architecture
Affects Versions: 1.3
Environment: WIN 2000 SOLARIS 8
Reporter: Heemanshu Jain
Priority: Blocker
Hi,
I am using Apache Axis 1.3 and JDK 1.5 to consume web services from a
SOAP webserver.
I have a loop which executes every 5 seconds and makes a call to the web
service.
The code works fine for a few requests but I get this error after some
requests at regular intervals. Nearly 1 failure in 50 requests.
I have another program written in plain java code. This program is
executing with no errors. This proves that there is no problem at the server
side. (This program has hardcoded SOAP request so cannot use this plain java
code for production).
Is this a known bug. Is there any workaround for the same
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketException: Connection reset
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
Connec
tion reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPS
ender.java:583)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.bt.www.mta._2005._09.MTASoapPortStub.requestCheck(MTASoapPortStub
.java:298)
at com.bt.www.mta.types._2005._09.Main4test.main(Main4test.java:92)
{http://xml.apache.org/axis/}hostname:DSCP07364
java.net.SocketException: Connection reset
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.bt.www.mta._2005._09.MTASoapPortStub.requestCheck(MTASoapPortStub
.java:298)
at com.bt.www.mta.types._2005._09.Main4test.main(Main4test.java:92)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
[jira] [Commented] (AXIS2-5663) wsdl2java creates invalid java code with extension + choice
[
https://issues.apache.org/jira/browse/AXIS2-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081627#comment-14081627
]
Martin Gainty commented on AXIS2-5663:
--
IF the test is choice and as long as we have properties then the value is set
xsl:if test=$choice
/** Whenever a new property is set ensure all others are unset
* There can be only one choice and the last one wins
*/
private void clearAllSettingTrackers() {
xsl:for-each select=property
xsl:if test=not(@attribute)
localxsl:value-of select=@javaname/Tracker = false;
/xsl:if
/xsl:for-each
}
/xsl:if
this is a genuine bug here is the code:
org.apache.axis2.schema.template.ADBBeanTemplate.xsl:
remember that the previous criteria was
IF the test is choice and as long as we have properties then the value is set
xsl:if test=not(enumFacet) //?
//? this SHOULD be in xsl:if test=not(enumFacet) or (test=$choice))
!-- Generate a tracker only if the min occurs is zero,
which means if the user does
not bother to set that value, we do not send it --
xsl:if test=$min=0 or $choice
/* This tracker boolean wil be used to detect
whether the user called the set method
* for this attribute. It will be used to determine
whether to include this field
* in the serialized XML
*/
protected boolean xsl:value-of select=$settingTracker/ =
false ; //IF $min==null AND $choice is null dont generate
/xsl:if
/xsl:if
So the problem seems to be org.apache.axis2.schema.template.ADBBeanTemplate.xsl:
Good Catch!
wsdl2java creates invalid java code with extension + choice
---
Key: AXIS2-5663
URL: https://issues.apache.org/jira/browse/AXIS2-5663
Project: Axis2
Issue Type: Bug
Components: wsdl
Affects Versions: 1.6.2
Environment: Windows 7 SP1 64bit
axis2 1.6.2
Reporter: Daniel Johnson
Labels: wsdl2java
Attachments: example.wsdl, trimmed.xsd
When trying to generate java source for a vendor provided WSDL file (with
XSD), I got java source that would not compile because it referenced fields
which did not exist.
I ran:
{noformat}
wsdl2java -uri example.wsdl -u
ant
{noformat}
The compilation error is:
{noformat}
[javac]
c:\Users\djohnson\Documents\Intrado\WSDL\trimmed\src\com\example\namespaces\def\UpdateResponseType.java:31:
error: cannot find symbol
[javac]localInteger1Tracker = false;
[javac]^
[javac] symbol: variable localInteger1Tracker
[javac] location: class UpdateResponseType
{noformat}
(+5 more of these)
I spent this afternoon creating this reduced testcase which is attached. The
above errors are from the reduced testcase, although they are essentially
identical to the ones I got with the real WSDL.
My uneducated guess is that the generator is treating the base type's
sequence members as choices of the subtype. But I have only a basic
understanding of WSDL or XML Schemas, so I am out of my element here.
Please let me know if there is any more information that would be useful, I'd
be happy to provide it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-4427) axis sends soap messages on error in http binded services
[
https://issues.apache.org/jira/browse/AXIS2-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072730#comment-14072730
]
Martin Gainty commented on AXIS2-4427:
--
JAX-WS supports RPC or DOC-LITERAL styles in @SoapBinding
http://www.mkyong.com/webservices/jax-ws/jax-ws-hello-world-example-document-style/
if you want rest calls bound to HTTP Methods implement JAX-RS
http://www.mkyong.com/tutorials/jax-rs-tutorials
Good Luck
Martin
axis sends soap messages on error in http binded services
-
Key: AXIS2-4427
URL: https://issues.apache.org/jira/browse/AXIS2-4427
Project: Axis2
Issue Type: Bug
Affects Versions: 1.5
Environment: fedora 11 openjdk 1.6 tomcat 6
Reporter: Christoph Höger
I have the followoing POJO deployed:
@WebService(name=counterService,
targetNamespace=http://www.umpa-net.de/services/counterService;)
@BindingType(value=HTTPBinding.HTTP_BINDING)
public class Service {
@WebMethod(operationName = echoMethod)
public String echoString(@WebParam(name=stringIn)String s){
return s;
}
@WebMethod(operationName = greeting)
public String sendGreeting() {
return Hello from a webservice, Mareike!;
}
}
Invoking:
http://192.168.2.106:8080/axis2/services/ServiceService/echoMethod?inString=Hallo
works as expected, but the error case
http://192.168.2.106:8080/axis2/services/ServiceService/echoMethod
returns:
soapenv:Reason
soapenv:Text xml:lang=en-USjava.lang.NullPointerException/soapenv:Text
/soapenv:Reason
Why do I get SOAP stuff on http binded services? Shouldn't that be plain text?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5660) AXIS 2 Doc correction
Martin Gainty created AXIS2-5660:
Summary: AXIS 2 Doc correction
Key: AXIS2-5660
URL: https://issues.apache.org/jira/browse/AXIS2-5660
Project: Axis2
Issue Type: Bug
Components: documentation
Affects Versions: 1.6.2
Reporter: Martin Gainty
Handlers and Chains can be defined to have 'per-access', 'per-request', or
'singleton' scope although the registry currently only distinguishes between
these by constructing non-singleton scope objects when requested and
constructing singleton scope objects once and holding on to them for use on
subsequent creation requests.
There are NO singleton implementations of Handlers ..here is proof:
public class FactoryRegistry {
private static volatile MapClass, Object table;
private static Object lockbox = new Object();
private static final Log log = LogFactory.getLog(FactoryRegistry.class);
static {
try {
init();
} catch (Throwable t){
log.error(t.getMessage(), t);
}
}
private static final void init() {
// An unsynchronized Map is used to ensure that gets are fast.
table = new HashMapClass, Object(64, .5f);
table.put(HandlerInvokerFactory.class, new HandlerInvokerFactoryImpl());
}
//later on when you access HandlerInvokerFactory you get the
//SAME HandlerInvokerFactoryImpl that you instantated:
/**
* Get the factory. This may be called frequently.
* @param intface of the Factory
* @return Object that is the factory implementation for the intface
*/
public static Object getFactory(Class intface) {
Map m = table;
return m.get(intface);
}
//so the RegistryFactory exhibits Singleton like behaviour
//but what happens when I create a HandlerInvokeFactory?
package org.apache.axis2.jaxws.handler.factory.impl;
/**
* This is the default implementation of the HandlerInvokerFactory,
* and it will be registered with the FactoryRegistry.
*/
public class HandlerInvokerFactoryImpl implements HandlerInvokerFactory {
public HandlerInvoker createHandlerInvoker(MessageContext messageContext) {
return new HandlerInvokerImpl();
}
}
If this is NOT singleton which clearly it is not then you need to
correct this documentation asap
http://axis.apache.org/axis/java/architecture-guide.html
16 July 2014
Martin Gainty
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5654) [JAVA2WSDL][WS-I compliance] [SOAP1.2] wsdl fails ws-i compliance for soap 1.2 binding
[ https://issues.apache.org/jira/browse/AXIS2-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030840#comment-14030840 ] Martin Gainty commented on AXIS2-5654: -- There is no basic profile 1.2 compliance XSD specified as of this date (at least none i could find) http://ws-i.org/profiles/basic-profiles/1.2/bp12.xsd produces 404 but a non-normative version of schema is displayed here: xs:schema targetNamespace='http://ws-i.org/profiles/basic-profile/1.2/' xmlns:xs='http://www.w3.org/2001/XMLSchema' elementFormDefault='qualified' blockDefault='#all' xs:element name='Conformant' xs:complexType xs:sequence xs:any namespace='##other' processContents='lax' minOccurs='0' maxOccurs='unbounded'/ /xs:sequence xs:anyAttribute namespace='##other' processContents='lax' / /xs:complexType /xs:element /xs:schema http://ws-i.org/profiles/basicprofile-1.2-2010-11-09.html#schm How does AXIS 2 not conform to this format? Martin [JAVA2WSDL][WS-I compliance] [SOAP1.2] wsdl fails ws-i compliance for soap 1.2 binding -- Key: AXIS2-5654 URL: https://issues.apache.org/jira/browse/AXIS2-5654 Project: Axis2 Issue Type: Bug Components: jaxws, wsdl Affects Versions: 1.6.2 Reporter: Waruna Perera Labels: compliance, java2wsdl, soap12, ws-i Created java web service and got the wsdl using java2wsdl and checked the ws-i compliance for soap binding 1.2. Compliance check failed. Checked the compliance using soapui 5.00 and it passes for soap binding 1.1. I got the asserts BP2402 and BP2032. For more on ws-i asserts http://www.ws-i.org/Testing/Tools/2005/01/BP11_TAD_1-1.htm -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS-2899) adb-codegen REGEX expression failure on ^
Martin Gainty created AXIS-2899: --- Summary: adb-codegen REGEX expression failure on ^ Key: AXIS-2899 URL: https://issues.apache.org/jira/browse/AXIS-2899 Project: Axis Issue Type: Task Components: Basic Architecture Environment: AXIS 2-1.6.2 Reporter: Martin Gainty Priority: Minor Fix For: 1.5 AXIS2 v1.6.2 adb-codegen does not interpret xsd:pattern value=^(NA|UN).*/ change to: xsd:pattern value=(AN|NU).*/ fixes this assumes NOT NA and NOT UN must be changed to what specifically you are seeking For Reg Ex matching of [^(NA|UN)] does not currently work -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3828) Unable to compile code generated from WSDL
[ https://issues.apache.org/jira/browse/AXIS2-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861551#comment-13861551 ] Martin Gainty commented on AXIS2-3828: -- consider http://www.w3.org/TR/2003/WD-wsdl12-20030303/#Definitions_targetnamespace_attribute example from SOAP-1.2 spec ?xml version=1.0 encoding=UTF-8? definitions name=TicketAgent targetNamespace=http://airline.wsdl/ticketagent/; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:tns=http://airline.wsdl/ticketagent/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsd1=http://airline/; import location=TicketAgent.xsd namespace=http://airline// message name=listFlightsRequest part name=depart type=xsd:dateTime/ part name=origin type=xsd:string/ !-- string is of type http://www.w3.org/2001/XMLSchema -- part name=destination type=xsd:string/ !-- string is of type http://www.w3.org/2001/XMLSchema -- /message message name=listFlightsResponse part name=result type=xsd1:ArrayOfString/ !--ArrayOfString is custom element ArrayOfString defined by xsd TicketAgent.xsd -- /message !-- unless otherwise mapped you need to allow soap 1.2 types to map to Java elements (integer,string,date) -- !--did you contact the indian consultant that created this definition to inquire which SOAP version he is using ? -- http://www.webservicex.net/WS/contact.aspx i...@webservicex.net Unable to compile code generated from WSDL -- Key: AXIS2-3828 URL: https://issues.apache.org/jira/browse/AXIS2-3828 Project: Axis2 Issue Type: Bug Components: codegen Affects Versions: 1.4 Environment: Linux Ubuntu, Java 6 Reporter: Jason Spangler Attempting to generate code for the WSDL at : http://www.webservicex.net/stockquote.asmx?WSDL Generate code through ANT command using ADB data binding Code generates, however does not compile, The Compiler gives the following error: /net/webservicex/www/StockQuoteStub.java:34: incompatible types found : java.lang.String required: net.webservicex.www.String -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5618) Unable to engage rampart at client side when using it as a classpath resource
[
https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829971#comment-13829971
]
Martin Gainty commented on AXIS2-5618:
--
build..package..and deploy routines are implemented by Maven pom.xm and are
thus version/classifier specific
If you show us the axiom dependency from the pom.xml in error we can correct
and refactor your error..Here is mine as an example:
rampart pom.xml :
properties
axis2.version1.7.0-SNAPSHOT/axis2.version
axiom.version1.2.15-SNAPSHOT/axiom.version !-- here is axiom --
wss4j.version1.6.4/wss4j.version
opensaml.version2.5.1-1/opensaml.version
bcprov.jdk15.version140/bcprov.jdk15.version
!-- distribution properties --
dist.dirrampart-${project.version}/dist.dir
failIfNoTestsfalse/failIfNoTests
jacoco.version0.6.1.201212231917/jacoco.version
/properties
!-- Since Rampart depends on DOOM, but axiom-dom is not a transitive
dependency, we need to manage the Axiom version. --
dependency
groupIdorg.apache.ws.commons.axiom/groupId
artifactIdaxiom-api/artifactId
version${axiom.version}/version
/dependency
Many Thanks for identifying this bug Robert (and Brian)
Martin--
Unable to engage rampart at client side when using it as a classpath resource
-
Key: AXIS2-5618
URL: https://issues.apache.org/jira/browse/AXIS2-5618
Project: Axis2
Issue Type: Bug
Components: client-api
Affects Versions: 1.5.2
Environment: Mac OS, Java 1.6, Liferay portal
Reporter: Robert Hall
I have a bug in which I cannot access rampart from the classpath. I'm using
Axis2 for client webservices in a deployment environment, I can't access a
repository/modules folder with the rampart.mar file as I can when running a
test client from the command line. I've tried placing the rampart file
directly on the classpath and in a modules folder on the classpath.
I try and engage rampart with
contextWSStub._getServiceClient()..engageModule(new QName(rampart));
but to no avail, at run time I get org.apache.axis2.AxisFault: Unable to
engage module : rampart
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5618) Unable to engage rampart at client side when using it as a classpath resource
[ https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829580#comment-13829580 ] Martin Gainty commented on AXIS2-5618: -- 'standard location for axis2 modules' is /WEB-INF/modules' $CATALINA_HOME/webapps/axis2/WEB-INF/modules 11/23/2011 07:07 PM 285,705 rampart-1.4.mar 04/12/2010 03:58 PM 150,044 rampart-policy.mar 01/08/2010 04:54 PM 147,638 rampart-SNAPSHOT.mar 04/12/2010 02:49 PM 100,239 rampart-trust-SNAPSHOT.mar engagement of rampart module programatically as Brian suggested: client = new ServiceClient(cfgCntxt, null); //stuff client.engageModule(rampart); Let us know both situations work for your OSX environment: I dont have OSX here ..brian can you test? thanks, Martin- Unable to engage rampart at client side when using it as a classpath resource - Key: AXIS2-5618 URL: https://issues.apache.org/jira/browse/AXIS2-5618 Project: Axis2 Issue Type: Bug Components: client-api Affects Versions: 1.5.2 Environment: Mac OS, Java 1.6, Liferay portal Reporter: Robert Hall I have a bug in which I cannot access rampart from the classpath. I'm using Axis2 for client webservices in a deployment environment, I can't access a repository/modules folder with the rampart.mar file as I can when running a test client from the command line. I've tried placing the rampart file directly on the classpath and in a modules folder on the classpath. I try and engage rampart with contextWSStub._getServiceClient()..engageModule(new QName(rampart)); but to no avail, at run time I get org.apache.axis2.AxisFault: Unable to engage module : rampart -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5585) java.lang.Invocation Target error in eclipse-codegen-wizard-1.6.2
[
https://issues.apache.org/jira/browse/AXIS2-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809156#comment-13809156
]
Martin Gainty commented on AXIS2-5585:
--
One possible reason is null returned by getContainer()
try {
getContainer().run(false, true, op);
} catch (InvocationTargetException e1) {
throw new RuntimeException(e1);
}
Wizard.java:
public IWizardContainer getContainer() {
return container;
}
-IWizardContainer is not implemented by
org.apache.axis2.tool.codegen.eclipse.CodeGenWizard
and should be
-reference a constructed class which already implements IWizardContainer such
as WizardPropertyPage
http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.4.2/org.eclipse.ui/workbench/3.4.2/org/eclipse/ui/preferences/WizardPropertyPage.java
java.lang.Invocation Target error in eclipse-codegen-wizard-1.6.2
-
Key: AXIS2-5585
URL: https://issues.apache.org/jira/browse/AXIS2-5585
Project: Axis2
Issue Type: Bug
Environment: -Windows 7
-JDK 1.6.xx
-eclipse Android Developer Tools Build: v21.1.0-569685
-axis2 V. 1.6.2
-axis2-eclipse-codegen-wizard-1.6.2
-axis2-eclipse-service-archiver-wizard-1.6.2
Reporter: kan_susan
Original Estimate: 720h
Remaining Estimate: 720h
Developing xml Using Apache Axis2 Eclipse Plugins
produces at the end of Generate WSDL from java source file the ERROR
message: ...java.lang.reflect.Invocation Target exception
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5607) FVDCodeBaseImpl cannot be cast to CodeBase
[ https://issues.apache.org/jira/browse/AXIS2-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13773456#comment-13773456 ] Martin Gainty commented on AXIS2-5607: -- so we can debug in the same location of the *.idl place this service definition in NameOfService.xml where NameOfService is the actual name of the service service name=NameOfService descriptionDescriptionGoesHere/description parameter name=idlFileNameOfService.idl/parameter parameter name=interfaceNameexample::calculator/parameter !-- get this from corba admin -- !-- get the URL below from the corba admin -- parameter name=namingServiceUrlcorbaloc::localhost:900/NameService/parameter !-- name of object to obtain ..get this from corba admin -- parameter name=objectNamecalculator/parameter /service please display contents of the following files: idl service.xml FVDCodeBaseImpl cannot be cast to CodeBase -- Key: AXIS2-5607 URL: https://issues.apache.org/jira/browse/AXIS2-5607 Project: Axis2 Issue Type: Bug Components: corba Affects Versions: 1.6.2 Environment: Java 7 Reporter: Jürgen Weber Priority: Minor I tried the Exposing CORBA Services as Web Services - Introduction to the Axis2 CORBA Module sample from http://wso2.com/library/2807/ using Yoko 1.3 There seems to be an incompatibility between Yoko 1.3 and the Java 1.7 Orb, the client shows the stack trace below. I configured the corba module to use the sun orb, too, then the sample works: parameter name=orbClasscom.sun.corba.se.impl.orb.ORBImpl/parameter parameter name=orbSingletonClasscom.sun.corba.se.impl.orb.ORBSingleton/parameter Exception in thread main org.apache.axis2.AxisFault: com.sun.corba.se.impl.io.FVDCodeBaseImpl cannot be cast to org.omg.SendingContext.CodeBase at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165) at test.MycorbaserverStub.concat(MycorbaserverStub.java:209) at test.Client.main(Client.java:18) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)
[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661152#comment-13661152 ] Martin Gainty commented on AXIS2-5379: -- 17 May 2013 Update I ran Svens testcase and came up with this error in the logs java.lang.NoSuchMethodError: org.apache.axis2.engine.AxisEngine.init(Lorg/apache/axis2/context/ConfigurationContext;)V at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135) what this means is that when the transport RESTUtil passes to AxisEngine a constructor with org.apache.axis2.context.ConfigurationContext parameter is expected Options 1)rollback to Axis2-1.4 2)file JIRA Martin Gainty The third URL parameter can not be processed (REST web service with WSDL 2.0) - Key: AXIS2-5379 URL: https://issues.apache.org/jira/browse/AXIS2-5379 Project: Axis2 Issue Type: Bug Components: wsdl Affects Versions: 1.6.2 Reporter: Sven Strohschein Priority: Blocker Attachments: Hellorequest.java, Helloresponse.java, hello-rest-modified.wsdl, hello-rest.wsdl, helloWebServiceREST.aar, HelloWebServiceREST.java, RESTSample_1.0.0.aar, services.xml, wsdl2code-result-wsdl2.0.zip, wsdl2code-result.zip I have developed a simple hello world REST web service with WSDL 2.0 and Axis2. There are three URL parameters defined, but the third URL parameter can not be processed (ADBException regarding unexpected element). The first two parameters are processed correctly. I could not get an answer via the axis2 mailing list regarding this problem ( http://mail-archives.apache.org/mod_mbox/axis-java-user/201207.mbox/%3C500F0ADF.1050108%40gmx.de%3E ), could not find any examples, tutorials or documentation for a REST web service with WSDL 2.0 and more than two parameters. The full example code, wsdl, etc. is attached to this issue. URL calls http://localhost:8080/services/helloWebServiceREST/getHello?input=test - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2 - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2third=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement second) http://localhost:8080/services/helloWebServiceREST/getHello?input=testthird=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement input) Request element xsd:element name=hellorequest xsd:complexType xsd:sequence xsd:element minOccurs=0 name=input nillable=true type=xsd:string/ xsd:element minOccurs=0 name=second nillable=true type=xsd:string/ xsd:element minOccurs=0 name=third nillable=true type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5574) RESTUTIL hardcoded call to 1.4 AxisEngine
Martin Gainty created AXIS2-5574: Summary: RESTUTIL hardcoded call to 1.4 AxisEngine Key: AXIS2-5574 URL: https://issues.apache.org/jira/browse/AXIS2-5574 Project: Axis2 Issue Type: Bug Components: transports Reporter: Martin Gainty -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5574) RESTUTIL hardcoded call to 1.4 AxisEngine
[ https://issues.apache.org/jira/browse/AXIS2-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661157#comment-13661157 ] Martin Gainty commented on AXIS2-5574: -- java.lang.NoSuchMethodError: org.apache.axis2.engine.AxisEngine.init(Lorg/apache/axis2/context/ConfigurationContext;)V at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135) Problem RESTUTIL.java contains hardcoded call to Axis-1.4 AxisEngine(ConfigurationContext) Suggested workaround Code org.apache.axis2.transport.http.util.RESTUtil to instantiate AxisEngine by using reflection rather than hardcoded new AxisEngine(ConfigurationContext) Martin- RESTUTIL hardcoded call to 1.4 AxisEngine - Key: AXIS2-5574 URL: https://issues.apache.org/jira/browse/AXIS2-5574 Project: Axis2 Issue Type: Bug Components: transports Reporter: Martin Gainty -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)
[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658996#comment-13658996 ] Martin Gainty commented on AXIS2-5379: -- please attach HelloWebServiceRESTSkeletonInterface.java Martin The third URL parameter can not be processed (REST web service with WSDL 2.0) - Key: AXIS2-5379 URL: https://issues.apache.org/jira/browse/AXIS2-5379 Project: Axis2 Issue Type: Bug Components: wsdl Affects Versions: 1.6.2 Reporter: Sven Strohschein Priority: Blocker Attachments: Hellorequest.java, Helloresponse.java, hello-rest-modified.wsdl, hello-rest.wsdl, helloWebServiceREST.aar, HelloWebServiceREST.java, RESTSample_1.0.0.aar, services.xml I have developed a simple hello world REST web service with WSDL 2.0 and Axis2. There are three URL parameters defined, but the third URL parameter can not be processed (ADBException regarding unexpected element). The first two parameters are processed correctly. I could not get an answer via the axis2 mailing list regarding this problem ( http://mail-archives.apache.org/mod_mbox/axis-java-user/201207.mbox/%3C500F0ADF.1050108%40gmx.de%3E ), could not find any examples, tutorials or documentation for a REST web service with WSDL 2.0 and more than two parameters. The full example code, wsdl, etc. is attached to this issue. URL calls http://localhost:8080/services/helloWebServiceREST/getHello?input=test - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2 - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2third=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement second) http://localhost:8080/services/helloWebServiceREST/getHello?input=testthird=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement input) Request element xsd:element name=hellorequest xsd:complexType xsd:sequence xsd:element minOccurs=0 name=input nillable=true type=xsd:string/ xsd:element minOccurs=0 name=second nillable=true type=xsd:string/ xsd:element minOccurs=0 name=third nillable=true type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)
[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659080#comment-13659080 ] Martin Gainty commented on AXIS2-5379: -- need de.hello.webservice.rest.HelloWebServiceRESTMessageReceiverInOut .java Error: org.apache.axis2.deployment.DeploymentException: A ClassNotFoundException error occurred in loading the message receiver de.hello.webservice.rest.HelloWebServiceRESTMessageReceiverInOut Martin The third URL parameter can not be processed (REST web service with WSDL 2.0) - Key: AXIS2-5379 URL: https://issues.apache.org/jira/browse/AXIS2-5379 Project: Axis2 Issue Type: Bug Components: wsdl Affects Versions: 1.6.2 Reporter: Sven Strohschein Priority: Blocker Attachments: Hellorequest.java, Helloresponse.java, hello-rest-modified.wsdl, hello-rest.wsdl, helloWebServiceREST.aar, HelloWebServiceREST.java, RESTSample_1.0.0.aar, services.xml I have developed a simple hello world REST web service with WSDL 2.0 and Axis2. There are three URL parameters defined, but the third URL parameter can not be processed (ADBException regarding unexpected element). The first two parameters are processed correctly. I could not get an answer via the axis2 mailing list regarding this problem ( http://mail-archives.apache.org/mod_mbox/axis-java-user/201207.mbox/%3C500F0ADF.1050108%40gmx.de%3E ), could not find any examples, tutorials or documentation for a REST web service with WSDL 2.0 and more than two parameters. The full example code, wsdl, etc. is attached to this issue. URL calls http://localhost:8080/services/helloWebServiceREST/getHello?input=test - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2 - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2third=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement second) http://localhost:8080/services/helloWebServiceREST/getHello?input=testthird=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement input) Request element xsd:element name=hellorequest xsd:complexType xsd:sequence xsd:element minOccurs=0 name=input nillable=true type=xsd:string/ xsd:element minOccurs=0 name=second nillable=true type=xsd:string/ xsd:element minOccurs=0 name=third nillable=true type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)
[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655683#comment-13655683 ] Martin Gainty commented on AXIS2-5379: -- Sven please attach the following generated java files hello_ws_rest.Hellorequest.java hello_ws_rest.Helloresponse.java Martin The third URL parameter can not be processed (REST web service with WSDL 2.0) - Key: AXIS2-5379 URL: https://issues.apache.org/jira/browse/AXIS2-5379 Project: Axis2 Issue Type: Bug Components: wsdl Affects Versions: 1.6.2 Reporter: Sven Strohschein Priority: Blocker Attachments: hello-rest-modified.wsdl, hello-rest.wsdl, helloWebServiceREST.aar, HelloWebServiceREST.java, RESTSample_1.0.0.aar, services.xml I have developed a simple hello world REST web service with WSDL 2.0 and Axis2. There are three URL parameters defined, but the third URL parameter can not be processed (ADBException regarding unexpected element). The first two parameters are processed correctly. I could not get an answer via the axis2 mailing list regarding this problem ( http://mail-archives.apache.org/mod_mbox/axis-java-user/201207.mbox/%3C500F0ADF.1050108%40gmx.de%3E ), could not find any examples, tutorials or documentation for a REST web service with WSDL 2.0 and more than two parameters. The full example code, wsdl, etc. is attached to this issue. URL calls http://localhost:8080/services/helloWebServiceREST/getHello?input=test - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2 - working http://localhost:8080/services/helloWebServiceREST/getHello?input=testsecond=test2third=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement second) http://localhost:8080/services/helloWebServiceREST/getHello?input=testthird=test3 - not working (org.apache.axis2.databinding.ADBException: Unexpected subelement input) Request element xsd:element name=hellorequest xsd:complexType xsd:sequence xsd:element minOccurs=0 name=input nillable=true type=xsd:string/ xsd:element minOccurs=0 name=second nillable=true type=xsd:string/ xsd:element minOccurs=0 name=third nillable=true type=xsd:string/ /xsd:sequence /xsd:complexType /xsd:element -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5518) adb-codegen: ADBBeanTemplate.xsl generates erroneous code resulting in javac error: 'else' without 'if'
[
https://issues.apache.org/jira/browse/AXIS2-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647415#comment-13647415
]
Martin Gainty commented on AXIS2-5518:
--
public static java.lang.Object getTypeObject(java.lang.String
namespaceURI,
java.lang.String
typeName,
javax.xml.stream.XMLStreamReader reader) throws java.lang.Exception{
xsl:for-each select=type
if (
xsl:value-of select=@nsuri/.equals(namespaceURI)
amp;amp;
xsl:value-of select=@shortname/.equals(typeName)){
xsl:choose
xsl:when test=$helperMode
return xsl:value-of
select=@classname/Helper.INSTANCE.parse(reader);
/xsl:when
xsl:otherwise
return xsl:value-of
select=@classname/.Factory.parse(reader);
/xsl:otherwise
/xsl:choose
}
/xsl:for-each
throw new org.apache.axis2.databinding.ADBException(Unsupported
type + namespaceURI + + typeName);
}
a mismatch between opening
(
and closing
}
https://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBBeanTemplate.xsl
Martin-
adb-codegen: ADBBeanTemplate.xsl generates erroneous code resulting in javac
error: 'else' without 'if'
---
Key: AXIS2-5518
URL: https://issues.apache.org/jira/browse/AXIS2-5518
Project: Axis2
Issue Type: Bug
Components: adb
Affects Versions: 1.5.1
Environment: Various Windows and Java 6 JDKs have produced this error
Reporter: William Walsh
Priority: Minor
It appears that the code in ADBBeanTemplate.xsl at line 2837 generates the
beginning of a try block whose end and subsequent catch block, generated at
line 3552, fall after the else generated at line 2819.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5511) Missing close call on FileInputStream
[
https://issues.apache.org/jira/browse/AXIS2-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635877#comment-13635877
]
Martin Gainty commented on AXIS2-5511:
--
Erik
org.apache.axis2.util
public class XMLPrettyPrinter
{
public static void prettify(OMElement wsdlElement, OutputStream out) throws
Exception
{
ByteArrayOutputStream baos = new ByteArrayOutputStream();
wsdlElement.serialize(baos);
Source stylesheetSource = new StreamSource(new
ByteArrayInputStream(prettyPrintStylesheet.getBytes()));
Source xmlSource = new StreamSource(new
ByteArrayInputStream(baos.toByteArray()));
TransformerFactory tf = TransformerFactory.newInstance();
Templates templates = tf.newTemplates(stylesheetSource);
Transformer transformer = templates.newTransformer();
transformer.transform(xmlSource, new StreamResult(out));
}
...
}
bra fånga erik
Martin
Missing close call on FileInputStream
-
Key: AXIS2-5511
URL: https://issues.apache.org/jira/browse/AXIS2-5511
Project: Axis2
Issue Type: Bug
Components: kernel
Affects Versions: 1.6.2
Reporter: Erik Vikström
Priority: Trivial
The prettify(File) method within org.apache.axis2.util.XMLPrettyPrinter
creates a FileInputStream but does not close it explicitly. Hence XML files
are locked for a while after this feature is being used; the stream is closed
implicitly when the FileInputStream instance is garbage collected, but you
never now when in time this happens.
Since this class is used when running the code-generator, which we are using
frequently within our application, this results in that we cannot tidy up
files after this task has completed.
Current workaround for us was to implement a custom Emitter and avoid running
the XML pretty printing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3618) WSDL2Java produces code that causes javac to fail with code to large
[
https://issues.apache.org/jira/browse/AXIS2-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624244#comment-13624244
]
Martin Gainty commented on AXIS2-3618:
--
This is not the fault of Axis but the fault of Class.getMethod failure to
interrogate code size=64K
but there is a workaround available:
XSL does blind substitution ..the solution is to extend fromOM to output a
Collection ( as seen here )
Original:
java.lang.Object object = fromOM(
_returnEnv.getBody().getFirstElement() ,
xsl:value-of
select=$outputtype/.class,
getEnvelopeNamespaces(_returnEnv));
New:
Collection collection_of_object=fromOM_Collection
_returnEnv.getBody().getFirstElement() ,
xsl:value-of select=$outputtype/.class,
getEnvelopeNamespaces(_returnEnv));
!-- Class.getMethod would need the new Class so we must change messageClass
from
java.lang.reflect.Method m = exceptionClass.getMethod(setFaultMessage,
new java.lang.Class[]{messageClass});
--
while (collection_of_object.iterator().hasNext())
{
Object object=collection_of_object.iterator().next().
Class messageClass =object.getClass();
java.lang.reflect.Method m = exceptionClass.getMethod(setFaultMessage,
new java.lang.Class[]{messageClass});
!-- assume fromOM outputs objects
object
/object
/objects
--
xsl:for-each select=objects/object
!-- IF output/param[@location='body']/param) drives each record to be unique
then we can retain outputparamcount as our counter
otherwise we could need another counter to make sure each xsl:when
test is unique for each
object
--
xsl:when test=$outputparamcount=1 return get
xsl:value-of select=$outputparamshorttype/
xsl:value-of select=$outputparampartname/((xsl:value-of
select=$outputtype/)object);
/xsl:when
xsl:when test=$outputparamcount=2 return get
xsl:value-of select=$outputparamshorttype/
xsl:value-of select=$outputparampartname/((xsl:value-of
select=$outputtype/)object);
/xsl:when
/xsl:for-each
} !-- end when --
Personally I would prefer to twiddle Class.getMethod but thats part of the JDK
so the only solution
is to have fromOM create multiple classes (with identical method names) e.g.
class Object1Class { public void method1, public void method2... };
class Object2Class { public void method1, public void method2...};
Everyone uses toOM and fromOM to generate their XML and then to transform XML
to code
so these methods need to be left as is
ToOM_Collection and fromOM_Collection is the only solution that would work
Martin.. 5 April 2013
WSDL2Java produces code that causes javac to fail with code to large
--
Key: AXIS2-3618
URL: https://issues.apache.org/jira/browse/AXIS2-3618
Project: Axis2
Issue Type: Bug
Components: codegen
Affects Versions: 1.3
Environment: We have encountered this problem both on linux using jdk
1.6 and on Windows using jdk 1.5.
Reporter: Peter Canning
Priority: Critical
Attachments: Axis2Patch, vimService.wsdl, vim.wsdl
When generating stubs from a large WSDL document using either the ADB or
XMLBeans databindings, the generated code causes javac to fail with the
following error
[javac]
/exit26/home/pcanning/visdk_clients/2.5/axis2-1.3/axis_stubs/src/com/vmware/vim/VimServiceStub.java:3090:
code too large
[javac] private void populateFaults() {
[javac] ^
FYI: In order to successfully run the Axis2-1.3 stub generator, I had to
modify axis2.sh to add -Xmx512M to increase the maximum heap size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5507) deprecated enableRESTInAxis2MainServlet should be removed from axis2.xml examples
Martin Gainty created AXIS2-5507: Summary: deprecated enableRESTInAxis2MainServlet should be removed from axis2.xml examples Key: AXIS2-5507 URL: https://issues.apache.org/jira/browse/AXIS2-5507 Project: Axis2 Issue Type: Bug Components: codegen Affects Versions: 1.6.2 Environment: All environments that Support Axis2 1.6.2 Reporter: Martin Gainty Priority: Minor enableRESTInAxis2MainServlet is a deprecated parameter that should be removed from all axis2.xml examples -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS-2886) xs:date not serialized/deserialized correctly
[
https://issues.apache.org/jira/browse/AXIS-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13544026#comment-13544026
]
Martin Gainty commented on AXIS-2886:
-
namespace prefix must be registered to http://www.w3.org/2001/XMLSchema
java.lang.String namespacePrefix =
registerPrefix(xmlWriter,http://www.w3.org/2001/XMLSchema;);
if ((namespacePrefix != null)
(namespacePrefix.trim().length() 0)){
writeAttribute(xsi,http://www.w3.org/2001/XMLSchema-instance,type;,
namespacePrefix+:date,
xmlWriter);
} else {
writeAttribute(xsi,http://www.w3.org/2001/XMLSchema-instance,type;,
date,
xmlWriter);
}
in this case namespace prefix xs is assigned to the url
http://www.w3.org/2001/XMLSchema
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
so this declaration should resolve correctly
xs:complexType name=date
xs:simpleContent
xs:extension base=xs:date
xs:attributeGroup ref=tns:commonAttributes /
/xs:extension
/xs:simpleContent
/xs:complexType
xs:date not serialized/deserialized correctly
--
Key: AXIS-2886
URL: https://issues.apache.org/jira/browse/AXIS-2886
Project: Axis
Issue Type: Bug
Components: Serialization/Deserialization
Affects Versions: 1.4
Reporter: Mike
I am using Axis 1.4 for a web-service client application. all the classes and
stubs have been generated through wsdl2java .
While consuming a web service , we are getting the below exception.
java.lang.NumberFormatException: Invalid date
at
org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:180)
Axis is throwing this excpeption specifically for xsd:date type , where as
xsd:dateTime type it is working .
I have gone through the previous links in Jira forum on the same issue
https://issues.apache.org/jira/browse/AXIS-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863365#action_12863365
Can you please help on the issue . Do i have to use Axis2 , to avoid this
issue , or i can continue using Axis 1.4 with some bug fix .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5431) No Header in response
Martin Gainty created AXIS2-5431: Summary: No Header in response Key: AXIS2-5431 URL: https://issues.apache.org/jira/browse/AXIS2-5431 Project: Axis2 Issue Type: Bug Components: kernel Affects Versions: 1.6.2 Reporter: Martin Gainty -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5431) No Header in response
[
https://issues.apache.org/jira/browse/AXIS2-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13467675#comment-13467675
]
Martin Gainty commented on AXIS2-5431:
--
if the SOAPHeaders were never populated in Service Client in the first place
(then the headers ArrayList wont contain MUST_UNDERSTAND or any other attribute)
here in ServiceClient
public void sendRobust(QName operation, OMElement elem) throws AxisFault {
MessageContext mc = new MessageContext();
fillSOAPEnvelope(mc, elem);
//at this point headers should be filled with SOAPHeaderBlock
OperationClient mepClient = createClient(operation);
mepClient.addMessageContext(mc);
mepClient.execute(true);
}
//which calls fillSOAPEnveloper with the aforementioned MessageContext and the
xmlPayload
private void fillSOAPEnvelope(MessageContext messageContext, OMElement
xmlPayload)
throws AxisFault {
messageContext.setServiceContext(serviceContext);
SOAPFactory soapFactory = getSOAPFactory();
SOAPEnvelope envelope = soapFactory.getDefaultEnvelope();
if (xmlPayload != null) {
envelope.getBody().addChild(xmlPayload);
}
addHeadersToEnvelope(envelope);
messageContext.setEnvelope(envelope);
}
//which calls addHeadersToEnvelope with the envelope (previously constructed
from SOAPFactory)
public void addHeadersToEnvelope(SOAPEnvelope envelope) {
if (headers != null) {
SOAPHeader soapHeader = envelope.getHeader();
for (Object header : headers) {
soapHeader.addChild((OMElement)header);
}
}
}
/ /where do the headers come from..they are added with addHeader(OMElement) or
addHeader(SOAPHeaderBlock) ..note the difference!
/**
* Add an arbitrary XML element as a header to be sent with outgoing
messages.
* @param header header to be sent (non-codenull/code)
*/
public void addHeader(OMElement header) {
/ /at this point the attributes of MUST_UNDERSTAND_PROPERTY are lost
if (headers == null) {
headers = new ArrayListOMElement();
}
headers.add(header);
}
/**
* Add SOAP Header to be sent with outgoing messages.
* @param header header to be sent (non-codenull/code)
*/
public void addHeader(SOAPHeaderBlock header) {
if (headers == null) {
headers = new ArrayListOMElement();
/ /wrong...we cannot use an ArrayListOMElement to contain
ArrayListSOAPHeaderBlock
}
/ / MUST_UNDERSTAND_PROPERTY is lost ..there is no way to retrieve from headers
array
headers.add(header);
}
noting the difference of OMElement and SOAPHeaderBlock
public interface SOAPHeaderBlock extends OMSourcedElement {
/**
* A SOAPHeaderBlock may be represented as an unexpanded OMSourcedElement.
* In such cases, the underlying OMDataSource may have a property that
contains
* the value of the ROLE/ACTOR, RELAY or MUST_UNDERSTAND setting.
*/
public String ROLE_PROPERTY = org.apache.axiom.soap.SOAPHeader.ROLE;
public String RELAY_PROPERTY = org.apache.axiom.soap.SOAPHeader.RELAY;
public String MUST_UNDERSTAND_PROPERTY =
org.apache.axiom.soap.SOAPHeader.MUST_UNDERSTAND;
...
}
so the downcast of SOAPHeaderBlock to OMElement to fit into
ArrayListOMElement loses MUST_UNDERSTAND_PROPERTY
the ArrayListOMElement needs to be ArrayListSOAPHeaderBlock
this is not good and needs to be rectified ASAP
No Header in response
-
Key: AXIS2-5431
URL: https://issues.apache.org/jira/browse/AXIS2-5431
Project: Axis2
Issue Type: Bug
Components: kernel
Affects Versions: 1.6.2
Reporter: Martin Gainty
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5424) OutofMemory
[ https://issues.apache.org/jira/browse/AXIS2-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461416#comment-13461416 ] Martin Gainty commented on AXIS2-5424: -- echo $JAVA_OPTS -Xms1024m -Xmx1024m adbmvn -e -X package [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 4:18.507s [INFO] Finished at: Sun Sep 23 09:48:00 EDT 2012 [INFO] Final Memory: 12M/102M [INFO] from $AXIS2_HOME\modules\adb echo $JAVA_OPTS mvn -e -X package if there are no errors then the culprit is most likely JDeveloper Martin OutofMemory --- Key: AXIS2-5424 URL: https://issues.apache.org/jira/browse/AXIS2-5424 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.6.2 Environment: Windows and unix operator. using Jdeveloper 10.1.3 as an IDE Reporter: Sudha Mathew Priority: Critical Labels: newbie I am getting Exception in thread main java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2760) at java.util.Arrays.copyOf(Arrays.java:2734) at java.util.ArrayList.ensureCapacity(ArrayList.java:167) at java.util.ArrayList.add(ArrayList.java:351) at com.westernunion.www.schema.xrsi.AgentMiscInfo$Factory.parse(AgentMiscInfo.java:3531) at com.westernunion.www.schema.xrsi.SignonReply$Factory.parse(SignonReply.java:1600) at com.westernunion.www.schema.xrsi.SignonReplyE$Factory.parse(SignonReplyE.java:316) at amgitd.wu.ws.SignOn_Service_H2HStub.fromOM(SignOn_Service_H2HStub.java:542) at amgitd.wu.ws.SignOn_Service_H2HStub.signOn(SignOn_Service_H2HStub.java:205) at utils.WService.signOn(WService.java:158) at utils.WService.callSignOn(WService.java:182) at utils.WService.init(WService.java:82) at utils.WService.main(WService.java:368) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5080) The combination of rampart and jaxb databinding leads to an UnsupportedOperationException when attempting to sign a message response.
[
https://issues.apache.org/jira/browse/AXIS2-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057244#comment-13057244
]
Martin Gainty commented on AXIS2-5080:
--
/* (non-Javadoc)
* @see
org.apache.axiom.om.OMFactory#createOMElement(org.apache.axiom.om.OMDataSource,
java.lang.String, org.apache.axiom.om.OMNamespace)
*/
public OMSourcedElement createOMElement(OMDataSource source, String
localName, OMNamespace ns) {
throw new UnsupportedOperationException(Not supported for DOM);
}
1.2.11 Axiom
org.apache.axiom.om.impl.dom.factory.OMDOMFactory createOMElement methods are
stubbed out with UnsupportedMethodException
real world customers are implementing this module so can we correct this asap?
The combination of rampart and jaxb databinding leads to an
UnsupportedOperationException when attempting to sign a message response.
-
Key: AXIS2-5080
URL: https://issues.apache.org/jira/browse/AXIS2-5080
Project: Axis2
Issue Type: Bug
Affects Versions: 1.5.5, 1.6.0
Environment: axis2 1.5.5 and 1.6, axiom 1.2.11, rampart 1.5.1 and 1.6.
Reporter: Brett Okken
The problem appears to be in the way that jaxb is converted to axiom does not
work with DOM.
Caused by: java.lang.UnsupportedOperationException: Not supported for DOM
at
org.apache.axiom.om.impl.dom.factory.OMDOMFactory.createOMElement(OMDOMFactory.java:194)
at
org.apache.axis2.datasource.jaxb.JAXBCustomBuilder.create(JAXBCustomBuilder.java:91)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.createWithCustomBuilder(StAXOMBuilder.java:344)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:221)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)
at org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:447)
at
org.apache.axiom.om.impl.dom.ParentNode.getChildNodes(ParentNode.java:168)
at
org.apache.ws.security.util.WSSecurityUtil.findChildElement(WSSecurityUtil.java:596)
at
org.apache.ws.security.util.WSSecurityUtil.findWsseSecurityHeaderBlock(WSSecurityUtil.java:717)
at
org.apache.ws.security.message.WSSecHeader.insertSecurityHeader(WSSecHeader.java:145)
at
org.apache.rampart.RampartMessageData.init(RampartMessageData.java:379)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61)
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
at org.apache.axis2.engine.Phase.invoke(Phase.java:318)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:419)
at
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:196)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] Created: (AXIS-2841) ADBXMLStreamReaderTest.java has faulty test for testComplexObjectArrayScenarioWithNulls
ADBXMLStreamReaderTest.java has faulty test for
testComplexObjectArrayScenarioWithNulls
---
Key: AXIS-2841
URL: https://issues.apache.org/jira/browse/AXIS-2841
Project: Axis
Issue Type: Bug
Components: Basic Architecture
Affects Versions: 1.3
Environment: cd /modules/ADB
mvn -e -X package
and watch the fireworks
Reporter: Martin Gainty
Priority: Minor
Fix For: 1.3
/** complex array scenario with nulls in between */
public void testComplexObjectArrayScenarioWithNulls()
{
System.out.println(*testComplexObjectArrayScenarioWithNulls**);
try
{
String expectedXML =
ns1:TestComplexStringArrayScenario
xmlns:ns1=\http://testComplexStringArrayScenario.org\; +
AdditionalDependent +
NameFooTwo/Name +
Age25/Age +
SexMale/Sex +
/AdditionalDependent +
AdditionalDependent +
NameFooTwo/Name +
Age25/Age +
SexMale/Sex +
/AdditionalDependent +
AdditionalDependent +
NameFooTwo/Name +
Age25/Age +
SexMale/Sex +
/AdditionalDependent +
AdditionalDependent xsi:nil=\true\
xmlns:xsi=\http://www.w3.org/2001/XMLSchema-instance\; +
/AdditionalDependent +
BarSome More Text/Bar +
/ns1:TestComplexStringArrayScenario;
System.out.println(testComplexObjectArrayScenarioWithNulls
expectedXML=+expectedXML);
ArrayList propertyList = new ArrayList();
System.out.println(before ADBBean[] adbBeans = new
ADBBean[4]);
ADBBean[] adbBeans = new ADBBean[4];
System.out.println(adbBeans=+adbBeans);
for (int i = 0; i 4; i++)
{
System.out.println(before adbBeans[i] = new
DummyADBBean());
adbBeans[i] = new DummyADBBean();
System.out.println(adbBeans[i]=+adbBeans[i]);
}
adbBeans[3] = null;
System.out.println(before for (int i = 0; i
adbBeans.length; i++) );
for (int i = 0; i adbBeans.length; i++)
{
QName qname1=new QName(AdditionalDependent);
System.out.println(before propertyList.add(new
QName(AdditionalDependent where qname1=+qname1);
//!!This is the change to add the adbBean to
propertyList
propertyList.add(qname1);
System.out.println(propertyList after add of
qname1=+propertyList);
propertyList.add(adbBeans[i]);
System.out.println(propertyList after add of
adbBeans[i]=+adbBeans[i]);
}
propertyList.add(Bar);
System.out.println(propertyList after add(Bar)=+propertyList);
propertyList.add(Some More Text);
System.out.println(propertyList after add(Some More
Text)=+propertyList);
QName qname1=new QName(http://testComplexStringArrayScenario.org;,
TestComplexStringArrayScenario,ns1);
System.out.println(qname1=+qname1);
Object[] objects=propertyList.toArray();
System.out.println(objects=+objects);
System.out.println(before XMLStreamReader pullParser = new
ADBXMLStreamReaderImpl(new QName();
XMLStreamReader pullParser = new ADBXMLStreamReaderImpl(
qname1,
objects, null);
System.out.println(beforeString actualXML =
getStringXML(pullParser) where pullParser=+pullParser);
String actualXML = getStringXML(pullParser);
System.out.println(testComplexObjectArrayScenarioWithNulls before
assertXMLEqual(newDocument(expectedXML), newDocument(actualXML))
expectedXML=+expectedXML);
System.out.println( actualXML=+actualXML);
assertXMLEqual(newDocument(expectedXML), newDocument(actualXML));
}
catch (ParserConfigurationException e)
{
System.out.println(ParserConfigurationException Error has occurred
+ e.getMessage());
}
catch (SAXException e)
{
System.out.println(SAXException Error has occurred +
e.getMessage());
}
[jira] Commented: (AXIS2-4903) ScriptModule logs the error AxisConfiguration getRepository returns null, cannot deploy scripts
[
https://issues.apache.org/jira/browse/AXIS2-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12965216#action_12965216
]
Martin Gainty commented on AXIS2-4903:
--
Herr Mueller
in maven the repository location defaults to $USER_HOME/.m2/repository
does this help?
Martin--
ScriptModule logs the error AxisConfiguration getRepository returns null,
cannot deploy scripts
-
Key: AXIS2-4903
URL: https://issues.apache.org/jira/browse/AXIS2-4903
Project: Axis2
Issue Type: Bug
Components: deployment
Affects Versions: 1.6, 1.5.4, 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4.1, nightly
Environment: Debian 5.0.7, Tomcat 5.5.26
Reporter: Zsolt Müller
Original Estimate: 4h
Remaining Estimate: 4h
Conditions for the error to occur:
- use of the scripting module (ie. add axis2-scripting-*.mar to your
modules/modules.list)
- use of the axis2.xml.url web.xml parameter or packaging of the webapp
into a WAR/EAR
The problem is that during the initialization of the scripting module (ie.
the call to org.apache.axis2.scripting.ScriptModule.init()) it checks for the
repository in the axisconfiguration to be not null.
The relevant code is:
AxisConfiguration axisConfig = configContext.getAxisConfiguration();
if (axisConfig.getRepository() == null) {
log.error(AxisConfiguration getRepository returns null, cannot deploy
scripts);
} else {
... // scripting module initialization
}
If ConfigurationContext.getAxisConfiguration().getRepository() returns null,
then the scripting module logs an error and the module is not initialized.
Now the problem causing this to happen is in
org.apache.axis2.deployment.DeploymentEngine.loadRepositoryFromURL().
The exact callstack will look like this (without line numbers, because I
don't want to get version-specific):
- DeploymentEngine.loadRepositoryFromURL(URL repoURL)
- WarBasedAxisConfigurator.getAxisConfiguration()
- ConfigurationContextFactory.createConfigurationContext(AxisConfigurator
axisConfigurator)
- AxisServlet.initConfigContext(ServletConfig config)
- AxisServlet.init(ServletConfig config)
If you take a look at WarBasedAxisConfigurator.getAxisConfiguration(), you'll
see that depeding on the configuration it executes one of the following to
load the repository:
- DeploymentEngine.loadRepository(String repoDir)
- DeploymentEngine.loadRepositoryFromURL(URL repoURL)
- DeploymentEngine.loadFromClassPath()
In case of loadRepository(String repoDir) there's a call to
axisConfig.setRepository(axisRepo.toURL()) which sets the repository
reference in the axis configuration.
In case of loadRepositoryFromURL(URL repoURL) there's no such call, which
results in ScriptModule.init() in the error message I described earlier.
The fix is easy: in
org.apache.axis2.deployment.DeploymentEngine.loadRepositoryFromURL(URL
repoURL) put a axisConfig.setRepository(repoURL) call before the
axisConfig.validateSystemPredefinedPhases() call.
As for DeploymentEngine.loadFromClassPath(), I don't know how to set the
repository URL.
Any idea? Or any other way to use the scripting module without an axis2.xml?
My guess is that ScriptModule should be modified to handle the case, when
repository is loaded from CLASSPATH. Ie. it should try to pick up the
scriptServicesDirectory from the CLASSPATH as well.
Currently it's hard-coded to look for the scriptServicesDirectory within a
filesystem entry pointed to by a File object.
P.S.: this bug is present in v1.4.1, v1.5.3 and in SVN trunk (at the moment
of writing). I guess this has been around from the beginning.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
