[jira] Commented: (AXIS2-810) Axis2 1.0 server remove nillable attributes
[ http://issues.apache.org/jira/browse/AXIS2-810?page=comments#action_12417809 ] Sébastien Arod commented on AXIS2-810: -- This seems to be a XmlSchema bug : see http://issues.apache.org/jira/browse/WSCOMMONS-48?watch=true > Axis2 1.0 server remove nillable attributes > --- > > Key: AXIS2-810 > URL: http://issues.apache.org/jira/browse/AXIS2-810 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: wsdl > Versions: 1.0 > Environment: Widows XP > JDK 1.5.0_06 > apache-tomcat-5.5.12 > Axis2 1.0 webapp > Reporter: Sébastien Arod > Priority: Critical > Attachments: WSCity.wsdl, WSCity_modified.wsdl > > When I deploy a web service with a specified WSDL in the Axis2 webapp the xsd > nillable attributes are removed from WSDL by Axis2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-676) An exception is thrown while getting WSDL for a deployed service
[ http://issues.apache.org/jira/browse/AXIS2-676?page=all ] Sébastien Arod updated AXIS2-676: - Attachment: AxisService2OM_patch.txt The code used to generate wsdl from schema assume default encoding is UTF8 (AxisOMService.java line 160) : XMLStreamReader xmlReader = StAXUtils .createXMLStreamReader(new ByteArrayInputStream(schemaString.getBytes())); Indeed String.getBytes() uses default JVM encoding (ISO-8859-1 in my case) and StAXUtils.createXMLStreamReader(InputStream) use UTF-8 as default encoding It seems to me that as we read from a string a reader is more convenient : XMLStreamReader xmlReader = StAXUtils.createXMLStreamReader(new StringReader(schemaString)); A patch is attached > An exception is thrown while getting WSDL for a deployed service > > > Key: AXIS2-676 > URL: http://issues.apache.org/jira/browse/AXIS2-676 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Versions: 1.0 > Environment: Widows XP > JDK 1.5.0_06 > apache-tomcat-5.5.12 > Axis2 1.0 webapp > Reporter: Sébastien Arod > Assignee: Deepal Jayasinghe > Priority: Critical > Attachments: AxisService2OM_patch.txt, MyService.wsdl > > I deployed a service in the Axis2 webapp. > The WSDL (UTF-8 encoded) in the aar contains accents (e.g. word "prénom") in > the XSD element annotations. > When I try to get WSDL from deployed service (MyService?wsdl) an Exception is > thrown : > javax.servlet.ServletException: com.ctc.wstx.exc.WstxIOException: Invalid > UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: > org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: > Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) > org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:111) > javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > cause mère > org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 > middle byte 0x6e (at char #1999, byte #-1); nested exception is: > org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: > Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) > org.apache.axis2.description.AxisService.getWSDL(AxisService.java:558) > org.apache.axis2.description.AxisService.printWSDL(AxisService.java:533) > > org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:144) > > org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:89) > org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:109) > javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > The WSDL was created with JAXP/DOM : Here is the java code to write DOM > document to file > Transformer xformer = TransformerFactory.newInstance().newTransformer(); > xformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8"); //$NON-NLS-1$ > OutputStream os = new FileOutputStream(getWSDLFile()); > Writer writer = new OutputStreamWriter(os, "UTF8"); //$NON-NLS-1$ > xformer.transform(new DOMSource(mDocument), new StreamResult(writer)); > os.close(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-676) An exception is thrown while getting WSDL for a deployed service
[ http://issues.apache.org/jira/browse/AXIS2-676?page=comments#action_12417990 ] Sébastien Arod commented on AXIS2-676: -- Yes this patch solves my problem > An exception is thrown while getting WSDL for a deployed service > > > Key: AXIS2-676 > URL: http://issues.apache.org/jira/browse/AXIS2-676 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Versions: 1.0 > Environment: Widows XP > JDK 1.5.0_06 > apache-tomcat-5.5.12 > Axis2 1.0 webapp > Reporter: Sébastien Arod > Assignee: Deepal Jayasinghe > Priority: Critical > Attachments: AxisService2OM_patch.txt, MyService.wsdl > > I deployed a service in the Axis2 webapp. > The WSDL (UTF-8 encoded) in the aar contains accents (e.g. word "prénom") in > the XSD element annotations. > When I try to get WSDL from deployed service (MyService?wsdl) an Exception is > thrown : > javax.servlet.ServletException: com.ctc.wstx.exc.WstxIOException: Invalid > UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: > org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: > Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) > org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:111) > javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > cause mère > org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 > middle byte 0x6e (at char #1999, byte #-1); nested exception is: > org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: > Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) > org.apache.axis2.description.AxisService.getWSDL(AxisService.java:558) > org.apache.axis2.description.AxisService.printWSDL(AxisService.java:533) > > org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:144) > > org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:89) > org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:109) > javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > The WSDL was created with JAXP/DOM : Here is the java code to write DOM > document to file > Transformer xformer = TransformerFactory.newInstance().newTransformer(); > xformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8"); //$NON-NLS-1$ > OutputStream os = new FileOutputStream(getWSDLFile()); > Writer writer = new OutputStreamWriter(os, "UTF8"); //$NON-NLS-1$ > xformer.transform(new DOMSource(mDocument), new StreamResult(writer)); > os.close(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-810) Axis2 1.0 server remove nillable attributes
[ http://issues.apache.org/jira/browse/AXIS2-810?page=comments#action_12420866 ] Sébastien Arod commented on AXIS2-810: -- The bug is now fixed in XmlSchema SVN > Axis2 1.0 server remove nillable attributes > --- > > Key: AXIS2-810 > URL: http://issues.apache.org/jira/browse/AXIS2-810 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: wsdl > Versions: 1.0 > Environment: Widows XP > JDK 1.5.0_06 > apache-tomcat-5.5.12 > Axis2 1.0 webapp > Reporter: Sébastien Arod > Priority: Critical > Attachments: WSCity.wsdl, WSCity_modified.wsdl > > When I deploy a web service with a specified WSDL in the Axis2 webapp the xsd > nillable attributes are removed from WSDL by Axis2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS-2523) WSDL wrong code generation using xs:union
WSDL wrong code generation using xs:union
-
Key: AXIS-2523
URL: http://issues.apache.org/jira/browse/AXIS-2523
Project: Apache Axis
Issue Type: Bug
Components: WSDL processing
Affects Versions: 1.4
Environment: Windows XP, Java 1.4.2_05, Axis 1.4
Reporter: Victor Méndez
Hi, we've found something strange using wsdl2java in AXIS 1.4 which was not
happening on 1.3:
Given next xsd example:
wsdl2Java generates next clases:
- CommonErrorCodeEnumMPE.java:...it's OK
- SendRefErrorCodeEnum.java:.Compilation errors: The class
SendRefErrorCodeEnum has a "value" String attribute but its accessors have a
CommonErrorCodeEnumMPE type
- SendRefErrorCodeEnumNull.java: .What's the meaning of this?
The source of these classes is:
/**
* CommonErrorCodeEnumMPE.java
*
* This file was auto-generated from WSDL
* by the Apache Axis 1.4 Apr 22, 2006 (06:55:48 PDT) WSDL2Java emitter.
*/
package es.mobipay.xsd;
public class CommonErrorCodeEnumMPE implements java.io.Serializable {
private java.lang.String _value_;
private static java.util.HashMap _table_ = new java.util.HashMap();
// Constructor
protected CommonErrorCodeEnumMPE(java.lang.String value) {
_value_ = value;
_table_.put(_value_,this);
}
public static final java.lang.String _value1 = "E-UNKNOWN";
public static final java.lang.String _value2 = "E-COM-UNKNOWN";
public static final java.lang.String _value3 = "E-BADREQUEST";
public static final java.lang.String _value4 = "E-NOSERVICE";
public static final java.lang.String _value5 = "E-BADMATCH";
public static final java.lang.String _value6 = "E-NOMATCH";
public static final java.lang.String _value7 = "E-NOPREVTRX";
public static final java.lang.String _value8 = "E-TIMEOUT";
public static final java.lang.String _value9 = "E-NOMPI";
public static final java.lang.String _value10 = "E-MBLOCK";
public static final java.lang.String _value11 = "E-MSIMBLOCK";
public static final CommonErrorCodeEnumMPE value1 = new
CommonErrorCodeEnumMPE(_value1);
public static final CommonErrorCodeEnumMPE value2 = new
CommonErrorCodeEnumMPE(_value2);
public static final CommonErrorCodeEnumMPE value3 = new
CommonErrorCodeEnumMPE(_value3);
public static final CommonErrorCodeEnumMPE value4 = new
CommonErrorCodeEnumMPE(_value4);
public static final CommonErrorCodeEnumMPE value5 = new
CommonErrorCodeEnumMPE(_value5);
public static final CommonErrorCodeEnumMPE value6 = new
CommonErrorCodeEnumMPE(_value6);
public static final CommonErrorCodeEnumMPE value7 = new
CommonErrorCodeEnumMPE(_value7);
public static final CommonErrorCodeEnumMPE value8 = new
CommonErrorCodeEnumMPE(_value8);
public static final CommonErrorCodeEnumMPE value9 = new
CommonErrorCodeEnumMPE(_value9);
public static final CommonErrorCodeEnumMPE value10 = new
CommonErrorCodeEnumMPE(_value10);
public static final CommonErrorCodeEnumMPE value11 = new
CommonErrorCodeEnumMPE(_value11);
public java.lang.String getValue() { return _value_;}
public static CommonErrorCodeEnumMPE fromValue(java.lang.String value)
throws java.lang.IllegalArgumentException {
CommonErrorCodeEnumMPE enumeration = (CommonErrorCodeEnumMPE)
_table_.get(value);
if (enumeration==null) throw new java.lang.IllegalArgumentException();
return enumeration;
}
public static CommonErrorCodeEnumMPE fromString(java.lang.String value)
throws java.lang.IllegalArgumentException {
return fromValue(value);
}
public boolean equals(java.lang.Object obj) {return (obj == this);}
public int hashCode() { return toString().hashCode();}
public java.lang.String toString() { return _value_;}
public java.lang.Object readResolve() throws java.io.ObjectStreamException
{ return fromValue(_value_);}
public static org.apache.axis.encoding.Serializer getSerializer(
java.lang.String mechType,
java.lang.Class _javaType,
javax.xml
[jira] Commented: (AXIS-2523) WSDL wrong code generation using xs:union
[
http://issues.apache.org/jira/browse/AXIS-2523?page=comments#action_12421108 ]
Enrique Fernández commented on AXIS-2523:
-
It happens in 1.3 as well
> WSDL wrong code generation using xs:union
> -
>
> Key: AXIS-2523
> URL: http://issues.apache.org/jira/browse/AXIS-2523
> Project: Apache Axis
> Issue Type: Bug
> Components: WSDL processing
>Affects Versions: 1.4
> Environment: Windows XP, Java 1.4.2_05, Axis 1.4
>Reporter: Victor Méndez
>
> Hi, we've found something strange using wsdl2java in AXIS 1.4 which was not
> happening on 1.3:
> Given next xsd example:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>value="E-SEN-MERNOAVAI"/>
>value="E-SEN-POSNOAVAI"/>
>
>value="E-SEN-INVAADDATA"/>
>
>
>
>
> wsdl2Java generates next clases:
> - CommonErrorCodeEnumMPE.java:...it's OK
> - SendRefErrorCodeEnum.java:.Compilation errors: The class
> SendRefErrorCodeEnum has a "value" String attribute but its accessors have a
> CommonErrorCodeEnumMPE type
> - SendRefErrorCodeEnumNull.java: .What's the meaning of this?
> The source of these classes is:
> /**
> * CommonErrorCodeEnumMPE.java
> *
> * This file was auto-generated from WSDL
> * by the Apache Axis 1.4 Apr 22, 2006 (06:55:48 PDT) WSDL2Java emitter.
> */
> package es.mobipay.xsd;
> public class CommonErrorCodeEnumMPE implements java.io.Serializable {
> private java.lang.String _value_;
> private static java.util.HashMap _table_ = new java.util.HashMap();
> // Constructor
> protected CommonErrorCodeEnumMPE(java.lang.String value) {
> _value_ = value;
> _table_.put(_value_,this);
> }
> public static final java.lang.String _value1 = "E-UNKNOWN";
> public static final java.lang.String _value2 = "E-COM-UNKNOWN";
> public static final java.lang.String _value3 = "E-BADREQUEST";
> public static final java.lang.String _value4 = "E-NOSERVICE";
> public static final java.lang.String _value5 = "E-BADMATCH";
> public static final java.lang.String _value6 = "E-NOMATCH";
> public static final java.lang.String _value7 = "E-NOPREVTRX";
> public static final java.lang.String _value8 = "E-TIMEOUT";
> public static final java.lang.String _value9 = "E-NOMPI";
> public static final java.lang.String _value10 = "E-MBLOCK";
> public static final java.lang.String _value11 = "E-MSIMBLOCK";
> public static final CommonErrorCodeEnumMPE value1 = new
> CommonErrorCodeEnumMPE(_value1);
> public static final CommonErrorCodeEnumMPE value2 = new
> CommonErrorCodeEnumMPE(_value2);
> public static final CommonErrorCodeEnumMPE value3 = new
> CommonErrorCodeEnumMPE(_value3);
> public static final CommonErrorCodeEnumMPE value4 = new
> CommonErrorCodeEnumMPE(_value4);
> public static final CommonErrorCodeEnumMPE value5 = new
> CommonErrorCodeEnumMPE(_value5);
> public static final CommonErrorCodeEnumMPE value6 = new
> CommonErrorCodeEnumMPE(_value6);
> public static final CommonErrorCodeEnumMPE value7 = new
> CommonErrorCodeEnumMPE(_value7);
> public static final CommonErrorCodeEnumMPE value8 = new
> CommonErrorCodeEnumMPE(_value8);
> public static final CommonErrorCodeEnumMPE value9 = new
> CommonErrorCodeEnumMPE(_value9);
> public static final CommonErrorCodeEnumMPE value10 = new
> CommonErrorCodeEnumMPE(_value10);
> public static final CommonErrorCodeEnumMPE value11 = new
> CommonErrorCodeEnumMPE(_value11);
> public java.lang.String getValue() { return _value_;}
> public static CommonErrorCodeEnumMPE fromValue(java.lang.String value)
> throws java.lang.IllegalArgumentException {
> CommonErrorCodeEnumMPE enumeration = (CommonErrorCodeEnumMPE)
> _table_.g
[jira] Commented: (AXIS2-802) Possible header formation bug
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12421813 ]
Matthias Göttler commented on AXIS2-802:
Maybe not really fitting to the situation explained in the original
description, but we experienced the named exception
("org.apache.axis2.AxisFault: SOAPEnvelope must contain a body element which is
either first or second child element of the SOAPEnvelope.") when using an Axis2
host with JMeter as a client.
The solution was that JMeter as a default set the "Content-Type" for the
SOAP-Request-Header to "text/html". Manually setting it to "text/xml" in JMeter
fixed the problem.
Greetings,
Matthias
> Possible header formation bug
> -
>
> Key: AXIS2-802
> URL: http://issues.apache.org/jira/browse/AXIS2-802
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core
>Affects Versions: 1.0
> Environment: Linux Fedora Core 5, JBoss 4.1
>Reporter: Denis Orlov
>
> I am trying to test a service with the header. I auto generated stubs
> and every time I invoke the service it returns the following message:
> org.apache.axis2.AxisFault: SOAPEnvelope must contain a body element
> which is either first or second child element of the SOAPEnvelope.
> The service works fine if the header is not set. The header is a simple
> object with 3 string fields. I do not have a header handler on the
> server side.
> Here is the SOAP message:
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> xmlns:ns1="http://tests.ws.dbvr.com/types";>11111egehh
> xmlns:ns1="http://tests.ws.dbvr.com/types";>erewtr4sfddffcewefewfde
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS-2546) java2wsdl attempts to write duplicate schema element
java2wsdl attempts to write duplicate schema element
Key: AXIS-2546
URL: http://issues.apache.org/jira/browse/AXIS-2546
Project: Apache Axis
Issue Type: Bug
Components: WSDL processing
Affects Versions: 1.4
Environment: Windows XP, Java 1.4
Reporter: Mariano Eloy Fernández
I tried to generate a WRAPPED WSDL document from a Java interface with several
overloaded methods.
This exception is thrown:
[axis-java2wsdl] {http://xml.apache.org/axis/}stackTrace:
Attempted to write duplicate schema element :
{urn:es.infonova.codigospostales.ws}obtenerCodigosPostales
[axis-java2wsdl] at
org.apache.axis.wsdl.fromJava.Types.writeSchemaElementDecl(Types.java:865)
...
This exception is not thrown if the style of WSDL document is RPC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1084) Calling Document.serialize() or OMElement.serializeandConsume() throws a "org.apache.axiom.om.OMException: Unsupported Operation" Exception
Calling Document.serialize() or OMElement.serializeandConsume() throws a "org.apache.axiom.om.OMException: Unsupported Operation" Exception --- Key: AXIS2-1084 URL: http://issues.apache.org/jira/browse/AXIS2-1084 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: om Affects Versions: 1.0 Environment: jdk 1.5.0, Axiom 1.0, Reporter: Sven Lösekann Attachments: xml-read-write.zip I try to serialize an object tree using Axiom. I create a document and put the OMElement in it but I cannot write the the tree to a file. If I call document.serialize() I get the exeption an if I do a OMElement.serializeandConsume() on the root element I get the same Exception. I have put together a demo eclipse project without the jar files to show the problem. It is attached to the Issue. I hope there is someone who can help me solve this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-810) Axis2 1.0 server remove nillable attributes
[ http://issues.apache.org/jira/browse/AXIS2-810?page=comments#action_12434383 ] Sébastien Arod commented on AXIS2-810: -- The bug was on the XmlSchema side. (see http://issues.apache.org/jira/browse/WSCOMMONS-48?watch=true) Nothing changed on the Axis2 code. Seb > Axis2 1.0 server remove nillable attributes > --- > > Key: AXIS2-810 > URL: http://issues.apache.org/jira/browse/AXIS2-810 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: 1.0 > Environment: Widows XP > JDK 1.5.0_06 > apache-tomcat-5.5.12 > Axis2 1.0 webapp >Reporter: Sébastien Arod >Priority: Critical > Attachments: WSCity.wsdl, WSCity_modified.wsdl > > > When I deploy a web service with a specified WSDL in the Axis2 webapp the xsd > nillable attributes are removed from WSDL by Axis2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1191) Axis2 webapp looses xmlns in Schema
Axis2 webapp looses xmlns in Schema --- Key: AXIS2-1191 URL: http://issues.apache.org/jira/browse/AXIS2-1191 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.0 Environment: Windows Java 1.5 Reporter: Sébastien Arod Priority: Critical Attachments: Test.wsdl The WSDL published by Axis2 modify types and contains invalid xmlns values : xmlns="" is added to some tag See attached files : Test.wsdl the original file (contained in .aar) Test.axis2.wsdl the WSDL published by the webapp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1191) Axis2 webapp looses xmlns in Schema
[ http://issues.apache.org/jira/browse/AXIS2-1191?page=all ] Sébastien Arod updated AXIS2-1191: -- Attachment: Test.wsdl Original WSDL > Axis2 webapp looses xmlns in Schema > --- > > Key: AXIS2-1191 > URL: http://issues.apache.org/jira/browse/AXIS2-1191 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: 1.0 > Environment: Windows > Java 1.5 >Reporter: Sébastien Arod >Priority: Critical > Attachments: Test.wsdl > > > The WSDL published by Axis2 modify types and contains invalid xmlns values : > xmlns="" is added to some tag > See attached files : > Test.wsdl the original file (contained in .aar) > Test.axis2.wsdl the WSDL published by the webapp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1191) Axis2 webapp looses xmlns in Schema
[ http://issues.apache.org/jira/browse/AXIS2-1191?page=all ] Sébastien Arod updated AXIS2-1191: -- Attachment: Test.axis2.wsdl Published WSDL > Axis2 webapp looses xmlns in Schema > --- > > Key: AXIS2-1191 > URL: http://issues.apache.org/jira/browse/AXIS2-1191 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: 1.0 > Environment: Windows > Java 1.5 >Reporter: Sébastien Arod >Priority: Critical > Attachments: Test.axis2.wsdl, Test.wsdl > > > The WSDL published by Axis2 modify types and contains invalid xmlns values : > xmlns="" is added to some tag > See attached files : > Test.wsdl the original file (contained in .aar) > Test.axis2.wsdl the WSDL published by the webapp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1191) Axis2 webapp looses xmlns in Schema
[ http://issues.apache.org/jira/browse/AXIS2-1191?page=comments#action_12436136 ] Sébastien Arod commented on AXIS2-1191: --- I actually do use the latest nightly (2006-09-19) Sorry I did not mentioned that > Axis2 webapp looses xmlns in Schema > --- > > Key: AXIS2-1191 > URL: http://issues.apache.org/jira/browse/AXIS2-1191 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: 1.0 > Environment: Windows > Java 1.5 >Reporter: Sébastien Arod >Priority: Critical > Attachments: Test.axis2.wsdl, Test.wsdl > > > The WSDL published by Axis2 modify types and contains invalid xmlns values : > xmlns="" is added to some tag > See attached files : > Test.wsdl the original file (contained in .aar) > Test.axis2.wsdl the WSDL published by the webapp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2934) Wrong Axis2-Skeletongeneration with base64binary param and returntype
Wrong Axis2-Skeletongeneration with base64binary param and returntype - Key: AXIS2-2934 URL: https://issues.apache.org/jira/browse/AXIS2-2934 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Andreas Schörk Attachments: XmlPacketService.wsdl, XmlPacketServiceSkeleton.java, XmlPacketServiceSkeletonInterface.java Hello, I created a webservice providing 2 methods 1. StringExchange 2. GzippedStringExchange. The latter one has parameter and returntype xsd:Base64binary. The generated skeleton is ok for 1. the other function has an empty paramlist and returns void. wsdl, generated Skeletons and build.xml will be attached -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2934) Wrong Axis2-Skeletongeneration with base64binary param and returntype
[ https://issues.apache.org/jira/browse/AXIS2-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schörk updated AXIS2-2934: -- Attachment: XmlPacketServiceSkeletonInterface.java XmlPacketServiceSkeleton.java XmlPacketService.wsdl wsdl, SkeletonInterface and Skeleton > Wrong Axis2-Skeletongeneration with base64binary param and returntype > - > > Key: AXIS2-2934 > URL: https://issues.apache.org/jira/browse/AXIS2-2934 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Andreas Schörk > Attachments: XmlPacketService.wsdl, XmlPacketServiceSkeleton.java, > XmlPacketServiceSkeletonInterface.java > > > Hello, > I created a webservice providing 2 methods > 1. StringExchange > 2. GzippedStringExchange. > The latter one has parameter and returntype xsd:Base64binary. > The generated skeleton is ok for 1. the other function has an empty paramlist > and returns void. > wsdl, generated Skeletons and build.xml will be attached -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2934) Wrong Axis2-Skeletongeneration with base64binary param and returntype
[ https://issues.apache.org/jira/browse/AXIS2-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schörk updated AXIS2-2934: -- Attachment: axis2servicegen.xml ant-build for webservice generation > Wrong Axis2-Skeletongeneration with base64binary param and returntype > - > > Key: AXIS2-2934 > URL: https://issues.apache.org/jira/browse/AXIS2-2934 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: adb >Affects Versions: nightly >Reporter: Andreas Schörk > Attachments: axis2servicegen.xml, XmlPacketService.wsdl, > XmlPacketServiceSkeleton.java, XmlPacketServiceSkeletonInterface.java > > > Hello, > I created a webservice providing 2 methods > 1. StringExchange > 2. GzippedStringExchange. > The latter one has parameter and returntype xsd:Base64binary. > The generated skeleton is ok for 1. the other function has an empty paramlist > and returns void. > wsdl, generated Skeletons and build.xml will be attached -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2934) Wrong Axis2-Skeletongeneration with base64binary param and returntype
[ https://issues.apache.org/jira/browse/AXIS2-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schörk updated AXIS2-2934: -- Component/s: adb Environment: Java 1.6, Windows, Nightly Axis-Snapshot 20070708 Affects Version/s: nightly > Wrong Axis2-Skeletongeneration with base64binary param and returntype > - > > Key: AXIS2-2934 > URL: https://issues.apache.org/jira/browse/AXIS2-2934 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: adb >Affects Versions: nightly > Environment: Java 1.6, Windows, Nightly Axis-Snapshot 20070708 >Reporter: Andreas Schörk > Attachments: axis2servicegen.xml, XmlPacketService.wsdl, > XmlPacketServiceSkeleton.java, XmlPacketServiceSkeletonInterface.java > > > Hello, > I created a webservice providing 2 methods > 1. StringExchange > 2. GzippedStringExchange. > The latter one has parameter and returntype xsd:Base64binary. > The generated skeleton is ok for 1. the other function has an empty paramlist > and returns void. > wsdl, generated Skeletons and build.xml will be attached -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2949) ADB: Wrong variable name in Factory class generated from XSD file
ADB: Wrong variable name in Factory class generated from XSD file
-
Key: AXIS2-2949
URL: https://issues.apache.org/jira/browse/AXIS2-2949
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.2
Environment: Fedora, Eclipse 3.2, codegen as ant-task
Reporter: Łukasz Zaręba
The problem occurs when processing WSDL file which imports types from external
schema file (XSD file looks like it was generated by .NET).
When using ADB binding codegen generates variables with incorrect names.
Variable names are linked to attribute names, and contain '-' characters. All
errors occur in parse method of the Factory class. Example of generated code:
// handle attribute "order-wlr-service-package_Id_0"
java.lang.String tempAttriborder-wlr-service-package_Id_0 =
reader.getAttributeValue("http://t.pl","order-wlr-service-package_Id_0";);
The corresponding XSD file fragment:
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2949) ADB: Wrong variable name in Factory class generated from XSD file
[
https://issues.apache.org/jira/browse/AXIS2-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Łukasz Zaręba updated AXIS2-2949:
-
Attachment: OrderWlrServiceElement_type2.java
File generated by codegen.
> ADB: Wrong variable name in Factory class generated from XSD file
> -
>
> Key: AXIS2-2949
> URL: https://issues.apache.org/jira/browse/AXIS2-2949
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.2
> Environment: Fedora, Eclipse 3.2, codegen as ant-task
>Reporter: Łukasz Zaręba
> Attachments: OrderWlrServiceElement_type2.java
>
>
> The problem occurs when processing WSDL file which imports types from
> external schema file (XSD file looks like it was generated by .NET).
> When using ADB binding codegen generates variables with incorrect names.
> Variable names are linked to attribute names, and contain '-' characters. All
> errors occur in parse method of the Factory class. Example of generated code:
> // handle attribute "order-wlr-service-package_Id_0"
> java.lang.String tempAttriborder-wlr-service-package_Id_0
> = reader.getAttributeValue("http://t.pl","order-wlr-service-package_Id_0";);
> The corresponding XSD file fragment:
>msprop:Generator_UserColumnName="order-wlr-service-package_Id_0"
> msprop:Generator_ColumnVarNameInTable="_columnorder_wlr_service_package_Id_0"
> msprop:Generator_ColumnPropNameInRow="_order_wlr_service_package_Id_0"
> msprop:Generator_ColumnPropNameInTable="_order_wlr_service_package_Id_0Column"
> name="order-wlr-service-package_Id_0" type="xs:int" use="prohibited" />
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-2934) Wrong Axis2-Skeletongeneration with base64binary param and returntype
[ https://issues.apache.org/jira/browse/AXIS2-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schörk closed AXIS2-2934. - Sorry for the inconveniences, I relied too much on eclipse to generate wsdl right. And forgot one step. > Wrong Axis2-Skeletongeneration with base64binary param and returntype > - > > Key: AXIS2-2934 > URL: https://issues.apache.org/jira/browse/AXIS2-2934 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: adb >Affects Versions: nightly > Environment: Java 1.6, Windows, Nightly Axis-Snapshot 20070708 >Reporter: Andreas Schörk >Assignee: Amila Chinthaka Suriarachchi > Attachments: axis2servicegen.xml, XmlPacketService.wsdl, > XmlPacketServiceSkeleton.java, XmlPacketServiceSkeletonInterface.java > > > Hello, > I created a webservice providing 2 methods > 1. StringExchange > 2. GzippedStringExchange. > The latter one has parameter and returntype xsd:Base64binary. > The generated skeleton is ok for 1. the other function has an empty paramlist > and returns void. > wsdl, generated Skeletons and build.xml will be attached -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2845) Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
[ https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517695 ] Jorge Fernández commented on AXIS2-2845: Do you mean code generator?? I'm using Eclipse Axis2 code generator plugin > Throwing exceptions causes 400 HTTP header appearing when running under Tomcat > -- > > Key: AXIS2-2845 > URL: https://issues.apache.org/jira/browse/AXIS2-2845 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2 >Reporter: Jorge Fernández >Assignee: Glen Daniels > Fix For: 1.3 > > Attachments: exception.txt > > > When I integrate Axis2 with Tomcat and I try to throw any exception, the > response message is added a HTTP header meaning Bad Request and the exception > in the SOAP message is OK but when my client sees the HTTP header doesn' t go > on parsing the SOAP message. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3076) WSDL2Java doesn't finish when generating client without -u option
WSDL2Java doesn't finish when generating client without -u option - Key: AXIS2-3076 URL: https://issues.apache.org/jira/browse/AXIS2-3076 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: Windows XP SP2, Java 1.6, Axis2 1.3 RC3 Reporter: Jorge Fernández When using -u option for client generation, it works ok but without that option, it never ends and it uses big loads of CPU -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3076) WSDL2Java doesn't finish when generating client without -u option
[ https://issues.apache.org/jira/browse/AXIS2-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández updated AXIS2-3076: --- Priority: Blocker (was: Major) > WSDL2Java doesn't finish when generating client without -u option > - > > Key: AXIS2-3076 > URL: https://issues.apache.org/jira/browse/AXIS2-3076 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.3 > Environment: Windows XP SP2, Java 1.6, Axis2 1.3 RC3 >Reporter: Jorge Fernández >Priority: Blocker > Attachments: JIRAService.wsdl, wsdl2java-medici-link.bat > > > When using -u option for client generation, it works ok but without that > option, it never ends and it uses big loads of CPU -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3076) WSDL2Java doesn't finish when generating client without -u option
[ https://issues.apache.org/jira/browse/AXIS2-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517940 ] Jorge Fernández commented on AXIS2-3076: Last time I tried, it took almost 2 minutes to complete the operation with the WSDL of the JIRA. I tried specifying ns2p option and without it. Would it be maybe random?? Because I'm pretty sure that I had waited for more than 2 minutes when I had done the same operation before. In 1.2, it finished in less than 10 seconds for a more complex WSDL and in 1.3 it lasted more than 8 minutes, specifying some of the namespaces mapping. The strange thing is that code seems to be generated in about 15 or 20 seconds but the console is still open. > WSDL2Java doesn't finish when generating client without -u option > - > > Key: AXIS2-3076 > URL: https://issues.apache.org/jira/browse/AXIS2-3076 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.3 > Environment: Windows XP SP2, Java 1.6, Axis2 1.3 RC3 >Reporter: Jorge Fernández >Assignee: Amila Chinthaka Suriarachchi > Attachments: JIRAService.wsdl, wsdl2java-medici-link.bat > > > When using -u option for client generation, it works ok but without that > option, it never ends and it uses big loads of CPU -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3076) WSDL2Java doesn't finish when generating client without -u option
[ https://issues.apache.org/jira/browse/AXIS2-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518119 ] Jorge Fernández commented on AXIS2-3076: The problem seems to be resolved dropping out jalopy.jar > WSDL2Java doesn't finish when generating client without -u option > - > > Key: AXIS2-3076 > URL: https://issues.apache.org/jira/browse/AXIS2-3076 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.3 > Environment: Windows XP SP2, Java 1.6, Axis2 1.3 RC3 >Reporter: Jorge Fernández >Assignee: Amila Chinthaka Suriarachchi > Attachments: JIRAService.wsdl, wsdl2java-medici-link.bat > > > When using -u option for client generation, it works ok but without that > option, it never ends and it uses big loads of CPU -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Issue Comment Edited: (AXIS2-2845) Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
[ https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518229 ] informaticu007-pfc edited comment on AXIS2-2845 at 8/7/07 12:35 PM: - Hi Glen, Now exceptions come with 500 HTTP header and the client works ok with them. was (Author: informaticu007-pfc): Now, exceptions come with 500 HTTP header and the client works ok with them > Throwing exceptions causes 400 HTTP header appearing when running under Tomcat > -- > > Key: AXIS2-2845 > URL: https://issues.apache.org/jira/browse/AXIS2-2845 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2 >Reporter: Jorge Fernández >Assignee: Glen Daniels > Attachments: exception.txt > > > When I integrate Axis2 with Tomcat and I try to throw any exception, the > response message is added a HTTP header meaning Bad Request and the exception > in the SOAP message is OK but when my client sees the HTTP header doesn' t go > on parsing the SOAP message. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2845) Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
[ https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518229 ] Jorge Fernández commented on AXIS2-2845: Now, exceptions come with 500 HTTP header and the client works ok with them > Throwing exceptions causes 400 HTTP header appearing when running under Tomcat > -- > > Key: AXIS2-2845 > URL: https://issues.apache.org/jira/browse/AXIS2-2845 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2 >Reporter: Jorge Fernández >Assignee: Glen Daniels > Attachments: exception.txt > > > When I integrate Axis2 with Tomcat and I try to throw any exception, the > response message is added a HTTP header meaning Bad Request and the exception > in the SOAP message is OK but when my client sees the HTTP header doesn' t go > on parsing the SOAP message. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Issue Comment Edited: (AXIS2-2845) Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
[ https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518229 ] informaticu007-pfc edited comment on AXIS2-2845 at 8/7/07 12:40 PM: - Hi Glen, Now exceptions come with 500 HTTP header: HTTP/1.1 500 Error Interno del Servidor Server: Apache-Coyote/1.1 Content-Type: application/soap+xml; action="http://service.medici_link/Medici_LinkPortType/logout/Fault/DataAccessFault";charset=UTF-8 Transfer-Encoding: chunked Date: Tue, 07 Aug 2007 19:36:42 GMT Connection: close 346 http://www.w3.org/2003/05/soap-envelope"; xmlns:wsa="http://www.w3.org/2005/08/addressing";> http://service.medici_link/Medici_LinkPortType/logout/Fault/DataAccessFault urn:uuid:20F5EFD2CCF889D0FB1186515400973 soapenv:Receiver Validation Fault http://op_messages.medici_link/xsd";> System not validated. You must validate before invoking a method. 0 In the client I can't see the exception description: java.rmi.RemoteException: Validation; nested exception is: client.Validation: Validation at client.Medici_LinkStub.getPatientsByType(Medici_LinkStub.java:4187) at client.ClientUtilities.getPatientsTest(ClientUtilities.java:322) at client.Client.main(Client.java:53) Caused by: client.Validation: Validation at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source)Closing session... at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at client.Medici_LinkStub.getPatientsByType(Medici_LinkStub.java:4173) ... 2 more java.rmi.RemoteException: Validation; nested exception is: client.Validation: Validation at client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:4453) at client.ClientUtilities.getDetailedMonitoringStagesTest(ClientUtilities.java:356) at client.Client.main(Client.java:59) Caused by: client.Validation: Validation at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:4439) ... 2 more java.rmi.RemoteException: Validation; nested exception is: client.Validation: Validation at client.Medici_LinkStub.logout(Medici_LinkStub.java:1056) was (Author: informaticu007-pfc): Hi Glen, Now exceptions come with 500 HTTP header and the client works ok with them. > Throwing exceptions causes 400 HTTP header appearing when running under Tomcat > -- > > Key: AXIS2-2845 > URL: https://issues.apache.org/jira/browse/AXIS2-2845 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2 >Reporter: Jorge Fernández >Assignee: Glen Daniels > Attachments: exception.txt > > > When I integrate Axis2 with Tomcat and I try to throw any exception, the > response message is added a HTTP header meaning Bad Request and the exception > in the SOAP message is OK but when my client sees the HTTP header doesn' t go > on parsing the SOAP message. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2845) Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
[ https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518240 ] Jorge Fernández commented on AXIS2-2845: Well, I'm not sure. The exception shown in the client is the correct one but the description sent from the server (System not validated. You must validate before invoking a method.) is not shown. I don't know if this is related with sendFullStackTrace parameter in axis2.xml in the server. The default is false and whenever I modify that in the file in new release, Axis2 stops working. > Throwing exceptions causes 400 HTTP header appearing when running under Tomcat > -- > > Key: AXIS2-2845 > URL: https://issues.apache.org/jira/browse/AXIS2-2845 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2 >Reporter: Jorge Fernández >Assignee: Glen Daniels > Attachments: exception.txt > > > When I integrate Axis2 with Tomcat and I try to throw any exception, the > response message is added a HTTP header meaning Bad Request and the exception > in the SOAP message is OK but when my client sees the HTTP header doesn' t go > on parsing the SOAP message. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
Internal server error when modifying axis2.xml in axis2 1.3 war distribution Key: AXIS2-3099 URL: https://issues.apache.org/jira/browse/AXIS2-3099 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: deployment Affects Versions: 1.3 Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 Reporter: Jorge Fernández Whenever I modify axis2.xml of the war distribution, I get an error page from listServices page or when I display an WSDL In Hapiness Page I see: Examinin Version Service: There was a problem in Axis2 version service , may be the service not available or some thing has gone wrong. But this does not mean system is not working ! Try to upload some other service and check to see whether it is working. For stoping that problem I have to backup and restore the original axis2.xml file that came in the war distribution When that happens I receive this at the client the message in the attached file when invoking the service. Also I can see that each time I run tomcat, my services.xml is updated, apparently with no changes but is modified on disk and the same happens with axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández updated AXIS2-3099: --- Attachment: excepcion.txt > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández > Attachments: excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández updated AXIS2-3099: --- Priority: Blocker (was: Major) > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Blocker > Attachments: excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[
https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518300
]
Jorge Fernández commented on AXIS2-3099:
With axis2 binary distribution, I'm trying to engage rampart module for testing
and when I write
I'm getting the exception:
Exception in thread "main" org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x3f (at char
#2840, byte #-1)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:130)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:359)
at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:568)
at
org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:96)
at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:79)
at
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:595)
at
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:115)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:180)
at client.Client.main(Client.java:26)
Caused by: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x3f (at
char #2840, byte #-1)
at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:153)
... 10 more
Caused by: java.io.CharConversionException: Invalid UTF-8 middle byte 0x3f (at
char #2840, byte #-1)
at com.ctc.wstx.io.UTF8Reader.reportInvalidOther(UTF8Reader.java:310)
at com.ctc.wstx.io.UTF8Reader.read(UTF8Reader.java:208)
at com.ctc.wstx.io.ReaderSource.readInto(ReaderSource.java:84)
at
com.ctc.wstx.io.BranchingReaderSource.readInto(BranchingReaderSource.java:57)
at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:967)
at com.ctc.wstx.sr.StreamScanner.getNext(StreamScanner.java:738)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:1995)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
... 11 more
I'm using it for the client side and I tried to do it with
ConfigurationContext configContext
=ConfigurationContextFactory.createConfigurationContextFromFileSystem(System.getenv("AXIS2_HOME")+"/repository",System.getenv("AXIS2_HOME")+"/conf/axis2.xml");
configContext.getAxisConfiguration().engageModule("rampart");
and it says:
org.apache.axis2.AxisFault: The system is attempting to engage a module that is
not available: rampart
at
org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:440)
at client.Client.main(Client.java:28)
> Internal server error when modifying axis2.xml in axis2 1.3 war distribution
>
>
> Key: AXIS2-3099
> URL: https://issues.apache.org/jira/browse/AXIS2-3099
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
>Affects Versions: 1.3
> Environment: Windows XP SP2, Tomcat 6.0, Java 6.0
>Reporter: Jorge Fernández
> Attachments: excepcion.txt
>
>
> Whenever I modify axis2.xml of the war distribution, I get an error page from
> listServices page or when I display an WSDL
> In Hapiness Page I see:
> Examinin Version Service:
> There was a problem in Axis2 version service , may be the service not
> available or some thing has gone wrong. But this does not mean system is not
> working ! Try to upload some other service and check to see whether it is
> working.
> For stoping that problem I have to backup and restore the original axis2.xml
> file that came in the war distribution
> When that happens I receive this at the client the message in the attached
> file when invoking the service.
> Also I can see that each time I run tomcat, my services.xml is updated,
> apparently with no changes but is modified on disk and the same happens with
> axis2.xml
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518306 ] Jorge Fernández commented on AXIS2-3099: Hi Charitha, what I did (last comment) was copyand change addressing for rampart. > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Blocker > Attachments: excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Issue Comment Edited: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518306 ] informaticu007-pfc edited comment on AXIS2-3099 at 8/7/07 7:21 PM: Hi Charitha, what I did (last comment) was copyand change addressing for rampart. In the first comment was change 8080 for 8081 and put true in the send StackTraceWithFaults parameter. If I did redo in my editor to leave the original file I kept getting the exception. I had to replace the file with the original one to get it working again was (Author: informaticu007-pfc): Hi Charitha, what I did (last comment) was copyand change addressing for rampart. > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Blocker > Attachments: excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518311 ] Jorge Fernández commented on AXIS2-3099: Windows XP SP2, Tomcat 6.0, Java 6.0, Jedit 4.2. I had never that problem using the same OS and editor. I sometimes observe that whenever tomcat stops or starts, Jedit detects that the file was changed but I can't see any diference. And this never happened before. > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Critical > Attachments: excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández updated AXIS2-3099: --- Attachment: axis2.xml Modified file. Changed port number > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Blocker > Attachments: axis2.xml, excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518314 ] Jorge Fernández commented on AXIS2-3099: That happened to me also when I changed port number, and setting sendStacktraceDetailsWithFaults to true. goin' to sleep ;) > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Blocker > Attachments: axis2.xml, excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518411 ] Jorge Fernández commented on AXIS2-3099: Hi, I don't know what is happening with rampart because I have the mar file in the repository/modules directory and copied the libraries to lib directory. I execute axis2server.bat and rampart is deployed. I see deploying module: rampart-SNAPSHOT but whenever I try to run the client or engage it programmatically, I receive the exception saying that is not present In war version it works OK. About the editor problem, when I used notepad it worked ok but I'm editing services.xml with Jedit and there is no problem. I can't see those strange characters. I've been using Jedit since axis2 1.1 and I had no problems with it > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Critical > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518428 ] Jorge Fernández commented on AXIS2-3099: Yes I have but don't worry. Both problems are resolved with the RC released today. I can use Jedit and axis2 detects rampart now. Thanks, Jorge Fernández > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Critical > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2845) Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
[ https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518430 ] Jorge Fernández commented on AXIS2-2845: In today's RC I receive faults with 400 HTTP header and client parses them OK and also, sometimes I'm receiving 500 HTTP, apparently working OK in both cases > Throwing exceptions causes 400 HTTP header appearing when running under Tomcat > -- > > Key: AXIS2-2845 > URL: https://issues.apache.org/jira/browse/AXIS2-2845 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2 >Reporter: Jorge Fernández >Assignee: Glen Daniels > Attachments: exception.txt > > > When I integrate Axis2 with Tomcat and I try to throw any exception, the > response message is added a HTTP header meaning Bad Request and the exception > in the SOAP message is OK but when my client sees the HTTP header doesn' t go > on parsing the SOAP message. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519217 ] Jorge Fernández commented on AXIS2-3099: In spite of being resolved, there is still a question: Why, every time I start/stop Tomcat, axis2.xml and services.xml is overwritten?? > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Critical > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3120) Exceptions throw in init method are only logged and cannot be managed
Exceptions throw in init method are only logged and cannot be managed - Key: AXIS2-3120 URL: https://issues.apache.org/jira/browse/AXIS2-3120 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Windows XP SP2, Java 1.6.0, Tomcat 6.0 Reporter: Jorge Fernández DependencyManager.initServiceClass is the method that calls init and all it does with exceptions thrown from init, is logging them. I think it should be possible for developers to manage them if there is any initialization problem that could affect service operation as it's my case. I need to start an element and if there is any error on initialization, the service won't realize about that and It will work incorrectly. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519821 ] Jorge Fernández commented on AXIS2-3099: The problem is again in axis2 1.3 final release > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Critical > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández updated AXIS2-3099: --- Priority: Minor (was: Critical) > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Minor > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández reopened AXIS2-3099: > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Minor > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3151) SOAP 1.1 faultcode:Server not possible with generated server skeleton interfaces
SOAP 1.1 faultcode:Server not possible with generated server skeleton interfaces Key: AXIS2-3151 URL: https://issues.apache.org/jira/browse/AXIS2-3151 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen, kernel Affects Versions: 1.1.1 Reporter: David Croé The SOAP 1.1 faultcode element defaults to Client and there is no possibility to change that within the generated server skeletons. The server skeleton interface declares only the exceptions which are generated from the fault entries in the wsdl. Throwing such a fault exceptions results in faultcode:client. Throwing a runtime exception results in faultcode:client. The only possible way, to throw an AxisFault and set the faultcode:Server is not possible because AxisFault is not declared in the skeleton interface. Greetings David Croé -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3165) Accessing to unexistant get() method from MessageReceiver when using xmlbeans databinding
Accessing to unexistant get() method from MessageReceiver when using xmlbeans databinding - Key: AXIS2-3165 URL: https://issues.apache.org/jira/browse/AXIS2-3165 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3 Environment: JDK 1.4 Reporter: David Rodríguez Alfayate Priority: Blocker I'm using XMLBeans generation from WSDL, when the message receiver access the skeleton the content response is processed as: wrappedType.get().<>. The generated method name is not "get()" but get<>, so it fails to compile. I think that i cannot use ADB since I need to know if primitive fields are null or not, and I haven't seen any mechanism in order to verifiy this nullity with this mechanism. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3165) Accessing to unexistant get() method from MessageReceiver when using xmlbeans databinding
[ https://issues.apache.org/jira/browse/AXIS2-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Rodríguez Alfayate updated AXIS2-3165: Attachment: ProxiaServices2.wsdl WSDL used which generates the incorrect code. > Accessing to unexistant get() method from MessageReceiver when using xmlbeans > databinding > - > > Key: AXIS2-3165 > URL: https://issues.apache.org/jira/browse/AXIS2-3165 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: JDK 1.4 >Reporter: David Rodríguez Alfayate >Priority: Blocker > Attachments: ProxiaServices2.wsdl > > > I'm using XMLBeans generation from WSDL, when the message receiver access the > skeleton the content response is > processed as: > wrappedType.get().<>. > The generated method name is not "get()" but get<>, so it fails > to compile. > I think that i cannot use ADB since I need to know if primitive fields are > null or not, and I haven't seen any mechanism in order to verifiy this > nullity with this mechanism. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3165) Accessing to unexistant get() method from MessageReceiver when using xmlbeans databinding
[ https://issues.apache.org/jira/browse/AXIS2-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524454 ] David Rodríguez Alfayate commented on AXIS2-3165: - I was trying with the -uw option, I've disabled it and the code generated is correct. So I suppose that perhaps could be a bug with this option. On the other hand, talking about handling primitive fields null values in ADB... In my opinion (and it's just an opinion) using the MIN_VALUE... is not a real good solution, taking into an account that in Java exists the primitive and the non primitive (Object) type, and that the second one is nilable, perhaps it could be better to convert the input data not to the primitive type but to the object type. Thanks a lot for your help, David. > Accessing to unexistant get() method from MessageReceiver when using xmlbeans > databinding > - > > Key: AXIS2-3165 > URL: https://issues.apache.org/jira/browse/AXIS2-3165 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: JDK 1.4 >Reporter: David Rodríguez Alfayate >Priority: Blocker > Attachments: ProxiaServices2.wsdl > > > I'm using XMLBeans generation from WSDL, when the message receiver access the > skeleton the content response is > processed as: > wrappedType.get().<>. > The generated method name is not "get()" but get<>, so it fails > to compile. > I think that i cannot use ADB since I need to know if primitive fields are > null or not, and I haven't seen any mechanism in order to verifiy this > nullity with this mechanism. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonas Boëthius reopened AXIS2-2389: --- Still not dispatching correct, now tested on Axis2, version 1.3. > Dispatching based on the SOAP message body does not work for document/literal > style > --- > > Key: AXIS2-2389 > URL: https://issues.apache.org/jira/browse/AXIS2-2389 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.1.1 > Environment: Axis2, version 1.1.1 > Tomcat 5.0 > JDK1.6.0 >Reporter: Jonas Boëthius >Assignee: Amila Chinthaka Suriarachchi >Priority: Blocker > Fix For: 1.3 > > > I am using a document/literal service and found that the dispatching based on > the message body does not seem to work. Any SOAPAction header except the one > defined in the WSDL causes the following fault: > org.apache.axis2.AxisFault: Operation Not found EPR is... > I've used ADB data binding and generated server side classes and services.xml > using the WSDL2Java utility. > When debugging, I can see that the SOAPMessageBodyBasedDispatcher > is invoked for the dispatching, that it finds the correct request element > name but when passing the call to the getOperation method in the AxisService > class, the operationsAliasesMap does not contain the name of the request > element. It seems like the initialization of the operationsAliasesMap does > not consider the case needed for the SOAPMessageBodyBasedDispatcher. > Found an easy work-around of manually adding the name of the request root > element as actionMapping in the generated services.xml file. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonas Boëthius updated AXIS2-2389: -- Attachment: EchoApi.wsdl WSDL of the tested service. > Dispatching based on the SOAP message body does not work for document/literal > style > --- > > Key: AXIS2-2389 > URL: https://issues.apache.org/jira/browse/AXIS2-2389 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.1.1 > Environment: Axis2, version 1.1.1 > Tomcat 5.0 > JDK1.6.0 >Reporter: Jonas Boëthius >Assignee: Amila Chinthaka Suriarachchi >Priority: Blocker > Fix For: 1.3 > > Attachments: EchoApi.wsdl > > > I am using a document/literal service and found that the dispatching based on > the message body does not seem to work. Any SOAPAction header except the one > defined in the WSDL causes the following fault: > org.apache.axis2.AxisFault: Operation Not found EPR is... > I've used ADB data binding and generated server side classes and services.xml > using the WSDL2Java utility. > When debugging, I can see that the SOAPMessageBodyBasedDispatcher > is invoked for the dispatching, that it finds the correct request element > name but when passing the call to the getOperation method in the AxisService > class, the operationsAliasesMap does not contain the name of the request > element. It seems like the initialization of the operationsAliasesMap does > not consider the case needed for the SOAPMessageBodyBasedDispatcher. > Found an easy work-around of manually adding the name of the request root > element as actionMapping in the generated services.xml file. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525116 ] Jonas Boëthius commented on AXIS2-2389: --- Correct dispatching (with default configuration) to a service based on the attached WSDL is made only when the SOAPAction header has the value stated in the WSDL. For other cases the dispatching fails with error "The endpoint reference (EPR) for the Operation not found". Client code is not attached since I use XML spy to manipulate the SOAPAction header. Use any client which makes it possible to control the value of the SOAPAction header to reproduce the problem. > Dispatching based on the SOAP message body does not work for document/literal > style > --- > > Key: AXIS2-2389 > URL: https://issues.apache.org/jira/browse/AXIS2-2389 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.1.1 > Environment: Axis2, version 1.1.1 > Tomcat 5.0 > JDK1.6.0 >Reporter: Jonas Boëthius >Assignee: Amila Chinthaka Suriarachchi >Priority: Blocker > Fix For: 1.3 > > Attachments: EchoApi.wsdl > > > I am using a document/literal service and found that the dispatching based on > the message body does not seem to work. Any SOAPAction header except the one > defined in the WSDL causes the following fault: > org.apache.axis2.AxisFault: Operation Not found EPR is... > I've used ADB data binding and generated server side classes and services.xml > using the WSDL2Java utility. > When debugging, I can see that the SOAPMessageBodyBasedDispatcher > is invoked for the dispatching, that it finds the correct request element > name but when passing the call to the getOperation method in the AxisService > class, the operationsAliasesMap does not contain the name of the request > element. It seems like the initialization of the operationsAliasesMap does > not consider the case needed for the SOAPMessageBodyBasedDispatcher. > Found an easy work-around of manually adding the name of the request root > element as actionMapping in the generated services.xml file. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonas Boëthius updated AXIS2-2389: -- Attachment: request_response.log This is my final comment on this issue. If you cannot reproduce the problem I must accept it (and that I probably do something wrong). The attached file contains the complete request-response for a successful invocation (with correct SOAPAction header) and a failed invocation (without the header). No stacktrace was generated. > Dispatching based on the SOAP message body does not work for document/literal > style > --- > > Key: AXIS2-2389 > URL: https://issues.apache.org/jira/browse/AXIS2-2389 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.1.1 > Environment: Axis2, version 1.1.1 > Tomcat 5.0 > JDK1.6.0 >Reporter: Jonas Boëthius >Assignee: Amila Chinthaka Suriarachchi >Priority: Blocker > Fix For: 1.3 > > Attachments: EchoApi.wsdl, request_response.log > > > I am using a document/literal service and found that the dispatching based on > the message body does not seem to work. Any SOAPAction header except the one > defined in the WSDL causes the following fault: > org.apache.axis2.AxisFault: Operation Not found EPR is... > I've used ADB data binding and generated server side classes and services.xml > using the WSDL2Java utility. > When debugging, I can see that the SOAPMessageBodyBasedDispatcher > is invoked for the dispatching, that it finds the correct request element > name but when passing the call to the getOperation method in the AxisService > class, the operationsAliasesMap does not contain the name of the request > element. It seems like the initialization of the operationsAliasesMap does > not consider the case needed for the SOAPMessageBodyBasedDispatcher. > Found an easy work-around of manually adding the name of the request root > element as actionMapping in the generated services.xml file. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3174) Can't avoid timeout
Can't avoid timeout --- Key: AXIS2-3174 URL: https://issues.apache.org/jira/browse/AXIS2-3174 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Windows XP SP2, Java 1.5.0 Tomcat 5.5 Reporter: Jorge Fernández Hi, My problem is that I want to control timeout myself and I would like to have an option to deactivate axis2 timeout. Also I think that timeout counter should be stopped while the service is running an operation invoked by the client. Thanks. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3175) Null arrays management is different when using hierarchies
Null arrays management is different when using hierarchies -- Key: AXIS2-3175 URL: https://issues.apache.org/jira/browse/AXIS2-3175 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.3 Environment: Windows XP SP2, Tomcat 5.5, Java 1.5.0 Reporter: Jorge Fernández Priority: Trivial Hi, I'm observing that when I have an object with array attributes, ADB behaves different depending on whether that attribute is inherited or not. If I have an inherited array, and I don't call its set method, that element won't appear in the SOAP message. The client will see that the array is null. If in the same case, I set it to null, the element will appear as nil in the SOAP message. The client sees an array of one null component. With a non-inherited array, the element will appear as nil if I set it to null and if I don't call the method too. The client sees an array of one null component. If I have an attribute that is not an array (ex: a String). Its behaviour is the same if it's inherited or not. The element will appear as nil. Why my client sees the array with one null component when the array comes as nil?? Shouldn't see it as a null array?? Shouldn't it be better for a null attribute, not to appear in the message? Thanks. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3183) Client stub generation fails for WSDL's with wsdl:import
[ https://issues.apache.org/jira/browse/AXIS2-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Jörg Hessmann updated AXIS2-3183: -- Attachment: WSDLdocument.zip This is the WSDL as provided from the server. > Client stub generation fails for WSDL's with wsdl:import > > > Key: AXIS2-3183 > URL: https://issues.apache.org/jira/browse/AXIS2-3183 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.3 > Environment: Eclipse 3.3 on Windows XP using Axis-2 1.3. > The imported WebService was hosted on a SAP Netweaver 7.0. >Reporter: Hans Jörg Hessmann > Attachments: WSDLdocument.zip > > > Axis2 1.3 is unable to generate a client stub for a simple echo service > that's WSDL is has been spread over several files. To reproduce save the > following WSDL files in a directory structure like this: > main.wsdl > bindings/WebserTestBasicAuth_document.wsdl > porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl > ---x--- contents of main.wsdl ---x--- > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; name="WebserviceTestWsd" > targetNamespace="urn:WebserviceTestWsd" > xmlns:bns0="urn:WebserviceTestWsd/WebserTestBasicAuth/document" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> >namespace="urn:WebserviceTestWsd/WebserTestBasicAuth/document"/> > > binding="bns0:WebserTestBasicAuthBinding"> >location="http://mp5db.metrogroup-networking.com:50500/WebserviceTest/WebserTestBasicAuth?style=document"/> > > > > ---x--- contents of bindings/WebserTestBasicAuth_document.wsdl ---x--- > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > targetNamespace="urn:WebserviceTestWsd/WebserTestBasicAuth/document" > xmlns:prt0="urn:WebserviceTestWsd/WebserviceTestVi/document" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> >location="../porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl" > namespace="urn:WebserviceTestWsd/WebserviceTestVi/document"/> >type="prt0:WebserviceTestVi_Document"> > http://schemas.xmlsoap.org/soap/http"; > style="document"/> > > > > > > > > > > > > ---x--- contents of > porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl ---x--- > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:ns0="urn:WebserviceTestVi" > targetNamespace="urn:WebserviceTestWsd/WebserviceTestVi/document" > xmlns:tns="urn:WebserviceTestWsd/WebserviceTestVi/document"> > > http://www.w3.org/2001/XMLSchema"; > targetNamespace="urn:WebserviceTestVi" xmlns:tns="urn:WebserviceTestVi" > elementFormDefault="qualified"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ---x--x--- > Axis-1 accepts theses files and I was able to generate an axis-2 client stub > after I merged the WSDL's manually into one file. It looks like axis-2 has a > problem with wsdl:import. Replacing the relative pathes with absolute pathes > and hosting the WSDL on a server doesn't help either. > The full stacktrace was: > Exception occurred while code generation for WSDL null > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > org.eclipse.jst.ws.axis2.consumption.core.utils.WSDL2JavaGenerator.getAxisService(WSDL2JavaGenerator.java:379) > at > org.eclipse.jst.ws.axis2.consumption.core.command.Axis2ClientCodegenCommand.execute(Axis2ClientCodegenCommand.java:89) > at > org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:418) > at > org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:358) > at > or
[jira] Created: (AXIS2-3183) Client stub generation fails for WSDL's with wsdl:import
Client stub generation fails for WSDL's with wsdl:import Key: AXIS2-3183 URL: https://issues.apache.org/jira/browse/AXIS2-3183 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.3 Environment: Eclipse 3.3 on Windows XP using Axis-2 1.3. The imported WebService was hosted on a SAP Netweaver 7.0. Reporter: Hans Jörg Hessmann Axis2 1.3 is unable to generate a client stub for a simple echo service that's WSDL is has been spread over several files. To reproduce save the following WSDL files in a directory structure like this: main.wsdl bindings/WebserTestBasicAuth_document.wsdl porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl ---x--- contents of main.wsdl ---x--- http://schemas.xmlsoap.org/wsdl/"; name="WebserviceTestWsd" targetNamespace="urn:WebserviceTestWsd" xmlns:bns0="urn:WebserviceTestWsd/WebserTestBasicAuth/document" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> http://mp5db.metrogroup-networking.com:50500/WebserviceTest/WebserTestBasicAuth?style=document"/> ---x--- contents of bindings/WebserTestBasicAuth_document.wsdl ---x--- http://schemas.xmlsoap.org/wsdl/"; targetNamespace="urn:WebserviceTestWsd/WebserTestBasicAuth/document" xmlns:prt0="urn:WebserviceTestWsd/WebserviceTestVi/document" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> http://schemas.xmlsoap.org/soap/http"; style="document"/> ---x--- contents of porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl ---x--- http://schemas.xmlsoap.org/wsdl/"; xmlns:ns0="urn:WebserviceTestVi" targetNamespace="urn:WebserviceTestWsd/WebserviceTestVi/document" xmlns:tns="urn:WebserviceTestWsd/WebserviceTestVi/document"> http://www.w3.org/2001/XMLSchema"; targetNamespace="urn:WebserviceTestVi" xmlns:tns="urn:WebserviceTestVi" elementFormDefault="qualified"> ---x--x--- Axis-1 accepts theses files and I was able to generate an axis-2 client stub after I merged the WSDL's manually into one file. It looks like axis-2 has a problem with wsdl:import. Replacing the relative pathes with absolute pathes and hosting the WSDL on a server doesn't help either. The full stacktrace was: Exception occurred while code generation for WSDL null java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.jst.ws.axis2.consumption.core.utils.WSDL2JavaGenerator.getAxisService(WSDL2JavaGenerator.java:379) at org.eclipse.jst.ws.axis2.consumption.core.command.Axis2ClientCodegenCommand.execute(Axis2ClientCodegenCommand.java:89) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:418) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:358) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:253) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:252) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:222) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:96) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:255) at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:380) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) at org.
[jira] Created: (AXIS2-3222) OMException with the message "localname can not be null or empty"
OMException with the message "localname can not be null or empty"
-
Key: AXIS2-3222
URL: https://issues.apache.org/jira/browse/AXIS2-3222
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.3
Reporter: Björn Hamann
I am getting an OMException in my generated MessageReiceiverInOut-Class when
using a wsdl fault in my wsdl (enclosed).
In the method invokeBusinessLogic the thrown EfmServiceException is caught an
the method toOM is called to create the OMElement for the fault:
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
In the method toOM the following code is generated to create the OMElement:
factory.createOMElement(source, "", namespace);
Here the empty string is raising a OMException with the message "localname can
not be null or empty". If the e.getFaultMessage() returns null everything works
fine, but of course no data is transportet to the client.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3222) OMException with the message "localname can not be null or empty"
[
https://issues.apache.org/jira/browse/AXIS2-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Björn Hamann updated AXIS2-3222:
Attachment: EfmService_1_0.wsdl
the wsdl
> OMException with the message "localname can not be null or empty"
> -
>
> Key: AXIS2-3222
> URL: https://issues.apache.org/jira/browse/AXIS2-3222
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.3
>Reporter: Björn Hamann
> Attachments: EfmService_1_0.wsdl
>
>
> I am getting an OMException in my generated MessageReiceiverInOut-Class when
> using a wsdl fault in my wsdl (enclosed).
> In the method invokeBusinessLogic the thrown EfmServiceException is caught an
> the method toOM is called to create the OMElement for the fault:
> if (e.getFaultMessage() != null){
> f.setDetail(toOM(e.getFaultMessage(),false));
> }
> In the method toOM the following code is generated to create the OMElement:
> factory.createOMElement(source, "", namespace);
> Here the empty string is raising a OMException with the message "localname
> can not be null or empty". If the e.getFaultMessage() returns null everything
> works fine, but of course no data is transportet to the client.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3222) OMException with the message "localname can not be null or empty"
[
https://issues.apache.org/jira/browse/AXIS2-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529350
]
Björn Hamann commented on AXIS2-3222:
-
I forgot to mention that the problem occurs when using jaxbri databinding.
> OMException with the message "localname can not be null or empty"
> -
>
> Key: AXIS2-3222
> URL: https://issues.apache.org/jira/browse/AXIS2-3222
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.3
>Reporter: Björn Hamann
> Attachments: EfmService_1_0.wsdl
>
>
> I am getting an OMException in my generated MessageReiceiverInOut-Class when
> using a wsdl fault in my wsdl (enclosed).
> In the method invokeBusinessLogic the thrown EfmServiceException is caught an
> the method toOM is called to create the OMElement for the fault:
> if (e.getFaultMessage() != null){
> f.setDetail(toOM(e.getFaultMessage(),false));
> }
> In the method toOM the following code is generated to create the OMElement:
> factory.createOMElement(source, "", namespace);
> Here the empty string is raising a OMException with the message "localname
> can not be null or empty". If the e.getFaultMessage() returns null everything
> works fine, but of course no data is transportet to the client.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2058) JiBX databinding doesn't work with eclipse code generator plugin
[ https://issues.apache.org/jira/browse/AXIS2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández resolved AXIS2-2058. Resolution: Fixed Fix Version/s: 1.3 > JiBX databinding doesn't work with eclipse code generator plugin > > > Key: AXIS2-2058 > URL: https://issues.apache.org/jira/browse/AXIS2-2058 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.1.1 > Environment: Windows XP Proffesional SP2, Java 1.5, Eclipse 3.2.1 >Reporter: Jorge Fernández >Assignee: Lahiru Sandakith >Priority: Minor > Fix For: 1.3 > > > These are the steps I followed: > 1 - Uncomment the line "databindingTypeCombo.add(DATA_BINDING_JIBX);" from > method > "private void fillDatabinderCombo() ;" in class > org.apache.axis2.tool.codegen.eclipse.ui.OptionsPage. > 2 - Compile the source code modified with eclipse IDE (as a standar Java > Project). Also tried with Ant 1.6.5 with the version 1.2.0 of the plugin > (Axis2 1.1). > 3 - Put the new classes generated into Axis2CodegenWizard.jar. (The size > changed from 77 to 98 KB) > 4 - Add following lines to plugin.xml > > > > > > > > > > 5 - Copy files axis2-jibx-1.1.1.jar, jibx-bind-1.1.3.jar and > jibx-run-1.1.3.jar to plugin's lib directory > And the problem was that when I tried to code generate with JiBX I got the > following Error: > an error occurred while completing process -java.lang.InterruptedException: > java.lang.RuntimeException: JiBX framework jars not in classpath -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Issue Comment Edited: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519821 ] informaticu007-pfc edited comment on AXIS2-3099 at 9/24/07 9:09 AM: - The problem is again in axis2 1.3 final release. Seems to be random was (Author: informaticu007-pfc): The problem is again in axis2 1.3 final release > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Minor > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3099) Internal server error when modifying axis2.xml in axis2 1.3 war distribution
[ https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández resolved AXIS2-3099. Resolution: Fixed Fix Version/s: 1.3 > Internal server error when modifying axis2.xml in axis2 1.3 war distribution > > > Key: AXIS2-3099 > URL: https://issues.apache.org/jira/browse/AXIS2-3099 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0, Java 6.0 >Reporter: Jorge Fernández >Priority: Minor > Fix For: 1.3 > > Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml, > excepcion.txt > > > Whenever I modify axis2.xml of the war distribution, I get an error page from > listServices page or when I display an WSDL > In Hapiness Page I see: > Examinin Version Service: > There was a problem in Axis2 version service , may be the service not > available or some thing has gone wrong. But this does not mean system is not > working ! Try to upload some other service and check to see whether it is > working. > For stoping that problem I have to backup and restore the original axis2.xml > file that came in the war distribution > When that happens I receive this at the client the message in the attached > file when invoking the service. > Also I can see that each time I run tomcat, my services.xml is updated, > apparently with no changes but is modified on disk and the same happens with > axis2.xml -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3225) Destroy method is called again when
Destroy method is called again when Key: AXIS2-3225 URL: https://issues.apache.org/jira/browse/AXIS2-3225 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Jorge Fernández -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3225) Destroy method is called again when undeploying Axis2
[ https://issues.apache.org/jira/browse/AXIS2-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández updated AXIS2-3225: --- Component/s: kernel Description: The problem here is that I invoke manually destroy when I want to close a session and when Axis2 is undeployed it's called again. It seems that sessions are not closed correctly the first time. As I clean some variables when I close my session, I get null pointer exception when destroy is called again. Environment: Windows XP SP2, Tomcat 6.0 Affects Version/s: 1.3 Summary: Destroy method is called again when undeploying Axis2 (was: Destroy method is called again when ) > Destroy method is called again when undeploying Axis2 > - > > Key: AXIS2-3225 > URL: https://issues.apache.org/jira/browse/AXIS2-3225 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.3 > Environment: Windows XP SP2, Tomcat 6.0 >Reporter: Jorge Fernández > > The problem here is that I invoke manually destroy when I want to close a > session and when Axis2 is undeployed it's called again. It seems that > sessions are not closed correctly the first time. > As I clean some variables when I close my session, I get null pointer > exception when destroy is called again. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3226) MTOM has problems when I create an attachtment from a byte array of zero elements
[ https://issues.apache.org/jira/browse/AXIS2-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Fernández updated AXIS2-3226: --- Attachment: message1.txt > MTOM has problems when I create an attachtment from a byte array of zero > elements > - > > Key: AXIS2-3226 > URL: https://issues.apache.org/jira/browse/AXIS2-3226 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Environment: Windows XP SP2, Tomcat 6.0 >Reporter: Jorge Fernández > Attachments: message1.txt > > > If I define a DataHandler from an ByteArrayDataSource and this one from a > byte array of zero elements, I get the following exception in the client: > org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME > Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) > at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:50213) > at client.Medici_LinkStub.getSignalData(Medici_LinkStub.java:6500) > at client.ClientUtilities.getSignalDataTest(ClientUtilities.java:600) > at client.Client.main(Client.java:172) > Caused by: org.apache.axiom.om.OMException: Referenced Attachment not found > in the MIME Message. > ContentID:1.urn:uuid:[EMAIL PROTECTED] > at > org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler(MTOMStAXSOAPModelBuilder.java:106)Closing > session... > at > client.Medici_LinkStub$ExtDataSegment$Factory.parse(Medici_LinkStub.java:34167) > at > client.Medici_LinkStub$ExtSignalData$Factory.parse(Medici_LinkStub.java:35862) > at > client.Medici_LinkStub$GetSignalDataResponse$Factory.parse(Medici_LinkStub.java:8777) > at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:49766) > ... 3 more -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3226) MTOM has problems when I create an attachtment from a byte array of zero elements
MTOM has problems when I create an attachtment from a byte array of zero elements - Key: AXIS2-3226 URL: https://issues.apache.org/jira/browse/AXIS2-3226 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: Windows XP SP2, Tomcat 6.0 Reporter: Jorge Fernández If I define a DataHandler from an ByteArrayDataSource and this one from a byte array of zero elements, I get the following exception in the client: org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:50213) at client.Medici_LinkStub.getSignalData(Medici_LinkStub.java:6500) at client.ClientUtilities.getSignalDataTest(ClientUtilities.java:600) at client.Client.main(Client.java:172) Caused by: org.apache.axiom.om.OMException: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] at org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler(MTOMStAXSOAPModelBuilder.java:106)Closing session... at client.Medici_LinkStub$ExtDataSegment$Factory.parse(Medici_LinkStub.java:34167) at client.Medici_LinkStub$ExtSignalData$Factory.parse(Medici_LinkStub.java:35862) at client.Medici_LinkStub$GetSignalDataResponse$Factory.parse(Medici_LinkStub.java:8777) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:49766) ... 3 more -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS-2700) axisproviderlib.sda for SAP XI
axisproviderlib.sda for SAP XI -- Key: AXIS-2700 URL: https://issues.apache.org/jira/browse/AXIS-2700 Project: Axis Issue Type: Bug Affects Versions: 1.4 Environment: Linux 2.6.5-7.252-smp #1 SMP Tue Feb 14 11:11:04 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux SAP XI 7.0 SP013 on NW04s Reporter: Enrique José Marcos Fix For: 1.4 In order to create an Axis SOAP Adapter, we have followed the instructions contained in the SAP note 1028961. According to these instructions, to use the Axis framework in the SOAP adapter, we must compress the following Axis JAR files, version 1.4, in aii_af_axisprovider.sda: axis.jar commons-discovery-0.2.jar commons-logging-1.0.4.jar commons-net-1.0.0-dev.jar wsdl4j-1.5.1.jar We've successfully deployed aii_af_axisprovider.sda from SDM but, when we try to verify the Axis Adapter accessing to http://hseedxi.na.holcim.net:55000/XIAxisAdapter/MessageServlet we obtain this error: Axis Adapter Message Servlet Component Versions Adapter Common Library Version: ??? Adapter Application Version: 1.7.0013.20070811203925., 645_VAL_REL (2007-08-11 20:39) Axis Version: ??? Required Components • Apache-Axis Error: required component missing java.lang.NoClassDefFoundError: org.apache.axis.AxisEngine --- looking for org.apache.axis.AxisEngine in com.sap.aii.af.axisproviderlib/axis.jar; see http://ws.apache.org/axis/ • Jakarta-Commons Discovery Found: org.apache.commons.discovery.Resource at /usr/sap/DXI/DVEBMGS50/j2ee/cluster/server0/bin/ext/com.sap.aii.af.axisproviderlib/commons-discovery-0.2.jar • Jakarta-Commons Logging Found: org.apache.commons.logging.Log at /usr/sap/DXI/DVEBMGS50/j2ee/cluster/server0/bin/ext/com.sap.aii.af.axisproviderlib/commons-logging-1.0.4.jar Number of Missing Components: 1 Status: Error Optional Components • XML Security API Warning: optional component missing --- looking for org.apache.xml.security.Init in com.sap.aii.af.axisproviderlib/xmlsec.jar; see http://xml.apache.org/security/ • Apache Xalan Found: org.apache.xalan.Version at unknown • Jakarta-Commons Codec Warning: optional component missing --- looking for org.apache.commons.codec.Encoder in com.sap.aii.af.axisproviderlib/commons-codec.jar; see http://jakarta.apache.org/commons/codec/ • Jakarta-Commons Net Found: org.apache.commons.net.SocketFactory at /usr/sap/DXI/DVEBMGS50/j2ee/cluster/server0/bin/ext/com.sap.aii.af.axisproviderlib/commons-net-1.0.0-dev.jar • Jakarta-Commons HttpClient Warning: optional component missing --- looking for org.apache.commons.httpclient.HttpClient in com.sap.aii.af.axisproviderlib/commons-httpclient.jar; see http://jakarta.apache.org/commons/httpclient/ • Apache WSS4J Warning: optional component missing --- looking for org.apache.ws.security.WSSConfig in com.sap.aii.af.axisproviderlib/wss4j.jar; see http://ws.apache.org/wss4j/ • Apache Addressing Warning: optional component missing --- looking for org.apache.axis.message.addressing.Constants in com.sap.aii.af.axisproviderlib/addressing.jar; see http://ws.apache.org/addressing/ • Apache Sandesha Warning: optional component missing --- looking for org.apache.sandesha.Constants in com.sap.aii.af.axisproviderlib/Sandesha.jar; see http://ws.apache.org/sandesha/ Number of Missing Components: 6 Status: Warning $Id: //tc/xi/645_VAL_REL/src/_adapterframework/_axis/_ee/java/com/sap/aii/adapter/axis/web/MessageServlet.java#2 $ -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS-2664) Axis generate invalid soap when using RPC/encoded where exists omittable fields (minOccurs=0) and nillable=false
[
https://issues.apache.org/jira/browse/AXIS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537566
]
Marinó A. Jónsson commented on AXIS-2664:
-
I just hit this snag. My first google hit was issue AXIS-2054, which really
explains in detail my problem. The "resolution" for that issue, however, is
too superficial and doesn't work for me.
The key point Patrick makes here is that when a field _is not_ nillable but
_is_ omittable it should indeed be omitted.
So - a compromise might look something like this:
// if meta data says minOccurs=0, then we should skip
// it if its value is null and either it's not nillable or we
// aren't doing SOAP encoding.
if (isOmittable && (!isNillable || !isEncoded)) {
continue;
}
> Axis generate invalid soap when using RPC/encoded where exists omittable
> fields (minOccurs=0) and nillable=false
>
>
> Key: AXIS-2664
> URL: https://issues.apache.org/jira/browse/AXIS-2664
> Project: Axis
> Issue Type: Bug
> Components: Serialization/Deserialization
>Affects Versions: 1.4
>Reporter: Patrick Di Loreto
>
> While using axis 1.4 with webMethods EAI system I have encountered the
> following problem :
> Axis generate an invalid soap message in RPC/encoded WS where exists
> omittable (minOccurs="0") fields and nillable = "false".
> Axis don't omit the field when null but put it in soap message with nill
> value.
> Exploring source code I have found the following check in
> org.apache.axis.encoding.ser.BeanSerializer.java class at row : 222
> // if meta data says minOccurs=0, then we can skip
> // it if its value is null and we aren't doing
> SOAP
> // encoding.
> if (isOmittable && !isEncoded) {
> continue;
> }
> It seams a choice to not apply omittable behavior while using soap/encoding.
> Is it correct ? Is it a standard ? WebMethods aspect that this field was
> omitted and not nill.
> I fixed it just as follow :
> // if meta data says minOccurs=0, then we can skip
> // it if its value is null and we aren't doing
> SOAP
> // encoding.
> if (isOmittable){ // && !isEncoded) {
> continue;
> }
> What can I aspect on next version of Axis ?
> Thx
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-3183) Client stub generation fails for WSDL's with wsdl:import
[ https://issues.apache.org/jira/browse/AXIS2-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Jörg Hessmann closed AXIS2-3183. - I verified this with the nightly build of 17-Oct-2007. It works perfectly, now. Thanks a lot! > Client stub generation fails for WSDL's with wsdl:import > > > Key: AXIS2-3183 > URL: https://issues.apache.org/jira/browse/AXIS2-3183 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.3 > Environment: Eclipse 3.3 on Windows XP using Axis-2 1.3. > The imported WebService was hosted on a SAP Netweaver 7.0. >Reporter: Hans Jörg Hessmann > Attachments: WSDLdocument.zip > > > Axis2 1.3 is unable to generate a client stub for a simple echo service > that's WSDL is has been spread over several files. To reproduce save the > following WSDL files in a directory structure like this: > main.wsdl > bindings/WebserTestBasicAuth_document.wsdl > porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl > ---x--- contents of main.wsdl ---x--- > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; name="WebserviceTestWsd" > targetNamespace="urn:WebserviceTestWsd" > xmlns:bns0="urn:WebserviceTestWsd/WebserTestBasicAuth/document" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> >namespace="urn:WebserviceTestWsd/WebserTestBasicAuth/document"/> > > binding="bns0:WebserTestBasicAuthBinding"> >location="http://mp5db.metrogroup-networking.com:50500/WebserviceTest/WebserTestBasicAuth?style=document"/> > > > > ---x--- contents of bindings/WebserTestBasicAuth_document.wsdl ---x--- > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > targetNamespace="urn:WebserviceTestWsd/WebserTestBasicAuth/document" > xmlns:prt0="urn:WebserviceTestWsd/WebserviceTestVi/document" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> >location="../porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl" > namespace="urn:WebserviceTestWsd/WebserviceTestVi/document"/> >type="prt0:WebserviceTestVi_Document"> > http://schemas.xmlsoap.org/soap/http"; > style="document"/> > > > > > > > > > > > > ---x--- contents of > porttypes/WebserTestBasicAuth_WebserviceTestVi_document.wsdl ---x--- > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:ns0="urn:WebserviceTestVi" > targetNamespace="urn:WebserviceTestWsd/WebserviceTestVi/document" > xmlns:tns="urn:WebserviceTestWsd/WebserviceTestVi/document"> > > http://www.w3.org/2001/XMLSchema"; > targetNamespace="urn:WebserviceTestVi" xmlns:tns="urn:WebserviceTestVi" > elementFormDefault="qualified"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ---x--x--- > Axis-1 accepts theses files and I was able to generate an axis-2 client stub > after I merged the WSDL's manually into one file. It looks like axis-2 has a > problem with wsdl:import. Replacing the relative pathes with absolute pathes > and hosting the WSDL on a server doesn't help either. > The full stacktrace was: > Exception occurred while code generation for WSDL null > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > org.eclipse.jst.ws.axis2.consumption.core.utils.WSDL2JavaGenerator.getAxisService(WSDL2JavaGenerator.java:379) > at > org.eclipse.jst.ws.axis2.consumption.core.command.Axis2ClientCodegenCommand.execute(Axis2ClientCodegenCommand.java:89) > at > org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:418) > at > org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentE
[jira] Created: (AXIS2-3312) Switch to XmlBeans 2.3.0. Adapt to xmlbeans dependency renaming.
Switch to XmlBeans 2.3.0. Adapt to xmlbeans dependency renaming. Key: AXIS2-3312 URL: https://issues.apache.org/jira/browse/AXIS2-3312 Project: Axis 2.0 (Axis2) Issue Type: Improvement Affects Versions: 1.4 Reporter: Felix Röthenbacher Priority: Minor Fix For: 1.4 XmlBeans renamed its Maven dependency to org.apache.xmlbeans with version 2.3.0 Update to 2.3.0 and update dependencies. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3312) Switch to XmlBeans 2.3.0. Adapt to xmlbeans dependency renaming.
[ https://issues.apache.org/jira/browse/AXIS2-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Röthenbacher updated AXIS2-3312: -- Attachment: axis2-xmlbeans-2.3.0.diff Patch for updating to org.apache.xmlbeans:xmlbeans:jar 2.3.0. > Switch to XmlBeans 2.3.0. Adapt to xmlbeans dependency renaming. > > > Key: AXIS2-3312 > URL: https://issues.apache.org/jira/browse/AXIS2-3312 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Felix Röthenbacher >Priority: Minor > Fix For: 1.4 > > Attachments: axis2-xmlbeans-2.3.0.diff > > > XmlBeans renamed its Maven dependency to org.apache.xmlbeans with version > 2.3.0 > Update to 2.3.0 and update dependencies. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1220) AxisServlet.initContextRoot assumes 1 level deep context
[
https://issues.apache.org/jira/browse/AXIS2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545880
]
Olof Jönsson commented on AXIS2-1220:
-
I've embedded axis2 into OSGi and I'm using the HTTP service. Unfortunately, I
get the same problem here where the endpoint references lack the actual path to
the servlet. I get http://localhost:8080/service/... directly in the WSDL
instead of http://localhost:8080/axis2/service when the servlet is deployed on
"/axis2". Isn't the problem here that getServletPath() isn't used? I changed
the following lines of initContextRoot():
String contextPath = req.getContextPath();
//handling ROOT scenario, for servlets in the default (root) context,
this method returns ""
if (contextPath != null && contextPath.length() == 0) {
contextPath = "/";
}
this.contextRoot = contextPath;
into this single line:
this.contextRoot = req.getContextPath() + req.getServletPath();
which corrected the problem for me.
> AxisServlet.initContextRoot assumes 1 level deep context
>
>
> Key: AXIS2-1220
> URL: https://issues.apache.org/jira/browse/AXIS2-1220
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.1
> Environment: all
>Reporter: Bob Stevenson
>Assignee: Deepal Jayasinghe
>
> initContextRoot only grabs the first part of the context. My context is
> /shop/wsengine , but this routine sets the contextRoot to only /shop.
> Then getEPRsForService() seems to rely on this for building the endpoints,
> which are incorrect.
> if (contextRoot == null) {
> String [] parts = JavaUtils.split(req.getContextPath(), '/');
> if (parts != null) {
> for (int i = 0; i < parts.length; i++) {
> if (parts[i].length() > 0) {
> contextRoot = parts[i];
> break;
> }
> }
> }
> if (contextRoot == null || req.getContextPath().equals("/")) {
> contextRoot = "/";
> }
> log.warn("contextRoot2: " + req.getContextPath());
> //configContext.setContextRoot(contextRoot);
> configContext.setContextRoot(req.getContextPath());
> }
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3373) Axis2 fails to parse "Multipart/Related"-Messages from SAAJ-Webservice
Axis2 fails to parse "Multipart/Related"-Messages from SAAJ-Webservice
--
Key: AXIS2-3373
URL: https://issues.apache.org/jira/browse/AXIS2-3373
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.3, 1.4
Environment: Axis2 1.3 Client
Spring-WS (SAAJ 1.3) Webservice
Reporter: Herbert Gerngroß
Axis2 fails to parse a "Multipart/Related"-MTOM-Message sent from
Spring-WS-Webservice (SAAJ 1.3).
The AxisConfigBuilder-Class in package org.apache.axis2.deployment registers a
MIMEBuilder-Instance for contentType "multipart/related".
When the client parses an incoming message it uses
org.apache.axis2.builder.BuilderUtil.getBuilderFromSelector(String type,
MessageContext msgContext) to find a adequate builder for the message.
Because this lookup is case-sensitive no MIMEBuilder is found.
The result is the following error stacktrace:
org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxUnexpectedCharException:
Unexpected character '-' (code 45) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:89)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
at.gv.brz.springplz.webservice.plz.PLZSucheServiceStub.GetAllPLZObjectsAsPdf(PLZSucheServiceStub.java:1509)
at
at.gv.brz.springplz.webservice.client.PLZSucheTestCase.test6PLZSucheGetAllPLZObjectsAsPdf(PLZSucheTestCase.java:237)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code
45) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:161)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:110)
at
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:610)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:178)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87)
... 24 more
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
'-' (code 45) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:623)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:153)
... 30 more
--
This message is
[jira] Updated: (AXIS2-3373) Axis2 fails to parse "Multipart/Related"-Messages from SAAJ-Webservice
[
https://issues.apache.org/jira/browse/AXIS2-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herbert Gerngroß updated AXIS2-3373:
Attachment: BuilderUtil_14_patch.java
Changed Builder-Lookup in BuilderUtil.getBuilderFromSelector(String type,
MessageContext msgContext)
from:
Builder builder = configuration.getMessageBuilder(type);
to:
Builder builder = configuration.getMessageBuilder(type.toLowerCase());
With this patch Axis2 can parse MIME-Message sent from Spring-WS (SAAJ)
> Axis2 fails to parse "Multipart/Related"-Messages from SAAJ-Webservice
> --
>
> Key: AXIS2-3373
> URL: https://issues.apache.org/jira/browse/AXIS2-3373
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.4, 1.3
> Environment: Axis2 1.3 Client
> Spring-WS (SAAJ 1.3) Webservice
>Reporter: Herbert Gerngroß
> Attachments: BuilderUtil_14_patch.java
>
>
> Axis2 fails to parse a "Multipart/Related"-MTOM-Message sent from
> Spring-WS-Webservice (SAAJ 1.3).
> The AxisConfigBuilder-Class in package org.apache.axis2.deployment registers
> a MIMEBuilder-Instance for contentType "multipart/related".
> When the client parses an incoming message it uses
> org.apache.axis2.builder.BuilderUtil.getBuilderFromSelector(String type,
> MessageContext msgContext) to find a adequate builder for the message.
> Because this lookup is case-sensitive no MIMEBuilder is found.
> The result is the following error stacktrace:
> org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxUnexpectedCharException:
> Unexpected character '-' (code 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
> at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:89)
> at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> at
> at.gv.brz.springplz.webservice.plz.PLZSucheServiceStub.GetAllPLZObjectsAsPdf(PLZSucheServiceStub.java:1509)
> at
> at.gv.brz.springplz.webservice.client.PLZSucheTestCase.test6PLZSucheGetAllPLZObjectsAsPdf(PLZSucheTestCase.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code
> 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239)
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:161)
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:110)
>
[jira] Commented: (AXIS2-3412) Custom exception handling issue with pojos
[
https://issues.apache.org/jira/browse/AXIS2-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553655
]
Pär Malmqvist commented on AXIS2-3412:
--
Note that this JIRA includes two issues.
The first issue is that the code doesn't compile for a nightly build.
The second issue is that Custom Exceptions probably not is handled that well
when using "code-first" approach.
Its hard to catch the custom exceptions at client side.
So dont forget to check this link please,
http://marc.info/?l=axis-user&m=119805625224409&w=2
> Custom exception handling issue with pojos
> --
>
> Key: AXIS2-3412
> URL: https://issues.apache.org/jira/browse/AXIS2-3412
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
>Affects Versions: nightly
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Assignee: Amila Chinthaka Suriarachchi
>Priority: Critical
> Attachments: CustomexceptionService.aar
>
>
> 'Duplicate nested type CustomException' Compile error can be seen in the
> generated stub if a service is deployed using a pojo which throws a custom
> exception.
> A similar issue has been reported by par Malmqvist in the Axis2 user list.
> See http://marc.info/?l=axis-user&m=119805625224409&w=2 for more information.
> Steps to reproduce:
> ===
> 1. Create service impl class and custom exception class as follows
> public class CustomexceptionService {
>
> public int addOneToPositiveValue(int value) throws CustomException {
> if(value < 1) {
> throw(new CustomException());
> }
>
> return(value + 1);
> }
> }
> public class CustomException extends Exception{
>
>private static final long serialVersionUID = 9;
> public CustomException() {
> super();
> }
> public String toString() {
> return(super.toString() + "org.test.CustomException");
> }
> }
> 2. Create a service archive and deploy the service
> 3. Generate client stub using the ?wsdl of the service
> wsdl2java.bat -uri
> http://10.100.1.118:9762/services/CustomExceptionService?wsdl -o
> C:\wsas\wsas-2.2\qa-build2\wso2wsas-SNAPSHOT\bin\out -p org.mytest
> 4. Check the generated stub
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3418) Unexpected subelement - pojo - Inherited Complex Type
Unexpected subelement - pojo - Inherited Complex Type - Key: AXIS2-3418 URL: https://issues.apache.org/jira/browse/AXIS2-3418 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.3 Environment: jdk jdk1.5.0_14, axis2 1.3, Fedora 8, Intel x86 Reporter: Mehmet Döngel $AXİS2_HOME/samples/pojo sample, I created ZEntry class with "String custom" field and updated Entry class to extend ZEntry class, after deployment I build and run adb client and got org.apache.axis2.databinding.ADBException: Unexpected subelement city exception. Response Message: http://www.w3.org/2003/05/soap-envelope";> http://service.addressbook.sample";> http://entry.addressbook.sample/xsd"; type="sample.addressbook.entry.Entry"> Sesame City Abby Cadabby 1 Sesame State Sesame Street http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/> Reason for that exception is that generated stub expects first "custom" element because schema for Entry and ZEntry class in wsdl is : * http://entry.addressbook.sample/xsd"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://entry.addressbook.sample/xsd";> * Reason for expected response (first Entry fields (city,name,postalCode,state,street) and then super class ZEntry fields (custom) ) is BeanUtil class takes all the fields and put to an arraylist and then sort that array list. Because ZEntry.custom field comes after Entry.xxx fields,custom element is serialized last. When I use AEntry class instead of ZEntry class, no problem occurs. My solution to this problem is changing BeanUtil class in such a way that, first get super class properties and sort that properties and then put to an arrayList containing all properties, and after that get sub class properties and sort that properties and then put to that arrayList. Any other ideas, solutions? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3418) Unexpected subelement - pojo - Inherited Complex Type
[ https://issues.apache.org/jira/browse/AXIS2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehmet Döngel updated AXIS2-3418: - Attachment: pojo_Working.tar.gz AddressBookService_Working.wsdl AddressBookService_NotWorking.wsdl > Unexpected subelement - pojo - Inherited Complex Type > - > > Key: AXIS2-3418 > URL: https://issues.apache.org/jira/browse/AXIS2-3418 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: adb >Affects Versions: 1.3 > Environment: jdk jdk1.5.0_14, axis2 1.3, Fedora 8, Intel x86 >Reporter: Mehmet Döngel > Attachments: AddressBookService_NotWorking.wsdl, > AddressBookService_Working.wsdl, pojo_NotWorking.tar.gz, pojo_Working.tar.gz > > > $AXİS2_HOME/samples/pojo sample, > I created ZEntry class with "String custom" field and updated Entry class to > extend ZEntry class, after deployment I build and run adb client and got > org.apache.axis2.databinding.ADBException: Unexpected subelement city > exception. > Response Message: > > http://www.w3.org/2003/05/soap-envelope";> > > http://service.addressbook.sample";> > http://entry.addressbook.sample/xsd"; > type="sample.addressbook.entry.Entry"> > Sesame City > Abby Cadabby > 1 > Sesame State > Sesame Street > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/> > > > > > Reason for that exception is that generated stub expects first "custom" > element because schema for Entry and ZEntry class in wsdl is : > * > http://entry.addressbook.sample/xsd"; > attributeFormDefault="qualified" elementFormDefault="qualified" > targetNamespace="http://entry.addressbook.sample/xsd";> > > > type="xs:string"/> > > > > > > > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > > > > > > * > Reason for expected response (first Entry fields > (city,name,postalCode,state,street) and then super class ZEntry fields > (custom) ) is BeanUtil class takes all the fields and put to an arraylist > and then sort that array list. Because ZEntry.custom field comes after > Entry.xxx fields,custom element is serialized last. > When I use AEntry class instead of ZEntry class, no problem occurs. > My solution to this problem is changing BeanUtil class in such a way that, > first get super class properties and sort that properties and then put to an > arrayList containing all properties, and after that get sub class properties > and sort that properties and then put to that arrayList. > Any other ideas, solutions? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3418) Unexpected subelement - pojo - Inherited Complex Type
[ https://issues.apache.org/jira/browse/AXIS2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehmet Döngel updated AXIS2-3418: - Attachment: pojo_NotWorking.tar.gz > Unexpected subelement - pojo - Inherited Complex Type > - > > Key: AXIS2-3418 > URL: https://issues.apache.org/jira/browse/AXIS2-3418 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: adb >Affects Versions: 1.3 > Environment: jdk jdk1.5.0_14, axis2 1.3, Fedora 8, Intel x86 >Reporter: Mehmet Döngel > Attachments: AddressBookService_NotWorking.wsdl, > AddressBookService_Working.wsdl, pojo_NotWorking.tar.gz, pojo_Working.tar.gz > > > $AXİS2_HOME/samples/pojo sample, > I created ZEntry class with "String custom" field and updated Entry class to > extend ZEntry class, after deployment I build and run adb client and got > org.apache.axis2.databinding.ADBException: Unexpected subelement city > exception. > Response Message: > > http://www.w3.org/2003/05/soap-envelope";> > > http://service.addressbook.sample";> > http://entry.addressbook.sample/xsd"; > type="sample.addressbook.entry.Entry"> > Sesame City > Abby Cadabby > 1 > Sesame State > Sesame Street > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/> > > > > > Reason for that exception is that generated stub expects first "custom" > element because schema for Entry and ZEntry class in wsdl is : > * > http://entry.addressbook.sample/xsd"; > attributeFormDefault="qualified" elementFormDefault="qualified" > targetNamespace="http://entry.addressbook.sample/xsd";> > > > type="xs:string"/> > > > > > > > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > > > > > > * > Reason for expected response (first Entry fields > (city,name,postalCode,state,street) and then super class ZEntry fields > (custom) ) is BeanUtil class takes all the fields and put to an arraylist > and then sort that array list. Because ZEntry.custom field comes after > Entry.xxx fields,custom element is serialized last. > When I use AEntry class instead of ZEntry class, no problem occurs. > My solution to this problem is changing BeanUtil class in such a way that, > first get super class properties and sort that properties and then put to an > arrayList containing all properties, and after that get sub class properties > and sort that properties and then put to that arrayList. > Any other ideas, solutions? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3418) Unexpected subelement - pojo - Inherited Complex Type
[ https://issues.apache.org/jira/browse/AXIS2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehmet Döngel updated AXIS2-3418: - Attachment: BeanUtil.java > Unexpected subelement - pojo - Inherited Complex Type > - > > Key: AXIS2-3418 > URL: https://issues.apache.org/jira/browse/AXIS2-3418 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: adb >Affects Versions: 1.3 > Environment: jdk jdk1.5.0_14, axis2 1.3, Fedora 8, Intel x86 >Reporter: Mehmet Döngel > Attachments: AddressBookService_NotWorking.wsdl, > AddressBookService_Working.wsdl, BeanUtil.java, pojo_NotWorking.tar.gz, > pojo_Working.tar.gz > > > $AXİS2_HOME/samples/pojo sample, > I created ZEntry class with "String custom" field and updated Entry class to > extend ZEntry class, after deployment I build and run adb client and got > org.apache.axis2.databinding.ADBException: Unexpected subelement city > exception. > Response Message: > > http://www.w3.org/2003/05/soap-envelope";> > > http://service.addressbook.sample";> > http://entry.addressbook.sample/xsd"; > type="sample.addressbook.entry.Entry"> > Sesame City > Abby Cadabby > 1 > Sesame State > Sesame Street > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/> > > > > > Reason for that exception is that generated stub expects first "custom" > element because schema for Entry and ZEntry class in wsdl is : > * > http://entry.addressbook.sample/xsd"; > attributeFormDefault="qualified" elementFormDefault="qualified" > targetNamespace="http://entry.addressbook.sample/xsd";> > > > type="xs:string"/> > > > > > > > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > > > > > > * > Reason for expected response (first Entry fields > (city,name,postalCode,state,street) and then super class ZEntry fields > (custom) ) is BeanUtil class takes all the fields and put to an arraylist > and then sort that array list. Because ZEntry.custom field comes after > Entry.xxx fields,custom element is serialized last. > When I use AEntry class instead of ZEntry class, no problem occurs. > My solution to this problem is changing BeanUtil class in such a way that, > first get super class properties and sort that properties and then put to an > arrayList containing all properties, and after that get sub class properties > and sort that properties and then put to that arrayList. > Any other ideas, solutions? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3418) Unexpected subelement - pojo - Inherited Complex Type
[ https://issues.apache.org/jira/browse/AXIS2-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehmet Döngel updated AXIS2-3418: - Priority: Critical (was: Major) > Unexpected subelement - pojo - Inherited Complex Type > - > > Key: AXIS2-3418 > URL: https://issues.apache.org/jira/browse/AXIS2-3418 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: adb >Affects Versions: 1.3 > Environment: jdk jdk1.5.0_14, axis2 1.3, Fedora 8, Intel x86 >Reporter: Mehmet Döngel >Priority: Critical > Attachments: AddressBookService_NotWorking.wsdl, > AddressBookService_Working.wsdl, BeanUtil.java, pojo_NotWorking.tar.gz, > pojo_Working.tar.gz > > > $AXİS2_HOME/samples/pojo sample, > I created ZEntry class with "String custom" field and updated Entry class to > extend ZEntry class, after deployment I build and run adb client and got > org.apache.axis2.databinding.ADBException: Unexpected subelement city > exception. > Response Message: > > http://www.w3.org/2003/05/soap-envelope";> > > http://service.addressbook.sample";> > http://entry.addressbook.sample/xsd"; > type="sample.addressbook.entry.Entry"> > Sesame City > Abby Cadabby > 1 > Sesame State > Sesame Street > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/> > > > > > Reason for that exception is that generated stub expects first "custom" > element because schema for Entry and ZEntry class in wsdl is : > * > http://entry.addressbook.sample/xsd"; > attributeFormDefault="qualified" elementFormDefault="qualified" > targetNamespace="http://entry.addressbook.sample/xsd";> > > > type="xs:string"/> > > > > > > > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > nillable="true" type="xs:string"/> > > > > > > * > Reason for expected response (first Entry fields > (city,name,postalCode,state,street) and then super class ZEntry fields > (custom) ) is BeanUtil class takes all the fields and put to an arraylist > and then sort that array list. Because ZEntry.custom field comes after > Entry.xxx fields,custom element is serialized last. > When I use AEntry class instead of ZEntry class, no problem occurs. > My solution to this problem is changing BeanUtil class in such a way that, > first get super class properties and sort that properties and then put to an > arrayList containing all properties, and after that get sub class properties > and sort that properties and then put to that arrayList. > Any other ideas, solutions? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3487) Dependency resolution mess with axis2-wsdl2code-maven-plugin
[ https://issues.apache.org/jira/browse/AXIS2-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Röthenbacher updated AXIS2-3487: -- Attachment: WSDL2CodeMojo.java.diff Patch removing code interfering with standard Maven dependency resolution. Any dependencies necessary at compile time should be added in project pom, not programmatically by a plugin. > Dependency resolution mess with axis2-wsdl2code-maven-plugin > > > Key: AXIS2-3487 > URL: https://issues.apache.org/jira/browse/AXIS2-3487 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Reporter: Felix Röthenbacher > Fix For: 1.4 > > Attachments: WSDL2CodeMojo.java.diff > > > axis2-wsdl2code-maven-plugin programmatically adds dependencies during build > process messing up regular behaviour of Maven. Plugin dependencies are added > as regular project artifact dependencies bringing in these dependencies into > regular compile process and are not removed after plugin execution. These > programmatically added dependencies interfere with standard Maven dependency > management/resolution. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3487) Dependency resolution mess with axis2-wsdl2code-maven-plugin
Dependency resolution mess with axis2-wsdl2code-maven-plugin Key: AXIS2-3487 URL: https://issues.apache.org/jira/browse/AXIS2-3487 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Reporter: Felix Röthenbacher Fix For: 1.4 axis2-wsdl2code-maven-plugin programmatically adds dependencies during build process messing up regular behaviour of Maven. Plugin dependencies are added as regular project artifact dependencies bringing in these dependencies into regular compile process and are not removed after plugin execution. These programmatically added dependencies interfere with standard Maven dependency management/resolution. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1900) December 20 nightly build -- jsp exception
[ https://issues.apache.org/jira/browse/AXIS2-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568571#action_12568571 ] Mario NUñez commented on AXIS2-1900: Hi Santiago, i had same problem, i were using tomcat 5.5.20, axis2-1.1 and java1.6. I had found that the problem is with java version, later i tried with java1.5 and the axis2 admin page loads perfectly. Try it out. bye! > December 20 nightly build -- jsp exception > -- > > Key: AXIS2-1900 > URL: https://issues.apache.org/jira/browse/AXIS2-1900 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: admin console >Affects Versions: nightly > Environment: Tomcat 5.5.15, axis2 1.1.1 nightly >Reporter: Gul Onural > Attachments: localhost.2006-12-20.log > > > I have downloaded the December 20, axis2 nightly build axis2.war and > installed in tomcat. > When I try to access axis2 admin page (http://localhost:8080/axis2/) from a > web browser I get > following jsp exception. Tomcat log is also attached. > Gul > HTTP Status 500 - > type Exception report > message > description The server encountered an internal error () that prevented it > from fulfilling this request. > exception > org.apache.jasper.JasperException: Exception in JSP: /axis2-web/index.jsp:23 > 20: */ > 21: %> > 22: > 23: > 24: Axis 2 - Home > 25: type="text/css"/> > 26: > Stacktrace: > > org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:504) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > root cause > org.apache.jasper.JasperException > > org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) > > org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > root cause > java.lang.NullPointerException > > org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(org.apache.jsp.axis2_002dweb.include.httpbase_jsp:22) > org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:78) > > org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:155) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) > > org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > note The full stack trace of the root cause is available in the Apache > Tomcat/5.5.15 logs. > Apache Tomcat/5.5.15 -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS-2065) Serialization of (Integer-)array in array not compatible with .NET
Serialization of (Integer-)array in array not compatible with .NET
--
Key: AXIS-2065
URL: http://issues.apache.org/jira/browse/AXIS-2065
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions: 1.2, 1.2.1
Environment: Windows XP, Tomcat 5.0
Reporter: Jürgen Moßgraber
I have the following WSDL code:
The value paramter may contain an array which was serialized in 1.2RC3 like
this:
1.2 RC3:
http://schemas.xmlsoap.org/soap/encoding/";
xsi:type="ns13:Param">
children
In 1.2 and 1.2.1 "item" was changed to "value" which can't be (strangely) not
deserialized with a .NET (C#) client:
http://schemas.xmlsoap.org/soap/encoding/";
xsi:type="ns11:Param">
children
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (AXIS-2071) ant task axis-java2wsdl classpathref does not work
ant task axis-java2wsdl classpathref does not work -- Key: AXIS-2071 URL: http://issues.apache.org/jira/browse/AXIS-2071 Project: Apache Axis Type: Bug Versions: 1.2.1 Environment: Win XP, JDK 1.4.2 Reporter: Haug Bürger ant task axis-java2wsdl classpathref attribute deos not work the complexType classes must be part of the taskdef classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS-2070) axis-1_2_1/docs/ant/axis-java2wsdl.html complexType fields missing
axis-1_2_1/docs/ant/axis-java2wsdl.html complexType fields missing -- Key: AXIS-2070 URL: http://issues.apache.org/jira/browse/AXIS-2070 Project: Apache Axis Type: Bug Components: Documentation Versions: 1.2.1 Reporter: Haug Bürger ant task description incomplete! The complexType fields missing completly. axis-1_2_1/docs/ant/axis-java2wsdl.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Erstellt: (AXIS-2075) 59f0 added if HTTP/1.1 is used
59f0 added if HTTP/1.1 is used --- Key: AXIS-2075 URL: http://issues.apache.org/jira/browse/AXIS-2075 Project: Apache Axis Type: Bug Components: Basic Architecture Versions: 1.2.1 Environment: Windows XP, JDK 1.4.2 Reporter: Haug Bürger The response contains 59f before the XML begins and a 0 afterwards. Traced with tcpmon. POST /tws/services/TestWS HTTP/1.1 Accept: text/xml SOAPAction: "" Content-Type: text/xml User-Agent: Borland SOAP 1.1 Host: localhost:8085 Content-Length: 587 Connection: Keep-Alive Cache-Control: no-cache http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";>http://schemas.xmlsoap.org/soap/encoding/";>service:TestWS";>1234 HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=utf-8 Transfer-Encoding: chunked Date: Wed, 22 Jun 2005 09:04:26 GMT 59f http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>service:TestWS";>service:TestWS";>121DisplayText-1address01falseabcdöservice:TestWS";>221DisplayText-1address01falseabcdö 0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Kommentiert: (AXIS-2075) 59f0 added if HTTP/1.1 is used
[ http://issues.apache.org/jira/browse/AXIS-2075?page=comments#action_12314208 ] Haug Bürger commented on AXIS-2075: --- Resending the same message with POST /tws/services/TestWS HTTP/1.0 solves the issue. > 59f0 added if HTTP/1.1 is used > --- > > Key: AXIS-2075 > URL: http://issues.apache.org/jira/browse/AXIS-2075 > Project: Apache Axis > Type: Bug > Components: Basic Architecture > Versions: 1.2.1 > Environment: Windows XP, JDK 1.4.2 > Reporter: Haug Bürger > > The response contains 59f before the XML begins and a 0 afterwards. Traced > with tcpmon. > POST /tws/services/TestWS HTTP/1.1 > Accept: text/xml > SOAPAction: "" > Content-Type: text/xml > User-Agent: Borland SOAP 1.1 > Host: localhost:8085 > Content-Length: 587 > Connection: Keep-Alive > Cache-Control: no-cache > > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> xmlns:NS1="service:TestWS";>1 xsi:type="xsd:int">23 xsi:type="xsd:int">4 > HTTP/1.1 200 OK > Server: Apache-Coyote/1.1 > Content-Type: text/xml;charset=utf-8 > Transfer-Encoding: chunked > Date: Wed, 22 Jun 2005 09:04:26 GMT > 59f > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> xmlns="service:TestWS";> xsi:type="ns1:PTLInfoElement" > xmlns:ns1="service:TestWS";>121DisplayText-1address01falseabcdö xsi:type="ns2:PTLInfoElement" > xmlns:ns2="service:TestWS";>221DisplayText-1address01falseabcdö > 0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS-2076) WebappClassLoader: Lifecycle error : CL stopped
WebappClassLoader: Lifecycle error : CL stopped
---
Key: AXIS-2076
URL: http://issues.apache.org/jira/browse/AXIS-2076
Project: Apache Axis
Type: Bug
Components: Basic Architecture
Versions: 1.2.1
Environment: Tomcat 4
Reporter: Daniel David Schäfer
Priority: Minor
After a webapp containing the AxisServlet was reloaded (e.g. touch on the
web.xml) I get the message
WebappClassLoader: Lifecycle error : CL stopped
This happens because Axis continues to use the old configuration with the old
webapp-classloader.
I have located a place where a wrong parameter leads to this behaviour.
in org.apache.axis.transport.http.AxisServletBase there is a piece of code that
tries to locate the axis-configuration:
EngineConfiguration config =
EngineConfigurationFactoryFinder.newFactory(servlet)
.getServerEngineConfig();
This call is passed to EngineConfigurationFactoryServlet.newFactory.(Object
param) which checks if
the given param is an instance of ServletConfig. Unfortunately the calling code
did not provide a ServletConfig but a HttpServlet.
I patched this in the code below.
I did not make use of the EngineConfigurationFactoryFinder instead I directly
called the EngineConfigurationFactoryServlet,
because it has no risk to confuse the required configuration in this context.
===
RCS file:
/usr/local/cvsroot/dev_projects/axis121/src/org/apache/axis/transport/http/AxisServletBase.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
---
dev_projects/axis121/src/org/apache/axis/transport/http/AxisServletBase.java
2005/06/22 07:05:27 1.3
+++
dev_projects/axis121/src/org/apache/axis/transport/http/AxisServletBase.java
2005/06/22 07:49:29 1.4
@@ -35,6 +35,7 @@
import org.apache.axis.EngineConfiguration;
import org.apache.axis.components.logger.LogFactory;
import org.apache.axis.configuration.EngineConfigurationFactoryFinder;
+import org.apache.axis.configuration.EngineConfigurationFactoryServlet;
import org.apache.axis.server.AxisServer;
import org.apache.axis.utils.JavaUtils;
import org.apache.commons.logging.Log;
@@ -270,9 +271,8 @@
environment.put(AxisEngine.ENV_SERVLET_REALPATH,
webInfPath + File.separator + "attachments");
-EngineConfiguration config =
-EngineConfigurationFactoryFinder.newFactory(servlet)
-.getServerEngineConfig();
+EngineConfiguration config =
EngineConfigurationFactoryServlet.newFactory(
+servlet.getServletConfig()).getServerEngineConfig();
if (config != null) {
environment.put(EngineConfiguration.PROPERTY_NAME, config);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (AXIS-2077) axis 1.2.1 serializes primitive types as multirefs
axis 1.2.1 serializes primitive types as multirefs
--
Key: AXIS-2077
URL: http://issues.apache.org/jira/browse/AXIS-2077
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions: 1.2.1
Reporter: Daniel David Schäfer
I discovered a problem in axis 1.2.1 that also occurred in previous releases.
The soap-request gets blown up by many multirefs that only contain integers or
other primitve types.
I have provided a patch that solves this problem.
===
RCS file:
/usr/local/cvsroot/dev_projects/axis121/src/org/apache/axis/encoding/SerializationContext.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- dev_projects/axis121/src/org/apache/axis/encoding/SerializationContext.java
2005/06/22 12:34:12 1.1
+++ dev_projects/axis121/src/org/apache/axis/encoding/SerializationContext.java
2005/06/22 12:49:59 1.2
@@ -610,12 +610,21 @@
public boolean isPrimitive(Object value)
{
if (value == null) return true;
-
+
Class javaType = value.getClass();
if (javaType.isPrimitive()) return true;
-
+
+if (javaType == Integer.class) return true;
+if (javaType == Long.class) return true;
+if (javaType == Double.class) return true;
+if (javaType == Float.class) return true;
+if (javaType == Boolean.class) return true;
+if (javaType == Short.class) return true;
+if (javaType == Character.class) return true;
+if (javaType == Byte.class) return true;
if (javaType == String.class) return true;
+
if (Calendar.class.isAssignableFrom(javaType)) return true;
if (Date.class.isAssignableFrom(javaType)) return true;
if (HexBinary.class.isAssignableFrom(javaType)) return true;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (AXIS-2091) Namespaces dissappear when they appeared before
Namespaces dissappear when they appeared before --- Key: AXIS-2091 URL: http://issues.apache.org/jira/browse/AXIS-2091 Project: Apache Axis Type: Bug Versions: 1.2, 1.2.1 Environment: windows xp; java full version "1.5.0_02-b09" Reporter: Laura Baño The problem is the next one: I sent the following request to a web service using axis 1.2.1: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://www.w3.org/2000/09/xmldsig#"; xmlns:dss="http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd"; xmlns:ns="http://www.openuri.org/"; xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";>http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";>urn:ietf:rfc:3369MIIE9AYJKoZIhvcNAQcCoIIE5TCCBOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3 DQEHAaCCA5owggOWMIIC/6ADAgECAgEhMA0GCSqGSIb3DQEBBAUAMHcxCzAJBgNV BAYTAkVTMQ8wDQYDVQQIEwZNdXJjaWExDzANBgNVBAcTBk11cmNpYTEdMBsGA1UE ChMUVW5pdmVyc2l0eSBvZiBNdXJjaWExETAPBgNVBAsTCFVNVS1ESUlDMRQwEgYD VQQDEwtVTVUtRElJQyBDQTAeFw0wNTA1MjUwOTA5MzJaFw0wNjA1MjUwOTA5MzJa MIGBMQswCQYDVQQGEwJFUzEPMA0GA1UECBMGTXVyY2lhMQ8wDQYDVQQHEwZNdXJj aWExHTAbBgNVBAoTFFVuaXZlcnNpdHkgb2YgTXVyY2lhMRcwFQYDVQQLEw5VTVUt RElJQyBBdGljYTEYMBYGA1UEAxMPU2Vydmlkb3IgZUFkbWluMIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQCn60bp4dlLt5KVAYqY4Pk03mLR6sQhpyxx1JfwL3el 1Y50BAm85Zq2SIUSlcx0f7yMCaHIvaWXS+rBMfsIxkVpQ5oERKjrLKygXrdHLadr oB2tlM5hNgladluLPQfNCJcuGeH4M4LjXstNWGRqIeVKMiKGPtRkXfc69vvPPjNp HQIDAQABo4IBJTCCASEwDgYDVR0PAQH/BAQDAgXgMD8GA1UdHwQ4MDYwNKAyoDCG Lmh0dHA6Ly9nb3Jnb3JvdGgudW11LmV1cm82aXgub3JnL3NlcnZsZXQvQ1JMZHAw gaAGCCsGAQUFBwEBBIGTMIGQMCwGCCsGAQUFBzAChiBsZGFwOi8vZ29yZ29yb3Ro LnVtdS5ldXJvNml4Lm9yZzBgBggrBgEFBQcwAYZUaHR0cDovL2dvcmdvcm90aC51 bXUuZXVybzZpeC5vcmcvcGlzY2lzL3NlcnZsZXQvcGlzY2lzLnBraS5jYS5zZXJ2 bGV0cy5PQ1NQUmVzcG9uZGVyMBEGCWCGSAGG+EIBAQQEAwIF4DAYBgNVHREEETAP gQ1hcm1AZGlmLnVtLmVzMA0GCSqGSIb3DQEBBAUAA4GBAIMqLk0aCGkRCWotFFnr HyDmahKKzpFf6+K8vRhAgEyHiK8x8v2Jylv9kf+gbxbjlTFC3PYS63Qsh57IxYSg CYVQDnYxweLVTsruBZ20dwks8PlyNCH7DAkztGpG2p0VIsO69xPscsjnm23nuzGy OUL+fGDvvGFOloSRVQKODQbNMYIBIjCCAR4CAQEwfDB3MQswCQYDVQQGEwJFUzEP MA0GA1UECBMGTXVyY2lhMQ8wDQYDVQQHEwZNdXJjaWExHTAbBgNVBAoTFFVuaXZl cnNpdHkgb2YgTXVyY2lhMREwDwYDVQQLEwhVTVUtRElJQzEUMBIGA1UEAxMLVU1V LURJSUMgQ0ECASEwCQYFKw4DAhoFADANBgkqhkiG9w0BAQEFAASBgA2ic+k6Wxfn XVpk/0FX33BOaMKPkNkuzIPhFmnfdyA21nKFWkkh6GXYO4rcJ3SwHEvsq3n+gNmI 9LPPlhdklsa1sAPjR+7DOCJhZw55xSPvdNoGpJ2+fx7ikZ8kdrWpaQCCq3+9SqoG xZWyieVKxGF+g0OGETolGXvHgUZUWyvDhttp://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";>http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";>http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";>http://www.openuri.org/";>Laura I print the request when the service receives it and I get this: http://www.w3.org/2000/09/xmldsig#"; xmlns:dss="http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd"; xmlns:ns="http://www.openuri.org/"; xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";>http://ea.carm.es/schemas/funcionales/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";>urn:ietf:rfc:3369MIIE9AYJKoZIhvcNAQcCoIIE5TCCBOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3 DQEHAaCCA5owggOWMIIC/6ADAgECAgEhMA0GCSqGSIb3DQEBBAUAMHcxCzAJBgNV BAYTAkVTMQ8wDQYDVQQIEwZNdXJjaWExDzANBgNVBAcTBk11cmNpYTEdMBsGA1UE ChMUVW5pdmVyc2l0eSBvZiBNdXJjaWExETAPBgNVBAsTCFVNVS1ESUlDMRQwEgYD VQQDEwtVTVUtRElJQyBDQTAeFw0wNTA1MjUwOTA5MzJaFw0wNjA1MjUwOTA5MzJa MIGBMQswCQYDVQQGEwJFUzEPMA0GA1UECBMGTXVyY2lhMQ8wDQYDVQQHEwZNdXJj aWExHTAbBgNVBAoTFFVuaXZlcnNpdHkgb2YgTXVyY2lhMRcwFQYDVQQLEw5VTVUt RElJQyBBdGljYTEYMBYGA1UEAxMPU2Vydmlkb3IgZUFkbWluMIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQCn60bp4dlLt5KVAYqY4Pk03mLR6sQhpyxx1JfwL3el 1Y50BAm85Zq2SIUSlcx0f7yMCaHIvaWXS+rBMfsIxkVpQ5oERKjrLKygXrdHLadr oB2tlM5hNgladluLPQfNCJcuGeH4M4LjXstNWGRqIeVKMiKGPtRkXfc69vvPPjNp HQIDAQABo4IBJTCCASEwDgYDVR0PAQH/BAQDAgXgMD8GA1UdHwQ4MDYwNKAyoDCG Lmh0dHA6Ly9nb3Jnb3JvdGgudW11LmV1cm82aXgub3JnL3NlcnZsZXQvQ1JMZHAw gaAGCCsGAQUFBwEBBIGTMIGQMCwGCCsGAQUFBzAChiBsZGFwOi8vZ29yZ29yb3Ro LnVtdS5ldXJvNml4Lm9yZzBgBggrBgEFBQcwAYZUaHR0cDovL2dvcmdvcm90aC51 bXUuZXVybzZpeC5vcmcvcGlzY2lzL3NlcnZsZXQvcGlzY2lzLnBraS5jYS5zZXJ2 bGV0cy5PQ1NQUmVzcG9uZGVyMBEGCWCGSAGG+EIBAQQEAwIF4DAYBgNVHREEETAP gQ1hcm1AZGlmLnVtLmVzMA0GCSqGSIb3DQEBBAUAA4GBAIMqLk0aCGkRCWotFFnr HyDmahKKzpFf6+K8vRhAgEyHiK8x8v2Jylv9kf+gbxbjlTFC3PYS63Qsh57IxYSg CYVQDnYxweLVTsruBZ
[jira] Created: (AXIS-2150) Error calling web service after a re-deploy
Error calling web service after a re-deploy --- Key: AXIS-2150 URL: http://issues.apache.org/jira/browse/AXIS-2150 Project: Apache Axis Type: Bug Versions: 1.2.1 Environment: Java sdk1.4.2_06 JBoss 4.0.2 / TomCat 5.0 / WebSphere 6.0 Reporter: João Portela After a redeploy of an application (that called a web service), when I try to call a web service the following error occurs: “Unable to locate a valid EngineConfigurationFactory” java.lang.NullPointerException at org.apache.axis.client.Service.getEngineConfiguration(Service.java:812) at org.apache.axis.client.Service.getAxisClient(Service.java:103) at org.apache.axis.client.Service.(Service.java:112) at myapp.WebService1Soap_BindingStub.(Unknown Source) ... Notes: - I have an axis configuration file in my ear/war application file. - It seems that after the redeploy it tries to use previous (load) configurations but due to the redeploy, the configuration no longer exists. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS-2175) Axis creates more parameters in the WSDL than specified in the java declaration
Axis creates more parameters in the WSDL than specified in the java declaration --- Key: AXIS-2175 URL: http://issues.apache.org/jira/browse/AXIS-2175 Project: Apache Axis Type: Bug Components: WSDL processing Versions: 1.2.1 Reporter: César Ariza Axis creates more parameters than specified in the java declaration. If the java code has a getFieldX process, axis will generate the "FieldX" element in the WSDL. This normally happend when you change the name of the properties but forgot to change the names of the gets' and sets' methods. If the getFiled remains in your code, in the wsdl you will have an element "Field" and another "newField". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1994) CommonsHTTPSender failing to set host name
[
http://issues.apache.org/jira/browse/AXIS-1994?page=comments#action_12319383 ]
Javier Cámara commented on AXIS-1994:
-
Hi Jayachandra!
The section of code being patched is not the one when the host "is listed in
the proxy list", but when the host "is not listed in the non-proxy list". This
is, when there is a proxy set and the target host is not in the list of hosts
for which the proxy must not be used.
I do not think your guess about config.setHost() annullating the effect of
config.setProxy() is correct. From the documentation and source of CommonsHTTP,
HttpConnectionParams is just a container of variables specifying the host and
port you want to connect to, and the proxy to be used, if any. This means that,
if you want to connect to a host using a proxy, you must specify both, and not
only the proxy, and thus calling setHost() is independent of calling setProxy().
The exception being thrown is not an unhandled one, but an explicit one. This
is the code of org.apache.commons.httpclient.HttpConnection causing it:
if (host == null) {
throw new IllegalArgumentException("host parameter is null");
}
For me it is clear that CommonsHTTPSender is blatantly wrong when not setting a
host name before invoking HttpConnection, as it does in other cases, and makes
me think that this case has not been tested. Thus my simple patch.
If you want to reproduce the problem, all you have to do to use
CommonsHTTPSender through a proxy. My original test was with a proxy requesting
NTLM authentication, but it fails equally when the proxy does not require any
authentication at all, and I guess it will too if it requires BASIC
authentication. If you do not have a proxy at hand I think you can use TCPMon
as one. This is how I am getting the exception (with a proxy without
authentication):
- Configure client-config.wsdd to use CommonsHTTPSender instead of HTTPSender
- Put client-config.wsdd in the classpath along with commons-codec-1.3.jar
- Set the system properties http.proxyHost, http.proxyPort
If you are not able to reproduce the original problem with this configuration,
please tell me because there must be some mistake somewhere.
Regards
> CommonsHTTPSender failing to set host name
> --
>
> Key: AXIS-1994
> URL: http://issues.apache.org/jira/browse/AXIS-1994
> Project: Apache Axis
> Type: Bug
> Components: Basic Architecture
> Versions: 1.2
> Reporter: Javier Cámara
> Assignee: Jayachandra Sekhara Rao Sunkara
> Priority: Minor
>
> I tried to use Axis 1.2 to trespass a firewall with NTLM authentication (I
> think it is NTLM; at least it asks for an Active Directory Domain).
> I configured client-config.wsdd to use CommonsHTTPSender, and installed
> commons-codec-1.3.jar in the classpath. But I got the following exception:
>
> java.lang.IllegalArgumentException: host parameter is null
> at
> org.apache.commons.httpclient.HttpConnection.<init>(HttpConnection.java:206)
> at
> org.apache.commons.httpclient.HttpConnection.<init>(HttpConnection.java:155)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionWithReference.<init>(MultiThreadedHttpConnectionManager.java:1123)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$ConnectionPool.createConnection(MultiThreadedHttpConnectionManager.java:748)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:469)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:394)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:393)
> at
> org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:186)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.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:2765)
> at org.apache.axis.client.Call.invoke(Call.java:2748)
> at org.apache.axis.client.Call.invoke(Call.java:1784)
> (...)
>
> Then I had a look into CommonsHTTPSender and saw that the
> getHostConfiguration(HttpClient, MessageContext, URL) method seemed to fail
> to call config.setHost(
[jira] Commented: (AXIS-1686) java.lang.IncompatibleClassChangeError for org.apache.axis.message.MessageElement.addTextNode(MessageElement.java:1388)
[ http://issues.apache.org/jira/browse/AXIS-1686?page=comments#action_12320560 ] Ole-Martin Mørk commented on AXIS-1686: --- Is the fix in axis-1.2.1? Which files were changed? > java.lang.IncompatibleClassChangeError for > org.apache.axis.message.MessageElement.addTextNode(MessageElement.java:1388) > --- > > Key: AXIS-1686 > URL: http://issues.apache.org/jira/browse/AXIS-1686 > Project: Apache Axis > Type: Bug > Versions: 1.2RC1, 1.2RC2 > Environment: tomcat 4.1.x + jdk 1.4.2 > Reporter: GU Lei > Assignee: Dominik Kacprzak > Priority: Minor > > Soap request with > > > ... > > if only with > > ... > > there is no error > I modify the implementation of this method to > org.apache.axis.message.Text text = new > org.apache.axis.message.Text(s); > text.setOwnerDocument(getOwnerDocument()); > appendChild(text); > it does work for me. > I guest it's because javax.xml.**.java in axis are incompatible with > saaj.jar/jaxrpc.jar in axis/lib -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-278) Addressing Out handler being engaged twice in the out flow
[
http://issues.apache.org/jira/browse/AXIS2-278?page=comments#action_12332598 ]
Jiří Hanuš commented on AXIS2-278:
--
Doesn't. For each client's request, headers are populated with new set of
wsa:.. . So third request has 3x addressing headers, and so on. Each
instantiation of client stub adds a new addressing handler into service outflow.
The problem is, that each Stub instantiation fires building Flows for all
service' operations (PhaseResolver.buildChains()). It seems that this operation
populates service's handler chains with module and global ones, but the base
Stub class has a __static__ filed which holds this information for particular
service. So, when the stub is instantiated second time, handlers are duplicated
in the service's chains.
There is a little 'clash' between the static field for service description and
running config builder in constructor.
I've fixed it locally as follows, but its a bit dirty:
1) make field "_service" non-static in class Stub
2) move entire "static {}" block of generated stub into init() method and call
it in the constructor as the first thing
Regards,
Jiri
> Addressing Out handler being engaged twice in the out flow
> --
>
> Key: AXIS2-278
> URL: http://issues.apache.org/jira/browse/AXIS2-278
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: deployment
> Reporter: Eran Chinthaka
> Assignee: Deepal Jayasinghe
> Fix For: 0.93
>
> One can see two copies of addressing headers in the OUT message. The reason
> for this seems to be that the addressing out handler is being engaged twice
> in the out flow.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-287) Facet minInclusive causes RunTimeException
Facet minInclusive causes RunTimeException
--
Key: AXIS2-287
URL: http://issues.apache.org/jira/browse/AXIS2-287
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: Tools
Versions: 0.92
Environment: Red Hat 9
Reporter: Lars Jütten
(1) Trying to compile the WSDL file using:
./WSDL2Java.sh -o /tmp/ -p net.t_mobile.wlan.xtc -uri Xaction60Stateful.wsdl
(2) ... leads to:
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error:
cvc-complex-type.2.4a: Expected elements '[EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema' instead of '[EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema' here in element [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:104)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:30)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error:
cvc-complex-type.2.4a: Expected elements '[EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema' instead of '[EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema' here in element [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:168)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:75)
... 2 more
Caused by: org.apache.xmlbeans.XmlException: error: cvc-complex-type.2.4a:
Expected elements '[EMAIL PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema' instead of '[EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema' here in element [EMAIL
PROTECTED]://www.w3.org/2001/XMLSchema
at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:665)
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:147)
... 3 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
