[jira] Commented: (AXIS2-2477) Unusual service name/epr is presented when a pojo annotation class is deployed

[ https://issues.apache.org/jira/browse/AXIS2-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986273#action_12986273 ] Isuru Eranga Suriarachchi commented on AXIS2-2477: -- Hi Ruwan, I think thi

Re: Axis2 1.6 release plan

May be we need to think about down-stream project release plans as well. It would be ideal to have Rampart and Sandesha2 also released with Axis2 1.6 Thanks, Samisa... On Tue, Jan 25, 2011 at 1:20 PM, Ruwan Linton wrote: > Thanks Andreas for volunteering for the Axiom release. > > I will have a

Re: Axis2 1.6 release plan

+1, any volunteers for those releases?? Ruwan On Tue, Jan 25, 2011 at 1:48 PM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > May be we need to think about down-stream project release plans as well. > > It would be ideal to have Rampart and Sandesha2 also released with Axis2 > 1.6 > >

[jira] Commented: (AXIS2-4362) If WSDL has multiple services, DeploymentEngine uses incorrect one

[ https://issues.apache.org/jira/browse/AXIS2-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986289#action_12986289 ] Pradeep Fernando commented on AXIS2-4362: - Hi, I tested this behaviour in the late

[jira] Updated: (AXIS2-4362) If WSDL has multiple services, DeploymentEngine uses incorrect one

[ https://issues.apache.org/jira/browse/AXIS2-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Fernando updated AXIS2-4362: Attachment: HelloTwo.aar HelloOne.aar HelloOne.aar is a normal scenario, wh

Re: Send response to client from inflow handler.

Hi, On Mon, Jan 24, 2011 at 11:32 PM, Alessio Luna wrote: > > Hi all, > i have the following systembase on axis2: > Client java axiom (no stub stuff) ->ServerSide InFlow Handler ->Server java > axiom > > My problem is: > From Handler i read the Header and check something. If check test result > f

[jira] Resolved: (AXIS2-4362) If WSDL has multiple services, DeploymentEngine uses incorrect one

[ https://issues.apache.org/jira/browse/AXIS2-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Linton resolved AXIS2-4362. - Resolution: Cannot Reproduce As per the comment from Pradeep > If WSDL has multiple services, De

Re: Axis2 1.6 release plan

I have configured Maven release plug in locally for Woden trunk and had a successful dry run in last December, Woden M9 release can be start any time. If Axis2 1.6 plan to go with Axiom 1.2.11 version it's better to use same Axiom version for Woden too. I will start Woden release just after the Axo

[jira] Commented: (AXIS2-4772) Generated classes can't compile

[ https://issues.apache.org/jira/browse/AXIS2-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986306#action_12986306 ] Pradeep Fernando commented on AXIS2-4772: - hi Martin, thank you for reporting this

Re: Axis2 1.6 release plan

Thanks Sagara, that helps a lot. Neethi doesn't seem to have much activity around it, and I assume that could be released without much issue as well, I will see what are the changes after the previous release and will try to see if we can go with the previous version of neethi, but not sure about

Re: Axis2 1.6 release plan

I will start on working Rampart 1.6 release. Thanks, Thilina Thilina Mahesh Buddhika http://blog.thilinamb.com On Tue, Jan 25, 2011 at 2:48 PM, Ruwan Linton wrote: > +1, any volunteers for those releases?? > > Ruwan > > > On Tue, Jan 25, 2011 at 1:48 PM, Samisa Abeysinghe < > samisa.abeysin...

Re: Axis2 1.6 release plan

Indeed, all should go together. Deepal > May be we need to think about down-stream project release plans as well. > > It would be ideal to have Rampart and Sandesha2 also released with > Axis2 1.6 > > Thanks, > Samisa... > > On Tue, Jan 25, 2011 at 1:20 PM, Ruwan Linton

[jira] Commented: (AXIS2-4881) Added invoke_stage1 and invoke_stage2 methods to AbstractHandler

[ https://issues.apache.org/jira/browse/AXIS2-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986384#action_12986384 ] Deepal Jayasinghe commented on AXIS2-4881: -- I would not consider this as a blocker

Re: .net and axis2/rampart

Hi, It seems the client cannot find the key with the value 'a7e24d986ef9fdef06efd76fb33825d502279e95'. Is it possible to specify the key name to something else? I think the client has given it a proper name. Thanks On 24 January 2011 14:11, Thilina Mahesh Buddhika wrote: > It looks like the cer

Re: Axis2 1.6 release plan

Yeah, but for the time being they are separate modules, so we need to do separate releases in sync this time. Ruwan On Tue, Jan 25, 2011 at 7:00 PM, Deepal jayasinghe wrote: > Indeed, all should go together. > > Deepal > > May be we need to think about down-stream project release plans as well.

Re: Axis2 1.6 release plan

Thanks Thilina, who is going to work on the Sandesha2 release? Ruwan On Tue, Jan 25, 2011 at 4:54 PM, Thilina Mahesh Buddhika < thilin...@gmail.com> wrote: > I will start on working Rampart 1.6 release. > > Thanks, > Thilina > > Thilina Mahesh Buddhika > http://blog.thilinamb.com > > > > On Tue,

[jira] Commented: (AXIS2-4881) Added invoke_stage1 and invoke_stage2 methods to AbstractHandler

[ https://issues.apache.org/jira/browse/AXIS2-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986452#action_12986452 ] Ruwan Linton commented on AXIS2-4881: - Deepal, this API is wired and this is a commonly

[jira] Commented: (AXIS2-4881) Added invoke_stage1 and invoke_stage2 methods to AbstractHandler

[ https://issues.apache.org/jira/browse/AXIS2-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986461#action_12986461 ] Glen Daniels commented on AXIS2-4881: - +1 to Ruwan and Andreas' -1's. :) In other word

Re: Axis2 1.6 release plan

I thought we agreed to basically making them be one release- with the mars being in the same dist even? Sanjiva. On Tue, Jan 25, 2011 at 1:48 PM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > May be we need to think about down-stream project release plans as well. > > It would be ide

Re: Axis2 1.6 release plan

Ruwan what about the JAX-WS TCK? It seems to me it would be better to release with that passed? I have no idea what that implies in terms of effort and time .. Sanjiva. On Tue, Jan 25, 2011 at 7:13 AM, Ruwan Linton wrote: > Folks, > > After a set of hackathons on Axis2 trunk it is sort of at a s

Re: Axis2 1.6 release plan

+1, for getting JAX-WS TCK (if we have enough man power). Deepal > Ruwan what about the JAX-WS TCK? It seems to me it would be better to > release with that passed? I have no idea what that implies in terms of > effort and time .. > > Sanjiva. > > On Tue, Jan 25, 2011 at 7:13 AM, Ruwan Linton

Re: .net and axis2/rampart

Hi all, A little more information. My client has said they do the following in .net to setup the client: --- proxyClient.ClientCredentials.ClientCertificate.SetCertificate(System.Security.Cryptography.X509Certificates.StoreLocation.CurrentUser, System.Security.Cryptography.X509Certif

[jira] Created: (AXIS2-4940) java.util.List is not known to this context

java.util.List is not known to this context --- Key: AXIS2-4940 URL: https://issues.apache.org/jira/browse/AXIS2-4940 Project: Axis2 Issue Type: Bug Components: adb, Addressing, codegen, jaxw

[jira] Updated: (AXIS2-4940) java.util.List is not known to this context

[ https://issues.apache.org/jira/browse/AXIS2-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Martins updated AXIS2-4940: -- Description: Calling a simple method which returns java.util.List causes the server to throw t

Axis2 on Websphere 7 class conflict

We are getting classloading conflicts when trying to deploy Axis2 1.5.3 on Websphere 7, Fixpack 13 that are preventing the addressing-1.5.3.mar from loading: [1/24/11 18:53:53:765 CST] 0030 ModuleDeploye E org.apache.axis2.deployment.ModuleDeployer deploy The addressing-1.5.3.mar module,

[jira] Updated: (AXIS2-4940) java.util.List is not known to this context

[ https://issues.apache.org/jira/browse/AXIS2-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Martins updated AXIS2-4940: -- Attachment: wstest.zip I attached a tiny file (wstest.zip) which is an eclipse maven project to

Re: Axis2 1.6 release plan

What we have agreed is to create a separate distro with all bundled together and release that inline with Axis2 core, as moving the rampart and sandesha modules into axis2 required a bit of SVN refactoring too. I think we should be able to create that distro. Just a matter of writing an assembly, b

Re: Axis2 1.6 release plan

I will evaluate this effort and get back to the list, to be frank I don't have a clear idea as of now on how much work this adds to the release and the time frame either. Ruwan On Tue, Jan 25, 2011 at 10:10 PM, Sanjiva Weerawarana wrote: > Ruwan what about the JAX-WS TCK? It seems to me it woul