[jira] Created: (AXIS2-4833) Modules not getting loaded from classpath in Oracle WebLogic 10.x

Modules not getting loaded from classpath in Oracle WebLogic 10.x - Key: AXIS2-4833 URL: https://issues.apache.org/jira/browse/AXIS2-4833 Project: Axis2 Issue Type: Bug

[jira] Updated: (AXIS2-4832) -

[ https://issues.apache.org/jira/browse/AXIS2-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Spiegel updated AXIS2-4832: - Summary: - (was: Modules not getting loaded from classpath in BEA Weblogic 10.x) A

[jira] Closed: (AXIS2-4832) -

[ https://issues.apache.org/jira/browse/AXIS2-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Spiegel closed AXIS2-4832. Resolution: Fixed > - > - > > Key: AXIS2-4832 > URL: https://issues

[jira] Updated: (AXIS2-4832) -

[ https://issues.apache.org/jira/browse/AXIS2-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Spiegel updated AXIS2-4832: - Description: Sorry, this was my first try to create a ticket. Please remove! > - > - > >

[jira] Deleted: (AXIS2-4832) -

[ https://issues.apache.org/jira/browse/AXIS2-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen deleted AXIS2-4832: --- > - > - > > Key: AXIS2-4832 > URL: https://issues.apache.org/jira

[jira] Updated: (AXIS2-4833) Modules not getting loaded from classpath in Oracle WebLogic 10.x

[ https://issues.apache.org/jira/browse/AXIS2-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Spiegel updated AXIS2-4833: - Affects Version/s: 1.5.1 (was: 1.4.1) Environment: JDK 1.6.0_

[jira] Updated: (AXIS2-4833) Modules not getting loaded from classpath in Oracle WebLogic 10.x

[ https://issues.apache.org/jira/browse/AXIS2-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Spiegel updated AXIS2-4833: - Description: I've tried to loading the logging-module from the classpath which did not work on a

[jira] Updated: (AXIS2-4833) Modules not getting loaded from classpath in Oracle WebLogic 10.x

[ https://issues.apache.org/jira/browse/AXIS2-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Spiegel updated AXIS2-4833: - Attachment: bug_4833_pic1.jpg bug_4833_pic2.jpg Debugger Screenshots > Modules n

[jira] Updated: (AXIS2-4833) Modules not getting loaded from classpath in Oracle WebLogic 10.x

[ https://issues.apache.org/jira/browse/AXIS2-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4833: --- Assignee: (was: Andreas Veithen) > Modules not getting loaded from classpath in Oracle We

[jira] Assigned: (AXIS2-4716) Threading issue in CommonsHTTPTransportSender when different messages use different HTTP versions or transfer encoding settings

[ https://issues.apache.org/jira/browse/AXIS2-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS2-4716: -- Assignee: Andreas Veithen > Threading issue in CommonsHTTPTransportSender when differen

Hudson build is back to normal : Axis2-trunk-java-1.6 #169

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: svn commit: r983407 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/client/ServiceClient.java

Rich, Can you please explain in which context you got a NPE in this piece of code? As Amila pointed out in AXIS2-4648, transportOut=null (or sender=null) is not a normal condition and this change probably hides a more fundamental problem. Andreas On Sun, Aug 8, 2010 at 14:50, wrote: > Author:

[jira] Updated: (AXIS2-4716) Threading issue in CommonsHTTPTransportSender when different messages use different HTTP versions or transfer encoding settings

[ https://issues.apache.org/jira/browse/AXIS2-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4716: --- Affects Version/s: 1.5.2 (was: nightly) > Threading issue in Commo

[jira] Resolved: (AXIS2-4716) Threading issue in CommonsHTTPTransportSender when different messages use different HTTP versions or transfer encoding settings

[ https://issues.apache.org/jira/browse/AXIS2-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4716. Fix Version/s: 1.6 Resolution: Fixed Fixed by r1002140 on the trunk, i.e. for 1.6. P

Re: svn commit: r991441 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/description/java2wsdl/Java2WSDLConstants.java

On Mon, Sep 27, 2010 at 9:48 PM, Andreas Veithen wrote: > Isuru, > > Actually, the proper way of doing this is to configure an > ExtensionRegistry on the WSDLReader so that WSDL4J knows what is the > expected type for the wsas:Action attribute (otherwise it will try to > guess the attribute type,

Re: [VOTE] Release WSS4J 1.5.9 [attn Rampart devs]

Confirmed. I would like to set up continuous integration between WSS4J and Rampart. If you update the version of the 1.5 branch to 1.5.10-SNAPSHOT, then I can set up a Hudson job for WSS4J (including automatic deployment of snapshots to the Nexus repository). Andreas On Tue, Sep 28, 2010 at 14:2

Hudson build is back to normal : Rampart #101

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] Assigned: (AXIS2-4821) For an InOutAxisOperation, HTTPConstants.AUTO_RELEASE_CONNECTION property is always true

[ https://issues.apache.org/jira/browse/AXIS2-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS2-4821: -- Assignee: Andreas Veithen > For an InOutAxisOperation, HTTPConstants.AUTO_RELEASE_CONNE

[jira] Updated: (AXIS2-4821) For an InOutAxisOperation, HTTPConstants.AUTO_RELEASE_CONNECTION property is always true

[ https://issues.apache.org/jira/browse/AXIS2-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4821: --- Affects Version/s: 1.5.2 (was: 1.6) > For an InOutAxisOperation, H

RES: How to remove the soapenv:mustUnderstand attribute

I would like to share my disappointing with this mailing list. Yesterday was the second time (the first time was in 26/08/2010) I asked about removing the soapenv:mustUnderstand attribute from the SOAP message. Both of my messages was completely ignored. This mailing list looks like a close

Hudson build is still unstable: axis2-transports-trunk #183

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Hudson build is still unstable: axis2-transpor ts-trunk » Apache Axis2 - Transport - Sms #183

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] Commented: (AXIS2-4821) For an InOutAxisOperation, HTTPConstants.AUTO_RELEASE_CONNECTION property is always true

[ https://issues.apache.org/jira/browse/AXIS2-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915747#action_12915747 ] Andreas Veithen commented on AXIS2-4821: I believe that this is just a workaround t

Re: RES: How to remove the soapenv:mustUnderstand attribute

I am so sad to hear that. Let me see whether I can help you on this. You can always add and remove soap headers (or any other element) to the SOAP message by using a handler. If you want to do that for the incoming message add a handler in the in-flow and remove the element. One thing I noticed

Re: [VOTE] Release WSS4J 1.5.9 [attn Rampart devs]

I've created a job [1] in Hudson, but the test suite fails because the JDK is not configured with unlimited strength encryption. I've asked [email protected] for advice. Andreas [1] https://hudson.apache.org/hudson/view/WS/job/wss4j-1.5/ On Tue, Sep 28, 2010 at 15:05, Colm O hEigeartaigh wrote:

[jira] Issue Comment Edited: (AXIS2-4541) IllegalArgumentException with pojo based service using useOriginalwsdl=true and static WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915750#action_12915750 ] Iván San Antonio Martínez edited comment on AXIS2-4541 at 9/28/10 10:02 AM: -

[jira] Commented: (AXIS2-4541) IllegalArgumentException with pojo based service using useOriginalwsdl=true and static WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915750#action_12915750 ] Iván San Antonio Martínez commented on AXIS2-4541: -- As this bug was report

Re: HTTP connection management in Axis

What are actually valid use cases for explicitly setting one's own HttpClient instance? With "valid" I mean use cases other than working around the broken connection management in the HTTP transport? Andreas On Sat, Sep 18, 2010 at 10:51, Amila Suriarachchi wrote: > > > On Sat, Sep 18, 2010 at 1

[jira] Updated: (AXIS2-4821) For an InOutAxisOperation, HTTPConstants.AUTO_RELEASE_CONNECTION property is always true

[ https://issues.apache.org/jira/browse/AXIS2-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4821: --- Component/s: transports > For an InOutAxisOperation, HTTPConstants.AUTO_RELEASE_CONNECTION pr

[jira] Resolved: (AXIS2-3104) HttpCoreNIOListener is binding address agnostic

[ https://issues.apache.org/jira/browse/AXIS2-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-3104. Resolution: Duplicate This issue has been solved by SYNAPSE-117. > HttpCoreNIOListener is

Re: RES: How to remove the soapenv:mustUnderstand attribute

Hi Fernando: It would help if you could give us a few more details about exactly what you want to do here. First off, are you using Axis2 as a client or a server, and when you say you want to remove the mustUnderstand attribute, do you mean when you're sending a message, or receiving one? In oth

RES: RES: How to remove the soapenv:mustUnderstand attribute

Glen and Deepal, I'm sending below more details: 1 - In my project I'm using Axis2 as both client and server, but in this case I'm using as a client; 2 - When I say I want to remove the mustUnderstand attribute, I mean I'm sending a message and this message can't have the mustUnderstand attribut

[jira] Resolved: (AXIS2-4821) For an InOutAxisOperation, HTTPConstants.AUTO_RELEASE_CONNECTION property is always true

[ https://issues.apache.org/jira/browse/AXIS2-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4821. Fix Version/s: 1.6 Resolution: Fixed This should be fixed by r1002204. > For an InO

Re: [VOTE] Release WSS4J 1.5.9 [attn Rampart devs]

We found a JDK with unlimited strength encryption and the build is successfully running on Hudson. There are still three things to do: 1. Allow [email protected] to post to the wss4j-dev list, so that the developers will receive notifications about failed builds. I don't know who can do thi

Hudson build is back to stable : axis2-transpo rts-trunk » Apache Axis2 - Transport - Sms #184

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Hudson build is back to stable : axis2-transports-trunk #184

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: RES: RES: How to remove the soapenv:mustUnderstand attribute

Hi Fernando, So how are you putting the header into the message in the first place? Is this client code that you generated from a WSDL, or are you using code to inject it? --Glen On 9/28/2010 10:51 AM, Fernando Cesar Silva wrote: > Glen and Deepal, > > I'm sending below more details: > > 1 -

Build failed in Hudson: rampart-trunk-axis2-1.5 #18

See -- Failed to access build log hudson.util.IOException2: remote file operation failed: /home/hudson/hudson-slave/workspace/rampart-trunk-axis2-1.5 at hudson.remoting.chan...@243b2059:ub

Build failed in Hudson: Axis2-trunk-java-1.6 #170

See -- Failed to access build log hudson.util.IOException2: remote file operation failed: /home/hudson/hudson-slave/workspace/Axis2-trunk-java-1.6 at hudson.remoting.chan...@243b2059:ubuntu1