[jira] Closed: (AXIS2C-646) Rampart does not work with Guththila xml parser
[ https://issues.apache.org/jira/browse/AXIS2C-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjula Peiris closed AXIS2C-646. - Resolution: Fixed Supun has fixed the bugs related to this issue in Guththila. Rampart/C is now working with guththila xml parser. Rampart does not work with Guththila xml parser --- Key: AXIS2C-646 URL: https://issues.apache.org/jira/browse/AXIS2C-646 Project: Axis2-C Issue Type: Bug Affects Versions: Current (Nightly) Reporter: Manjula Peiris Fix For: 1.1.0 Attachments: scenario3.xml, services.xml There are 5 samples in rampart . The behaviour of these samples depend on policy files and attached policies in services.xml. When guththila xml parser is used to parse these xml documents it does not parse the xml correctly. For an example I have attached the services.xml used in rampart/samples/scenario5. I have tried to parse this xml using axiom/test/om/test_om.c. But it does not parse correctly. It fails to return the text value inside the following element. rampc:ReceiverCertificate/home/manjula/axis2/c/deploy/bin/samples/rampart/keys/bhome/alice_cert.cert/rampc:ReceiverCertificate when I debug it seems to me some problem in the guththila_token_close method. please change the AXIS2C_HOME string in the attached file to home/manjula/axis2/c/deploy when you are testing with test_om. -- 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: (AXIS2C-651) When an invalid policy namespace uri is specified in the policy.xml, the rampart samples segfaults (neethi)
[ https://issues.apache.org/jira/browse/AXIS2C-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjula Peiris resolved AXIS2C-651. --- Resolution: Fixed Fix Version/s: Current (Nightly) This is fixed when fixing AXIS2C-649. When an invalid policy namespace uri is specified in the policy.xml, the rampart samples segfaults (neethi) Key: AXIS2C-651 URL: https://issues.apache.org/jira/browse/AXIS2C-651 Project: Axis2-C Issue Type: Bug Environment: Windows XP Reporter: Evanthika Amarasiri Assignee: Manjula Peiris Fix For: Current (Nightly) 1. Change the namespace URI to something invalid E.g.: - rampc:RampartConfig xmlns:rampc=http://ws.apache.org/rampart/c/policysss; 2. When executing the samples a segfault occurs *** neethi.dll!neethi_policy_get_name(neethi_policy_t * neethi_policy=0x, const axutil_env * env=0x00ce2a18) Line 236 + 0x3 bytesC *** -- 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]
RE: [Rampart/C] Generating incorrect digests?
This works perfectly, thanks very much! Cheers, Jamie -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: 01 August 2007 06:30 To: Apache AXIS C Developers List Subject: Re: [Rampart/C] Generating incorrect digests? Hi Jamie, It appears to me that the tcp log and the server log don't tally. The tcp-log shows attribute in Timestamp as u:Id whilst the server-log shows wsu:Id. May be the server expects attribute to be with wsu: prefix. Could you please try this... 1. Open RAMPART/src/util/rampart_signature.c 2. Change line(273) to oxs_axiom_add_attribute(env, node_to_sign, RAMPART_WSU, RAMPART_WSU_XMLNS,OXS_ATTR_ID, id); See that I've changed prefix, from u: to wsu: Let me know if this works with Axis1. If not we might have to dig further into the problem :). Cheers, Kaushalye Jamie Lyon wrote: Replies inline: I've successfully got Rampart/C set up, and have the client signing messages, however the digests are failing to verify for all items apart from the Body. You mean the digest of the body is verified but not for other parts? It appears to be that way, yes. At least, the Axis1/Java isn't throwing any verification failed errors for the Body. It might also be of interest that even with just sp:Body/ in the SignedParts, the timestamp is still signed, so I can't test to see if the message is accepted when only the Body is signed (is there a way to turn this off?). There is also the message No Signed parts specified. Using the body. when only the body is specified. The behavior is, if a Timestamp is present Rampart/C signs it as per the WS-Security Policy Specification(Section 7.2). So if signing is enabled, and there is a Timestamp, Rampart/C signs it. Okay, this is fine, I would want to sign it eventually anyway, I was just curious as to whether there was a way to disable it for testing purposes. An error that might be significant is: OXS ERROR [x509.c:385 in openssl_x509_get_subject_key_identifier] oxs defualt error , The extenension index of NID_subject_key_identifier is not valid (spelling mistakes in original error message). Did you get this error in the client side? (Since you are using Rampart/C client against WSS4J ) Yes, that's from the client with Axis2/C|Rampart/C, it can be seen in the debug.log I included with the last message, just above the first c14n debug output, but it's also printed to the screen when running. The reference belongs to the Timestamp element, in which the digest verification fails. But the problem is how the Body signature was verified? (please confirm this). Have you tried to use Rampart/C for the verification of a message signed by WSS4J? BTW, Rampart/C interop with Rampart/Java, which uses WSS4J. :) I've attached the Axis logs for messages with and without a timestamp. It appears to me as though the one without the timestamp is being verified correctly, although it then of course returns to me a 'timestamp missing' error. Could the problem be that the c14n transforms are not working correctly? I'm currently trying to get axis/java to output the xml that it is producing a digest on, to make sure that they match. Thanks, Jamie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://kaushalye.blogspot.com/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-650) When some xml blocks are commented out in the policy.xml so that it does not match with the services.xml, the rampart samples segfaults
[ https://issues.apache.org/jira/browse/AXIS2C-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjula Peiris resolved AXIS2C-650. --- Resolution: Fixed Fix Version/s: Current (Nightly) Make the client fails when the policy is syntactically wrong. When some xml blocks are commented out in the policy.xml so that it does not match with the services.xml, the rampart samples segfaults Key: AXIS2C-650 URL: https://issues.apache.org/jira/browse/AXIS2C-650 Project: Axis2-C Issue Type: Bug Environment: Windows XP Reporter: Evanthika Amarasiri Assignee: Manjula Peiris Fix For: Current (Nightly) When you comment policy blocks such as given in the example below so that it does not match with the services.xml file, the rampart samples segfaults E.g.:- sp:Layouts !--wsp:Policy sp:Strict/ /wsp:Policy-- sp:Layouts * axiom.dll!axiom_node_get_node_type(axiom_node * om_node=0x, const axutil_env * env=0x00ce2a18) Line 811 + 0x3 bytes C * -- 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: (AXIS2C-649) Rampart samples segfaults when there are errors in the policy.xml (neethi)
[ https://issues.apache.org/jira/browse/AXIS2C-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjula Peiris resolved AXIS2C-649. --- Resolution: Fixed Fix Version/s: Current (Nightly) Fixed to return an error. Rampart samples segfaults when there are errors in the policy.xml (neethi) -- Key: AXIS2C-649 URL: https://issues.apache.org/jira/browse/AXIS2C-649 Project: Axis2-C Issue Type: Bug Environment: Windows XP Reporter: Evanthika Amarasiri Assignee: Manjula Peiris Fix For: Current (Nightly) 1. Make a change to the existing policy file making the xml invalid ** sp:Layout !--wsp:Policy-- sp:Strict/ /wsp:Policy /sp:Layout ** 2. When executing the sample, a segfault occurs *** neethi.dll!neethi_policy_get_name(neethi_policy_t * neethi_policy=0x, const axutil_env * env=0x00ce2a18) Line 236 + 0x3 bytesC *** -- 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]
Re: [Rampart/C] Generating incorrect digests?
You are welcome. :) The reason might be having two prefixes pointing to the same namespace in the Timestamp. Which I consider legal. So the digest calculation based on C14N might differ in two implementations. Anyways thank you too, for pointing this out. Cheers, Kaushalye Jamie Lyon wrote: This works perfectly, thanks very much! Cheers, Jamie -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: 01 August 2007 06:30 To: Apache AXIS C Developers List Subject: Re: [Rampart/C] Generating incorrect digests? Hi Jamie, It appears to me that the tcp log and the server log don't tally. The tcp-log shows attribute in Timestamp as u:Id whilst the server-log shows wsu:Id. May be the server expects attribute to be with wsu: prefix. Could you please try this... 1. Open RAMPART/src/util/rampart_signature.c 2. Change line(273) to oxs_axiom_add_attribute(env, node_to_sign, RAMPART_WSU, RAMPART_WSU_XMLNS,OXS_ATTR_ID, id); See that I've changed prefix, from u: to wsu: Let me know if this works with Axis1. If not we might have to dig further into the problem :). Cheers, Kaushalye Jamie Lyon wrote: Replies inline: I've successfully got Rampart/C set up, and have the client signing messages, however the digests are failing to verify for all items apart from the Body. You mean the digest of the body is verified but not for other parts? It appears to be that way, yes. At least, the Axis1/Java isn't throwing any verification failed errors for the Body. It might also be of interest that even with just sp:Body/ in the SignedParts, the timestamp is still signed, so I can't test to see if the message is accepted when only the Body is signed (is there a way to turn this off?). There is also the message No Signed parts specified. Using the body. when only the body is specified. The behavior is, if a Timestamp is present Rampart/C signs it as per the WS-Security Policy Specification(Section 7.2). So if signing is enabled, and there is a Timestamp, Rampart/C signs it. Okay, this is fine, I would want to sign it eventually anyway, I was just curious as to whether there was a way to disable it for testing purposes. An error that might be significant is: OXS ERROR [x509.c:385 in openssl_x509_get_subject_key_identifier] oxs defualt error , The extenension index of NID_subject_key_identifier is not valid (spelling mistakes in original error message). Did you get this error in the client side? (Since you are using Rampart/C client against WSS4J ) Yes, that's from the client with Axis2/C|Rampart/C, it can be seen in the debug.log I included with the last message, just above the first c14n debug output, but it's also printed to the screen when running. The reference belongs to the Timestamp element, in which the digest verification fails. But the problem is how the Body signature was verified? (please confirm this). Have you tried to use Rampart/C for the verification of a message signed by WSS4J? BTW, Rampart/C interop with Rampart/Java, which uses WSS4J. :) I've attached the Axis logs for messages with and without a timestamp. It appears to me as though the one without the timestamp is being verified correctly, although it then of course returns to me a 'timestamp missing' error. Could the problem be that the c14n transforms are not working correctly? I'm currently trying to get axis/java to output the xml that it is producing a digest on, to make sure that they match. Thanks, Jamie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://kaushalye.blogspot.com/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://kaushalye.blogspot.com/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] CodeSynthesis XSD 3.0.0 - Open-source XML Schema to C++ compiler
Hi, I am pleased to announce the availability of CodeSynthesis XSD 3.0.0. CodeSynthesis XSD is an open-source (GPL2 + proprietary license), cross- platform W3C XML Schema to C++ data binding compiler. Provided with a schema, it generates C++ classes that represent the given vocabulary as well as parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with elements, attributes, and text in a direct representation of XML such as DOM or SAX. XSD supports both in-memory and stream-oriented processing models by implementing two C++ mappings: C++/Tree and C++/Parser. The C++/Tree mapping represents the information stored in XML instance documents as a tree-like, in-memory object model. The C++/Parser mapping generates parser skeletons for data types defined in XML Schema. Using these parser skeletons you can build your own in-memory representations or perform immediate processing of XML documents. Major new features in this release: C++/Tree: * Generation of documentation in the Doxygen format. * New XML Schema wildcards mapping which represents the matched content as DOM fragments. * Support for binary serialization in the XDR format. * Support for polymorphic binary serialization. * New Getting Started guide. C++/Parser: * Parser implementations for all built-in XML Schema types. * Automatic generation of sample parser implementations and test drivers. * Support for parsing XML vocabularies with multiple document roots. * New Getting Started guide. For a complete list of new features see http://www.codesynthesis.com/pipermail/xsd-announcements/2007/23.html XSD is available on IBM AIX, GNU/Linux, HP-UX, Mac OS X, Solaris, and Windows. Supported C++ compilers include: GNU g++, HP aCC, IBM XL C++, Intel C++, Sun C++, and MS Visual C++. More information as well as precompiled binaries for all supported platforms are available from http://www.codesynthesis.com/products/xsd/ Best Regards, Boris -- Boris Kolpackov Code Synthesis Tools CC http://www.codesynthesis.com tel: +27 76 1672134 fax: +27 21 5526869 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [WSDL2Code/C] Embedding soap operations in body (with adb databinding)
Okay, I've been looking through the templates, and have a question:
Should lines 1315:1332 in :
xsl:if test=not(@type)
xsl:for-each select=property
xsl:if test=position()=1
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
/xsl:if
/xsl:for-each
/xsl:if
Actually be (something similar to):
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
xsl:if test=not(@type)
xsl:for-each select=property
xsl:if test=position()=1
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
/xsl:if
/xsl:for-each
/xsl:if
I.e. One unconditional element namespace creation, followed by element
and namespaces for all the children?
Unless there's a specific property for the root node, which I can't
find, so you could do something like:
xsl:for-each select=root and property (pseudo)
Any suggestions?
-Jamie
-Original Message-
From: Jamie Lyon [mailto:[EMAIL PROTECTED]
Sent: 01 August 2007 11:44
To: Apache AXIS C Developers List
Subject: [WSDL2Code/C] Embedding soap operations in body (with adb
databinding)
DataService.wsdl Hi,
I'm having some problems with the WSDL2C tool. I'm running the latest
nightly build (Aug 1st). All of the methods below were generated using
adb databinding from the attached wsdl file using the following
command:
wsdl2c.sh -uri DataService.wsdl -g -f -d adb -u -o output
Where wsdl2c.sh is just wsdl2java.sh with the line:
sh `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2Java $*
replaced with:
sh `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2C $*
There are several small problems:
1) When compiling the wsdl file I attached, I get a re-defined warning
on adb_GetResourceProperty_get_qname in adb_GetResourceProperty.c.
2) A known bug is not yet fixed in the nightly, though a fix is known
-
basically rampart/c does not work with autogenerated stubs with adb
databinding:
Problem:
http://www.nabble.com/rampart-c-not-working-with-stubs-generated-using-w
sdl2c-t4125131.html
Solution:
http://www.nabble.com/Re%3A-rampart-c-not-working-with-stubs-generated-u
sing-wsdl2c-p11760941.html
These are all fixable via manual edits in a small amount of time
however, and are really just minor inconveniences.
The last problem however I cannot find a fix for:
When a request contains no parameters, no soap operation is defined in
the body, only the SOAPAction in the HTTP header is generated. If you
generate the attached wsdl file, you will get the following operation
(and more):
getResources - this has no parameters, and as such the soap body looks
like:
soapenv:Body wsu:Id=SigID-b5477fd2-3f48-1dc1
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-utility-1.0.xsd
/soapenv:Body
When it should look like:
soapenv:Body wsu:Id=SigID-b5477fd2-3f48-1dc1
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-utility-1.0.xsd
getResources/getResources
/soapenv:Body
Looking at the source code for this operation
(adb_getResources_serialize in adb_getResources.c) you can see the
reason for it, all the code for generating the root element, such as
that found in the operation 'save', is not
Re: [WSDL2Code/C] Embedding soap operations in body (with adb databinding)
Hi Jamie,
First sorry for the late reply. These days I am stuck with my mid semester
exams and assignments, so I didn't found a free time look at this. I think
cause for this complexity is something we have done to improve the data
binding performance. We have introduce stream writer into serialize function
and we use this stream to serialize child nodes. We write strings to the
stream and then namesapace problem occur because we must manually add
namespaces to that string. I do some changes to fix this by declaring child
namespaces in parent element and I think that is the problem what you
pointing out. I will look at these bugs as soon as possible.
Thanks
Milinda
On 8/1/07, Jamie Lyon [EMAIL PROTECTED] wrote:
Okay, I've been looking through the templates, and have a question:
Should lines 1315:1332 in :
xsl:if test=not(@type)
xsl:for-each select=property
xsl:if test=position()=1
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
/xsl:if
/xsl:for-each
/xsl:if
Actually be (something similar to):
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
xsl:if test=not(@type)
xsl:for-each select=property
xsl:if test=position()=1
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
/xsl:if
/xsl:for-each
/xsl:if
I.e. One unconditional element namespace creation, followed by element
and namespaces for all the children?
Unless there's a specific property for the root node, which I can't
find, so you could do something like:
xsl:for-each select=root and property (pseudo)
Any suggestions?
-Jamie
-Original Message-
From: Jamie Lyon [mailto:[EMAIL PROTECTED]
Sent: 01 August 2007 11:44
To: Apache AXIS C Developers List
Subject: [WSDL2Code/C] Embedding soap operations in body (with adb
databinding)
DataService.wsdl Hi,
I'm having some problems with the WSDL2C tool. I'm running the latest
nightly build (Aug 1st). All of the methods below were generated using
adb databinding from the attached wsdl file using the following
command:
wsdl2c.sh -uri DataService.wsdl -g -f -d adb -u -o output
Where wsdl2c.sh is just wsdl2java.sh with the line:
sh `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2Java $*
replaced with:
sh `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2C $*
There are several small problems:
1) When compiling the wsdl file I attached, I get a re-defined warning
on adb_GetResourceProperty_get_qname in adb_GetResourceProperty.c.
2) A known bug is not yet fixed in the nightly, though a fix is known
-
basically rampart/c does not work with autogenerated stubs with adb
databinding:
Problem:
http://www.nabble.com/rampart-c-not-working-with-stubs-generated-using-w
sdl2c-t4125131.html
Solution:
http://www.nabble.com/Re%3A-rampart-c-not-working-with-stubs-generated-u
sing-wsdl2c-p11760941.html
These are all fixable via manual edits in a small amount of time
however, and are really just minor inconveniences.
The last problem however I cannot find a fix for:
When a request contains no parameters, no soap operation is defined in
the body, only
RE: [WSDL2Code/C] Embedding soap operations in body (with adb databinding)
Excellent, whenever you find time. It was more the axiom_element_create part I
was pointing out however, as when there is no parameter no calls to that
function are made, so no root element is created (I'll give an example of what
I mean tomorrow when I have access to the system with the code on). I'm not
entirely sure why this is, but I shall continue to help look into it (it will
help me gain knowledge of the templating system even if I don't find the
solution).
Thanks,
Jamie
-Original Message-
From: Milinda Pathirage [mailto:[EMAIL PROTECTED]
Sent: Wed 8/1/2007 6:28 PM
To: Apache AXIS C Developers List
Subject: Re: [WSDL2Code/C] Embedding soap operations in body (with adb
databinding)
Hi Jamie,
First sorry for the late reply. These days I am stuck with my mid semester
exams and assignments, so I didn't found a free time look at this. I think
cause for this complexity is something we have done to improve the data
binding performance. We have introduce stream writer into serialize function
and we use this stream to serialize child nodes. We write strings to the
stream and then namesapace problem occur because we must manually add
namespaces to that string. I do some changes to fix this by declaring child
namespaces in parent element and I think that is the problem what you
pointing out. I will look at these bugs as soon as possible.
Thanks
Milinda
On 8/1/07, Jamie Lyon [EMAIL PROTECTED] wrote:
Okay, I've been looking through the templates, and have a question:
Should lines 1315:1332 in :
xsl:if test=not(@type)
xsl:for-each select=property
xsl:if test=position()=1
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
/xsl:if
/xsl:for-each
/xsl:if
Actually be (something similar to):
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
xsl:if test=not(@type)
xsl:for-each select=property
xsl:if test=position()=1
if( parent == NULL)
{
current_element = axiom_element_create (env, parent,
xsl:value-of select=$originalName/, ns1,
amp;current_node);
axiom_element_set_namespace( current_element, env,
ns1, current_node);
xsl:if test=@child-nsuri and @child-nsprefix and
@ours
ns1 = axiom_namespace_create (env,
xsl:value-of select=@child-nsuri/,
xsl:value-of select=@child-nsprefix/);
axiom_element_declare_namespace( current_element,
env, current_node, ns1);
/xsl:if
parent = current_node;
}
/xsl:if
/xsl:for-each
/xsl:if
I.e. One unconditional element namespace creation, followed by element
and namespaces for all the children?
Unless there's a specific property for the root node, which I can't
find, so you could do something like:
xsl:for-each select=root and property (pseudo)
Any suggestions?
-Jamie
-Original Message-
From: Jamie Lyon [mailto:[EMAIL PROTECTED]
Sent: 01 August 2007 11:44
To: Apache AXIS C Developers List
Subject: [WSDL2Code/C] Embedding soap operations in body (with adb
databinding)
DataService.wsdl Hi,
I'm having some problems with the WSDL2C tool. I'm running the latest
nightly build (Aug 1st). All of the methods below were generated using
adb databinding from the attached wsdl file using the following
command:
wsdl2c.sh -uri DataService.wsdl -g -f -d adb -u -o output
Where wsdl2c.sh is just wsdl2java.sh with the line:
sh `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2Java $*
replaced with:
sh `dirname $0`/axis2.sh org.apache.axis2.wsdl.WSDL2C $*
There are several small problems:
1) When compiling the wsdl file I attached, I get a re-defined warning
on
[jira] Created: (AXIS2C-655) WSDL2C generated code not compiling
WSDL2C generated code not compiling - Key: AXIS2C-655 URL: https://issues.apache.org/jira/browse/AXIS2C-655 Project: Axis2-C Issue Type: Bug Components: wsdl2c tool Affects Versions: 1.0.0 Environment: RHEL 3 , jdk 1.5.0 as well as 1.4.2_30 Reporter: Manoj Kumar Pradhan When I tried to compile I got Syntax error befor * token . This refers to the client stub genertaed axis2_stub_t* axis2_stub_HelloWorld_create( ) ; I grep and had gone thru axis2_stub.h there it is defined as typedef struct axis2_stub axis2_stub_t ; But i did not get where axis2_stub is defined . whether i have to set it manually as env parameter ... or I am missing any thing ? I checkout all codes on 30-july 2007 . plese help . -- 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-3041) WSDL2java does not provoide circular wsdl import support
[ https://issues.apache.org/jira/browse/AXIS2-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516875 ] Davanum Srinivas commented on AXIS2-3041: - Exception with that patch: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Malformed uri: X10-NoTimestamp_IPin gService_Ping_Input_policy at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: Malformed uri: X10-NoTimestamp_IPingService_Ping_Input_policy at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1363) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247) ... 2 more Caused by: java.lang.RuntimeException: Malformed uri: X10-NoTimestamp_IPingService_Ping_Input_policy at org.apache.neethi.PolicyReference.getRemoteReferedElement(PolicyReference.java:161) at org.apache.neethi.PolicyReference.getRemoteReferencedPolicy(PolicyReference.java:175) at org.apache.neethi.PolicyReference.normalize(PolicyReference.java:111) at org.apache.axis2.util.PolicyUtil.getMergedPolicy(PolicyUtil.java:220) at org.apache.axis2.description.AxisBindingMessage.getEffectivePolicy(AxisBindingMessage.java:236) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getBindingPolicyFromMessage(AxisServiceBasedMultiLanguageEmitter.java:282) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getInputElement(AxisServiceBasedMultiLanguageEmitter.java:2649) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.generateMethodElement(AxisServiceBasedMultiLanguageEmitter.java:2191) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:2117) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForSkeleton(AxisServiceBasedMultiLanguageEmitter.java:2033) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1964) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1320) ... 3 more WSDL2java does not provoide circular wsdl import support Key: AXIS2-3041 URL: https://issues.apache.org/jira/browse/AXIS2-3041 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Amila Chinthaka Suriarachchi Assignee: Amila Chinthaka Suriarachchi Attachments: patch-AXIS2-3041.diff use the wsdl2java tool with the following wsdl, to generate client. http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl it fails since wsdl2java does not support circular imports. -- 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]
Re: [Axis2] Axis2 1.3 Documentation Updates]
Pleas use following wiki page http://wiki.apache.org/ws/FrontPage/Axis2/changesfrom1.2to1.3 Thanks Deepal R J Scheuerle Jr wrote: Thanks Depal, Where is the wiki page for version 1.3 ? Then I can update the page myself. The new changes for JAX-WS 2.0 include: * Completion of major function. JAX-WS passes CTS testing with Geronimo * Supports JAX-WS Application Handlers. * Major upgrades to the MetaData layer * Supports SOAP 1.1, SOAP 1.2 and XML/HTTP. * Supports document/literal, rpc/literal, and document/literal wrapped apis * Some performance improvements Some known deficiencies include: * Performance. More changes are necessary. * Hook-Up JAX-WS application handlers with MustUnderstand processing. * More trace * Support for JAX-WS 2.1 Rich Scheuerle IBM Web Services Apache Axis2 ([EMAIL PROTECTED]) 512-838-5115 (IBM TL 678-5115) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed!
Are you using Axis2 1.2 ?. Please do try this scenario using latest Axis2
trunk.
Thank you,
Saminda
On 7/29/07, Navnit Jindal [EMAIL PROTECTED] wrote:
-- Forwarded message --
From: Navnit Jindal [EMAIL PROTECTED]
Date: Jul 29, 2007 11:57 AM
Subject: org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
axis-dev@ws.apache.org
Appreciate your help with this issue. Is there a revised code that can be
used?
org.apache.axis2.AxisFault: problem accessing the parser. Parser already
accessed!
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
CommonsHTTPTransportSender.java:221)
at org.apache.axis2.engine.AxisEngine.send (AxisEngine.java:452)
at org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:330)
===
Code I am using to set the Authentication using Axis2
options.setProperty(HTTPConstants.AUTHENTICATE, getAuthenticator(username,
password));
private HttpTransportProperties.Authenticator getAuthenticator(String
_username, String _password)
{
HttpTransportProperties.Authenticator authenticator = new
HttpTransportProperties.Authenticator ();
//HttpTransportProperties. basicAuthentication
authenticator.setUsername(_username);
authenticator.setPassword(_password);
authenticator.setPreemptiveAuthentication(true);
authenticator.setAllowedRetry(true);
return authenticator;
}
--
Saminda Abeyruwan
Software Engineer
WSO2 Inc. - www.wso2.org
[jira] Updated: (AXIS2-3041) WSDL2java does not provoide circular wsdl import support
[ https://issues.apache.org/jira/browse/AXIS2-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3041: Attachment: patch-AXIS2-3041.diff Patch against 1.3 Branch. WSDL2java does not provoide circular wsdl import support Key: AXIS2-3041 URL: https://issues.apache.org/jira/browse/AXIS2-3041 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Amila Chinthaka Suriarachchi Assignee: Amila Chinthaka Suriarachchi Attachments: patch-AXIS2-3041.diff use the wsdl2java tool with the following wsdl, to generate client. http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl it fails since wsdl2java does not support circular imports. -- 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-3043) wsdl2java using jaxbri data binding fails
wsdl2java using jaxbri data binding fails
-
Key: AXIS2-3043
URL: https://issues.apache.org/jira/browse/AXIS2-3043
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: databinding
Affects Versions: nightly
Environment: Axis2 1.3 Nightly; websphere6; eclipse 3.3
Reporter: Pierre Casenove
When trying to generate the java code from the attached wsdl using jaxbri
databinding, an Exception is returned:
[java] Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped to
the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
[java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
[java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
[java] Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException:No type was mapped to
the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1363
)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
[java] ... 2 more
[java] Caused by: org.apache.axis2.wsdl.databinding.UnmatchedTypeException:
No type was mapped to the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.databinding.TypeMappingAdapter.getTypeMappingName(TypeMappingAdapter.java:82
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getInputParamElement(AxisServiceBasedMultiLanguageEmitter.java:2823
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getInputElement(AxisServiceBasedMultiLanguageEmitter.java:2623
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.generateMethodElement(AxisServiceBasedMultiLanguageEmitter.java:2191
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:2117
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForSkeleton(AxisServiceBasedMultiLanguageEmitter.java:2033
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1964
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1320
)
[java] ... 3 more
Using the xjc.bat script provided in the offcial JAXB2.0.5 release, the classes
are generated correctly.
Java code is also generated correctly with xmlbeans and adb databinding.
Ant task:
target name=wsdl2java depends=clean,prepare
delete dir=output /
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath /
arg value=-d /
arg value=jaxbri /
arg value=-u /
arg value=-uri /
arg file=${dir.wsdl}/${uri.wsdl} /
arg value=-ss /
arg value=-wv /
arg value=1.1 /
arg value=-g /
arg value=-sd /
arg value=-o /
arg file=output /
arg value=-p /
arg value=${package.prefix} /
/java
mkdir dir=output/resources/META-INF /
move todir=output/resources/META-INF
fileset dir=output/resources
!-- axis2 web services definitions file --
include name=services.xml /
include name=*.wsdl /
include name=*.xsd /
/fileset
/move
/target
--
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-3043) wsdl2java using jaxbri data binding fails
[
https://issues.apache.org/jira/browse/AXIS2-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Casenove updated AXIS2-3043:
---
Attachment: faultywsdl.zip
Attaching the faulty wsdl. The issue seems to be linked with the xsd import as
the code is correctly generated if I don't do any imports.
wsdl2java using jaxbri data binding fails
-
Key: AXIS2-3043
URL: https://issues.apache.org/jira/browse/AXIS2-3043
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: databinding
Affects Versions: nightly
Environment: Axis2 1.3 Nightly; websphere6; eclipse 3.3
Reporter: Pierre Casenove
Attachments: faultywsdl.zip
When trying to generate the java code from the attached wsdl using jaxbri
databinding, an Exception is returned:
[java] Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped
to the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
[java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
[java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
[java] Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException:No type was mapped
to the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1363
)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
[java] ... 2 more
[java] Caused by:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped
to the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.databinding.TypeMappingAdapter.getTypeMappingName(TypeMappingAdapter.java:82
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getInputParamElement(AxisServiceBasedMultiLanguageEmitter.java:2823
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getInputElement(AxisServiceBasedMultiLanguageEmitter.java:2623
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.generateMethodElement(AxisServiceBasedMultiLanguageEmitter.java:2191
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:2117
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForSkeleton(AxisServiceBasedMultiLanguageEmitter.java:2033
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1964
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1320
)
[java] ... 3 more
Using the xjc.bat script provided in the offcial JAXB2.0.5 release, the
classes are generated correctly.
Java code is also generated correctly with xmlbeans and adb databinding.
Ant task:
target name=wsdl2java depends=clean,prepare
delete dir=output /
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath /
arg value=-d /
arg value=jaxbri /
arg value=-u /
arg value=-uri /
arg file=${dir.wsdl}/${uri.wsdl} /
arg value=-ss /
arg value=-wv /
arg value=1.1 /
arg value=-g /
arg value=-sd /
arg value=-o /
arg file=output /
arg value=-p /
arg value=${package.prefix} /
/java
mkdir dir=output/resources/META-INF /
move todir=output/resources/META-INF
fileset dir=output/resources
!-- axis2 web services definitions file --
include name=services.xml /
include name=*.wsdl /
include name=*.xsd /
/fileset
/move
/target
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To
[jira] Commented: (AXIS2-3037) 'RuntimeException: Unexpected subelement' when wsdl adds a new property
[ https://issues.apache.org/jira/browse/AXIS2-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516889 ] Amila Chinthaka Suriarachchi commented on AXIS2-3037: - Well people can argue this as an bug and feature as well. I recently I added an option to off the strict valications. This is basically do not throw an exception when not receiving an expected element. So you are talking about the otherside. I'll put this too from the next release. but there won't be enough time for Axis2 1.3. 'RuntimeException: Unexpected subelement' when wsdl adds a new property --- Key: AXIS2-3037 URL: https://issues.apache.org/jira/browse/AXIS2-3037 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.2 Environment: Win2k3, Java 6.0, Axis2 1.2 Reporter: Chris B Priority: Critical Attachments: futures_new.wsdl, futures_old.wsdl, TestRunner.java I have an client app that was created and had been working, it makes a call to one webservice. The webservice was upgraded, it added some new methods and it also added a new property (Type) to one of the return types I was using. Now my app will no longer work, i get a runtime error, java.lang.RuntimeException: Unexpected subelement Type, when the results are returned to my service. If i rebuilt the client stub code using wsdl2java with the new wsdl my app will work again. As I understand it, adding fields to a object should not break any existing code. Any Xml elements returned that are not known elements should be ignored and not cause exceptions in the client code. I have tested my assumption with Visual Studio 2005, if i genereate web service client code using the old wsdl I can still call the new service without an exception being thrown because of the new Xml element being returned. Is there some option that I don't know of that will allow for new elements to be returned without exceptions being throw? -- 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-3044) Cannot generate code giving a remote HTTP URI, when the client is behind an HTTP proxy server
Cannot generate code giving a remote HTTP URI, when the client is behind an HTTP proxy server - Key: AXIS2-3044 URL: https://issues.apache.org/jira/browse/AXIS2-3044 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Afkham Azeez Assignee: Amila Chinthaka Suriarachchi Priority: Critical Fix For: nightly We should provide a options to wsdl2java such as; http-proxy-host http-proxy-port to facilitate this. At the moment, users behind a proxy server cannot codegen for remote WSDLs exposed via HTTP. -- 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-3016) using HTTPSListener when configuring transports per service
[ https://issues.apache.org/jira/browse/AXIS2-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-3016. -- Resolution: Fixed applied the patch with modification using HTTPSListener when configuring transports per service --- Key: AXIS2-3016 URL: https://issues.apache.org/jira/browse/AXIS2-3016 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: kernel Affects Versions: 1.2 Environment: tomcat 5.5 , windows xp Reporter: Nencho Lupanov Attachments: ListingAgent.diff org.apache.axis2.transport.http.HTTPSListener defined in org.apache.axis2.transport.http.ListingAgent should be declared public and not private as it is rith now.Furthure more, the port parameter that comes from axis2.xml should be taken into account in the init method in order to set the port memeber variable(see the source).About the scheme member variable, i think it can be hardcoded to https ? -- 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] Assigned: (AXIS2-3034) Axis2 Serialization problem with emptyset bitflag enums.
[
https://issues.apache.org/jira/browse/AXIS2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3034:
Assignee: Amila Chinthaka Suriarachchi
Axis2 Serialization problem with emptyset bitflag enums.
Key: AXIS2-3034
URL: https://issues.apache.org/jira/browse/AXIS2-3034
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Reporter: David R. Kraus
Assignee: Amila Chinthaka Suriarachchi
I created a bitflag enum, where one value is associated with each bit of the
enum, and multiple values/bits can be set for the value of the enum (see
dotnet generated WSDL below). The DotNet generated WSDL was taken and used
to create Java serialization classes (wsdl2java).The problem is that Axis2
can't handle the zero length string that is passed representing the empty
set. A bitflag enum can have more than one value, because each possible enum
value is represented by a bit. The problem occurs when none of the values is
set, and a bitflag value of zero(0) is serialized as (zero length string).
Enums are a tricky type since their representation as a numeric entity (bits)
making them a non-nullable type, although their value is transfered as a
string with multiple concatenated enum values.
There are two classes generated by wsdl2java to handle the bitflag enum at
the server (eg. EnumMWSSearchFlags, EnumMWSSearchFlags_type0).
EnumMWSSearchFlags contains an array of EnumMWSearchFlags_type0, each element
of which can refer to a bit value.
Both dotnet and java clients serialize the empty set as a zero length string.
This zero length string is parsed, at the server, looking for individual enum
values. Of course, none are found, and when the zero length string is used in
a table lookup for valid members of the enum (in EnumMWSSearchFlags_type0) an
IllegalArgumentException is generated. I have been able to get this to work
by commenting out the check for valid enum members being passed in (server
side only), but obviously this isn't the best way to do this (see specific
commented out code below).
I have been able to workaround this on the server side by commenting out an
exception (described in email thread below), BUT the real problem now is that
this only handles the case where the enum is being passed into the service
from the client. Patching the client side is not an option (when empty enum
is passed to the client from the service). We do not have a workaround for
this problem (client side can't be patched) and are near the end of our
development cycle, so we are very concerned!
If Axis2 serialization code interprets the empty bitflag as a zero length
string when it serializes it, then the receiving code should then be able to
handle this zero length string. Right now that is not happening correctly. I
think this is a bug.
Thanks, Dave Kraus
Altered server side code - see comment:
public static EnumMWSSearchFlags_type0
fromValue(java.lang.String value)
throws java.lang.IllegalArgumentException {
EnumMWSSearchFlags_type0 enumeration =
(EnumMWSSearchFlags_type0)
_table_.get(value);
//drk: Comment out so that bitflag enum can accept an
emptyset enum
/*if (enumeration==null) throw new
java.lang.IllegalArgumentException();*/
return enumeration;
}
WSDL representation of a bitflag enum:
s:simpleType name=EnumMWSSearchFlags
s:list
s:simpleType
s:restriction base=s:string
s:enumeration value=MWSAbbreviationWildCard/
s:enumeration value=MWSDescriptionWildCard/
s:enumeration value=MWSFolderBrowseStyle/
s:enumeration value=MWSModificationTime/
s:enumeration value=MWSNameWildCard/
s:enumeration value=MWSRootRecursive/
s:enumeration value=MWSUsedByOneOf/
s:enumeration value=MWSUsedByRecursive/
s:enumeration value=MWSUsesOneOf/
s:enumeration value=MWSUsesRecursive/
s:enumeration value=MWSVisibleOnly/
s:enumeration value=MWSBrowseAsync/
s:enumeration value=MWSOwnedByCurrentUser/
/s:restriction
/s:simpleType
/s:list
/s:simpleType
WSDL representation of usage of the bitflag enum as a parameter showing
minoccurs=1 because it's a non-nullable type. So it really doesn't make sense
to pass in a null instead of the emptyset.
s:element maxOccurs=1 minOccurs=1 name=eFlags
type=tns:EnumMWSSearchFlags/
--
This message is
[jira] Resolved: (AXIS2-3030) SAAJ Implementation - SOAPBodyImpl.toSAAJNode fails when source node has unqualified attribute (at least, with Xerces parser)
[
https://issues.apache.org/jira/browse/AXIS2-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sumedha rubasinghe resolved AXIS2-3030.
---
Resolution: Fixed
Issue is already fixed.
SAAJ Implementation - SOAPBodyImpl.toSAAJNode fails when source node has
unqualified attribute (at least, with Xerces parser)
-
Key: AXIS2-3030
URL: https://issues.apache.org/jira/browse/AXIS2-3030
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Environment: All
Reporter: Jeff Faath
Assignee: sumedha rubasinghe
Priority: Minor
The SOAPBodyImpl.toSAAJNode contains a bug at this block of code that
converts the source DOM node attributes to SAAJ element attributes:
NamedNodeMap domAttrs = domEle.getAttributes();
for (int i = 0; i domAttrs.getLength(); i++) {
org.w3c.dom.Node attrNode = domAttrs.item(i);
saajEle.addAttribute(new PrefixedQName(attrNode.getNamespaceURI(),
attrNode.getLocalName(),
attrNode.getPrefix()),
attrNode.getNodeValue());
}
The problem is that when the current attrNode isn't qualified, the
getLocalName method returns null (using Xerces parser). Then, when trying to
create the new PrefixedQName, an exception is thrown for trying to create a
QName with a null LocalName.
The solution is to either just use attrNode.getName() (not sure if this is
thorough enough?) or to test if attrNode is of type AttrNSImpl or AttrImpl.
If AttrNSImpl, the current block works, otherwise, the getName() must be used
instead of getLocalName().
--
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-3045) Docs not opening due to syntax error in DOCTYPE
[ https://issues.apache.org/jira/browse/AXIS2-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suran Jayathilaka updated AXIS2-3045: - Attachment: Axis2-3045.patch Fixes the DOCTYPE syntax errors. Docs not opening due to syntax error in DOCTYPE --- Key: AXIS2-3045 URL: https://issues.apache.org/jira/browse/AXIS2-3045 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: nightly Environment: WindowsXP SP2, JDK 5.0, Firefox 2.0.0.6, IE7 Reporter: Suran Jayathilaka Priority: Trivial Fix For: nightly Attachments: Axis2-3045.patch Some of the guide docs in xdocs wouldn't open because of a syntax error in the DOCTYPE element. -- 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-3045) Docs not opening due to syntax error in DOCTYPE
Docs not opening due to syntax error in DOCTYPE --- Key: AXIS2-3045 URL: https://issues.apache.org/jira/browse/AXIS2-3045 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: nightly Environment: WindowsXP SP2, JDK 5.0, Firefox 2.0.0.6, IE7 Reporter: Suran Jayathilaka Priority: Trivial Fix For: nightly Some of the guide docs in xdocs wouldn't open because of a syntax error in the DOCTYPE element. -- 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] Assigned: (AXIS2-3037) 'RuntimeException: Unexpected subelement' when wsdl adds a new property
[ https://issues.apache.org/jira/browse/AXIS2-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3037: Assignee: Amila Chinthaka Suriarachchi 'RuntimeException: Unexpected subelement' when wsdl adds a new property --- Key: AXIS2-3037 URL: https://issues.apache.org/jira/browse/AXIS2-3037 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.2 Environment: Win2k3, Java 6.0, Axis2 1.2 Reporter: Chris B Assignee: Amila Chinthaka Suriarachchi Priority: Critical Attachments: futures_new.wsdl, futures_old.wsdl, TestRunner.java I have an client app that was created and had been working, it makes a call to one webservice. The webservice was upgraded, it added some new methods and it also added a new property (Type) to one of the return types I was using. Now my app will no longer work, i get a runtime error, java.lang.RuntimeException: Unexpected subelement Type, when the results are returned to my service. If i rebuilt the client stub code using wsdl2java with the new wsdl my app will work again. As I understand it, adding fields to a object should not break any existing code. Any Xml elements returned that are not known elements should be ignored and not cause exceptions in the client code. I have tested my assumption with Visual Studio 2005, if i genereate web service client code using the old wsdl I can still call the new service without an exception being thrown because of the new Xml element being returned. Is there some option that I don't know of that will allow for new elements to be returned without exceptions being throw? -- 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-3046) Axis2 session does not timeout as expected
Axis2 session does not timeout as expected -- Key: AXIS2-3046 URL: https://issues.apache.org/jira/browse/AXIS2-3046 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Fedora Core3, J2SE 1.5.0_11-b03, Axis2-1.2 (Integrated on a tomcat webapplication) Reporter: dinh anh khoa Priority: Blocker * As the default in Axis2.xml, session will expire after 3ms (30s). * I've engaged addressing module for both server and client * I setup a service * the client call a method, its fine * client call Thread.sleep(6) * client call that method again, and its still work. It's should not working here and receive a fault message to say Invalid serviceGroupId I'm newly use Axis2, I'm not know weather this is a bug or not? could you please explain me this? 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] Resolved: (AXIS2-3035) Same configured Options object cannot be used for multiple service invocations with the same ServiceClient instance
[ https://issues.apache.org/jira/browse/AXIS2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-3035. -- Resolution: Fixed Same configured Options object cannot be used for multiple service invocations with the same ServiceClient instance --- Key: AXIS2-3035 URL: https://issues.apache.org/jira/browse/AXIS2-3035 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Ruchith Udayanga Fernando Assignee: Deepal Jayasinghe Priority: Blocker org.apache.rampart.RampartTest fails due to this! -- 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]
Engaging modules from classpath
Hi Devs, This may be beyond Axis2 1.3. At the moment, for a given .jar, we could only have one module.xml to represent a module. Axis2 already ship addressing mar module.xml in the axis2-XX.jar. What if we need to have multiple module.xmls in a given jar. Looking at the work I've been engaged with there is a possibility of having this scenario. Thus, if a multiple module.xmlsneeded for a given .jar, wouldn't it be reasonable to give it as follows, foo +-META-INF +- module-a.xml +- module-b.xml ... Thus, at deployment time, xmls can be read with the prefix module and make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org
[jira] Commented: (AXIS2-3046) Axis2 session does not timeout as expected
[ https://issues.apache.org/jira/browse/AXIS2-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516921 ] Deepal Jayasinghe commented on AXIS2-3046: -- Did you deploy your service in SoapSession scope ? Thanks Deepal Axis2 session does not timeout as expected -- Key: AXIS2-3046 URL: https://issues.apache.org/jira/browse/AXIS2-3046 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Fedora Core3, J2SE 1.5.0_11-b03, Axis2-1.2 (Integrated on a tomcat webapplication) Reporter: dinh anh khoa Priority: Blocker * As the default in Axis2.xml, session will expire after 3ms (30s). * I've engaged addressing module for both server and client * I setup a service * the client call a method, its fine * client call Thread.sleep(6) * client call that method again, and its still work. It's should not working here and receive a fault message to say Invalid serviceGroupId I'm newly use Axis2, I'm not know weather this is a bug or not? could you please explain me this? 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]
[Axis2] Engaging modules from classpath
On 8/1/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Hi Devs, This may be beyond Axis2 1.3. At the moment, for a given .jar, we could only have one module.xml to represent a module. Axis2 already ship addressing mar module.xml in the axis2-XX.jar. What if we need to have multiple module.xmls in a given jar. Looking at the work I've been engaged with there is a possibility of having this scenario. Thus, if a multiple module.xmls needed for a given .jar, wouldn't it be reasonable to give it as follows, foo +-META-INF +- module-a.xml +- module-b.xml ... Thus, at deployment time, xmls can be read with the prefix module and make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org
[jira] Assigned: (AXIS2-3040) Can Axis2 support Spring-JPA configuration
[ https://issues.apache.org/jira/browse/AXIS2-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3040: Assignee: robert lazarski Can Axis2 support Spring-JPA configuration -- Key: AXIS2-3040 URL: https://issues.apache.org/jira/browse/AXIS2-3040 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: winxp , axis2 Reporter: tommy Assignee: robert lazarski I worked fine with my spring-JPA project alone, but when I add some axis2 features into this project, and upload .aar file to the server, it shows me the exception as follows: org.apache.axis2.deployment.DeploymentException: Processing Operations Modules w ith an error of sample.spring.service.SpringInit at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) Any help appreciated -- 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-3036) Duplicate global type when importing the same xsd from two other xsd's
[ https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516926 ] Stefan Lischke commented on AXIS2-3036: --- no it is not an xmlbeans issue, cause it works when using plain xmlbeans i'm just debugging it to find the solution. There is something with the AxisResolver, that is not used when working with plain XMLbeans. Duplicate global type when importing the same xsd from two other xsd's Key: AXIS2-3036 URL: https://issues.apache.org/jira/browse/AXIS2-3036 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Stefan Lischke Assignee: Amila Chinthaka Suriarachchi Fix For: 1.3 Attachments: AXIS2-JIRA-3036.wsdl, wsdl.zip When running wsdl2java on the attached wsdl xsd files i got: [java] Caused by: org.apache.xmlbeans.XmlException: project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2: Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig# (Original global type found in file: xmldsig-core-schema.xsd) xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd seems to be very similar to AXIS2-1885 and AXIS2-1781 -- 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] Assigned: (AXIS2-3042) axis2 idea plugin pom.xml
[ https://issues.apache.org/jira/browse/AXIS2-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3042: Assignee: Lahiru Sandakith axis2 idea plugin pom.xml --- Key: AXIS2-3042 URL: https://issues.apache.org/jira/browse/AXIS2-3042 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: axis2 idea plugin pom.xml Reporter: Shivantha Huruggamuwa Assignee: Lahiru Sandakith Attachments: Axis2_Idea_Plugin_Patch_PomXMl.txt pom xml hasn't some dependencies for jar. -- 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] Assigned: (AXIS2-3038) minimal catalina security policy needed
[ https://issues.apache.org/jira/browse/AXIS2-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3038: Assignee: Charitha Kankanamge minimal catalina security policy needed --- Key: AXIS2-3038 URL: https://issues.apache.org/jira/browse/AXIS2-3038 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: M2 Environment: Linux aj-5150 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux (Ubuntu Feisty Fawn) Apache/2.2.3 (Ubuntu) mod_jk/1.2.18 configured -- resuming normal operations Tomcat 5.5 Axis 1.3-RC2 Reporter: AJ Coon Assignee: Charitha Kankanamge Fix For: 1.3 From axis-user mailing list: http://marc.info/?l=axis-userm=118590376627510w=2 As a note, I modified /etc/init.d/tomcat5.5 in the following way: snip 45 # Use the Java security manager? (yes/no) 46 #TOMCAT5_SECURITY=yes 47 TOMCAT5_SECURITY=no /snip 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] Assigned: (AXIS2-3045) Docs not opening due to syntax error in DOCTYPE
[ https://issues.apache.org/jira/browse/AXIS2-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3045: Assignee: Sanka Samaranayake Docs not opening due to syntax error in DOCTYPE --- Key: AXIS2-3045 URL: https://issues.apache.org/jira/browse/AXIS2-3045 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: nightly Environment: WindowsXP SP2, JDK 5.0, Firefox 2.0.0.6, IE7 Reporter: Suran Jayathilaka Assignee: Sanka Samaranayake Priority: Trivial Fix For: nightly Attachments: Axis2-3045.patch Some of the guide docs in xdocs wouldn't open because of a syntax error in the DOCTYPE element. -- 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-3032) Anonymous WS operation invocation
[ https://issues.apache.org/jira/browse/AXIS2-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-3032. -- Resolution: Won't Fix Anonymous WS operation invocation - Key: AXIS2-3032 URL: https://issues.apache.org/jira/browse/AXIS2-3032 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Reporter: Severin Ecker Priority: Minor I'm not 100% positive that this really is a bug, but since i got no reply neither in the users nor in the developers list i'm filing it here to raise attention. I have a webservice (using axis2 to handle the soap stuff) and I wanted to use this service with both, WSDL-based access (i was using SOAPui for this) and anonymous operation invocation (with the ServiceClient.sendReceive(OMElement elem) method). Using WSDL base access everything works as intended (e.g.: using the following SOAP envelope) soap:Envelope xmlns:soap=http://www.w3.org/2003/05/soap-envelope; xmlns:ns=http://myNS.com; soap:Header/ soap:Body ns:GetCapabilitiesRequest/ /soap:Body /soap:Envelope At service implementation site within the method getCapabilities(OMElement e); (-- this is the invoked method) the parameter e is ns:GetCapabilitiesRequest/ So far so good. Now when trying to access anonymously I have to encode the operation somewhere so I have the following envelope soap:Envelope xmlns:soap=http://www.w3.org/2003/05/soap-envelope; xmlns:ns=http://myNS.com; soap:Header/ soap:Body ns:getCapabilities in0 ns:GetCapabilitiesRequest/ /in0 /ns:getCapabilities /soap:Body /soap:Envelope The request gets resolved correcty by axis (using the SOAPMessageBodyBasedDispatcher) BUT here's the catch. Suddenly the parameter which the (correct!) service operation gets is ns:getCapabilities in0 ns:GetCapabilitiesRequest/ /in0 /ns:getCapabilities This is rather useless because in that case the service operation must be ready to handle all kinds of different parameters depending on the invocation method used!? Shouldn't the SOAPMessageBodyBasedDispatcher remove the 'meta-informational' stuff (in this case the getCapabilities (aka operation-name), and in0 (parameter direction)) and only send the real parameter to the operation? If I'm mistaken, how can I invoke an operation anonymously and does not have the problem of ending up with wrong parameters on the service side? -- 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-3032) Anonymous WS operation invocation
[ https://issues.apache.org/jira/browse/AXIS2-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516931 ] Deepal Jayasinghe commented on AXIS2-3032: -- In the WSDL case (SOAP UI) case your service get dispatch using the SOAP action you have provided , otherwise there is no way to dispatch In the second case you are sending a SOAP message with body first child being operation local name, so in that case dispatching will happen using SoapMessageBodyBasedDispatcher (as you have mentioned). And the dispatcher does not have any idea whether the payload is meta-data or actual data so that guy can not and should not remove anything. Two invoke the service using service client you have two options - Generate the client stub using ADB or any other databinding tool - Send a message like below; soap:Envelope xmlns:soap=http://www.w3.org/2003/05/soap-envelope; xmlns:ns=http://myNS.com; soap:Header/ soap:Body ns:getCapabilities/ /soap:Body /soap:Envelope Anonymous WS operation invocation - Key: AXIS2-3032 URL: https://issues.apache.org/jira/browse/AXIS2-3032 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Reporter: Severin Ecker Priority: Minor I'm not 100% positive that this really is a bug, but since i got no reply neither in the users nor in the developers list i'm filing it here to raise attention. I have a webservice (using axis2 to handle the soap stuff) and I wanted to use this service with both, WSDL-based access (i was using SOAPui for this) and anonymous operation invocation (with the ServiceClient.sendReceive(OMElement elem) method). Using WSDL base access everything works as intended (e.g.: using the following SOAP envelope) soap:Envelope xmlns:soap=http://www.w3.org/2003/05/soap-envelope; xmlns:ns=http://myNS.com; soap:Header/ soap:Body ns:GetCapabilitiesRequest/ /soap:Body /soap:Envelope At service implementation site within the method getCapabilities(OMElement e); (-- this is the invoked method) the parameter e is ns:GetCapabilitiesRequest/ So far so good. Now when trying to access anonymously I have to encode the operation somewhere so I have the following envelope soap:Envelope xmlns:soap=http://www.w3.org/2003/05/soap-envelope; xmlns:ns=http://myNS.com; soap:Header/ soap:Body ns:getCapabilities in0 ns:GetCapabilitiesRequest/ /in0 /ns:getCapabilities /soap:Body /soap:Envelope The request gets resolved correcty by axis (using the SOAPMessageBodyBasedDispatcher) BUT here's the catch. Suddenly the parameter which the (correct!) service operation gets is ns:getCapabilities in0 ns:GetCapabilitiesRequest/ /in0 /ns:getCapabilities This is rather useless because in that case the service operation must be ready to handle all kinds of different parameters depending on the invocation method used!? Shouldn't the SOAPMessageBodyBasedDispatcher remove the 'meta-informational' stuff (in this case the getCapabilities (aka operation-name), and in0 (parameter direction)) and only send the real parameter to the operation? If I'm mistaken, how can I invoke an operation anonymously and does not have the problem of ending up with wrong parameters on the service side? -- 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-3036) Duplicate global type when importing the same xsd from two other xsd's
[ https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Lischke updated AXIS2-3036: -- Comment: was deleted Duplicate global type when importing the same xsd from two other xsd's Key: AXIS2-3036 URL: https://issues.apache.org/jira/browse/AXIS2-3036 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Stefan Lischke Assignee: Amila Chinthaka Suriarachchi Fix For: 1.3 Attachments: AXIS2-JIRA-3036.wsdl, AXIS2-JIRA-3036.zip, wsdl.zip When running wsdl2java on the attached wsdl xsd files i got: [java] Caused by: org.apache.xmlbeans.XmlException: project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2: Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig# (Original global type found in file: xmldsig-core-schema.xsd) xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd seems to be very similar to AXIS2-1885 and AXIS2-1781 -- 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-3036) Duplicate global type when importing the same xsd from two other xsd's
[ https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Lischke updated AXIS2-3036: -- Attachment: AXIS2-JIRA-3036.zip the latest example to track down the problem Duplicate global type when importing the same xsd from two other xsd's Key: AXIS2-3036 URL: https://issues.apache.org/jira/browse/AXIS2-3036 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Stefan Lischke Assignee: Amila Chinthaka Suriarachchi Fix For: 1.3 Attachments: AXIS2-JIRA-3036.wsdl, AXIS2-JIRA-3036.zip, wsdl.zip When running wsdl2java on the attached wsdl xsd files i got: [java] Caused by: org.apache.xmlbeans.XmlException: project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2: Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig# (Original global type found in file: xmldsig-core-schema.xsd) xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd seems to be very similar to AXIS2-1885 and AXIS2-1781 -- 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] Assigned: (AXIS2-3043) wsdl2java using jaxbri data binding fails
[
https://issues.apache.org/jira/browse/AXIS2-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3043:
Assignee: Amila Chinthaka Suriarachchi
wsdl2java using jaxbri data binding fails
-
Key: AXIS2-3043
URL: https://issues.apache.org/jira/browse/AXIS2-3043
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: databinding
Affects Versions: nightly
Environment: Axis2 1.3 Nightly; websphere6; eclipse 3.3
Reporter: Pierre Casenove
Assignee: Amila Chinthaka Suriarachchi
Attachments: faultywsdl.zip
When trying to generate the java code from the attached wsdl using jaxbri
databinding, an Exception is returned:
[java] Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped
to the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
[java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
[java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
[java] Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException:No type was mapped
to the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1363
)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
[java] ... 2 more
[java] Caused by:
org.apache.axis2.wsdl.databinding.UnmatchedTypeException: No type was mapped
to the name TEST_REQUETE with namespace
http://www.almerys.com/services/FSAServiceTest/xsd
[java] at
org.apache.axis2.wsdl.databinding.TypeMappingAdapter.getTypeMappingName(TypeMappingAdapter.java:82
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getInputParamElement(AxisServiceBasedMultiLanguageEmitter.java:2823
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getInputElement(AxisServiceBasedMultiLanguageEmitter.java:2623
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.generateMethodElement(AxisServiceBasedMultiLanguageEmitter.java:2191
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:2117
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForSkeleton(AxisServiceBasedMultiLanguageEmitter.java:2033
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1964
)
[java] at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1320
)
[java] ... 3 more
Using the xjc.bat script provided in the offcial JAXB2.0.5 release, the
classes are generated correctly.
Java code is also generated correctly with xmlbeans and adb databinding.
Ant task:
target name=wsdl2java depends=clean,prepare
delete dir=output /
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath /
arg value=-d /
arg value=jaxbri /
arg value=-u /
arg value=-uri /
arg file=${dir.wsdl}/${uri.wsdl} /
arg value=-ss /
arg value=-wv /
arg value=1.1 /
arg value=-g /
arg value=-sd /
arg value=-o /
arg file=output /
arg value=-p /
arg value=${package.prefix} /
/java
mkdir dir=output/resources/META-INF /
move todir=output/resources/META-INF
fileset dir=output/resources
!-- axis2 web services definitions file --
include name=services.xml /
include name=*.wsdl /
include name=*.xsd /
/fileset
/move
/target
--
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:
[jira] Commented: (AXIS2-3036) Duplicate global type when importing the same xsd from two other xsd's
[ https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516928 ] Stefan Lischke commented on AXIS2-3036: --- I've added the cleaned wsdl from Brian and downloaded the xsd and put them in a zip. that shows this bug. (AXIS2-JIRA-3036.zip) Duplicate global type when importing the same xsd from two other xsd's Key: AXIS2-3036 URL: https://issues.apache.org/jira/browse/AXIS2-3036 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Stefan Lischke Assignee: Amila Chinthaka Suriarachchi Fix For: 1.3 Attachments: AXIS2-JIRA-3036.wsdl, AXIS2-JIRA-3036.zip, wsdl.zip When running wsdl2java on the attached wsdl xsd files i got: [java] Caused by: org.apache.xmlbeans.XmlException: project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2: Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig# (Original global type found in file: xmldsig-core-schema.xsd) xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd seems to be very similar to AXIS2-1885 and AXIS2-1781 -- 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-3024) CodegenToolReference.html totally out of date
[ https://issues.apache.org/jira/browse/AXIS2-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-3024. - Resolution: Fixed update the wsdl2java documentation according to the current code. CodegenToolReference.html totally out of date - Key: AXIS2-3024 URL: https://issues.apache.org/jira/browse/AXIS2-3024 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Reporter: Davanum Srinivas Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Fix For: 1.3 Ant task documentation is totally out of date. (CodegenToolReference.html). Need to add documentation for m2 task as well. -- 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] Assigned: (AXIS2-3046) Axis2 session does not timeout as expected
[ https://issues.apache.org/jira/browse/AXIS2-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3046: Assignee: Deepal Jayasinghe Axis2 session does not timeout as expected -- Key: AXIS2-3046 URL: https://issues.apache.org/jira/browse/AXIS2-3046 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Fedora Core3, J2SE 1.5.0_11-b03, Axis2-1.2 (Integrated on a tomcat webapplication) Reporter: dinh anh khoa Assignee: Deepal Jayasinghe Priority: Blocker * As the default in Axis2.xml, session will expire after 3ms (30s). * I've engaged addressing module for both server and client * I setup a service * the client call a method, its fine * client call Thread.sleep(6) * client call that method again, and its still work. It's should not working here and receive a fault message to say Invalid serviceGroupId I'm newly use Axis2, I'm not know weather this is a bug or not? could you please explain me this? 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]
[Axis2] Code freeze in Axis2 1.3 branch
Hi Devs, I think now are in a good position to go ahead with the release so no need to fix any of the existing JIRAs , I am thinking of cutting the release immediately after Woden release their release. So lets us stop commiting to the branch and let's only commit the code which are related to - Release related - Documents changes Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2873) WS-Addressing EndpointReference elements not getting added in the outgoing soap message
[ https://issues.apache.org/jira/browse/AXIS2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516934 ] Deepal Jayasinghe commented on AXIS2-2873: -- Will you be able to test with Axis2 1.3 RC2 Thanks Deepal WS-Addressing EndpointReference elements not getting added in the outgoing soap message --- Key: AXIS2-2873 URL: https://issues.apache.org/jira/browse/AXIS2-2873 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Addressing Affects Versions: 1.2 Environment: Axis2 - 1.2 on windows xp Reporter: Shantanu Sen Assignee: Amila Chinthaka Suriarachchi I have deployed a service which requires WS-Addressing - here is a parrt of the WSDL --- wsdl:binding name=AddressBookServiceSOAP11Binding type=axis2:AddressBookServicePortType wsaw:UsingAddressing wsdl:required=true / wsdl:operation name=addEntry soap:operation soapAction=urn:addEntry style=document/ wsdl:input soap:body use=literal/ /wsdl:input /wsdl:operation wsdl:operation name=findEntry soap:operation soapAction=urn:findEntry style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=AddressBookService wsdl:port name=AddressBookServiceSOAP11port_http binding=axis2:AddressBookServiceSOAP11Binding http://localhost:8080/axis2/services/AddressBookService/ wsa:EndpointReference wsa:AddressRouterService/wsa:Address wsa:ReferenceParameters testhello/test /wsa:ReferenceParameters wsa:Metadata wsaw:ServiceNameServiceXXX/wsaw:ServiceName /wsa:Metadata /wsa:EndpointReference /wsdl:port /wsdl:service -- When I generate a stub with this wsdl, I do not see any of the wsa:EndpointReference that I specify in the wsdl. I thought that the stub should contain this and generate the content in the ws-addressing headers. Instead I only get the following headers in the outgoing call: --- soapenv:Header http://localhost:8070/axis2/services/AddressBookService wsa:MessageIDurn:uuid:E21E2EE85BA5DDC1121183011196876/wsa:MessageID wsa:Actionurn:addEntry/wsa:Action /soapenv:Header --- It should be mandatory to include the wsa:Metadata and wsaReferenceParameters etc from the wsdl in outgoing call from the client. The user should not have to do this manually - the generated stub should include these just as it includes the wsa:Action now. -- 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-703) Management module - persistent configuration
[ https://issues.apache.org/jira/browse/AXIS2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-703. - Resolution: Fixed seems like we have not found a use for this. Thanks Deepal Management module - persistent configuration Key: AXIS2-703 URL: https://issues.apache.org/jira/browse/AXIS2-703 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: modules Environment: Management Reporter: Chathura Ekanayake Assignee: Deepal Jayasinghe Priority: Minor Attachments: axis2management5.patch Management module provides functionalities to monitor and configur remote Axis2 engines. Currently it provides configuring API using web services and jmx. It also monitors statistics of remote engines like incoming and outgoing messages at global, service and operation levels. Code is located at the url: https://svn.apache.org/repos/asf/webservices/axis2/archive/java/scratch/Axis_Management_module Currently the configurations made for Axis2 by using the above management API or by the admin webapp are not persistent after system restarts. The management module is improved to provide such persistent support by saving the entire configuration to an xml file and loading it back to the remote engines after system restarts. -- 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-1943) RPC Message receivers does not validate the request against the schema
[ https://issues.apache.org/jira/browse/AXIS2-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1943. -- Resolution: Won't Fix RPC Message receivers does not validate the request against the schema Key: AXIS2-1943 URL: https://issues.apache.org/jira/browse/AXIS2-1943 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Deepal Jayasinghe Assignee: Deepal Jayasinghe soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body findEntry xmlns=http://service.addressbook.sample/xsd; arg0 xmlns=Abby Cadabby/arg0 /findEntry /soapenv:Body /soapenv:Envelope -- 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-2571) SOAPAction mismatch invoking service
[ https://issues.apache.org/jira/browse/AXIS2-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2571. -- Resolution: Invalid seems to me that , this is not an Axis2 issue SOAPAction mismatch invoking service Key: AXIS2-2571 URL: https://issues.apache.org/jira/browse/AXIS2-2571 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Addressing Environment: Ubuntu Linux 6.10, Sun JDK 1.4.2, Apache Tomcat 5.5.23 Reporter: Jose Antonio Assignee: Brian DePradine I'm trying to invoke an Axis2 service inside a Muse service. To do this I'm using the Axis2 service stub I generated but when I send a message I get the following: POST /axis2/services/RegistrationService HTTP/1.1 SOAPAction: http://docs.oasis-open.org/wscaf/2005/10/wscf/RegistrationServicePortType/addParticipantResponse; User-Agent: Axis2 Host: 127.0.0.1:8081 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 545 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:8081/axis2/services/RegistrationService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:63015A36B234BC96B8117708283322511/wsa:MessageID wsa:Actionhttp://docs.oasis-open.org/wscaf/2005/10/wscf/RegistrationServicePortType/addParticipant/wsa:Action /soapenv:Header As you can see, the SOAPAction and wsa Action elements are different and I don't know why. Using this same Stub in a local program I get the same text in both elements and the call succeed but using it in Muse gets this 'Response' part added. Is it a Muse or an Axis2 problem? Does Axis2 add a 'Response' element for every outgoing message in a service? -- 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-2148) AxisFault: Mapping qname not fond for the package:...
[
https://issues.apache.org/jira/browse/AXIS2-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2148.
--
Resolution: Fixed
No user comment on this issue, seems like issue is fixed.
Thanks
Deepal
AxisFault: Mapping qname not fond for the package:...
-
Key: AXIS2-2148
URL: https://issues.apache.org/jira/browse/AXIS2-2148
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: adb
Affects Versions: nightly
Environment: Linux Fedora5, tomcat 6.0.7 java1.5.0_0.9, Axis2 snapshot
Reporter: Federica Ciotti
Assignee: Deepal Jayasinghe
Trying to invoke a method that returns an object
org.apache.juddi.datatype.response.BusinessList this exception is thrown.
BusinessList is a complex structure that contains a BusinessInfos, that
contains a BusinessInfo, that contains a Vector.
How should be the returnType arg I pass to the RPCclient.invokeBlocking
method:
Class[] returnTypes = new Class[] {BusinessList.class, BusinessInfos.class,
BusinessInfo.class};
or just Class[] returnTypes = new Class[] {BusinessList.class};
How can I establish a mapping for packages?
Many Thanks
f
SEVERE: Exception occurred while trying to invoke service method findBusiness3
org.apache.axiom.om.OMException: java.lang.RuntimeException:
org.apache.axis2.AxisFault: Mapping qname not fond for the package:
org.apache.juddi.datatype.response
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:203)
at org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:318)
at
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:632)
at
org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:599)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:117)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:249)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:202)
at
org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:97)
at
org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:209)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:177)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:271)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:212)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:634)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping
qname not fond for the package: org.apache.juddi.datatype.response
at
org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:239)
at
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:948)
at
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:802)
at
org.apache.axis2.databinding.utils.reader.WrappingXMLStreamReader.next(WrappingXMLStreamReader.java:45)
at
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:824)
at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:68)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:120)
[jira] Resolved: (AXIS2-1846) Client code does not parse AxisFault correctly.
[
https://issues.apache.org/jira/browse/AXIS2-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1846.
--
Resolution: Fixed
First test with Axis2 1.3 RC2 , if the issue is there then please re-open the
issue with the necessary data to re-create the issue
Thanks
Deepal
Client code does not parse AxisFault correctly.
---
Key: AXIS2-1846
URL: https://issues.apache.org/jira/browse/AXIS2-1846
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: client-api, codegen
Affects Versions: 1.1
Environment: Linux.
Reporter: Sathija Pavuluri
Assignee: Thilina Gunarathne
I am investigating the exception handling capability of Axis and created a
sample web service.
My axis web service is throwing an exception wrapped inside an AxisFault. The
service uses rampart for security.
This is what is in the service class method:
if (devices == null) {
throw new AxisFault(new NullPointerException(No devices have
been rerieved));
}
and the method throws AxisFault.
When i invoke this call and no exception is returned, the result is obtained
without a problem.
However, when I invoke the axis client which calls this service with
parameters in a way that I expect to get the NullPointerException above, I
get the output stack shown below.
org.apache.rampart.RampartException: Error in extracting message properties
at
org.apache.rampart.RampartMessageData.init(RampartMessageData.java:281)
at org.apache.rampart.RampartEngine.process(RampartEngine.java:39)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:74)
at org.apache.axis2.engine.Phase.invoke(Phase.java:377)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:513)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:484)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:282)
at
com.emprisa.ena.ws.client.DeviceServiceStub.listDevices(DeviceServiceStub.java:157)
at
com.emprisa.ena.ws.client.DeviceServiceInvoker.invokeListDevices(DeviceServiceInvoker.java:83)
at
com.emprisa.ena.ws.client.DeviceServiceInvoker.main(DeviceServiceInvoker.java:66)
Caused by: org.apache.ws.security.WSSecurityException: Error in converting
SOAP Envelope to Document; nested exception is:
org.apache.axiom.om.OMException: java.lang.IllegalStateException:
Current state not START_ELEMENT
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:123)
at
org.apache.rampart.RampartMessageData.init(RampartMessageData.java:145)
... 10 more
Caused by: org.apache.axiom.om.OMException: java.lang.IllegalStateException:
Current state not START_ELEMENT
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:199)
at org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:316)
at
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:620)
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:87)
... 11 more
Caused by: java.lang.IllegalStateException: Current state not START_ELEMENT
at
com.ctc.wstx.sr.BasicStreamReader.getAttributeCount(BasicStreamReader.java:582)
at
org.apache.axiom.om.impl.builder.StAXBuilder.processAttributes(StAXBuilder.java:130)
at
org.apache.axiom.om.impl.mtom.MTOMStAXSOAPModelBuilder.createOMElement(MTOMStAXSOAPModelBuilder.java:126)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:125)
... 14 more
Given below is the soap response as seen in the tcp monitor. This response
looks as expected. I see the NullPointerException and the associated message.
--MIMEBoundaryurn_uuid_EFA4931C229F601AC111655076265521
content-type: application/xop+xml; charset=UTF-8; type=text/xml;
content-transfer-encoding: binary
content-id: 0.urn:uuid:[EMAIL PROTECTED]
?xml version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header /
soapenv:Bodysoapenv:Faultfaultcodesoapenv:Client/faultcodefaultstringNo
devices have been rerieved; nested exception is:
java.lang.NullPointerException: No devices have been
rerieved/faultstringdetail
Exceptionorg.apache.axis2.AxisFault: No devices have been rerieved;
nested exception is:
java.lang.NullPointerException: No devices have been rerieved
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:184)
[jira] Updated: (AXIS2-3046) Axis2 session does not timeout as expected
[ https://issues.apache.org/jira/browse/AXIS2-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe updated AXIS2-3046: - Priority: Critical (was: Blocker) Axis2 session does not timeout as expected -- Key: AXIS2-3046 URL: https://issues.apache.org/jira/browse/AXIS2-3046 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Fedora Core3, J2SE 1.5.0_11-b03, Axis2-1.2 (Integrated on a tomcat webapplication) Reporter: dinh anh khoa Assignee: Deepal Jayasinghe Priority: Critical * As the default in Axis2.xml, session will expire after 3ms (30s). * I've engaged addressing module for both server and client * I setup a service * the client call a method, its fine * client call Thread.sleep(6) * client call that method again, and its still work. It's should not working here and receive a fault message to say Invalid serviceGroupId I'm newly use Axis2, I'm not know weather this is a bug or not? could you please explain me this? 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] Commented: (AXIS2-1943) RPC Message receivers does not validate the request against the schema
[ https://issues.apache.org/jira/browse/AXIS2-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516939 ] Martijn Kooijman commented on AXIS2-1943: - Why is this set to won't fix ? Isn't it important to validate incoming requests? Or is there some other way to validate that I missed? RPC Message receivers does not validate the request against the schema Key: AXIS2-1943 URL: https://issues.apache.org/jira/browse/AXIS2-1943 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Deepal Jayasinghe Assignee: Deepal Jayasinghe soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body findEntry xmlns=http://service.addressbook.sample/xsd; arg0 xmlns=Abby Cadabby/arg0 /findEntry /soapenv:Body /soapenv:Envelope -- 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-2243) When running the databinding sample if a wrong symbol is specified, a successful response is given without throwing an error
[ https://issues.apache.org/jira/browse/AXIS2-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanka Samaranayake resolved AXIS2-2243. --- Resolution: Fixed Already applied. Thanks Suran When running the databinding sample if a wrong symbol is specified, a successful response is given without throwing an error Key: AXIS2-2243 URL: https://issues.apache.org/jira/browse/AXIS2-2243 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: nightly Environment: Windows XP, JDK 1.4.2_13, Firefox version 1.5.0.8 Reporter: Evanthika Amarasiri Assignee: Deepal Jayasinghe Priority: Critical Fix For: 1.3 Attachments: AXIS2-2243.patch Was running the databinding sample and experienced the following. Below are the steps taken to produce the issue 1. Execute the command ant run.client -Durl=http://localhost:8080/axis2/services/StockQuoteService -Dsymbol=IBM and received the results successfully. 2. Executed the same command with a wrong symbol E.g.:- ant run.client -Durl=http://localhost:8080/axis2/services/StockQuoteService -Dsymbol=TEST and you will still get the same results. Since this symbol does not exist, it should throw an error instead. -- 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]
Re: [Axis2] Engaging modules from classpath
Would it be feasible (and possible) to describe multiple modules within a single XML file? Instead of having multiple XML files in a JAR could we allow the use of a modules.xml with multipe module elements? If this is possible it may make things easier on the end user by reducing the number of deployment descriptors that need to be produced/maintained. Saminda Abeyruwan [EMAIL PROTECTED] wrote: On 8/1/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Hi Devs, This may be beyond Axis2 1.3. At the moment, for a given .jar, we could only have one module.xml to represent a module. Axis2 already ship addressing mar module.xml in the axis2-XX.jar. What if we need to have multiple module.xmls in a given jar. Looking at the work I've been engaged with there is a possibility of having this scenario. Thus, if a multiple module.xmls needed for a given .jar, wouldn't it be reasonable to give it as follows, foo +-META-INF +- module-a.xml +- module-b.xml ... Thus, at deployment time, xmls can be read with the prefix module and make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.
[jira] Commented: (AXIS2-3040) Can Axis2 support Spring-JPA configuration
[ https://issues.apache.org/jira/browse/AXIS2-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516953 ] robert lazarski commented on AXIS2-3040: When you say JPA, are you running this in tomcat or some other application server? Could you clarify your environment further? Please upload your AAR or create simple test case that can be uploaded as an AAR. Can Axis2 support Spring-JPA configuration -- Key: AXIS2-3040 URL: https://issues.apache.org/jira/browse/AXIS2-3040 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: winxp , axis2 Reporter: tommy Assignee: robert lazarski I worked fine with my spring-JPA project alone, but when I add some axis2 features into this project, and upload .aar file to the server, it shows me the exception as follows: org.apache.axis2.deployment.DeploymentException: Processing Operations Modules w ith an error of sample.spring.service.SpringInit at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) Any help appreciated -- 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]
Re: [Axis2] Code freeze in Axis2 1.3 branch
How about a RC3 while we wait for Woden? thanks, dims On 8/1/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Devs, I think now are in a good position to go ahead with the release so no need to fix any of the existing JIRAs , I am thinking of cutting the release immediately after Woden release their release. So lets us stop commiting to the branch and let's only commit the code which are related to - Release related - Documents changes Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3045) Docs not opening due to syntax error in DOCTYPE
[ https://issues.apache.org/jira/browse/AXIS2-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanka Samaranayake resolved AXIS2-3045. --- Resolution: Fixed Applied. Thanks Suran. Committed revision 561777. Committed revision 561781. Docs not opening due to syntax error in DOCTYPE --- Key: AXIS2-3045 URL: https://issues.apache.org/jira/browse/AXIS2-3045 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: nightly Environment: WindowsXP SP2, JDK 5.0, Firefox 2.0.0.6, IE7 Reporter: Suran Jayathilaka Assignee: Sanka Samaranayake Priority: Trivial Fix For: nightly Attachments: Axis2-3045.patch Some of the guide docs in xdocs wouldn't open because of a syntax error in the DOCTYPE element. -- 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]
Re: [Axis2] Engaging modules from classpath
+1 to modules.xml with multipe module elements On 8/1/07, Dustin Amrhein [EMAIL PROTECTED] wrote: Would it be feasible (and possible) to describe multiple modules within a single XML file? Instead of having multiple XML files in a JAR could we allow the use of a modules.xml with multipe module elements? If this is possible it may make things easier on the end user by reducing the number of deployment descriptors that need to be produced/maintained. Saminda Abeyruwan [EMAIL PROTECTED] wrote: On 8/1/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Hi Devs, This may be beyond Axis2 1.3. At the moment, for a given .jar, we could only have one module.xml to represent a module. Axis2 already ship addressing mar module.xml in the axis2-XX.jar. What if we need to have multiple module.xmls in a given jar. Looking at the work I've been engaged with there is a possibility of having this scenario. Thus, if a multiple module.xmls needed for a given .jar, wouldn't it be reasonable to give it as follows, foo +-META-INF +- module-a.xml +- module-b.xml ... Thus, at deployment time, xmls can be read with the prefix module and make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3047) Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault XmlComplexContentImpl
[ https://issues.apache.org/jira/browse/AXIS2-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Granado updated AXIS2-3047: - Description: Hi! This is my first bug submission, so I'll try to do it correctly (^__^) We have used the attached wsdl (validated against Eclipse WTP and Oxygen) to create a webservice using the wsdl2java as follows (axis2 1.2): java -cp $CLASSPATH org.apache.axis2.wsdl.WSDL2Java -uri ../amService-SOAP/resources/amService-new_v5.wsdl -p eu.eu4all.services.recommendations -d adb -s -ss -sd -g -t It worked ok, so we learned how to add code at the generated skeleton (attached too) and we tested using both a java client and a different webservice platform (openACS), with same result (using tcpmon to take a look at the xml exchange): HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:11:55 GMT Connection: close 11d ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringData binding error/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope In case of java client the exception was org.apache.axis2.AxisFault: Data binding error at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at eu.eu4all.services.recommendations.AmServiceStub.sendEventToAm(AmServiceStub.java:151) at Client.multipleParameters(Client.java:34) at Client.main(Client.java:11) So, reading some other bugs resolved around, we decided to jump to axis1.3RC2, compiled again everything and installing new services, with quite a different result: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:22:59 GMT Connection: close 140 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringorg.apache.xmlbeans.impl.values.XmlComplexContentImpl/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 But we can get no more information from logs... We're stuck here, we tried changing from Tomcat6 to 5, but results were the same. Please tell us if we can provide more information or debug dat. Thanks a lot for your help. Regards jorge was: Hi! This is my first bug submission, so I'll try to do it correctly (^__^) We have used the attached wsdl (validated against Eclipse WTP and Oxygen) to create a webservice using the wsdl2java as follows (axis2 1.2): java -cp $CLASSPATH org.apache.axis2.wsdl.WSDL2Java -uri ../amService-SOAP/resources/amService-new_v5.wsdl -p eu.eu4all.services.recommendations -d adb -s -ss -sd -g -t It worked ok, so we learned how to add code at the generated skeleton (attached too) and we tested using both a java client and a different webservice platform (openACS), with same result (using tcpmon to take a look at the xml exchange): HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:11:55 GMT Connection: close 11d ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringData binding error/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope In case of java client the exception was org.apache.axis2.AxisFault: Data binding error at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at eu.eu4all.services.recommendations.AmServiceStub.sendEventToAm(AmServiceStub.java:151) at Client.multipleParameters(Client.java:34) at Client.main(Client.java:11) So, reading some other bugs resolved around, we decided to jump to axis1.3RC2, compiled again everything and installing new services, with quite a different result: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01
[jira] Commented: (AXIS2-3036) Duplicate global type when importing the same xsd from two other xsd's
[
https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516966
]
Stefan Lischke commented on AXIS2-3036:
---
I found and fixed this issue
The problem was, that The Axis2EntityResolver returned an InputSource with a
Reader in it and not an InputStream. XMLBeans uses a digest value to find
already scanned files. And those digest is only generated when using an
InputStream in an InputSource, so just add replace Method
getSchemaAsReader(XmlSchema schema)
with
private InputStream getSchemaAsInputStream(XmlSchema schema){
ByteArrayOutputStream baos = new
ByteArrayOutputStream();
schema.write(baos);
return new ByteArrayInputStream(baos.toByteArray());
}
and modify the both calls to them.
;-)
Duplicate global type when importing the same xsd from two other xsd's
Key: AXIS2-3036
URL: https://issues.apache.org/jira/browse/AXIS2-3036
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Reporter: Stefan Lischke
Assignee: Amila Chinthaka Suriarachchi
Fix For: 1.3
Attachments: AXIS2-JIRA-3036.wsdl, AXIS2-JIRA-3036.zip, wsdl.zip
When running wsdl2java on the attached wsdl xsd files i got:
[java] Caused by: org.apache.xmlbeans.XmlException:
project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2:
Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig#
(Original global type found in file: xmldsig-core-schema.xsd)
xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd
seems to be very similar to AXIS2-1885 and AXIS2-1781
--
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-3047) Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault
[ https://issues.apache.org/jira/browse/AXIS2-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Granado updated AXIS2-3047: - Attachment: Client.java Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault --- Key: AXIS2-3047 URL: https://issues.apache.org/jira/browse/AXIS2-3047 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3, 1.2 Environment: Mac OS X 10.4.10, jdk 1.5.0_07, Tomcat 5 6, axis2 1.2 1.3RC2 Reporter: Jorge Granado Priority: Blocker Attachments: amService.wsdl, AmServiceSkeleton.java, Client.java Hi! This is my first bug submission, so I'll try to do it correctly (^__^) We have used the attached wsdl (validated against Eclipse WTP and Oxygen) to create a webservice using the wsdl2java as follows (axis2 1.2): java -cp $CLASSPATH org.apache.axis2.wsdl.WSDL2Java -uri ../amService-SOAP/resources/amService-new_v5.wsdl -p eu.eu4all.services.recommendations -d adb -s -ss -sd -g -t It worked ok, so we learned how to add code at the generated skeleton (attached too) and we tested using both a java client and a different webservice platform (openACS), with same result (using tcpmon to take a look at the xml exchange): HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:11:55 GMT Connection: close 11d ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringData binding error/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope In case of java client the exception was org.apache.axis2.AxisFault: Data binding error at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at eu.eu4all.services.recommendations.AmServiceStub.sendEventToAm(AmServiceStub.java:151) at Client.multipleParameters(Client.java:34) at Client.main(Client.java:11) So, reading some other bugs resolved around, we decided to jump to axis1.3RC2, compiled again everything and installing new services, with quite a different result: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:22:59 GMT Connection: close 140 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringorg.apache.xmlbeans.impl.values.XmlComplexContentImpl/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 But we can get no more information from logs... We're stuck here, we tried changing from Tomcat6 to 5, but results were the same. Thanks a lot for your help. Regards jorge -- 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-3047) Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault
Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault --- Key: AXIS2-3047 URL: https://issues.apache.org/jira/browse/AXIS2-3047 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.2, 1.3 Environment: Mac OS X 10.4.10, jdk 1.5.0_07, Tomcat 5 6, axis2 1.2 1.3RC2 Reporter: Jorge Granado Priority: Blocker Attachments: amService.wsdl Hi! This is my first bug submission, so I'll try to do it correctly (^__^) We have used the attached wsdl (validated against Eclipse WTP and Oxygen) to create a webservice using the wsdl2java as follows (axis2 1.2): java -cp $CLASSPATH org.apache.axis2.wsdl.WSDL2Java -uri ../amService-SOAP/resources/amService-new_v5.wsdl -p eu.eu4all.services.recommendations -d adb -s -ss -sd -g -t It worked ok, so we learned how to add code at the generated skeleton (attached too) and we tested using both a java client and a different webservice platform (openACS), with same result (using tcpmon to take a look at the xml exchange): HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:11:55 GMT Connection: close 11d ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringData binding error/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope In case of java client the exception was org.apache.axis2.AxisFault: Data binding error at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at eu.eu4all.services.recommendations.AmServiceStub.sendEventToAm(AmServiceStub.java:151) at Client.multipleParameters(Client.java:34) at Client.main(Client.java:11) So, reading some other bugs resolved around, we decided to jump to axis1.3RC2, compiled again everything and installing new services, with quite a different result: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:22:59 GMT Connection: close 140 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringorg.apache.xmlbeans.impl.values.XmlComplexContentImpl/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 But we can get no more information from logs... We're stuck here, we tried changing from Tomcat6 to 5, but results were the same. Thanks a lot for your help. Regards jorge -- 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-3044) Cannot generate code giving a remote HTTP URI, when the client is behind an HTTP proxy server
[ https://issues.apache.org/jira/browse/AXIS2-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516959 ] Davanum Srinivas commented on AXIS2-3044: - Azeez, did you try the standard java properties? http.proxyHost etc. thanks, dims Cannot generate code giving a remote HTTP URI, when the client is behind an HTTP proxy server - Key: AXIS2-3044 URL: https://issues.apache.org/jira/browse/AXIS2-3044 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Afkham Azeez Assignee: Amila Chinthaka Suriarachchi Priority: Critical Fix For: nightly We should provide a options to wsdl2java such as; http-proxy-host http-proxy-port to facilitate this. At the moment, users behind a proxy server cannot codegen for remote WSDLs exposed via HTTP. -- 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-3047) Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault
[ https://issues.apache.org/jira/browse/AXIS2-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Granado updated AXIS2-3047: - Attachment: amService.wsdl Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault --- Key: AXIS2-3047 URL: https://issues.apache.org/jira/browse/AXIS2-3047 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3, 1.2 Environment: Mac OS X 10.4.10, jdk 1.5.0_07, Tomcat 5 6, axis2 1.2 1.3RC2 Reporter: Jorge Granado Priority: Blocker Attachments: amService.wsdl Hi! This is my first bug submission, so I'll try to do it correctly (^__^) We have used the attached wsdl (validated against Eclipse WTP and Oxygen) to create a webservice using the wsdl2java as follows (axis2 1.2): java -cp $CLASSPATH org.apache.axis2.wsdl.WSDL2Java -uri ../amService-SOAP/resources/amService-new_v5.wsdl -p eu.eu4all.services.recommendations -d adb -s -ss -sd -g -t It worked ok, so we learned how to add code at the generated skeleton (attached too) and we tested using both a java client and a different webservice platform (openACS), with same result (using tcpmon to take a look at the xml exchange): HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:11:55 GMT Connection: close 11d ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringData binding error/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope In case of java client the exception was org.apache.axis2.AxisFault: Data binding error at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at eu.eu4all.services.recommendations.AmServiceStub.sendEventToAm(AmServiceStub.java:151) at Client.multipleParameters(Client.java:34) at Client.main(Client.java:11) So, reading some other bugs resolved around, we decided to jump to axis1.3RC2, compiled again everything and installing new services, with quite a different result: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:22:59 GMT Connection: close 140 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringorg.apache.xmlbeans.impl.values.XmlComplexContentImpl/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 But we can get no more information from logs... We're stuck here, we tried changing from Tomcat6 to 5, but results were the same. Thanks a lot for your help. Regards jorge -- 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-3047) Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault
[ https://issues.apache.org/jira/browse/AXIS2-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Granado updated AXIS2-3047: - Attachment: AmServiceSkeleton.java Data Binding error using XMLBeans under axis1.2 turns into 1.3RC2 AxisFault --- Key: AXIS2-3047 URL: https://issues.apache.org/jira/browse/AXIS2-3047 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3, 1.2 Environment: Mac OS X 10.4.10, jdk 1.5.0_07, Tomcat 5 6, axis2 1.2 1.3RC2 Reporter: Jorge Granado Priority: Blocker Attachments: amService.wsdl, AmServiceSkeleton.java, Client.java Hi! This is my first bug submission, so I'll try to do it correctly (^__^) We have used the attached wsdl (validated against Eclipse WTP and Oxygen) to create a webservice using the wsdl2java as follows (axis2 1.2): java -cp $CLASSPATH org.apache.axis2.wsdl.WSDL2Java -uri ../amService-SOAP/resources/amService-new_v5.wsdl -p eu.eu4all.services.recommendations -d adb -s -ss -sd -g -t It worked ok, so we learned how to add code at the generated skeleton (attached too) and we tested using both a java client and a different webservice platform (openACS), with same result (using tcpmon to take a look at the xml exchange): HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:11:55 GMT Connection: close 11d ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringData binding error/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope In case of java client the exception was org.apache.axis2.AxisFault: Data binding error at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at eu.eu4all.services.recommendations.AmServiceStub.sendEventToAm(AmServiceStub.java:151) at Client.multipleParameters(Client.java:34) at Client.main(Client.java:11) So, reading some other bugs resolved around, we decided to jump to axis1.3RC2, compiled again everything and installing new services, with quite a different result: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 01 Aug 2007 12:22:59 GMT Connection: close 140 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringorg.apache.xmlbeans.impl.values.XmlComplexContentImpl/faultstring detail / /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 But we can get no more information from logs... We're stuck here, we tried changing from Tomcat6 to 5, but results were the same. Thanks a lot for your help. Regards jorge -- 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-3036) Duplicate global type when importing the same xsd from two other xsd's
[ https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516968 ] Davanum Srinivas commented on AXIS2-3036: - wow! that's excellent work! Duplicate global type when importing the same xsd from two other xsd's Key: AXIS2-3036 URL: https://issues.apache.org/jira/browse/AXIS2-3036 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Stefan Lischke Assignee: Amila Chinthaka Suriarachchi Fix For: 1.3 Attachments: AXIS2-JIRA-3036.wsdl, AXIS2-JIRA-3036.zip, wsdl.zip When running wsdl2java on the attached wsdl xsd files i got: [java] Caused by: org.apache.xmlbeans.XmlException: project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2: Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig# (Original global type found in file: xmldsig-core-schema.xsd) xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd seems to be very similar to AXIS2-1885 and AXIS2-1781 -- 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-1781) WSDL2Java: Tries to create databindings twice when a XSD with type definitions is imported into both another XSD and a WSDL
[ https://issues.apache.org/jira/browse/AXIS2-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1781. - Resolution: Fixed Fixed in trunk. thanks, dims WSDL2Java: Tries to create databindings twice when a XSD with type definitions is imported into both another XSD and a WSDL --- Key: AXIS2-1781 URL: https://issues.apache.org/jira/browse/AXIS2-1781 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1 Environment: Any Reporter: Michael Bevilacqua-Linn Assignee: Amila Chinthaka Suriarachchi Attachments: results.txt, WSDL.zip We've got our type definitions broken out into multiple files. -- 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]
[Axis2] Request for merge from trunk to branch.
Deepal, I checked in fixes to trunk for the following JIRA's https://issues.apache.org/jira/browse/AXIS2-3041 https://issues.apache.org/jira/browse/AXIS2-3036 I'd please kindly request you to consider at least 3036 for 1.3 branch. As it is low impact as it does not affect *any* other databindings other than xmlbeans and has been a long standing issue (earlier reports are AXIS2-1885, AXIS2-1781). thanks, dims On 8/1/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Devs, I think now are in a good position to go ahead with the release so no need to fix any of the existing JIRAs , I am thinking of cutting the release immediately after Woden release their release. So lets us stop commiting to the branch and let's only commit the code which are related to - Release related - Documents changes Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3041) WSDL2java does not provoide circular wsdl import support
[ https://issues.apache.org/jira/browse/AXIS2-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516971 ] Davanum Srinivas commented on AXIS2-3041: - I've checked in a fix to trunk - 561798. There is still a problem with computing effective policy. Here's the output. ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_Ping_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_Ping_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echo_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echo_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoXml_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoXml_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoDataSet_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoDataSet_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_header_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_header_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_fault_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_fault_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_Ping_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_Ping_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echo_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echo_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoXml_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoXml_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoDataSet_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoDataSet_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_header_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_header_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_fault_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_fault_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_Ping_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_Ping_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echo_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echo_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoXml_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoXml_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoDataSet_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_echoDataSet_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_header_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_header_output_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_fault_Input_policy ERROR: Ignoring policy - Malformed uri: X10-NoTimestamp_IPingService_fault_output_policy This is printed from Line 285 in AxisServiceBasedMultiLanguageEmitter.java thanks, dims WSDL2java does not provoide circular wsdl import support Key: AXIS2-3041 URL: https://issues.apache.org/jira/browse/AXIS2-3041 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Amila Chinthaka Suriarachchi Assignee: Amila Chinthaka Suriarachchi Attachments: patch-AXIS2-3041.diff use the wsdl2java tool with the following wsdl, to generate client. http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl it fails since wsdl2java does not support circular imports. -- 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-1781) WSDL2Java: Tries to create databindings twice when a XSD with type definitions is imported into both another XSD and a WSDL
[ https://issues.apache.org/jira/browse/AXIS2-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516975 ] Stefan Lischke commented on AXIS2-1781: --- This bug can be closed, i tested it with the fix i did for AXIS2-3036 and it worked well WSDL2Java: Tries to create databindings twice when a XSD with type definitions is imported into both another XSD and a WSDL --- Key: AXIS2-1781 URL: https://issues.apache.org/jira/browse/AXIS2-1781 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1 Environment: Any Reporter: Michael Bevilacqua-Linn Assignee: Amila Chinthaka Suriarachchi Attachments: results.txt, WSDL.zip We've got our type definitions broken out into multiple files. -- 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]
Re: [axis2] Importing source in Eclipse
please run mvn eclipse:eclipse -- dims On 8/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I am new to maven and interested in axis2 development. Could anybody suggest me how to import axis2 project in eclipse. So i can start my contribution to axis2 team. thanks, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty. IT Services Business Solutions Outsourcing =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] Importing source in Eclipse
Hi All, I am new to maven and interested in axis2 development. Could anybody suggest me how to import axis2 project in eclipse. So i can start my contribution to axis2 team. thanks, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty. IT Services Business Solutions Outsourcing =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
[jira] Resolved: (AXIS2-3036) Duplicate global type when importing the same xsd from two other xsd's
[ https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3036. - Resolution: Fixed Fix Version/s: (was: 1.3) nightly Applied in svn trunk 561802. Will petition the Release Manager to merge this change to 1.3 branch. thanks, dims Duplicate global type when importing the same xsd from two other xsd's Key: AXIS2-3036 URL: https://issues.apache.org/jira/browse/AXIS2-3036 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Stefan Lischke Assignee: Amila Chinthaka Suriarachchi Fix For: nightly Attachments: AXIS2-JIRA-3036.patch, AXIS2-JIRA-3036.wsdl, AXIS2-JIRA-3036.zip, wsdl.zip When running wsdl2java on the attached wsdl xsd files i got: [java] Caused by: org.apache.xmlbeans.XmlException: project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2: Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig# (Original global type found in file: xmldsig-core-schema.xsd) xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd seems to be very similar to AXIS2-1885 and AXIS2-1781 -- 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-3036) Duplicate global type when importing the same xsd from two other xsd's
[ https://issues.apache.org/jira/browse/AXIS2-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Lischke updated AXIS2-3036: -- Attachment: AXIS2-JIRA-3036.patch I attached a patch for this Bug, please review it and apply it if its ok for you... thanks a lot Duplicate global type when importing the same xsd from two other xsd's Key: AXIS2-3036 URL: https://issues.apache.org/jira/browse/AXIS2-3036 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Stefan Lischke Assignee: Amila Chinthaka Suriarachchi Fix For: 1.3 Attachments: AXIS2-JIRA-3036.patch, AXIS2-JIRA-3036.wsdl, AXIS2-JIRA-3036.zip, wsdl.zip When running wsdl2java on the attached wsdl xsd files i got: [java] Caused by: org.apache.xmlbeans.XmlException: project://local/xmldsig-core-schema.xsd:6:1: error: sch-props-correct.2: Duplicate global type: [EMAIL PROTECTED]://www.w3.org/2000/09/xmldsig# (Original global type found in file: xmldsig-core-schema.xsd) xmldsig-core-schema.xsd is imported from xkms.xsd and from xenc-schema.xsd seems to be very similar to AXIS2-1885 and AXIS2-1781 -- 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-2075) WSDL2Java generated stub with XMLBeans loads wrong *ResponseDocumentImpl for the expected interface *ResponseDocument
[
https://issues.apache.org/jira/browse/AXIS2-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516986
]
Stefan Lischke commented on AXIS2-2075:
---
that sounds like an issue i found while working on bug AXIS2-3036. If there are
two xsd's or wsdl's with the same namespace like your XMPieWSAPI the
Axis2EntityResolver.resolveEntity returns the first file if you want to have
the second one. If an entity was not found by sourceURI, there is a lookup for
namespace.
So i think Axis2 is not able to handle multiple xsd's or wsdl's with the same
namespace at all.
WSDL2Java generated stub with XMLBeans loads wrong *ResponseDocumentImpl for
the expected interface *ResponseDocument
-
Key: AXIS2-2075
URL: https://issues.apache.org/jira/browse/AXIS2-2075
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: databinding
Affects Versions: 1.1.1
Environment: Windows XP Pro SP2, SUN SDK 1.5.0_10, ANT 1.7.0, AXIS
1.1.1, Intel Xeon HT 3.6 GHz, 2GB RAM
Reporter: Cristian Malinescu
Assignee: Amila Chinthaka Suriarachchi
Attachments: account_SSP.wsdl, document_SSP.wsdl, SuiteRunner.java,
XMPie-document-ws-client-src.jar
See the title and the stack trace:
2007-02-01 11:50:16,426 DEBUG
[org.apache.axiom.om.impl.builder.StAXOMBuilder] - START_ELEMENT:
{XMPieWSAPI}GetPropertyResult:GetPropertyResult
2007-02-01 11:50:16,426 DEBUG
[org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder] - Build the
OMElelment GetPropertyResultBy the StaxSOAPModelBuilder
2007-02-01 11:50:16,457 ERROR
[com.capitalC.Kenna.xTalker.services.XMPie.axis.DocumentFactory] -
java.lang.ClassCastException:
com.capitalc.kenna.xtalker.xmpie.account.model.impl.GetPropertyResponseDocumentImpl
incompatible with
com.capitalc.kenna.xtalker.xmpie.document.model.GetPropertyResponseDocument
at
com.capitalc.kenna.xtalker.xmpie.document.model.GetPropertyResponseDocument$Factory.parse(GetPropertyResponseDocument.java:128)
at
com.capitalc.kenna.xtalker.xmpie.document.stubs.Document_SSPStub.fromOM(Document_SSPStub.java:5472)
at
com.capitalc.kenna.xtalker.xmpie.document.stubs.Document_SSPStub.GetProperty(Document_SSPStub.java:4013)
at
com.capitalC.Kenna.xTalker.services.XMPie.axis.DocumentFactory.getProperty(DocumentFactory.java:199)
at
com.capitalC.Kenna.xTalker.services.XMPie.axis.DocumentFactory.getPlanID(DocumentFactory.java:219)
at
com.capitalC.Kenna.xTalker.services.XMPie.SuiteRunner.document(SuiteRunner.java:55)
at
com.capitalC.Kenna.xTalker.services.XMPie.SuiteRunner.main(SuiteRunner.java:102)
2007-02-01 11:50:16,457 ERROR
[com.capitalC.Kenna.xTalker.services.XMPie.SuiteRunner] -
java.lang.NullPointerException
at
com.capitalC.Kenna.xTalker.services.XMPie.axis.DocumentFactory.getProperty(DocumentFactory.java:206)
at
com.capitalC.Kenna.xTalker.services.XMPie.axis.DocumentFactory.getPlanID(DocumentFactory.java:219)
at
com.capitalC.Kenna.xTalker.services.XMPie.SuiteRunner.document(SuiteRunner.java:55)
at
com.capitalC.Kenna.xTalker.services.XMPie.SuiteRunner.main(SuiteRunner.java:102)
--
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-3041) WSDL2java does not provoide circular wsdl import support
[ https://issues.apache.org/jira/browse/AXIS2-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3041. - Resolution: Fixed Fix Version/s: nightly Fixed in trunk only. i had inadvertently commented out the code the processes the policies. (561847) thanks, dims WSDL2java does not provoide circular wsdl import support Key: AXIS2-3041 URL: https://issues.apache.org/jira/browse/AXIS2-3041 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Amila Chinthaka Suriarachchi Assignee: Amila Chinthaka Suriarachchi Fix For: nightly Attachments: patch-AXIS2-3041.diff use the wsdl2java tool with the following wsdl, to generate client. http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl it fails since wsdl2java does not support circular imports. -- 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]
Re: [axis2] Importing source in Eclipse
There are currently a few issues with mvn eclipse:eclipse. It works for the most part, but there are some things that have to be fixed up manually. One of these is that any module that is packaged as a mar doesn't have the .classpath file generated. If you remove the line packagemar/package from the modules pom and rerun the command then it works. This affects the eclipse projects: addressing, axis2-scripting, mex, ping and soapmonitor. To build the axis2-kernel eclipse project will require you to modify the java build path property to add the test-resources/deployment directory to the excluded list for the test-resources directory. To build the axis2-codegen eclipse project will require you to delete all of the src directories that are not a part of the axis2-codegen project from the java build path property. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Davanum Srinivas [EMAIL PROTECTED] wrote on 01/08/2007 15:07:03: please run mvn eclipse:eclipse -- dims On 8/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi All, I am new to maven and interested in axis2 development. Could anybody suggest me how to import axis2 project in eclipse. So i can start my contribution to axis2 team. thanks, Deepak Jerambhai Pansheriya Tata Consultancy Services Yantra Park -(STPI) Mailto: [EMAIL PROTECTED] Website: http://www.tcs.com Experience certainty. IT Services Business Solutions Outsourcing =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
[jira] Created: (AXIS2-3048) wsdl2java exception with xmlbeans bindings - Imported schema has a target namespace that does not match the specified
wsdl2java exception with xmlbeans bindings - Imported schema has a target namespace that does not match the specified - Key: AXIS2-3048 URL: https://issues.apache.org/jira/browse/AXIS2-3048 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.2 Reporter: Michael Mattox Priority: Critical When using the ANT task Eclipse plugin for wsdl2java, I get this exception: Caused by: org.apache.xmlbeans.XmlException: D:\projects\MediaMetrie\projects\pam\workspace\MEDIAMAT2-ADM-SERVICE-WEBSERVICE\AdminProduction.xsd:2:1: error: Imported schema has a target namespace http://www.mediametrie.fr/mediamat2/operation/production/definitions/v1; that does not match the specified http://www.mediametrie.fr/mediamat2/gisement/production/v1; 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:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:174) ... 23 more I have verified my xsd with XML spy Eclipse WTP and they are valid: The xsd that includes the other one: schema xmlns=http://www.w3.org/2001/XMLSchema; xmlns:tns=http://www.mediametrie.fr/mediamat2/operation/production/definitions/v1; xmlns:pref=http://www.mediametrie.fr/mediamat2/gisement/production/v1; xmlns:adm=http://www.mediametrie.fr/mediamat2/gisement/commons/v1; targetNamespace=http://www.mediametrie.fr/mediamat2/operation/production/definitions/v1; elementFormDefault=qualified import namespace=http://www.mediametrie.fr/mediamat2/gisement/production/v1; schemaLocation=Production.xsd/ The xsd being included: schema xmlns=http://www.w3.org/2001/XMLSchema; xmlns:tns=http://www.mediametrie.fr/mediamat2/gisement/production/v1; xmlns:Q1=http://www.mediametrie.fr/mediamat2/gisement/commons/v1; targetNamespace=http://www.mediametrie.fr/mediamat2/gisement/production/v1; elementFormDefault=qualified If I change the namespace in the including xsd to anything else, my xsd doesn't validate. Now here is where it gets interesting, I can generate the xmlbeans classes using the xmlbeans ANT task without any errors. So I think this has something to do with axis2. When I search for the message on google, I find the source code for xmlbeans: http://jsourcery.com/output/apache/xml/xmlbeans/1.0.3/org/apache/xmlbeans/impl/schema/StscImporter.source.html look in the method public SchemaToProcess[] resolveImportsAndIncludes() I put this as critical because we can't generate any server files. If there is a way to not generate the xmlbeans classes, this would be a suitable workaround for me and we can lower the priority. I have a jar of my xmlbeans classes but I don't know how to tell wsdl2java to not generate them. -- 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-3049) The generated schema by axis2 seems invalid when OMElements are specified as input parameters in service implementation class
[
https://issues.apache.org/jira/browse/AXIS2-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated AXIS2-3049:
---
Attachment: Myaxistest.aar
Attached service archive.
The generated schema by axis2 seems invalid when OMElements are specified as
input parameters in service implementation class
--
Key: AXIS2-3049
URL: https://issues.apache.org/jira/browse/AXIS2-3049
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: om
Affects Versions: 1.3
Environment: winxp, jdk15, Axis2-SNAPSHOT (1.3)
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Critical
Attachments: Myaxistest.aar
Please correct me if i'm wrong. I feel there is an error when generating
schema if OMElements are included in service implementation class.
I have a service implementation class with following signature.
public OMElement echotest(OMElement x, OMElement y){
}
I deployed a service archive with above method and retrieved the schema by
issuing ?xsd. I got following.
xs:schema
xs:element name=echotest
xs:complexType
xs:sequence
xs:element minOccurs=0 name=echotest nillable=true type=xs:anyType/
/xs:sequence
/xs:complexType
/xs:element
xs:element name=echotestResponse
xs:complexType
xs:sequence
xs:element minOccurs=0 name=return nillable=true type=xs:anyType/
/xs:sequence
/xs:complexType
/xs:element
/xs:schema
As you can see, only one element is added as input parameter though the
method contains two params. If you deploy the same service by replacing
OMElement with other primitive type (int, String etc) you will get schema
with correct no. of input parameters.
xs:sequence
xs:element name=a nillable=true type=xs:anyType/
xs:element name=b nillable=true type=xs:anyType/
/xs:sequence
--
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-3049) The generated schema by axis2 seems invalid when OMElements are specified as input parameters in service implementation class
The generated schema by axis2 seems invalid when OMElements are specified as
input parameters in service implementation class
--
Key: AXIS2-3049
URL: https://issues.apache.org/jira/browse/AXIS2-3049
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: om
Affects Versions: 1.3
Environment: winxp, jdk15, Axis2-SNAPSHOT (1.3)
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Critical
Please correct me if i'm wrong. I feel there is an error when generating schema
if OMElements are included in service implementation class.
I have a service implementation class with following signature.
public OMElement echotest(OMElement x, OMElement y){
}
I deployed a service archive with above method and retrieved the schema by
issuing ?xsd. I got following.
xs:schema
xs:element name=echotest
xs:complexType
xs:sequence
xs:element minOccurs=0 name=echotest nillable=true type=xs:anyType/
/xs:sequence
/xs:complexType
/xs:element
xs:element name=echotestResponse
xs:complexType
xs:sequence
xs:element minOccurs=0 name=return nillable=true type=xs:anyType/
/xs:sequence
/xs:complexType
/xs:element
/xs:schema
As you can see, only one element is added as input parameter though the method
contains two params. If you deploy the same service by replacing OMElement with
other primitive type (int, String etc) you will get schema with correct no. of
input parameters.
xs:sequence
xs:element name=a nillable=true type=xs:anyType/
xs:element name=b nillable=true type=xs:anyType/
/xs:sequence
--
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-3051) UTF-16 Interop problem
[
https://issues.apache.org/jira/browse/AXIS2-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3051.
-
Resolution: Fixed
Fixed *ONLY* in trunk 561888
thanks,
dims
UTF-16 Interop problem
--
Key: AXIS2-3051
URL: https://issues.apache.org/jira/browse/AXIS2-3051
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Reporter: Davanum Srinivas
Priority: Blocker
When i run wsdl2java against
http://131.107.72.15/MTOM_Service_Indigo/Soap11MtomUtf16.svc?wsdl
and use the following snippet:
public class Main {
public static void main(String[] args) throws Exception {
MtomServiceStub stub = new MtomServiceStub();
EchoStringAsBinary input = new EchoStringAsBinary();
input.setS(My String);
EchoStringAsBinaryResponse response = stub.EchoStringAsBinary(input);
DataHandler handler = response.getEchoStringAsBinaryResult();
EchoBinaryAsString input2 = new EchoBinaryAsString();
input2.setArray(handler);
EchoBinaryAsStringResponse response2 =
stub.EchoBinaryAsString(input2);
System.out.println(RESULT + [ +
response2.getEchoBinaryAsStringResult() + ]);
}
}
I get the following exception:
Exception in thread main org.apache.axis2.AxisFault: Character Set Encoding
from transport information does not match with character set encoding in the
received SOAP message
at
org.apache.axis2.builder.BuilderUtil.validateCharSetEncoding(BuilderUtil.java:684)
at
org.apache.axis2.builder.MTOMBuilder.processDocument(MTOMBuilder.java:60)
at
org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:62)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:160)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.tempuri.MtomServiceStub.EchoStringAsBinary(MtomServiceStub.java:474)
--
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]
Re: [Axis2] Request for merge from trunk to branch.
Deepal, Found one more *serious* bug and fixed it in trunk - AXIS2-3051. thanks, dims On 8/1/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Deepal, I checked in fixes to trunk for the following JIRA's https://issues.apache.org/jira/browse/AXIS2-3041 https://issues.apache.org/jira/browse/AXIS2-3036 I'd please kindly request you to consider at least 3036 for 1.3 branch. As it is low impact as it does not affect *any* other databindings other than xmlbeans and has been a long standing issue (earlier reports are AXIS2-1885, AXIS2-1781). thanks, dims On 8/1/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Devs, I think now are in a good position to go ahead with the release so no need to fix any of the existing JIRAs , I am thinking of cutting the release immediately after Woden release their release. So lets us stop commiting to the branch and let's only commit the code which are related to - Release related - Documents changes Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3051) UTF-16 Interop problem
UTF-16 Interop problem
--
Key: AXIS2-3051
URL: https://issues.apache.org/jira/browse/AXIS2-3051
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Reporter: Davanum Srinivas
Priority: Blocker
When i run wsdl2java against
http://131.107.72.15/MTOM_Service_Indigo/Soap11MtomUtf16.svc?wsdl
and use the following snippet:
public class Main {
public static void main(String[] args) throws Exception {
MtomServiceStub stub = new MtomServiceStub();
EchoStringAsBinary input = new EchoStringAsBinary();
input.setS(My String);
EchoStringAsBinaryResponse response = stub.EchoStringAsBinary(input);
DataHandler handler = response.getEchoStringAsBinaryResult();
EchoBinaryAsString input2 = new EchoBinaryAsString();
input2.setArray(handler);
EchoBinaryAsStringResponse response2 = stub.EchoBinaryAsString(input2);
System.out.println(RESULT + [ +
response2.getEchoBinaryAsStringResult() + ]);
}
}
I get the following exception:
Exception in thread main org.apache.axis2.AxisFault: Character Set Encoding
from transport information does not match with character set encoding in the
received SOAP message
at
org.apache.axis2.builder.BuilderUtil.validateCharSetEncoding(BuilderUtil.java:684)
at
org.apache.axis2.builder.MTOMBuilder.processDocument(MTOMBuilder.java:60)
at
org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:62)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:160)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.tempuri.MtomServiceStub.EchoStringAsBinary(MtomServiceStub.java:474)
--
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-3050) Reading indented XML using SAAJ (which uses AXIOM) treats line breaks and spaces as text nodes
Reading indented XML using SAAJ (which uses AXIOM) treats line breaks and spaces as text nodes -- Key: AXIS2-3050 URL: https://issues.apache.org/jira/browse/AXIS2-3050 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: om Affects Versions: 1.3 Environment: All Reporter: Jeff Faath Priority: Minor I am trying to read this XML snippet: ?xml version=1.0 encoding=utf-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body get_registryInfo generic=1.0 xmlns=urn:juddi-org:api_v2/ /soapenv:Body /soapenv:Envelope Using this code to read in and process: String s = the xml snippet MessageFactory msgFactory = MessageFactory.newInstance(); SOAPMessage soapReq = msgFactory.createMessage(null,new ByteArrayInputStream(s.getBytes())); SOAPBody soapReqBody = soapReq.getSOAPBody(); Then, on this line: Node n = soapReqBody.getFirstChild(); The node returned on this call is a Text node with a value of \n (line break with spaces). In other words, the code handles the indenting up until the SOAPBody element is isolated. Then calling the getFirstChild() method returns the indenting as a Text node. Stepping into the code reveals that the getFirstChild() method comes from SAAJ's SOAPElementImpl. This in turn calls getFirstChild() from it's element member variable which is of type SOAP11BodyImpl from AXIOM. It is this call that is returning the indentation. Not sure if this is a bug or if AXIOM doesn't allow indented 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]
[Axis2] Another RC while we wait for Woden.
Deepal, Folks, Suggestion #1: I think we have accumulated a lot of code changes since last RC and since we have time, let's please cut another RC. Suggestion #2: There are some significant changes in trunk that needs to be merged into branch. I was working on them and did not realize that the RM would freeze the branch last night. Could we please merge them? Suggestion #3: In future, Can we please amend the policy to give some notice before a code freeze? say 24hrs? thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
questions
Hi, all, I am new to axis2, and I have two questions about axis2: 1. I downloaded the source code from the svn repository and did a build successfully; it created an axis2-SNAPSHOT.jar file, then what to do with the jar file? I downloaded the axis2-1.3-SNAPSHOT-bin.zip file as well, from this file I ran ant script and created a war file which can be deployed, but the axis2-SNAPSHOT.jar file is not used in the creating war file process, because I searched all the jar files in the axis2-1.3-SNAPSHOT-bin.zip file, the axis2-SNAPSHOT.jar file is not in there. 2. I deployed the axis2.war file successfully to tomcat 4.1.36, I can see the version service from the admin happiness page, but when I deployed the same war file to Netscape Enterprise Server (NES) 6.2 (our development and production environment), I can access the admin welcome page, but not the happiness page to see the version service, because it threw an ServletException: The Dispatch phase is not found on the global InFlow phase of the axis2.xml file. (see the attached exception and axis2.xml file) the difference between tomcat 4.1.36 and NES6.2 is that, tomcat 4 supports servlet 2.3 and jsp 1.2, NE6.2 supports servlet 2.2 and jsp 1.1 (maybe 1.2, but not sure), does this difference cause the exception or it is a bug in the axis2? Thanks in advance. David [30/Jul/2007:05:02:43] info ( 6336): vs(https-dduRHL.pkipro)servlet 'AxisServlet' class = 'org.apache.axis2.transport.http.AxisServlet' loaded in context = '/axis2' [30/Jul/2007:05:02:43] info ( 6336): AxisServlet: init [30/Jul/2007:05:02:44] warning ( 6336): vs(https-dduRHL.pkipro)ServletException thrown in servlet.init; context = /axis2, servlet = 'AxisServlet'; stack tace: javax.servlet.ServletException: The Dispatch phase is not found on the global InFlow phase of the axis2.xml file. Make sure the phase is within the axis2.xml file. at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:433) at com.netscape.server.http.servlet.WServletEntity.loadAndInitServlet (WServ letEntity.java:98) at com.netscape.server.http.servlet.WebApplication.service(WebApplication.j ava:1199) at com.netscape.server.http.servlet.NSServletRunner.ServiceWebApp(NSServlet Runner.java:956) , root cause: javax.servlet.ServletException: The Dispatch phase is not found on the global InFlow phase of the axis2.xml file. Make sure the phase is within the axis2.xml file. at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle t.java:501) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:415) at com.netscape.server.http.servlet.WServletEntity.loadAndInitServlet (WServ letEntity.java:98) at com.netscape.server.http.servlet.WebApplication.service(WebApplication.j ava:1199) at com.netscape.server.http.servlet.NSServletRunner.ServiceWebApp(NSServlet Runner.java:956) [30/Jul/2007:05:02:44] warning ( 6336): Internal Error: Cannot load servlet 'AxisServlet'; context = 'https-dduRHL.pkipro' vsid = '/axis2'
Required jars for AXIS2 Client
Hi, I am trying to develop a AXIS2 Client. I would like to know what are the minimum required jars for the client ? I could n't find any where in docs. Can some one help me in this regard Thanks Ravinder
RE: [Axis2] Engaging modules from classpath
Gents, What you're discussing seems very closely related to a jira I filed a litte while ago: https://issues.apache.org/jira/browse/AXIS2-3026 https://issues.apache.org/jira/browse/AXIS2-3026 Is this essentially what you're asking for? Cheers, Mark B From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wed 8/1/2007 10:44 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Engaging modules from classpath +1 to modules.xml with multipe module elements On 8/1/07, Dustin Amrhein [EMAIL PROTECTED] wrote: Would it be feasible (and possible) to describe multiple modules within a single XML file? Instead of having multiple XML files in a JAR could we allow the use of a modules.xml with multipe module elements? If this is possible it may make things easier on the end user by reducing the number of deployment descriptors that need to be produced/maintained. Saminda Abeyruwan [EMAIL PROTECTED] wrote: On 8/1/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Hi Devs, This may be beyond Axis2 1.3. At the moment, for a given .jar, we could only have one module.xml to represent a module. Axis2 already ship addressing mar module.xml in the axis2-XX.jar. What if we need to have multiple module.xmls in a given jar. Looking at the work I've been engaged with there is a possibility of having this scenario. Thus, if a multiple module.xmls needed for a given .jar, wouldn't it be reasonable to give it as follows, foo +-META-INF +- module-a.xml +- module-b.xml ... Thus, at deployment time, xmls can be read with the prefix module and make them available for engagement. If there needed to be only single module descriptor, let it be either module.xml or module-foo.xml. Thank you Saminda -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3052) webapp reload on Tomcat 5.5 fails when persisting sessions
webapp reload on Tomcat 5.5 fails when persisting sessions -- Key: AXIS2-3052 URL: https://issues.apache.org/jira/browse/AXIS2-3052 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3 Environment: Tomcat 5.5.20 Axis 1.3-RC2 Reporter: simishag Priority: Minor Reloading the webapp from the Tomcat Manager causes the following exception: org.apache.catalina.session.ManagerBase - IOException while saving persisted sessions: java.io.FileNotFoundException: /var/lib/tomcat-5.5/work/Catalina/localhost/axis2/SESSIONS.ser (No such file or directory) I verified that the directory exists and is writable by the Tomcat user. I tried creating the SESSIONS.ser file in advance, setting permissions then reloading. Same exception happens, and the file actually gets removed. I have only seen this problem since I started using 1.3-RC2. -- 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-3040) Can Axis2 support Spring-JPA configuration
[ https://issues.apache.org/jira/browse/AXIS2-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517124 ] tommy commented on AXIS2-3040: -- I ran my spring-JPA project only in single java project mode, no any application server involved. It tested my project well. After I added some codes that are from sample pojoguidespring to my spring-JPA, it didn't work at all. The tomcat server gives me the excepiton just as above. I tried the sample pojoguidespring, it works. Why the server refused my deployment when I used the same springInit as pojoguidespring? Can Axis2 support Spring-JPA configuration -- Key: AXIS2-3040 URL: https://issues.apache.org/jira/browse/AXIS2-3040 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: winxp , axis2 Reporter: tommy Assignee: robert lazarski I worked fine with my spring-JPA project alone, but when I add some axis2 features into this project, and upload .aar file to the server, it shows me the exception as follows: org.apache.axis2.deployment.DeploymentException: Processing Operations Modules w ith an error of sample.spring.service.SpringInit at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) Any help appreciated -- 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]
Re: [Axis2] Another RC while we wait for Woden.
Deepal,
Here's the diff i'd like to merge from trunk to 1.3 branch:
- Fix for UTF-16LE/BE in transport header content type instead of just
UTF-16 (Interop problem with WCF/Indigo)
- Fix for circular wsdl's. (Found during WCF/Interop testing)
- Fix for Duplicate Global type during xmlbeans codegen
- Fix for NPE in AxisServlet (found during trying to send soap message
from jython)
thanks,
dims
On 8/1/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
Deepal, Folks,
Suggestion #1: I think we have accumulated a lot of code changes since
last RC and since we have time, let's please cut another RC.
Suggestion #2: There are some significant changes in trunk that needs
to be merged into branch. I was working on them and did not realize
that the RM would freeze the branch last night. Could we please merge
them?
Suggestion #3: In future, Can we please amend the policy to give some
notice before a code freeze? say 24hrs?
thanks,
dims
--
Davanum Srinivas :: http://davanum.wordpress.com
--
Davanum Srinivas :: http://davanum.wordpress.com
--- modules/kernel/src/org/apache/axis2/builder/BuilderUtil.java Wed Aug 01 13:48:41 2007
+++ modules/kernel/src/org/apache/axis2/builder/BuilderUtil.java Fri Jul 20 12:40:58 2007
@@ -670,8 +670,7 @@
if ((charsetEncodingFromXML != null)
!.equals(charsetEncodingFromXML)
(charsetEncodingFromTransport != null)
- !charsetEncodingFromXML.equalsIgnoreCase(charsetEncodingFromTransport)
- !isValidPair(charsetEncodingFromXML, charsetEncodingFromTransport))
+ !charsetEncodingFromXML.equalsIgnoreCase((String) charsetEncodingFromTransport))
{
String faultCode;
@@ -682,27 +681,8 @@
}
throw new AxisFault(Character Set Encoding from
-+ transport information [ + charsetEncodingFromTransport + ] does not match with
-+ character set encoding in the received SOAP message [ + charsetEncodingFromXML + ], faultCode);
++ transport information do not match with
++ character set encoding in the received SOAP message, faultCode);
}
-}
-
-/**
- * check if the pair is [UTF-16,UTF-16LE] [UTF-32, UTF-32LE],[UTF-16,UTF-16BE] [UTF-32, UTF-32BE] etc.
- *
- * @param enc1
- * @param enc2
- * @return
- */
-private static boolean isValidPair(String enc1, String enc2) {
-enc1 = enc1.toLowerCase();
-enc2 = enc2.toLowerCase();
-if (enc1.endsWith(be) || enc1.endsWith(le)) {
-enc1 = enc1.substring(0, enc1.length() - 2);
-}
-if (enc2.endsWith(be) || enc2.endsWith(le)) {
-enc2 = enc2.substring(0, enc2.length() - 2);
-}
-return enc1.equals(enc2);
}
}
--- modules/kernel/src/org/apache/axis2/description/WSDL11ToAxisServiceBuilder.java Wed Aug 01 11:50:57 2007
+++ modules/kernel/src/org/apache/axis2/description/WSDL11ToAxisServiceBuilder.java Wed Aug 01 08:38:58 2007
@@ -294,12 +294,6 @@
private void processTypes(Definition wsdlDefinition, AxisService axisService)
throws AxisFault {
-processTypes(wsdlDefinition, axisService, new Stack());
-}
-
-private void processTypes(Definition wsdlDefinition, AxisService axisService, Stack stack)
-throws AxisFault {
-stack.push(wsdlDefinition);
// process all the types in all the wsdls
Types types = wsdlDefinition.getTypes();
if (types != null) {
@@ -318,14 +312,10 @@
for (Iterator valuesIter = values.iterator(); valuesIter.hasNext();) {
wsdlImport = (Import) valuesIter.next();
// process the types recuresiveilt
-Definition innerDefinition = wsdlImport.getDefinition();
-if(!stack.contains(innerDefinition)){
-processTypes(innerDefinition, axisService, stack);
+processTypes(wsdlImport.getDefinition(), axisService);
}
}
}
-stack.pop();
-}
private void addDocumentation(AxisDescription axisDescription, Element documentationElement) {
if ((documentationElement != null) (documentationElement.getFirstChild() != null)) {
@@ -644,7 +634,7 @@
// setup the schemaMap
this.schemaMap = new HashMap();
-populateSchemaMap(wsdl4jDefinition, new Stack());
+populateSchemaMap(wsdl4jDefinition);
setPolicyRegistryFromService(axisService);
@@ -660,8 +650,8 @@
* @param definition
*/
-private void populateSchemaMap(Definition definition, Stack stack) {
-stack.push(definition);
+private void populateSchemaMap(Definition definition) {
+
Types types = definition.getTypes();
Object extensibilityElement;
if (types != null) {
@@ -683,14 +673,10 @@
values = (Vector)
[jira] Updated: (AXIS2-3053) when i have a method that takes GenericArrayType as a parameter, my web service project cannot be deployed in geronimo
[ https://issues.apache.org/jira/browse/AXIS2-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated AXIS2-3053: --- Attachment: axis2-3053.patch Tested in geronimo env. when i have a method that takes GenericArrayType as a parameter, my web service project cannot be deployed in geronimo -- Key: AXIS2-3053 URL: https://issues.apache.org/jira/browse/AXIS2-3053 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Lin Sun Fix For: 1.3 Attachments: axis2-3053.patch For example, I have the following parameter in one of the methods in my SEI - @WebParam(name = claimFormImage, targetNamespace = http://test.apache.org;) byte[] claimFormImage, The deployment will fail because of a NPE (from line 1092 of ServiceDescriptionImpl.java) as we built an empty ParameterDescriptionComposite for it. The attached patch will check if the paramType is GenericArrayType, if so, set the ParameterDescriptionComposite properly. -- 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-3040) Can Axis2 support Spring-JPA configuration
[ https://issues.apache.org/jira/browse/AXIS2-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517124 ] tommy edited comment on AXIS2-3040 at 8/1/07 7:41 PM: -- I ran my spring-JPA project only in single java project mode, no any application server involved. It tested my project well. After I added some codes that are from sample pojoguidespring to my spring-JPA, it didn't work at all. The tomcat server gives me the excepiton just as above. I tried the sample pojoguidespring, it works. Why the server refused my deployment when I used the same springInit as pojoguidespring? --- It seems that I found the problem, the axis2 dosen't support Spring2 .xsd declaration, am I right? How can I changed this to make my project work within the environment of Axis2 was: I ran my spring-JPA project only in single java project mode, no any application server involved. It tested my project well. After I added some codes that are from sample pojoguidespring to my spring-JPA, it didn't work at all. The tomcat server gives me the excepiton just as above. I tried the sample pojoguidespring, it works. Why the server refused my deployment when I used the same springInit as pojoguidespring? Can Axis2 support Spring-JPA configuration -- Key: AXIS2-3040 URL: https://issues.apache.org/jira/browse/AXIS2-3040 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: winxp , axis2 Reporter: tommy Assignee: robert lazarski I worked fine with my spring-JPA project alone, but when I add some axis2 features into this project, and upload .aar file to the server, it shows me the exception as follows: org.apache.axis2.deployment.DeploymentException: Processing Operations Modules w ith an error of sample.spring.service.SpringInit at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) Any help appreciated -- 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-3053) when i have a method that takes GenericArrayType as a parameter, my web service project cannot be deployed in geronimo
when i have a method that takes GenericArrayType as a parameter, my web service project cannot be deployed in geronimo -- Key: AXIS2-3053 URL: https://issues.apache.org/jira/browse/AXIS2-3053 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Lin Sun Fix For: 1.3 For example, I have the following parameter in one of the methods in my SEI - @WebParam(name = claimFormImage, targetNamespace = http://test.apache.org;) byte[] claimFormImage, The deployment will fail because of a NPE (from line 1092 of ServiceDescriptionImpl.java) as we built an empty ParameterDescriptionComposite for it. The attached patch will check if the paramType is GenericArrayType, if so, set the ParameterDescriptionComposite properly. -- 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-3046) Axis2 session does not timeout as expected
[ https://issues.apache.org/jira/browse/AXIS2-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517131 ] dinh anh khoa commented on AXIS2-3046: -- Yes, my service was deployed in soapsession scope Axis2 session does not timeout as expected -- Key: AXIS2-3046 URL: https://issues.apache.org/jira/browse/AXIS2-3046 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Fedora Core3, J2SE 1.5.0_11-b03, Axis2-1.2 (Integrated on a tomcat webapplication) Reporter: dinh anh khoa Assignee: Deepal Jayasinghe Priority: Critical * As the default in Axis2.xml, session will expire after 3ms (30s). * I've engaged addressing module for both server and client * I setup a service * the client call a method, its fine * client call Thread.sleep(6) * client call that method again, and its still work. It's should not working here and receive a fault message to say Invalid serviceGroupId I'm newly use Axis2, I'm not know weather this is a bug or not? could you please explain me this? 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]
Re: [Axis2] Another RC while we wait for Woden.
oops! forgot the change in WSDL11Writer.
thanks,
dims
On 8/1/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
Deepal,
Here's the diff i'd like to merge from trunk to 1.3 branch:
- Fix for UTF-16LE/BE in transport header content type instead of just
UTF-16 (Interop problem with WCF/Indigo)
- Fix for circular wsdl's. (Found during WCF/Interop testing)
- Fix for Duplicate Global type during xmlbeans codegen
- Fix for NPE in AxisServlet (found during trying to send soap message
from jython)
thanks,
dims
On 8/1/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
Deepal, Folks,
Suggestion #1: I think we have accumulated a lot of code changes since
last RC and since we have time, let's please cut another RC.
Suggestion #2: There are some significant changes in trunk that needs
to be merged into branch. I was working on them and did not realize
that the RM would freeze the branch last night. Could we please merge
them?
Suggestion #3: In future, Can we please amend the policy to give some
notice before a code freeze? say 24hrs?
thanks,
dims
--
Davanum Srinivas :: http://davanum.wordpress.com
--
Davanum Srinivas :: http://davanum.wordpress.com
--
Davanum Srinivas :: http://davanum.wordpress.com
--- modules/codegen/src/org/apache/axis2/wsdl/codegen/writer/WSDL11Writer.java Wed Aug 01 14:26:56 2007
+++ modules/codegen/src/org/apache/axis2/wsdl/codegen/writer/WSDL11Writer.java Fri Jul 20 12:47:54 2007
@@ -39,7 +39,6 @@
import java.util.Map;
import java.util.Vector;
import java.util.ArrayList;
-import java.util.Stack;
public class WSDL11Writer {
@@ -77,7 +76,7 @@
public void writeWSDL(AxisService axisService, Definition definition, Map changedMap) {
try {
if (axisService != null) {
-writeWSDL(definition, axisService.getName(), changedMap, new Stack());
+writeWSDL(definition, axisService.getName(), changedMap);
}
} catch (Exception e) {
throw new RuntimeException(WSDL writing failed!, e);
@@ -86,9 +85,7 @@
private void writeWSDL(Definition definition,
String serviceName,
- Map changedMap,
- Stack stack) throws Exception {
-stack.push(definition);
+ Map changedMap) throws Exception {
// first process the imports and save them.
Map imports = definition.getImports();
if (imports != null (imports.size() 0)) {
@@ -101,16 +98,13 @@
for (Iterator importsIter = importsVector.iterator(); importsIter.hasNext();) {
wsdlImport = (Import)importsIter.next();
wsdlName = wsdl_ + count++ + .wsdl;
-Definition innerDefinition = wsdlImport.getDefinition();
-if(!stack.contains(innerDefinition)) {
-writeWSDL(innerDefinition, wsdlName, changedMap, stack);
-}
+writeWSDL(wsdlImport.getDefinition(), wsdlName, changedMap);
wsdlImport.setLocationURI(wsdlName);
}
}
}
// change the locations on the imported schemas
-adjustWSDLSchemaLocations(definition, changedMap);
+adjustWSDLSchemaLocatins(definition, changedMap);
// finally save the file
WSDLWriter wsdlWriter = WSDLFactory.newInstance().newWSDLWriter();
File outputFile = FileWriter.createClassFile(baseFolder,
@@ -154,25 +148,14 @@
}
out.flush();
out.close();
-stack.pop();
-}
-
-/**
- * @deprecated please use adjustWSDLSchemaLocations
- * @param definition
- * @param changedSchemaLocations
- */
-public void adjustWSDLSchemaLocatins(Definition definition, Map changedSchemaLocations) {
-adjustWSDLSchemaLocations(definition, changedSchemaLocations);
}
/**
* adjust the schema locations in the original wsdl
*
- * @param definition
- * @param changedSchemaLocations
+ * @param changedScheamLocations
*/
-public void adjustWSDLSchemaLocations(Definition definition, Map changedSchemaLocations) {
+public void adjustWSDLSchemaLocatins(Definition definition, Map changedScheamLocations) {
Types wsdlTypes = definition.getTypes();
if (wsdlTypes != null) {
List extensibilityElements = wsdlTypes.getExtensibilityElements();
@@ -182,7 +165,7 @@
currentObject = iter.next();
if (currentObject instanceof Schema) {
schema = (Schema)currentObject;
-changeLocations(schema.getElement(), changedSchemaLocations);
+changeLocations(schema.getElement(), changedScheamLocations);
}
}
}
--- modules/kernel/src/org/apache/axis2/builder/BuilderUtil.java Wed Aug 01 13:48:41 2007
[jira] Updated: (AXIS2-3053) when i have a method that takes GenericArrayType as a parameter, my web service project cannot be deployed in geronimo
[ https://issues.apache.org/jira/browse/AXIS2-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated AXIS2-3053: --- Attachment: axis2-3053.patch This is a simpler patch and tested in geronimo env. when i have a method that takes GenericArrayType as a parameter, my web service project cannot be deployed in geronimo -- Key: AXIS2-3053 URL: https://issues.apache.org/jira/browse/AXIS2-3053 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Lin Sun Fix For: 1.3 Attachments: axis2-3053.patch, axis2-3053.patch For example, I have the following parameter in one of the methods in my SEI - @WebParam(name = claimFormImage, targetNamespace = http://test.apache.org;) byte[] claimFormImage, The deployment will fail because of a NPE (from line 1092 of ServiceDescriptionImpl.java) as we built an empty ParameterDescriptionComposite for it. The attached patch will check if the paramType is GenericArrayType, if so, set the ParameterDescriptionComposite properly. -- 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] Assigned: (AXIS2-3052) webapp reload on Tomcat 5.5 fails when persisting sessions
[ https://issues.apache.org/jira/browse/AXIS2-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3052: Assignee: Charitha Kankanamge Charitha, Will you be able to see whether what actually happening ? Thanks Deepal webapp reload on Tomcat 5.5 fails when persisting sessions -- Key: AXIS2-3052 URL: https://issues.apache.org/jira/browse/AXIS2-3052 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3 Environment: Tomcat 5.5.20 Axis 1.3-RC2 Reporter: simishag Assignee: Charitha Kankanamge Priority: Minor Reloading the webapp from the Tomcat Manager causes the following exception: org.apache.catalina.session.ManagerBase - IOException while saving persisted sessions: java.io.FileNotFoundException: /var/lib/tomcat-5.5/work/Catalina/localhost/axis2/SESSIONS.ser (No such file or directory) I verified that the directory exists and is writable by the Tomcat user. I tried creating the SESSIONS.ser file in advance, setting permissions then reloading. Same exception happens, and the file actually gets removed. I have only seen this problem since I started using 1.3-RC2. -- 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-3042) axis2 idea plugin pom.xml
[ https://issues.apache.org/jira/browse/AXIS2-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandakith resolved AXIS2-3042. - Resolution: Fixed Committed revision 562013, Thanks Sivantha. axis2 idea plugin pom.xml --- Key: AXIS2-3042 URL: https://issues.apache.org/jira/browse/AXIS2-3042 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: axis2 idea plugin pom.xml Reporter: Shivantha Huruggamuwa Assignee: Lahiru Sandakith Attachments: Axis2_Idea_Plugin_Patch_PomXMl.txt pom xml hasn't some dependencies for jar. -- 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]
Re: org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed!
I am using Axis2 1.2
On 8/1/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote:
Are you using Axis2 1.2 ?. Please do try this scenario using latest Axis2
trunk.
Thank you,
Saminda
On 7/29/07, Navnit Jindal [EMAIL PROTECTED] wrote:
-- Forwarded message --
From: Navnit Jindal [EMAIL PROTECTED]
Date: Jul 29, 2007 11:57 AM
Subject: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!
To: [EMAIL PROTECTED] , [EMAIL PROTECTED], [EMAIL PROTECTED],
axis-dev@ws.apache.org
Appreciate your help with this issue. Is there a revised code that can
be used?
org.apache.axis2.AxisFault: problem accessing the parser. Parser already
accessed!
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
CommonsHTTPTransportSender.java:221)
at org.apache.axis2.engine.AxisEngine.send (AxisEngine.java:452)
at org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:330)
===
Code I am using to set the Authentication using Axis2
options.setProperty(HTTPConstants.AUTHENTICATE,
getAuthenticator(username, password));
private HttpTransportProperties.AuthenticatorgetAuthenticator(String
_username, String _password)
{
HttpTransportProperties.Authenticator authenticator = new
HttpTransportProperties.Authenticator ();
//HttpTransportProperties. basicAuthentication
authenticator.setUsername(_username);
authenticator.setPassword(_password);
authenticator.setPreemptiveAuthentication(true);
authenticator.setAllowedRetry(true);
return authenticator;
}
--
Saminda Abeyruwan
Software Engineer
WSO2 Inc. - www.wso2.org
