[jira] Commented: (RAMPART-252) The way referncelist processing of SAML issued tokens doesn't work properly and algorithm validation required in PolicyBasedResultsValidator

[ https://issues.apache.org/jira/browse/RAMPART-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974100#action_12974100 ] Thilina Buddhika commented on RAMPART-252: -- We won't be able to resolve this unti

[jira] Issue Comment Edited: (RAMPART-252) The way referncelist processing of SAML issued tokens doesn't work properly and algorithm validation required in PolicyBasedResultsValidator

[ https://issues.apache.org/jira/browse/RAMPART-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974100#action_12974100 ] Thilina Buddhika edited comment on RAMPART-252 at 12/22/10 2:27 AM:

[jira] Commented: (RAMPART-198) Rampart 1.4 assumes WSS10 or WSS11 to be present in the policy

[ https://issues.apache.org/jira/browse/RAMPART-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974097#action_12974097 ] asela pathberiya commented on RAMPART-198: -- Verified in trunk. > Rampart 1.4 ass

[jira] Updated: (RAMPART-254) Public getter/setter setCallbackHander/getCallbackHander mis-spelled [ hander --> handler] in SAMLTokenIssuerConfig

[ https://issues.apache.org/jira/browse/RAMPART-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Buddhika updated RAMPART-254: - Attachment: RAMPART-254.patch Hi, Attached herewith the modified patch for the latest r

[jira] Resolved: (RAMPART-277) Rampart ignores token inclusion settings when using the asymmetric security binding

[ https://issues.apache.org/jira/browse/RAMPART-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-277. -- Resolution: Fixed Fix Version/s: NextVersion Applied the patch in revision 1051

[jira] Resolved: (RAMPART-259) SAML2TokenIssuer calls DefaultBootstrap.bootstrap() per every request and attribute call back handler not being called

[ https://issues.apache.org/jira/browse/RAMPART-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-259. -- Resolution: Fixed Resolving the issue since the patch is already applied. > SAML2Tok

[jira] Assigned: (RAMPART-277) Rampart ignores token inclusion settings when using the asymmetric security binding

[ https://issues.apache.org/jira/browse/RAMPART-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned RAMPART-277: Assignee: S.Uthaiyashankar (was: Ruchith Udayanga Fernando) > Rampart ignores tok

[jira] Commented: (RAMPART-259) SAML2TokenIssuer calls DefaultBootstrap.bootstrap() per every request and attribute call back handler not being called

[ https://issues.apache.org/jira/browse/RAMPART-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974092#action_12974092 ] Thilina Buddhika commented on RAMPART-259: -- This fix is already included in the c

[jira] Resolved: (AXIS2-3611) JAXB data binding and NPE with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi resolved AXIS2-3611. -- Resolution: Fixed Fix Version/s: 1.6 Hi Nipa, You've not attach

[jira] Updated: (RAMPART-277) Rampart ignores token inclusion settings when using the asymmetric security binding

[ https://issues.apache.org/jira/browse/RAMPART-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Buddhika updated RAMPART-277: - Attachment: RAMPART-277.patch Hi Dave, I found some conflicts when applying this patch

[jira] Resolved: (RAMPART-118) Rampart and MTOM not working together

[ https://issues.apache.org/jira/browse/RAMPART-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-118. -- Resolution: Duplicate Duplicate of RAMPART-96 > Rampart and MTOM not working together

[jira] Resolved: (AXIS2-4566) please create better error message if axis2.repository.url cannot be honoured

[ https://issues.apache.org/jira/browse/AXIS2-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4566. --- Resolution: Fixed patch applied > please create better error message if axis2.repository.ur

[jira] Assigned: (AXIS2-3611) JAXB data binding and NPE with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi reassigned AXIS2-3611: Assignee: Isuru Eranga Suriarachchi > JAXB data binding and NPE wit

[jira] Closed: (AXIS2-4904) org.apache.axis2.AxisFault: null

[ https://issues.apache.org/jira/browse/AXIS2-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antas Mishra closed AXIS2-4904. --- thanks for all your support > org.apache.axis2.AxisFault: null > >

[jira] Resolved: (AXIS2-3844) kernel clustering code Javadoc has pointers to blog entries.

[ https://issues.apache.org/jira/browse/AXIS2-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3844. - Resolution: Not A Problem These links simply provide more information > kernel clustering code J

[jira] Resolved: (RAMPART-313) Improvements to the site axis.apache.org/axis2/java/rampart/

[ https://issues.apache.org/jira/browse/RAMPART-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-313. -- Resolution: Fixed Fix Version/s: NextVersion Fixed in revision 1051769 Thank y

[jira] Resolved: (RAMPART-267) div class="xleft" does not work

[ https://issues.apache.org/jira/browse/RAMPART-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-267. -- Resolution: Fixed Fix Version/s: NextVersion Fixed in revision 1051769 > div c

[jira] Resolved: (AXIS2-3849) Version service WSDL generates wrong ERP URLs

[ https://issues.apache.org/jira/browse/AXIS2-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3849. - Resolution: Fixed You can use the hostname parameter in the axis2.xml HTTP/S tranport configurat

[jira] Assigned: (RAMPART-313) Improvements to the site axis.apache.org/axis2/java/rampart/

[ https://issues.apache.org/jira/browse/RAMPART-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned RAMPART-313: Assignee: S.Uthaiyashankar > Improvements to the site axis.apache.org/axis2/java/r

[jira] Resolved: (AXIS2-4179) Make PolicySubject of AxisDescription thread-safe

[ https://issues.apache.org/jira/browse/AXIS2-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4179. --- Resolution: Fixed this has been applied, not sure how ;) > Make PolicySubject of AxisDescrip

[jira] Resolved: (AXIS2-3336) Remove /services from the webservices endpoint URL

[ https://issues.apache.org/jira/browse/AXIS2-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3336. - Resolution: Fixed You can use the ServicePath parameter to override this. > Remove /services fro

[jira] Resolved: (AXIS2-4487) JAXB code generation fails with multiple schemas in WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi resolved AXIS2-4487. -- Resolution: Fixed Fix Version/s: 1.6 This issue doesn't exist in

[jira] Resolved: (RAMPART-314) Rampart distribution does not contain OpenSAML 1.1 jars

[ https://issues.apache.org/jira/browse/RAMPART-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-314. -- Resolution: Fixed Fixed in revision 1051768. Thank you very much Thilina for the patc

[jira] Resolved: (AXIS2-4180) [org.apache.axis2.deployment.WarBasedAxisConfigurator] The following handler exists is not valid: phase rule has not been specified

[ https://issues.apache.org/jira/browse/AXIS2-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4180. --- Resolution: Incomplete > [org.apache.axis2.deployment.WarBasedAxisConfigurator] The following

[jira] Assigned: (RAMPART-314) Rampart distribution does not contain OpenSAML 1.1 jars

[ https://issues.apache.org/jira/browse/RAMPART-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned RAMPART-314: Assignee: S.Uthaiyashankar > Rampart distribution does not contain OpenSAML 1.1 ja

[jira] Assigned: (AXIS2-4487) JAXB code generation fails with multiple schemas in WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi reassigned AXIS2-4487: Assignee: Isuru Eranga Suriarachchi > JAXB code generation fails wi

[jira] Resolved: (AXIS2-4776) roblem when hostname matches axis service URL path

[ https://issues.apache.org/jira/browse/AXIS2-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4776. --- Resolution: Fixed fixed this by checking not for service path but / etc, this will fix the i

[jira] Resolved: (RAMPART-224) Error in Rampart configuration schema

[ https://issues.apache.org/jira/browse/RAMPART-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-224. -- Resolution: Fixed Fix Version/s: NextVersion Fixed in revision 1051766. Thank

[jira] Updated: (RAMPART-314) Rampart distribution does not contain OpenSAML 1.1 jars

[ https://issues.apache.org/jira/browse/RAMPART-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Buddhika updated RAMPART-314: - Attachment: RAMPART-314.patch A patch is attached herewith to fix this issue with the co

[jira] Resolved: (RAMPART-121) Handling of KeyStores

[ https://issues.apache.org/jira/browse/RAMPART-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved RAMPART-121. --- Resolution: Fixed Fix Version/s: NextVersion Resolving as per the previous co

[jira] Created: (RAMPART-314) Rampart distribution does not contain OpenSAML 1.1 jars

Rampart distribution does not contain OpenSAML 1.1 jars --- Key: RAMPART-314 URL: https://issues.apache.org/jira/browse/RAMPART-314 Project: Rampart Issue Type: Bug Components: di

[jira] Assigned: (RAMPART-224) Error in Rampart configuration schema

[ https://issues.apache.org/jira/browse/RAMPART-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned RAMPART-224: Assignee: S.Uthaiyashankar (was: Samisa Abeysinghe) > Error in Rampart configurat

[jira] Resolved: (AXIS2-4204) Axis2server.bat error

[ https://issues.apache.org/jira/browse/AXIS2-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4204. --- Resolution: Cannot Reproduce please reopen with details if you still get the error with new v

[jira] Updated: (AXIS2-4337) Missing org.apache.axis2.transport.tcp.TCPTransportSender into Axis2 1.5 WAR

[ https://issues.apache.org/jira/browse/AXIS2-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera updated AXIS2-4337: -- Priority: Minor (was: Major) > Missing org.apache.axis2.transport.tcp.TCPTransportSender into

Re: [VOTE] Release Sandesha2 1.4 and Axis2 1.5.4

I have tested both these versions with the Synapse-2.0.0 proposed release and the functionality seems to be working fine. How ever on the Synapse startup I see the following log statement; 2010-12-22 11:13:18,740 [-] [main] ERROR SandeshaModule Could not load module policies. Using default values

[jira] Resolved: (AXIS2-4211) Support for 2004/03 version of ws-addressing

[ https://issues.apache.org/jira/browse/AXIS2-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4211. --- Resolution: Won't Fix We only support submission and final versions for Addressing > Support

Re: svn commit: r1051479 - /axis/axis2/java/core/trunk/modules/transport/http/src/org/apache/axis2/transport/http/AxisServlet.java

Actually, ListingAgent code does not belong in AxisServlet since this is something related to the Axis2 console. It was wrong to place that in AxisServlet in the first place. Azeez On Wed, Dec 22, 2010 at 10:58 AM, Afkham Azeez wrote: > Yeah, thanks for pointing out. I will move the ListingAgen

[jira] Assigned: (AXIS2-4776) roblem when hostname matches axis service URL path

[ https://issues.apache.org/jira/browse/AXIS2-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera reassigned AXIS2-4776: - Assignee: Srinath Perera > roblem when hostname matches axis service URL path > -

Re: svn commit: r1051479 - /axis/axis2/java/core/trunk/modules/transport/http/src/org/apache/axis2/transport/http/AxisServlet.java

Yeah, thanks for pointing out. I will move the ListingAgent init code to a separate method. Azeez On Wed, Dec 22, 2010 at 3:41 AM, Andreas Veithen wrote: > Afkham, > > Why would it be the responsibility of a method called "initTransport" > to initialize the ListingAgent? > > Andreas > > On Tue,

[jira] Updated: (RAMPART-313) Improvements to the site axis.apache.org/axis2/java/rampart/

[ https://issues.apache.org/jira/browse/RAMPART-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chanaka Jayasena updated RAMPART-313: - Attachment: images.zip rampart-site.patch > Improvements to the site axi

[jira] Issue Comment Edited: (RAMPART-121) Handling of KeyStores

[ https://issues.apache.org/jira/browse/RAMPART-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974056#action_12974056 ] Thilina Buddhika edited comment on RAMPART-121 at 12/22/10 12:09 AM: ---

[jira] Created: (RAMPART-313) Improvements to the site axis.apache.org/axis2/java/rampart/

Improvements to the site axis.apache.org/axis2/java/rampart/ Key: RAMPART-313 URL: https://issues.apache.org/jira/browse/RAMPART-313 Project: Rampart Issue Type: Improvement

[jira] Commented: (RAMPART-121) Handling of KeyStores

[ https://issues.apache.org/jira/browse/RAMPART-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974056#action_12974056 ] Thilina Buddhika commented on RAMPART-121: -- Hi, Now we have crypto caching in pl

[jira] Commented: (RAMPART-224) Error in Rampart configuration schema

[ https://issues.apache.org/jira/browse/RAMPART-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974044#action_12974044 ] Samisa Abeysinghe commented on RAMPART-224: --- It was not clear from the original

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

In the future how about bundling Rampart and Sandesha2 into the Axis2 distribution itself? It is really part of Axis2 I guess. The recent experience that I had with the Synapse release convinced me that Rampart and Sandesha2 are really part of Axis2? Why do't we create a one single distribution wit

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

On Wed, Dec 22, 2010 at 7:56 AM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > We have fixed loads of Rampart issues yesterday and we will be able to fix > some more today as well. > > How about a release ASAP? I think users will benefit by having latest > rampart working with latest A

[jira] Commented: (RAMPART-295) Rampart failing to extract keyinfo from SAML assertion

[ https://issues.apache.org/jira/browse/RAMPART-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974034#action_12974034 ] S.Uthaiyashankar commented on RAMPART-295: -- This is WSS4J issue. Moving to WSS4J

[jira] Updated: (RAMPART-295) Rampart failing to extract keyinfo from SAML assertion

[ https://issues.apache.org/jira/browse/RAMPART-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated RAMPART-295: - Priority: Major (was: Blocker) > Rampart failing to extract keyinfo from SAML assertion

[jira] Reopened: (RAMPART-224) Error in Rampart configuration schema

[ https://issues.apache.org/jira/browse/RAMPART-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Sosnoski reopened RAMPART-224: - The actual Rampart configuration is of the form (from sample08): ht

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

On Wed, Dec 22, 2010 at 8:16 AM, Selvaratnam Uthaiyashankar < uthaiyashan...@gmail.com> wrote: > On Wed, Dec 22, 2010 at 7:56 AM, Samisa Abeysinghe > wrote: > > We have fixed loads of Rampart issues yesterday and we will be able to > fix > > some more today as well. > > > > How about a release AS

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

On Wed, Dec 22, 2010 at 7:56 AM, Samisa Abeysinghe wrote: > We have fixed loads of Rampart issues yesterday and we will be able to fix > some more today as well. > > How about a release ASAP? I think users will benefit by having latest > rampart working with latest Axis2. +1. We haven't done a re

Release Rampart 1.5.1 in sync with Axis2 1.5.4

We have fixed loads of Rampart issues yesterday and we will be able to fix some more today as well. How about a release ASAP? I think users will benefit by having latest rampart working with latest Axis2. Samisa...

[jira] Resolved: (AXIS2-4564) Axis2 WSDL2Java Innvocation Target Exception

[ https://issues.apache.org/jira/browse/AXIS2-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4564. --- Resolution: Incomplete please attach the WSDL and reopen > Axis2 WSDL2Java Innvocation Targe

[jira] Resolved: (AXIS2-4678) AxisFault: The service could not be found for the end point refrence.

[ https://issues.apache.org/jira/browse/AXIS2-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4678. --- Resolution: Incomplete I do not think this is a bug, most probably a user error. If you stil

Hudson build became unstable: Axis2-trunk-java-1.6 #260

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Hudson build became unstable: Axis2-trunk-java- 1.6 » Apache Axis2 - JAXWS Integration Tests #260

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.ap

[jira] Commented: (AXIS2-4808) org.oasis_open.docs.ns.cmis.ws._200908.CmisException: CmisException

[ https://issues.apache.org/jira/browse/AXIS2-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974006#action_12974006 ] Srinath Perera commented on AXIS2-4808: --- Can you help us reproduce by providing servi

[jira] Commented: (AXIS2-4836) REST: operation dispatch fails due to inconsistent http locations

[ https://issues.apache.org/jira/browse/AXIS2-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974001#action_12974001 ] Srinath Perera commented on AXIS2-4836: --- HI Dennis, Cloud you explain what this pat

[jira] Commented: (AXIS2-4855) Support new SOAP/JMS binding ID

[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973997#action_12973997 ] Srinath Perera commented on AXIS2-4855: --- Hi Jeff, As per your last comment, I assum

[jira] Commented: (RAMPART-174) Rampart module says true to all assertions when canSupportAssertion is called

[ https://issues.apache.org/jira/browse/RAMPART-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973996#action_12973996 ] Samisa Abeysinghe commented on RAMPART-174: --- Nandana, I assume you know how to f

[jira] Resolved: (RAMPART-283) sp:ProtectTokens Assertion Ignored w/ Transport Security Binding

[ https://issues.apache.org/jira/browse/RAMPART-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved RAMPART-283. --- Resolution: Fixed Fix Version/s: NextVersion Assignee: Samisa Abeysin

[jira] Assigned: (RAMPART-288) Supporting Tokens Not Encrypted When Protection Order is Sign Before Encrypting

[ https://issues.apache.org/jira/browse/RAMPART-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned RAMPART-288: - Assignee: Samisa Abeysinghe (was: Ruchith Udayanga Fernando) > Supporting Token

[jira] Resolved: (RAMPART-288) Supporting Tokens Not Encrypted When Protection Order is Sign Before Encrypting

[ https://issues.apache.org/jira/browse/RAMPART-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved RAMPART-288. --- Resolution: Fixed Fix Version/s: NextVersion Applied patch: At revision: 1051

[jira] Resolved: (RAMPART-300) Rampart automaticaly tries to load an "Encryption user" if the security policy defines the use of a UsernameToken with a AsymmetricBinding

[ https://issues.apache.org/jira/browse/RAMPART-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved RAMPART-300. --- Resolution: Fixed Fix Version/s: NextVersion Assignee: Samisa Abeysin

[jira] Resolved: (RAMPART-225) SupportingToken UsernameToken is always encrypted

[ https://issues.apache.org/jira/browse/RAMPART-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved RAMPART-225. --- Resolution: Fixed Fix Version/s: NextVersion Assignee: Samisa Abeysin

[jira] Resolved: (RAMPART-303) Incorrect XML Passed to Digest Algorithm when XML Elements Belong to Empty Namespace

[ https://issues.apache.org/jira/browse/RAMPART-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved RAMPART-303. --- Resolution: Fixed Fix Version/s: NextVersion Fixed with the fix for RAMPART-3

[jira] Resolved: (RAMPART-309) Incorrect XML Passed to Digest Algorithm

[ https://issues.apache.org/jira/browse/RAMPART-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved RAMPART-309. --- Resolution: Fixed Fix Version/s: NextVersion Assignee: Samisa Abeysin

[jira] Updated: (AXIS2-4912) Improvements to http://axis.apache.org/axis2/java/core

[ https://issues.apache.org/jira/browse/AXIS2-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chanaka Jayasena updated AXIS2-4912: Attachment: menu-back.gif home-top.gif axis2site-patch.patch

[jira] Created: (AXIS2-4912) Improvements to http://axis.apache.org/axis2/java/core

Improvements to http://axis.apache.org/axis2/java/core -- Key: AXIS2-4912 URL: https://issues.apache.org/jira/browse/AXIS2-4912 Project: Axis2 Issue Type: Improvement Reporter:

[jira] Updated: (AXIS2-4911) Improvements to the axis.apache.org landing page

[ https://issues.apache.org/jira/browse/AXIS2-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chanaka Jayasena updated AXIS2-4911: Attachment: site.zip > Improvements to the axis.apache.org landing page > -

[jira] Created: (AXIS2-4911) Improvements to the axis.apache.org landing page

Improvements to the axis.apache.org landing page Key: AXIS2-4911 URL: https://issues.apache.org/jira/browse/AXIS2-4911 Project: Axis2 Issue Type: Improvement Reporter: Chanaka Jaya

Re: Is there a proper documentation on deploying AXIS2 in IBM Web Sphere

On Tue, Dec 21, 2010 at 07:54, Pradeep Fernando wrote: > Hi, > >> I've encountered this issue when trying to deploy an application that >> uses Plexus. The bug basically implies that all applications that >> create custom class loaders (and do some reasonably sophisticated >> stuff with them) will

Re: svn commit: r1051479 - /axis/axis2/java/core/trunk/modules/transport/http/src/org/apache/axis2/transport/http/AxisServlet.java

Afkham, Why would it be the responsibility of a method called "initTransport" to initialize the ListingAgent? Andreas On Tue, Dec 21, 2010 at 13:54, wrote: > Author: azeez > Date: Tue Dec 21 12:54:09 2010 > New Revision: 1051479 > > URL: http://svn.apache.org/viewvc?rev=1051479&view=rev > Log:

[jira] Commented: (AXIS2-4892) User should be able to set custom HTTP headers when using CommonsHTTPTransportSender

[ https://issues.apache.org/jira/browse/AXIS2-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973936#action_12973936 ] Andreas Veithen commented on AXIS2-4892: There is another issue (AXIS2-4754) that p

[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code

[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973933#action_12973933 ] William Walsh commented on AXIS2-4910: -- Andreas, I think you're correct that an IBM P

[jira] Reopened: (AXIS2-3818) CommonsHTTPTransportSender - static timeout parameter are not handled properly

[ https://issues.apache.org/jira/browse/AXIS2-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reopened AXIS2-3818: I think what Oliver wants to say is that the init method reads the parameter into two attribut

[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code

[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973903#action_12973903 ] Andreas Veithen commented on AXIS2-4910: I would say that this is definitely a bug

[jira] Resolved: (AXIS2-3465) ServiceClient.sendReceive blocks application forever

[ https://issues.apache.org/jira/browse/AXIS2-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-3465. Resolution: Fixed There have been several improvements to HTTP connection management starti

Re: svn commit: r1051511 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/description/ClientUtils.java

I'm not sure that this is a valid change: 1. The fact that a method only reads information doesn't automatically imply that it doesn't need synchronization. See the Java Memory Model for an explanation why this is an incorrect assumption. 2. The synchronization was added in r387691 to fix a "synch

[jira] Assigned: (AXIS2-4124) CLONE -Exception in XML serialization causes malformed/corrupted response

[ https://issues.apache.org/jira/browse/AXIS2-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando reassigned AXIS2-4124: -- Assignee: Senaka Fernando (was: Glen Daniels) > CLONE -Exception in XML serialization

[jira] Commented: (AXIS2-4008) Generated stub classes are copied to the Eclipse workspace folder instead of the project location

[ https://issues.apache.org/jira/browse/AXIS2-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973826#action_12973826 ] Harshana Eranga Martin commented on AXIS2-4008: --- Hi Norman, The line "This i

[jira] Issue Comment Edited: (AXIS2-4204) Axis2server.bat error

[ https://issues.apache.org/jira/browse/AXIS2-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973820#action_12973820 ] Harshana Eranga Martin edited comment on AXIS2-4204 at 12/21/10 2:07 PM:

[jira] Commented: (AXIS2-4204) Axis2server.bat error

[ https://issues.apache.org/jira/browse/AXIS2-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973820#action_12973820 ] Harshana Eranga Martin commented on AXIS2-4204: --- Hi Nikhil, Can you reproduc

[jira] Resolved: (AXIS2-4320) Error when running an Axis2 client code

[ https://issues.apache.org/jira/browse/AXIS2-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4320. --- Resolution: Incomplete If you need a fix, please attach the client code, service aar file, an

[jira] Commented: (AXIS2-4336) NPE when creating AxisConfigBuilder programatically. This happens only when log4j.logger.org.apache.axis2 is set to DEBUG

[ https://issues.apache.org/jira/browse/AXIS2-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973773#action_12973773 ] Srinath Perera commented on AXIS2-4336: --- Hi Venkat, I tried this this current trunk

Re: Hudson build became unstable: Axis2 » Apache Ax is2 - JAXWS Integration Tests #533

Just in case anybody wonders why the Axis2 build fails from time to time: there is a test case that attempts to send a SOAP request to this.is.not.a.valid.hostname.at.all.no.way and checks that this results in an UnknownHostException (wrapped in an appropriate JAX-WS exception). However, for some r

Hudson build is back to stable : Axis2 #534

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Hudson build is back to stable : Axis2 » A pache Axis2 - JAXWS Integration Tests #534

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] Resolved: (AXIS2-4448) DefaultObjectSupplier fails to instantiate static nested classes

[ https://issues.apache.org/jira/browse/AXIS2-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4448. --- Resolution: Fixed This is resolved as per Andreas's comment > DefaultObjectSupplier fails to

[jira] Resolved: (AXIS2-4267) possible null pointer exception in the createClientSideAxisService method

[ https://issues.apache.org/jira/browse/AXIS2-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva resolved AXIS2-4267. Resolution: Fixed Fixed by applying the patch. Thanks Pradeep for the contribution.

[jira] Resolved: (AXIS2-4467) Incorporate AxisAdminServlet into a jar file for easy on assembling a custom WAR file.

[ https://issues.apache.org/jira/browse/AXIS2-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4467. --- Resolution: Won't Fix > Incorporate AxisAdminServlet into a jar file for easy on assembling a

[jira] Resolved: (AXIS2-4491) Unable to use the java.net.URL connection to run om Appengine

[ https://issues.apache.org/jira/browse/AXIS2-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4491. --- Resolution: Won't Fix I have looked at this, and this is not exactly a bug in axis2. Fix ma

[jira] Commented: (RAMPART-268) Client sending a Security Header in Request expects security header in response and errors out

[ https://issues.apache.org/jira/browse/RAMPART-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973751#action_12973751 ] Thilina Buddhika commented on RAMPART-268: -- Hi, I doubt whether this is a user e

[jira] Resolved: (RAMPART-268) Client sending a Security Header in Request expects security header in response and errors out

[ https://issues.apache.org/jira/browse/RAMPART-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-268. -- Resolution: Fixed Resolving the issue. > Client sending a Security Header in Request

[jira] Assigned: (RAMPART-268) Client sending a Security Header in Request expects security header in response and errors out

[ https://issues.apache.org/jira/browse/RAMPART-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned RAMPART-268: Assignee: S.Uthaiyashankar (was: Ruchith Udayanga Fernando) > Client sending a Se

[jira] Resolved: (AXIS2-4492) Parameter shift in REST

[ https://issues.apache.org/jira/browse/AXIS2-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4492. --- Resolution: Fixed > Parameter shift in REST > --- > > Key

[jira] Resolved: (RAMPART-116) Policy Sample 04 on application scope fails with "Error in key derivation"

[ https://issues.apache.org/jira/browse/RAMPART-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-116. -- Resolution: Fixed This issue is no longer valid. Sample 04 works correctly with appl

[jira] Commented: (AXIS2-4509) Provider Performance Improvement.

[ https://issues.apache.org/jira/browse/AXIS2-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973749#action_12973749 ] Srinath Perera commented on AXIS2-4509: --- what is the status of this? Can you give det

[jira] Resolved: (AXIS2-3945) Threading issue in AbstractHTTPSender

[ https://issues.apache.org/jira/browse/AXIS2-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva resolved AXIS2-3945. Resolution: Fixed Fixed by synchronization of the getHttpClient method > Threading

[jira] Assigned: (RAMPART-116) Policy Sample 04 on application scope fails with "Error in key derivation"

[ https://issues.apache.org/jira/browse/RAMPART-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned RAMPART-116: Assignee: S.Uthaiyashankar > Policy Sample 04 on application scope fails with "Err

  1   2   3   >