Re: [Axis2] [1.4] Zero Blockers / RC4 this weekend / Plan for 1.4 Final

I think this is a serious serious problem [I would classify as blocker] (it affects rest and soap in 1.3 for optional String params where the first param is not set, the second will be marshaled in the wrong place on the server). All I did was make a Java class with a method that takes two str

[jira] Updated: (AXIS2-3693) JAXWSRIWSDLGenerator needs tool.jar on classpath

[ https://issues.apache.org/jira/browse/AXIS2-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated AXIS2-3693: --- Component/s: jaxws Fix Version/s: (was: 1.4) Affects Version/s: 1.4 > JAXWSRIWS

[jira] Created: (AXIS2-3693) JAXWSRIWSDLGenerator needs tool.jar on classpath

JAXWSRIWSDLGenerator needs tool.jar on classpath Key: AXIS2-3693 URL: https://issues.apache.org/jira/browse/AXIS2-3693 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Jarek Gaw

[Axis2] [1.4] Zero Blockers / RC4 this weekend / Plan for 1.4 Final

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks, Looks like there are no blockers on the JIRA marked for 1.4 https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12312460 So, I'll try to cut RC4 this friday and we can roll out the RC's for axiom/xmlschema/neethi e

[jira] Resolved: (AXIS2-3686) Attachments larger than Integer.MAX_VALUE (appr 2.1GB) fails

[ https://issues.apache.org/jira/browse/AXIS2-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3686. - Resolution: Fixed looks like the underlying issue in axiom is already fixed. Please try l

Re: WSDL 2.0 codegeration fails due to Woden assertion

Hi Lawrence, Here is the code that is used to read a WSDL. private Description readInTheWSDLFile(String wsdlURI) throws WSDLException { DocumentBuilderFactory documentBuilderFactory = DocumentBuilderFactory .newInstance(); documentBuilderFactory.setNamespaceAware(t

[jira] Resolved: (AXIS2-3685) org.apache.axis2.transport.jms.JMSListener.stop() doesn't shutdown the thread pool created in start() for JMSMessageReceiver

[ https://issues.apache.org/jira/browse/AXIS2-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3685. - Resolution: Fixed fixed in svn revision 643676. > org.apache.axis2.transport.jms.JMSList

[jira] Created: (AXIS2-3692) axis2-wsdl2code-maven-plugin - "java.lang.RuntimeException: JiBX framework jars not in classpath"

axis2-wsdl2code-maven-plugin - "java.lang.RuntimeException: JiBX framework jars not in classpath" -- Key: AXIS2-3692 URL: https://issues.apache.org/jira/browse/AXIS2-

[jira] Created: (AXIS2-3691) Add more jaxws-integration tests that use async MEP and/or Addressing

Add more jaxws-integration tests that use async MEP and/or Addressing - Key: AXIS2-3691 URL: https://issues.apache.org/jira/browse/AXIS2-3691 Project: Axis 2.0 (Axis2) Issue

[jira] Created: (AXIS2-3690) consolidate server side for doclitwr endpoint

consolidate server side for doclitwr endpoint - Key: AXIS2-3690 URL: https://issues.apache.org/jira/browse/AXIS2-3690 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws

[jira] Resolved: (AXIS2-3666) Unable to switch addressing mar on in jaxws-integration tests

[ https://issues.apache.org/jira/browse/AXIS2-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer resolved AXIS2-3666. - Resolution: Fixed Assignee: Mike Rheinheimer (was: Brian DePradine) > Unable to sw

[jira] Updated: (AXIS2-3666) Unable to switch addressing mar on in jaxws-integration tests

[ https://issues.apache.org/jira/browse/AXIS2-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer updated AXIS2-3666: Attachment: patch_643523_643524.txt Attached patch_643523-643524.txt is the final patch tha

Re: WSDL 2.0 codegeration fails due to Woden assertion

Hi Keith, Can you pass along the code that instantiates a Woden reader and reads a WSDL file? I want to make sure I'm performing the same steps as you because I'm not seeing this failure. Thanks, Lawrence "keith chapman" <[EMAIL PROTECTED]> 04/01/2008 09:56 AM Please respond to axis-dev@

[jira] Updated: (AXIS2-3666) Unable to switch addressing mar on in jaxws-integration tests

[ https://issues.apache.org/jira/browse/AXIS2-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer updated AXIS2-3666: Attachment: patch_candidate01.txt > Unable to switch addressing mar on in jaxws-integration

[jira] Updated: (AXIS2-3666) Unable to switch addressing mar on in jaxws-integration tests

[ https://issues.apache.org/jira/browse/AXIS2-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer updated AXIS2-3666: Attachment: (was: patch_candidate01.jar) > Unable to switch addressing mar on in jaxws-

[jira] Updated: (AXIS2-3666) Unable to switch addressing mar on in jaxws-integration tests

[ https://issues.apache.org/jira/browse/AXIS2-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer updated AXIS2-3666: Attachment: patch_candidate01.jar File patch_candidate01.jar attached. Several things incl

Re: FW: Why this wsdl is not valid Wsdl

Hi, First point is your working WSDL is working fine only because you have all referenced XML-Schemas accessible. (doesnt work with me) Second point is the imported XML-Schema MUST have a different Namespace than the importing XML-Schema. Third point is you should qualify all referenced elements

WLS 10 MP1 - Axis 2 1.3 - BouncyCastle problem

Has anyone else tried WLS 10? I would like to get this fixed as we can't always change the WLS default installation . -Simon From: Simon Nunn [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2008 8:46 AM To: '[EMAIL PROTECTED]' Subject: RE: WLS 10 MP1 - Axis 2 1.3 - BouncyCastle probl

Re: WSDL 2.0 codegeration fails due to Woden assertion

Hi Lawrence, I found the problem after some investigation. The problem was that I have set reader.setFeature(WSDLReader.FEATURE_VALIDATION, true); Is it possible to perform validation while continuing on error. I tried setting reader.setFeature(WSDLReader.FEATURE_VALIDATION, true); reader.setFe

[jira] Created: (AXIS2-3689) java.lang.String.valueOf(param).matches() work not with boolean param

java.lang.String.valueOf(param).matches() work not with boolean param - Key: AXIS2-3689 URL: https://issues.apache.org/jira/browse/AXIS2-3689 Project: Axis 2.0 (Axis2) Issue

[jira] Created: (AXIS2-3688) java.lang.String.valueOf(param).matches() work not with java.util.Calendar param

java.lang.String.valueOf(param).matches() work not with java.util.Calendar param -- Key: AXIS2-3688 URL: https://issues.apache.org/jira/browse/AXIS2-3688

[jira] Created: (AXIS2-3687) Unicode character blocks are not correctly transformed to java code "\p{Is...}"

Unicode character blocks are not correctly transformed to java code "\p{Is...}" --- Key: AXIS2-3687 URL: https://issues.apache.org/jira/browse/AXIS2-3687 Project: Axis 2.0 (Ax

[jira] Resolved: (AXIS2-3683) AddressingOutHandler may omit wsa:To on 2004/08 despite it being mandatory

[ https://issues.apache.org/jira/browse/AXIS2-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-3683. -- Resolution: Fixed Fix Version/s: 1.4 Assignee: David Illsley Fixed in r643041

RE: org.apache.axis2.AxisFault: Transport out has not been set

Hi, I have found the problem, just ignore my previous email. Regards, Mai Sun From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 01 April 2008 11:08 To: axis-dev@ws.apache.org Subject: org.apache.axis2.AxisFault: Transport out has not been set Hi a

org.apache.axis2.AxisFault: Transport out has not been set

Hi all, We're developing a web service client using Axis2 and we use code generator eclipse plugin to generate the client stub. The project compiles but when we try to call the web service we receive an error: org.apache.axis2.AxisFault: Transport out has not been set This error occured before

[jira] Commented: (AXIS2-3662) Can't use JMS transport from axis2.war on WebSphere Application Server 6.1

[ https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584054#action_12584054 ] Asankha C. Perera commented on AXIS2-3662: -- The original post above stated that:

[jira] Closed: (AXIS2-3602) NPE in MessageContextBuilder.createFaultEnvelope and SOAP12Constants.SOAP_FAULT_NODE_LOCAL_NAME property set in message context

[ https://issues.apache.org/jira/browse/AXIS2-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weber closed AXIS2-3602. - > NPE in MessageContextBuilder.createFaultEnvelope and > SOAP12Constants.SOAP_FAULT_NODE_LOCAL_NAME

[jira] Updated: (AXIS2-3681) wsdl2java -d jaxbri -uw unable to generate non-void web methods

[ https://issues.apache.org/jira/browse/AXIS2-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federica Ciotti updated AXIS2-3681: --- Description: I need to generate java artefacts from wsdl. The wsdl is attached and it respe

[jira] Created: (AXIS2-3686) Attachments larger than Integer.MAX_VALUE (appr 2.1GB) fails

Attachments larger than Integer.MAX_VALUE (appr 2.1GB) fails Key: AXIS2-3686 URL: https://issues.apache.org/jira/browse/AXIS2-3686 Project: Axis 2.0 (Axis2) Issue Type: Bug Aff