RE: problems while deploying using .aar files

d to axis2-1.1.1 which has this class Could some one please tell me what to do? Thanks in advance Prasad --- Brennan Spies <[EMAIL PROTECTED]> wrote: > This is the problem I was referring to before. Only > way to get around it is > to use "PARENT_LAST"

RE: problems while deploying using .aar files

sion.aar due to java.lang.NoSuchMethodError: javax.xml.namespace.QName: method (Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V not found.. Could any one pl lemme know what should be done if you came across such errors Thanks in advance, Prasad --- Brennan Spies <[EMAIL PROTECTED]> wrote: &

RE: qn reg. axis2 on RAD 6.0

This translates into "PARENT_LAST" classloading for WebSphere. This will get rid of the problem that WebSphere has many older/customized versions of jars that get loaded by the parent classloader. You may need to take the additional step of specifying the commons logging factory implementation as a

[jira] Commented: (AXIS2-1575) Axis2 does not decodes SOAP responses using the character encoding set on the response's XML declaration. Problem converting from iso-8859-1 to utf-8.

[ http://issues.apache.org/jira/browse/AXIS2-1575?page=comments#action_12446957 ] Brennan Spies commented on AXIS2-1575: -- http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0.html#Character_Encodings > Axis2 does not decodes S

RE: [jira] Commented: (AXIS2-1381) Need to enhance code generationfrom WSDL to support JMS extensions

:57 -0800, Brennan Spies (JIRA) wrote: > [ http://issues.apache.org/jira/browse/AXIS2-1381?page=comments#action_1244548 9 ] > > Brennan Spies commented on AXIS2-1381: > -- > > No problem. Glad to be of help. I personally woul

[jira] Commented: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

[ http://issues.apache.org/jira/browse/AXIS2-1381?page=comments#action_12445489 ] Brennan Spies commented on AXIS2-1381: -- No problem. Glad to be of help. I personally would not mind getting more actively involved with the project, if you

SOAP 1.2 extensibility elements

;t address this in the patch since it was specific to JMS support. -Original Message----- From: Brennan Spies (JIRA) [mailto:[EMAIL PROTECTED] Sent: Saturday, October 28, 2006 7:02 PM To: axis-dev@ws.apache.org Subject: [jira] Updated: (AXIS2-1381) Need to enhance code generation from WSDL

[jira] Updated: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

[ http://issues.apache.org/jira/browse/AXIS2-1381?page=all ] Brennan Spies updated AXIS2-1381: - Attachment: patch.zip This is a patch to fix this issue. Notes: 1. Have not dealt with native JMS binding, but the more common use case of SOAP JMS

[jira] Commented: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

[ http://issues.apache.org/jira/browse/AXIS2-1381?page=comments#action_12445051 ] Brennan Spies commented on AXIS2-1381: -- I'm putting the finishing touches on the patch, and am getting ready to test it. A few issues I've run ac

[jira] Commented: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

[ http://issues.apache.org/jira/browse/AXIS2-1381?page=comments#action_12444196 ] Brennan Spies commented on AXIS2-1381: -- For the WSIF, that's essentially what I've already done. What I was referring to was that there is one met

[jira] Commented: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

[ http://issues.apache.org/jira/browse/AXIS2-1381?page=comments#action_12444151 ] Brennan Spies commented on AXIS2-1381: -- I wouldn't mind supplying a patch to do this myself, if no one there has the bandwidth to do so. A) Ther

[jira] Updated: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

[ http://issues.apache.org/jira/browse/AXIS2-1381?page=all ] Brennan Spies updated AXIS2-1381: - Attachment: files.zip Example files to use. > Need to enhance code generation from WSDL to support JMS extensi

[jira] Created: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

) Issue Type: New Feature Components: codegen Affects Versions: 1.1 Environment: All Reporter: Brennan Spies Currently, there is no support for JMS WSDL extensions in Axis 2.0. Code generation for a WSDL service with JMS bindings succeeds, but the client stub is

[jira] Commented: (AXIS2-545) WSDL port address for JMS

[ http://issues.apache.org/jira/browse/AXIS2-545?page=comments#action_12442094 ] Brennan Spies commented on AXIS2-545: - OK, looks like they already have these in the org.apache.wsif.wsdl\extensions.jms package... > WSDL port address

[jira] Commented: (AXIS2-545) WSDL port address for JMS

[ http://issues.apache.org/jira/browse/AXIS2-545?page=comments#action_12442092 ] Brennan Spies commented on AXIS2-545: - Part 1. above needs to be done with WSDL4J. From WSIF docs: To Implement new WSDL extension using WSDL4J it is necessary

[jira] Commented: (AXIS2-545) WSDL port address for JMS

[ http://issues.apache.org/jira/browse/AXIS2-545?page=comments#action_12442070 ] Brennan Spies commented on AXIS2-545: - Using the current 1.1 nightly build, there are just a few things needed to add support: 1. Recognize the child (and

[jira] Commented: (AXIS2-1236) Undefined method generated (regression)

[ http://issues.apache.org/jira/browse/AXIS2-1236?page=comments#action_12437622 ] Brennan Spies commented on AXIS2-1236: -- Right...it is on second check (and a coffee), a missing method call. Something like toEnvelope(...) should be after

[jira] Created: (AXIS2-1236) Undefined method generated (regression)

Environment: Windows XP, Axis 2.0 nightly (9/25) Reporter: Brennan Spies The 9/25 nightly build seems to have introduced a regression bug, where the WSDL to Java code generator (using XMLBeans databinding) is referencing a non-existent method in the invokeBusinessLogic() method, namely

[jira] Commented: (AXIS2-1185) Generation of a return message when 'type' is specified on the output message part

[ http://issues.apache.org/jira/browse/AXIS2-1185?page=comments#action_12436277 ] Brennan Spies commented on AXIS2-1185: -- I am going to correct myself here. Use of the 'type' attribute on definitions/message/part is not a

[jira] Created: (AXIS2-1185) Generation of a return message when 'type' is specified on the output message part

Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.0 Environment: Axis 2.0 build: 2006-09-18, Windows XP Reporter: Brennan Spies When specifying a 'type' rather than 'element' on a WSDL message part,

[jira] Commented: (AXIS2-1116) WSDL2Java with Xmlbeans binding is not generating classes for all schema

[ http://issues.apache.org/jira/browse/AXIS2-1116?page=comments#action_12433158 ] Brennan Spies commented on AXIS2-1116: -- Downloaded nightly build (2006-09-07), and it looks like all of the issues except #2 have been fixed. > WSDL2J

[jira] Created: (AXIS2-1116) WSDL2Java with Xmlbeans binding is not generating classes for all schema

) Issue Type: Bug Components: databinding Affects Versions: 1.0 Environment: Windows XP, Axis 2.0 nightly build (2006-09-02) Reporter: Brennan Spies Attachments: files.zip I have 3 XML Schemas that are used by my service definition in Query.wsdl. I

[jira] Commented: (AXIS2-1107) WSDL2Java code generator not recognizing global element in referenced schema

[ http://issues.apache.org/jira/browse/AXIS2-1107?page=comments#action_12432361 ] Brennan Spies commented on AXIS2-1107: -- Actually, it looks like I've looks like I've made an error with the namespaces above, but this is not the

[jira] Created: (AXIS2-1107) WSDL2Java code generator not recognizing global element in referenced schema

(Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.0 Environment: Windows XP, Axis 2.0 version 1.0 as well as 2006-09-02 nightly build, see files attached to bug 1089 Reporter: Brennan Spies I have an issue doing code generation from my WSDL

[jira] Commented: (AXIS2-1089) WSDL2Java is generating invalid inner class, method with XmlBeans binding

[ http://issues.apache.org/jira/browse/AXIS2-1089?page=comments#action_12431722 ] Brennan Spies commented on AXIS2-1089: -- OK, I have switched to the latest nightly build (2006-08-29), and this problem seems to have been resolved. I had to

[jira] Created: (AXIS2-1089) WSDL2Java is generating invalid inner class, method with XmlBeans binding

) Issue Type: Bug Components: databinding Affects Versions: 1.0 Environment: Windows XP, Axis 2.0 release 1.0 (also latest nightly build Reporter: Brennan Spies Attachments: files.zip Using WSDL2Java for the attached files (specifying -d