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

[Isuru Eranga Suriarachchi (JIRA)]

[ 
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 this issue is still there. I tried to fix this by removing the port 
name attached to the service name. But then we need to change all EPR's used in 
test cases.

Thanks,
~Isuru

> Unusual service name/epr is presented when a pojo annotation class is 
> deployed 
> ---
>
> Key: AXIS2-2477
> URL: https://issues.apache.org/jira/browse/AXIS2-2477
> Project: Axis2
>  Issue Type: Bug
>  Components: jaxws
>Affects Versions: 1.2
> Environment: jdk15, tomcat 6.0.10
>Reporter: Charitha Kankanamge
>Assignee: Deepal Jayasinghe
> Fix For: 1.6
>
>
> I created a pojo with annotation and named it as 'HelloWorldService'. Then I 
> deployed it on tomcat 6.0.10 and accessed admin console to see the service.
> Following is the name of service shown in admin console.
> HelloWorldServiceService.HelloWorldServicePort
> EPR is given as 
> http://localhost:8080/axis2/services/HelloWorldServiceService.HelloWorldServicePort

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Axis2 1.6 release plan

[Samisa Abeysinghe]

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 look at Neethi and Wooden state.
>
> Thanks,
> Ruwan
>
>
> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
> andreas.veit...@gmail.com> wrote:
>
>> We need to figure out what releases we need from upstream projects.
>> Right now the trunk has the following snapshot dependencies:
>>
>>1.2.11-SNAPSHOT
>>3.0.0-SNAPSHOT
>>1.0-SNAPSHOT
>>
>> We definitely need a new Axiom release, but this is not a problem
>> because the code is in a releasable state. I can take care of this.
>>
>> The question is still open for Neethi and Woden.
>>
>> Andreas
>>
>> On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
>> wrote:
>> > Folks,
>> > After a set of hackathons on Axis2 trunk it is sort of at a stable sate
>> for
>> > the 1.6 release. I predict that if we start now we should be able to get
>> the
>> > first release candidate in the first week of february.
>> > Any volunteers to be the Release Manager for this release? and also any
>> > critical fixes to be included into the 1.6 release?
>> > Your thoughts are welcome.
>> > Thanks,
>> > Ruwan
>> >
>> > --
>> > Ruwan Linton
>> > Software Architect & Product Manager
>> > WSO2 Inc.; http://wso2.org
>> >
>> > Lean . Enterprise . Middleware
>> >
>> > phone: +1 408 754 7388 ext 51789
>> > email: ru...@wso2.com; cell: +94 77 341 3097
>> > blog: http://blog.ruwan.org
>> > linkedin: http://www.linkedin.com/in/ruwanlinton
>> > google: http://www.google.com/profiles/ruwan.linton
>> > tweet: http://twitter.com/ruwanlinton
>> >
>>
>> -
>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
>> For additional commands, e-mail: java-dev-h...@axis.apache.org
>>
>>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>

Re: Axis2 1.6 release plan

[Ruwan Linton]

+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
>
> 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 look at Neethi and Wooden state.
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
>> andreas.veit...@gmail.com> wrote:
>>
>>> We need to figure out what releases we need from upstream projects.
>>> Right now the trunk has the following snapshot dependencies:
>>>
>>>1.2.11-SNAPSHOT
>>>3.0.0-SNAPSHOT
>>>1.0-SNAPSHOT
>>>
>>> We definitely need a new Axiom release, but this is not a problem
>>> because the code is in a releasable state. I can take care of this.
>>>
>>> The question is still open for Neethi and Woden.
>>>
>>> Andreas
>>>
>>> On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
>>> wrote:
>>> > Folks,
>>> > After a set of hackathons on Axis2 trunk it is sort of at a stable sate
>>> for
>>> > the 1.6 release. I predict that if we start now we should be able to
>>> get the
>>> > first release candidate in the first week of february.
>>> > Any volunteers to be the Release Manager for this release? and also any
>>> > critical fixes to be included into the 1.6 release?
>>> > Your thoughts are welcome.
>>> > Thanks,
>>> > Ruwan
>>> >
>>> > --
>>> > Ruwan Linton
>>> > Software Architect & Product Manager
>>> > WSO2 Inc.; http://wso2.org
>>> >
>>> > Lean . Enterprise . Middleware
>>> >
>>> > phone: +1 408 754 7388 ext 51789
>>> > email: ru...@wso2.com; cell: +94 77 341 3097
>>> > blog: http://blog.ruwan.org
>>> > linkedin: http://www.linkedin.com/in/ruwanlinton
>>> > google: http://www.google.com/profiles/ruwan.linton
>>> > tweet: http://twitter.com/ruwanlinton
>>> >
>>>
>>> -
>>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
>>> For additional commands, e-mail: java-dev-h...@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>


-- 
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
Software Architect & Product Manager, WSO2 Inc.; http://wso2.org

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

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

[Pradeep Fernando (JIRA)]

[ 
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 latest axis2 trunk, and for me it worked without 
a problem. I even used the services.xml parameter  and found 
out that the service deployment works fine. Hence we should close this issue. I 
have attached the services archives i have used.

P.S : it would be great , if you can provide the artifacts when you are 
reporting an issue, since mere re-poroducing takes some time.



> If WSDL has multiple services, DeploymentEngine uses incorrect one
> --
>
> Key: AXIS2-4362
> URL: https://issues.apache.org/jira/browse/AXIS2-4362
> Project: Axis2
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.4
>Reporter: Ben Reif
>
> We have a WSDL file that defines multiple services. Each service is deployed 
> within a War as a seperate *.aar file, but they share the same WSDL file. 
> In DeploymentEngine.populateService(), it calls:
>  
> WSDL11ToAxisServiceBuilder wsdl2AxisServiceBuilder = new 
> WSDL11ToAxisServiceBuilder(wsdlStream, null, null);.
> It passes in null for the service QName, even though it has the value of 
> serviceName and it could get the target namespace from the services.xml or 
> the WSDL definition. If you pass in null, this causes the 
> WSDL11ToAxisServiceBuilder.findService() to just pick the first 
>  that has a Port. If you have multiple services defined in your 
> WSDL file, this results in the incorrect AxisService objects being put into 
> the AxisConfiguration since it's always just using the information from the 
> first one that it finds with a port.
> The  DeploymentEngine should determine the correct service QName in this case 
> and pass that into the WSDL11ToAxisServiceBuilder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

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

[Pradeep Fernando (JIRA)]

 [ 
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, where there are is only one service 
(HelloOne service)
HelloTwo.aar has a composite WSDL with HelloOne service definition as the first 
service element in the wsdl

> If WSDL has multiple services, DeploymentEngine uses incorrect one
> --
>
> Key: AXIS2-4362
> URL: https://issues.apache.org/jira/browse/AXIS2-4362
> Project: Axis2
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.4
>Reporter: Ben Reif
> Attachments: HelloOne.aar, HelloTwo.aar
>
>
> We have a WSDL file that defines multiple services. Each service is deployed 
> within a War as a seperate *.aar file, but they share the same WSDL file. 
> In DeploymentEngine.populateService(), it calls:
>  
> WSDL11ToAxisServiceBuilder wsdl2AxisServiceBuilder = new 
> WSDL11ToAxisServiceBuilder(wsdlStream, null, null);.
> It passes in null for the service QName, even though it has the value of 
> serviceName and it could get the target namespace from the services.xml or 
> the WSDL definition. If you pass in null, this causes the 
> WSDL11ToAxisServiceBuilder.findService() to just pick the first 
>  that has a Port. If you have multiple services defined in your 
> WSDL file, this results in the incorrect AxisService objects being put into 
> the AxisConfiguration since it's always just using the information from the 
> first one that it finds with a port.
> The  DeploymentEngine should determine the correct service QName in this case 
> and pass that into the WSDL11ToAxisServiceBuilder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Send response to client from inflow handler.

[Pradeep Fernando]

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
> false i wish to not call server java at all so i do
> return InvocationResponse.ABORT; This throw and exception like incoming
> message is null and it's ok.
> But the client doesn't recive nothing at all but:
> HTTP/1.1 202 Accepted
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Tue, 18 Jan 2011 22:18:33 GMT
>
> 0
>

This is the expected behavior if you abort in between a handler chain.
What you can do is create a AxisFault and throw if your test is
failed.

Then the message will go through the fault chain and you will be able
to return a custom fault message. The AxisFault is caught at
AxisServlet.java : 184 (in servlet transport) .

HTH,
--Pradeep.

> Ok i want to create soap fault message (and i know how to do) but i don't
> know how to send this message back to client!
>
> Thx in advice for help.
>
>
>



-- 
Pradeep Fernando.
http://pradeepfernando.blogspot.com/

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

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

[Ruwan Linton (JIRA)]

 [ 
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, DeploymentEngine uses incorrect one
> --
>
> Key: AXIS2-4362
> URL: https://issues.apache.org/jira/browse/AXIS2-4362
> Project: Axis2
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.4
>Reporter: Ben Reif
> Attachments: HelloOne.aar, HelloTwo.aar
>
>
> We have a WSDL file that defines multiple services. Each service is deployed 
> within a War as a seperate *.aar file, but they share the same WSDL file. 
> In DeploymentEngine.populateService(), it calls:
>  
> WSDL11ToAxisServiceBuilder wsdl2AxisServiceBuilder = new 
> WSDL11ToAxisServiceBuilder(wsdlStream, null, null);.
> It passes in null for the service QName, even though it has the value of 
> serviceName and it could get the target namespace from the services.xml or 
> the WSDL definition. If you pass in null, this causes the 
> WSDL11ToAxisServiceBuilder.findService() to just pick the first 
>  that has a Port. If you have multiple services defined in your 
> WSDL file, this results in the incorrect AxisService objects being put into 
> the AxisConfiguration since it's always just using the information from the 
> first one that it finds with a port.
> The  DeploymentEngine should determine the correct service QName in this case 
> and pass that into the WSDL11ToAxisServiceBuilder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Axis2 1.6 release plan

[Sagara Gunathunga]

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 Axom
release.

Thanks !


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...@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
>>
>> 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 look at Neethi and Wooden state.
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
>>> andreas.veit...@gmail.com> wrote:
>>>
 We need to figure out what releases we need from upstream projects.
 Right now the trunk has the following snapshot dependencies:

1.2.11-SNAPSHOT
3.0.0-SNAPSHOT
1.0-SNAPSHOT

 We definitely need a new Axiom release, but this is not a problem
 because the code is in a releasable state. I can take care of this.

 The question is still open for Neethi and Woden.

 Andreas

 On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
 wrote:
 > Folks,
 > After a set of hackathons on Axis2 trunk it is sort of at a stable
 sate for
 > the 1.6 release. I predict that if we start now we should be able to
 get the
 > first release candidate in the first week of february.
 > Any volunteers to be the Release Manager for this release? and also
 any
 > critical fixes to be included into the 1.6 release?
 > Your thoughts are welcome.
 > Thanks,
 > Ruwan
 >
 > --
 > Ruwan Linton
 > Software Architect & Product Manager
 > WSO2 Inc.; http://wso2.org
 >
 > Lean . Enterprise . Middleware
 >
 > phone: +1 408 754 7388 ext 51789
 > email: ru...@wso2.com; cell: +94 77 341 3097
 > blog: http://blog.ruwan.org
 > linkedin: http://www.linkedin.com/in/ruwanlinton
 > google: http://www.google.com/profiles/ruwan.linton
 > tweet: http://twitter.com/ruwanlinton
 >

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


>>>
>>>
>>> --
>>> Ruwan Linton
>>> Software Architect & Product Manager
>>> WSO2 Inc.; http://wso2.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> phone: +1 408 754 7388 ext 51789
>>> email: ru...@wso2.com; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>> google: http://www.google.com/profiles/ruwan.linton
>>> tweet: http://twitter.com/ruwanlinton
>>>
>>
>>
>
>
> --
> Ruwan Linton
> Member, Apache Software Foundation; http://www.apache.org
>
> Software Architect & Product Manager, WSO2 Inc.; http://wso2.org
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>
>


-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

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

[Pradeep Fernando (JIRA)]

[ 
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 issue. But with the given details we cannot 
reproduce your error. In order to reproduce this scenario we need the wsdl you 
used for code generation. Otherwise we cant give a fix for your issue.

thanks.



> Generated classes can't compile
> ---
>
> Key: AXIS2-4772
> URL: https://issues.apache.org/jira/browse/AXIS2-4772
> Project: Axis2
>  Issue Type: Bug
>  Components: adb
>Affects Versions: 1.4.1
> Environment: Windows XP, Java 1.5_22
>Reporter: Martin Lesner
>
> Some classes get generated with the wrong syntax:
> c:\dev\projects_doc\Stuffplan\wsdls\Schemas\build\client\src\uk\gov\govtalk\www\people\addressandpersonaldetails\InternationalPostCodeType.java:57:
>  ')' expected
> >>   [javac] if 
> >> (org.apache.axis2.databinding.utils.ConverterUtil.convertToString(param).matches("[A-Za-z0-9\\s~!"@#$%&'\\(\\)\\*\\+,\\-\\./:;<=>\\?\\[\\]_\\{\\
> >>  \\^£€]*")) {
> >>   [javac]  
> >>
> >>
> >>   ^
> It generates " inside the string so class can't be compiled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Axis2 1.6 release plan

[Ruwan Linton]

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 the relation to axiom, in
which case just a matter of cutting a release from the trunk.

So it seems Axiom is taking the lead, Andreas, can you propose a time line
for this?

Thanks,
Ruwan

On Tue, Jan 25, 2011 at 3:29 PM, Sagara Gunathunga <
sagara.gunathu...@gmail.com> wrote:

>
> 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 Axom
> release.
>
> Thanks !
>
>
>
> 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...@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
>>>
>>> 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 look at Neethi and Wooden state.

 Thanks,
 Ruwan


 On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
 andreas.veit...@gmail.com> wrote:

> We need to figure out what releases we need from upstream projects.
> Right now the trunk has the following snapshot dependencies:
>
>1.2.11-SNAPSHOT
>3.0.0-SNAPSHOT
>1.0-SNAPSHOT
>
> We definitely need a new Axiom release, but this is not a problem
> because the code is in a releasable state. I can take care of this.
>
> The question is still open for Neethi and Woden.
>
> Andreas
>
> On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
> wrote:
> > Folks,
> > After a set of hackathons on Axis2 trunk it is sort of at a stable
> sate for
> > the 1.6 release. I predict that if we start now we should be able to
> get the
> > first release candidate in the first week of february.
> > Any volunteers to be the Release Manager for this release? and also
> any
> > critical fixes to be included into the 1.6 release?
> > Your thoughts are welcome.
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Software Architect & Product Manager
> > WSO2 Inc.; http://wso2.org
> >
> > Lean . Enterprise . Middleware
> >
> > phone: +1 408 754 7388 ext 51789
> > email: ru...@wso2.com; cell: +94 77 341 3097
> > blog: http://blog.ruwan.org
> > linkedin: http://www.linkedin.com/in/ruwanlinton
> > google: http://www.google.com/profiles/ruwan.linton
> > tweet: http://twitter.com/ruwanlinton
> >
>
> -
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>
>


 --
 Ruwan Linton
 Software Architect & Product Manager
 WSO2 Inc.; http://wso2.org

 Lean . Enterprise . Middleware

 phone: +1 408 754 7388 ext 51789
 email: ru...@wso2.com; cell: +94 77 341 3097
 blog: http://blog.ruwan.org
 linkedin: http://www.linkedin.com/in/ruwanlinton
 google: http://www.google.com/profiles/ruwan.linton
 tweet: http://twitter.com/ruwanlinton

>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Member, Apache Software Foundation; http://www.apache.org
>>
>> Software Architect & Product Manager, WSO2 Inc.; http://wso2.org
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>



-- 
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
Software Architect & Product Manager, WSO2 Inc.; http://wso2.org

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: Axis2 1.6 release plan

[Thilina Mahesh Buddhika]

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...@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
>>
>> 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 look at Neethi and Wooden state.
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
>>> andreas.veit...@gmail.com> wrote:
>>>
 We need to figure out what releases we need from upstream projects.
 Right now the trunk has the following snapshot dependencies:

1.2.11-SNAPSHOT
3.0.0-SNAPSHOT
1.0-SNAPSHOT

 We definitely need a new Axiom release, but this is not a problem
 because the code is in a releasable state. I can take care of this.

 The question is still open for Neethi and Woden.

 Andreas

 On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
 wrote:
 > Folks,
 > After a set of hackathons on Axis2 trunk it is sort of at a stable
 sate for
 > the 1.6 release. I predict that if we start now we should be able to
 get the
 > first release candidate in the first week of february.
 > Any volunteers to be the Release Manager for this release? and also
 any
 > critical fixes to be included into the 1.6 release?
 > Your thoughts are welcome.
 > Thanks,
 > Ruwan
 >
 > --
 > Ruwan Linton
 > Software Architect & Product Manager
 > WSO2 Inc.; http://wso2.org
 >
 > Lean . Enterprise . Middleware
 >
 > phone: +1 408 754 7388 ext 51789
 > email: ru...@wso2.com; cell: +94 77 341 3097
 > blog: http://blog.ruwan.org
 > linkedin: http://www.linkedin.com/in/ruwanlinton
 > google: http://www.google.com/profiles/ruwan.linton
 > tweet: http://twitter.com/ruwanlinton
 >

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


>>>
>>>
>>> --
>>> Ruwan Linton
>>> Software Architect & Product Manager
>>> WSO2 Inc.; http://wso2.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> phone: +1 408 754 7388 ext 51789
>>> email: ru...@wso2.com; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>> google: http://www.google.com/profiles/ruwan.linton
>>> tweet: http://twitter.com/ruwanlinton
>>>
>>
>>
>
>
> --
> Ruwan Linton
> Member, Apache Software Foundation; http://www.apache.org
>
> Software Architect & Product Manager, WSO2 Inc.; http://wso2.org
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>
>

Re: Axis2 1.6 release plan

[Deepal jayasinghe]

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  > wrote:
>
> Thanks Andreas for volunteering for the Axiom release.
>
> I will have a look at Neethi and Wooden state.
>
> Thanks,
> Ruwan
>
>
> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen
> mailto:andreas.veit...@gmail.com>> wrote:
>
> We need to figure out what releases we need from upstream
> projects.
> Right now the trunk has the following snapshot dependencies:
>
>1.2.11-SNAPSHOT
>3.0.0-SNAPSHOT
>1.0-SNAPSHOT
>
> We definitely need a new Axiom release, but this is not a problem
> because the code is in a releasable state. I can take care of
> this.
>
> The question is still open for Neethi and Woden.
>
> Andreas
>
> On Tue, Jan 25, 2011 at 02:43, Ruwan Linton
> mailto:ruwan.lin...@gmail.com>> wrote:
> > Folks,
> > After a set of hackathons on Axis2 trunk it is sort of at a
> stable sate for
> > the 1.6 release. I predict that if we start now we should be
> able to get the
> > first release candidate in the first week of february.
> > Any volunteers to be the Release Manager for this release?
> and also any
> > critical fixes to be included into the 1.6 release?
> > Your thoughts are welcome.
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Software Architect & Product Manager
> > WSO2 Inc.; http://wso2.org
> >
> > Lean . Enterprise . Middleware
> >
> > phone: +1 408 754 7388 ext 51789
> > email: ru...@wso2.com ; cell: +94 77
> 341 3097
> > blog: http://blog.ruwan.org
> > linkedin: http://www.linkedin.com/in/ruwanlinton
> > google: http://www.google.com/profiles/ruwan.linton
> > tweet: http://twitter.com/ruwanlinton
> >
>
> -
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> 
> For additional commands, e-mail: java-dev-h...@axis.apache.org
> 
>
>
>
>
> -- 
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com ; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>
>

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

[Deepal Jayasinghe (JIRA)]

[ 
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.  In addition, it would be great if we 
can find a good usecase for this feature, otherwise we do not need to fix this 
for 1.6 release. 

> Added invoke_stage1 and invoke_stage2 methods to AbstractHandler
> 
>
> Key: AXIS2-4881
> URL: https://issues.apache.org/jira/browse/AXIS2-4881
> Project: Axis2
>  Issue Type: Bug
>Reporter: Rich Scheuerle
>Priority: Blocker
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The AbstractHandler class exposes an invoke() method that Handlers override 
> to provide the specific invoke code.
> Problem:
> Many Handlers actually have 2 stages of logic.  The first stage simply does 
> some quick processing to determine if the handler should be called.  The 
> second stage does the actual work.
> Because there is only one invoke method, these separate stages of processing 
> get lumped together.
> Solution:
> Provide an alternative (optional) invoke semantic.
> A Handler can choose to override the new invoke_stage1 and invoke_stage2 
> methods.
> All current Handlers will continue to work.  The existing invoke() method is 
> retained.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: .net and axis2/rampart

[Abid K.]

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 certificate used by client for signing/encrypting the
> message is not available in the key store of the service''s end.
> Also check the key store configurations of the service's end whether they
> are referring to the correct key store, etc.
> Thanks,
> Thilina
> Thilina Mahesh Buddhika
> http://blog.thilinamb.com
>
>
> On Mon, Jan 24, 2011 at 4:46 PM, Abid K.  wrote:
>>
>> Sorry for not replying sooner. The client receives the following error...
>>
>> ---
>> Cannot find the X.509 certificate using the following search criteria:
>> StoreName 'My', StoreLocation 'LocalMachine', FindType
>> 'FindByThumbprint', FindValue
>> 'a7e24d986ef9fdef06efd76fb33825d502279e95'.. --->
>> System.InvalidOperationException: Cannot find the X.509 certificate
>> using the following search criteria: StoreName 'My', StoreLocation
>> 'LocalMachine', FindType 'FindByThumbprint', FindValue
>> 'a7e24d986ef9fdef06efd76fb33825d502279e95'.
>> ---
>>
>> The value 'a7e24d986ef9fdef06efd76fb33825d502279e95' is the SHA1 value
>> for the certificate that seems to be used for signing the message on
>> the client side and I assume this is then being passed to the service
>> for verification.
>>
>> It seems the key cannot be found on the service side, but do you think
>> I need to change something on the client side?
>>
>> Thanks
>>
>> On 20 January 2011 04:14, Thilina Mahesh Buddhika 
>> wrote:
>> > Hi,
>> >
>> > It seems like the service has thrown an error when trying to process the
>> > secured request. The message being logged at RampartReceiver has the
>> > fault
>> > message 'An error occurred when verifying security for the
>> > message'.
>> >
>> > If you can check the logs at service end, it would provide the actual
>> > reason
>> > for the error.
>> >
>> > Thanks,
>> > Thilina
>> >
>> > Thilina Mahesh Buddhika
>> > http://blog.thilinamb.com
>> >
>> >
>> > On Wed, Jan 19, 2011 at 10:12 PM, Abid K.  wrote:
>> >>
>> >> Hi, I have created a client app using Axis2/Rampart and I'm having
>> >> difficulties getting it to work with .net/WCF(I think).
>> >>
>> >> My axis2.xml config contains (Also tried policy with same results):
>> >> ...
>> >>   
>> >>      
>> >>        Signature
>> >>        user
>> >>        PWCBHandler
>> >>        client.properties
>> >>        DirectReference
>> >>      
>> >>    
>> >> ... etc.
>> >>
>> >> client.properties:
>> >>
>> >>
>> >> org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
>> >> org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
>> >> org.apache.ws.security.crypto.merlin.file=key.pfx
>> >> org.apache.ws.security.crypto.merlin.keystore.password=password
>> >>
>> >>
>> >> I get the follow error:
>> >> org.apache.axis2.AxisFault: An error occurred when verifying security
>> >> for the message.
>> >>        at
>> >>
>> >> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
>> >>        at
>> >>
>> >> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
>> >>        at
>> >>
>> >> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
>> >>
>> >> Also get the following in the log:
>> >> 2011-01-19 16:02:38 [main] [DEBUG] Request body sent
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "HTTP/1.1 500 Internal Server
>> >> Error[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "HTTP/1.1 500 Internal Server
>> >> Error[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Date: Wed, 19 Jan 2011 16:02:39
>> >> GMT[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Server:
>> >> Microsoft-IIS/6.0[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "X-Powered-By: ASP.NET[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "X-AspNet-Version:
>> >> 2.0.50727[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Connection: close[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Cache-Control: private[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Content-Type:
>> >> application/soap+xml; charset=utf-8[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Content-Length: 643[\r][\n]"
>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "[\r][\n]"
>> >> ...
>> >> 2011-01-19 16:02:38 [main] [DEBUG] ***
>> >> RampartReceiver received
>> >> > >> xmlns:s="http://www.w3.org/2003/05/soap-envelope";
>> >> xmlns:a="http://www.w3.org/2005/08/addressing";>> >>
>> >>
>> >> s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/faulturn:uuid:C18F4C3E6ACADFD1F31295452955592s:Sender> >>
>> >>
>> >> xmlns:a="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>a:InvalidSecurity> >> xml:lang="en-GB">An erro

Re: Axis2 1.6 release plan

[Ruwan Linton]

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.
>
> 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 look at Neethi and Wooden state.
>>
>>  Thanks,
>> Ruwan
>>
>>
>> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
>> andreas.veit...@gmail.com> wrote:
>>
>>> We need to figure out what releases we need from upstream projects.
>>> Right now the trunk has the following snapshot dependencies:
>>>
>>>1.2.11-SNAPSHOT
>>>3.0.0-SNAPSHOT
>>>1.0-SNAPSHOT
>>>
>>> We definitely need a new Axiom release, but this is not a problem
>>> because the code is in a releasable state. I can take care of this.
>>>
>>> The question is still open for Neethi and Woden.
>>>
>>> Andreas
>>>
>>> On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
>>> wrote:
>>> > Folks,
>>> > After a set of hackathons on Axis2 trunk it is sort of at a stable sate
>>> for
>>> > the 1.6 release. I predict that if we start now we should be able to
>>> get the
>>> > first release candidate in the first week of february.
>>> > Any volunteers to be the Release Manager for this release? and also any
>>> > critical fixes to be included into the 1.6 release?
>>> > Your thoughts are welcome.
>>> > Thanks,
>>> > Ruwan
>>> >
>>> > --
>>> > Ruwan Linton
>>> > Software Architect & Product Manager
>>> > WSO2 Inc.; http://wso2.org
>>> >
>>> > Lean . Enterprise . Middleware
>>> >
>>> > phone: +1 408 754 7388 ext 51789
>>> > email: ru...@wso2.com; cell: +94 77 341 3097
>>> > blog: http://blog.ruwan.org
>>> > linkedin: http://www.linkedin.com/in/ruwanlinton
>>> > google: http://www.google.com/profiles/ruwan.linton
>>> > tweet: http://twitter.com/ruwanlinton
>>> >
>>>
>>>  -
>>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
>>> For additional commands, e-mail: java-dev-h...@axis.apache.org
>>>
>>>
>>
>>
>>  --
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>
>


-- 
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
Software Architect & Product Manager, WSO2 Inc.; http://wso2.org

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: Axis2 1.6 release plan

[Ruwan Linton]

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, 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...@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
>>>
>>> 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 look at Neethi and Wooden state.

 Thanks,
 Ruwan


 On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
 andreas.veit...@gmail.com> wrote:

> We need to figure out what releases we need from upstream projects.
> Right now the trunk has the following snapshot dependencies:
>
>1.2.11-SNAPSHOT
>3.0.0-SNAPSHOT
>1.0-SNAPSHOT
>
> We definitely need a new Axiom release, but this is not a problem
> because the code is in a releasable state. I can take care of this.
>
> The question is still open for Neethi and Woden.
>
> Andreas
>
> On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
> wrote:
> > Folks,
> > After a set of hackathons on Axis2 trunk it is sort of at a stable
> sate for
> > the 1.6 release. I predict that if we start now we should be able to
> get the
> > first release candidate in the first week of february.
> > Any volunteers to be the Release Manager for this release? and also
> any
> > critical fixes to be included into the 1.6 release?
> > Your thoughts are welcome.
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Software Architect & Product Manager
> > WSO2 Inc.; http://wso2.org
> >
> > Lean . Enterprise . Middleware
> >
> > phone: +1 408 754 7388 ext 51789
> > email: ru...@wso2.com; cell: +94 77 341 3097
> > blog: http://blog.ruwan.org
> > linkedin: http://www.linkedin.com/in/ruwanlinton
> > google: http://www.google.com/profiles/ruwan.linton
> > tweet: http://twitter.com/ruwanlinton
> >
>
> -
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>
>


 --
 Ruwan Linton
 Software Architect & Product Manager
 WSO2 Inc.; http://wso2.org

 Lean . Enterprise . Middleware

 phone: +1 408 754 7388 ext 51789
 email: ru...@wso2.com; cell: +94 77 341 3097
 blog: http://blog.ruwan.org
 linkedin: http://www.linkedin.com/in/ruwanlinton
 google: http://www.google.com/profiles/ruwan.linton
 tweet: http://twitter.com/ruwanlinton

>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Member, Apache Software Foundation; http://www.apache.org
>>
>> Software Architect & Product Manager, WSO2 Inc.; http://wso2.org
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>>
>


-- 
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
Software Architect & Product Manager, WSO2 Inc.; http://wso2.org

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

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

[Ruwan Linton (JIRA)]

[ 
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 used extension point in axis2, 
any module will get affected, if we do not properly do the API, so we need to 
fix the API before the 1.6 without that fix we cannot do the 1.6 release, so it 
is a blocker.

> Added invoke_stage1 and invoke_stage2 methods to AbstractHandler
> 
>
> Key: AXIS2-4881
> URL: https://issues.apache.org/jira/browse/AXIS2-4881
> Project: Axis2
>  Issue Type: Bug
>Reporter: Rich Scheuerle
>Priority: Blocker
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The AbstractHandler class exposes an invoke() method that Handlers override 
> to provide the specific invoke code.
> Problem:
> Many Handlers actually have 2 stages of logic.  The first stage simply does 
> some quick processing to determine if the handler should be called.  The 
> second stage does the actual work.
> Because there is only one invoke method, these separate stages of processing 
> get lumped together.
> Solution:
> Provide an alternative (optional) invoke semantic.
> A Handler can choose to override the new invoke_stage1 and invoke_stage2 
> methods.
> All current Handlers will continue to work.  The existing invoke() method is 
> retained.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

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

[Glen Daniels (JIRA)]

[ 
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 words, I don't think this API 
should be part of a public Axis2 release unless there is real consensus that it 
is needed.

> Added invoke_stage1 and invoke_stage2 methods to AbstractHandler
> 
>
> Key: AXIS2-4881
> URL: https://issues.apache.org/jira/browse/AXIS2-4881
> Project: Axis2
>  Issue Type: Bug
>Reporter: Rich Scheuerle
>Priority: Blocker
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The AbstractHandler class exposes an invoke() method that Handlers override 
> to provide the specific invoke code.
> Problem:
> Many Handlers actually have 2 stages of logic.  The first stage simply does 
> some quick processing to determine if the handler should be called.  The 
> second stage does the actual work.
> Because there is only one invoke method, these separate stages of processing 
> get lumped together.
> Solution:
> Provide an alternative (optional) invoke semantic.
> A Handler can choose to override the new invoke_stage1 and invoke_stage2 
> methods.
> All current Handlers will continue to work.  The existing invoke() method is 
> retained.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Axis2 1.6 release plan

[Sanjiva Weerawarana]

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 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 look at Neethi and Wooden state.
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
>> andreas.veit...@gmail.com> wrote:
>>
>>> We need to figure out what releases we need from upstream projects.
>>> Right now the trunk has the following snapshot dependencies:
>>>
>>>1.2.11-SNAPSHOT
>>>3.0.0-SNAPSHOT
>>>1.0-SNAPSHOT
>>>
>>> We definitely need a new Axiom release, but this is not a problem
>>> because the code is in a releasable state. I can take care of this.
>>>
>>> The question is still open for Neethi and Woden.
>>>
>>> Andreas
>>>
>>> On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
>>> wrote:
>>> > Folks,
>>> > After a set of hackathons on Axis2 trunk it is sort of at a stable sate
>>> for
>>> > the 1.6 release. I predict that if we start now we should be able to
>>> get the
>>> > first release candidate in the first week of february.
>>> > Any volunteers to be the Release Manager for this release? and also any
>>> > critical fixes to be included into the 1.6 release?
>>> > Your thoughts are welcome.
>>> > Thanks,
>>> > Ruwan
>>> >
>>> > --
>>> > Ruwan Linton
>>> > Software Architect & Product Manager
>>> > WSO2 Inc.; http://wso2.org
>>> >
>>> > Lean . Enterprise . Middleware
>>> >
>>> > phone: +1 408 754 7388 ext 51789
>>> > email: ru...@wso2.com; cell: +94 77 341 3097
>>> > blog: http://blog.ruwan.org
>>> > linkedin: http://www.linkedin.com/in/ruwanlinton
>>> > google: http://www.google.com/profiles/ruwan.linton
>>> > tweet: http://twitter.com/ruwanlinton
>>> >
>>>
>>> -
>>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
>>> For additional commands, e-mail: java-dev-h...@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: Axis2 1.6 release plan

[Sanjiva Weerawarana]

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 stable sate for
> the 1.6 release. I predict that if we start now we should be able to get the
> first release candidate in the first week of february.
>
> Any volunteers to be the Release Manager for this release? and also any
> critical fixes to be included into the 1.6 release?
>
> Your thoughts are welcome.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>



-- 
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: Axis2 1.6 release plan

[Deepal jayasinghe]

+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  > wrote:
>
> Folks,
>
> After a set of hackathons on Axis2 trunk it is sort of at a stable
> sate for the 1.6 release. I predict that if we start now we should
> be able to get the first release candidate in the first week of
> february.
>
> Any volunteers to be the Release Manager for this release? and
> also any critical fixes to be included into the 1.6 release?
>
> Your thoughts are welcome.
>
> Thanks,
> Ruwan
>
> -- 
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com ; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>
>
>
>
> -- 
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2; http://wso2.com/
> Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Member; Sahana Software Foundation; http://www.sahanafoundation.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>

Re: .net and axis2/rampart

[Abid K.]

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.X509Certificates.StoreName.My,


System.Security.Cryptography.X509Certificates.X509FindType.FindBySubjectName,

"John Doe");
---

Does anyone know how I can mimic this in Rampart configuration? or how
I can change the request to contain the John Doe subject name?

Thanks

On 25 January 2011 14:37, Abid K.  wrote:
> 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 certificate used by client for signing/encrypting the
>> message is not available in the key store of the service''s end.
>> Also check the key store configurations of the service's end whether they
>> are referring to the correct key store, etc.
>> Thanks,
>> Thilina
>> Thilina Mahesh Buddhika
>> http://blog.thilinamb.com
>>
>>
>> On Mon, Jan 24, 2011 at 4:46 PM, Abid K.  wrote:
>>>
>>> Sorry for not replying sooner. The client receives the following error...
>>>
>>> ---
>>> Cannot find the X.509 certificate using the following search criteria:
>>> StoreName 'My', StoreLocation 'LocalMachine', FindType
>>> 'FindByThumbprint', FindValue
>>> 'a7e24d986ef9fdef06efd76fb33825d502279e95'.. --->
>>> System.InvalidOperationException: Cannot find the X.509 certificate
>>> using the following search criteria: StoreName 'My', StoreLocation
>>> 'LocalMachine', FindType 'FindByThumbprint', FindValue
>>> 'a7e24d986ef9fdef06efd76fb33825d502279e95'.
>>> ---
>>>
>>> The value 'a7e24d986ef9fdef06efd76fb33825d502279e95' is the SHA1 value
>>> for the certificate that seems to be used for signing the message on
>>> the client side and I assume this is then being passed to the service
>>> for verification.
>>>
>>> It seems the key cannot be found on the service side, but do you think
>>> I need to change something on the client side?
>>>
>>> Thanks
>>>
>>> On 20 January 2011 04:14, Thilina Mahesh Buddhika 
>>> wrote:
>>> > Hi,
>>> >
>>> > It seems like the service has thrown an error when trying to process the
>>> > secured request. The message being logged at RampartReceiver has the
>>> > fault
>>> > message 'An error occurred when verifying security for the
>>> > message'.
>>> >
>>> > If you can check the logs at service end, it would provide the actual
>>> > reason
>>> > for the error.
>>> >
>>> > Thanks,
>>> > Thilina
>>> >
>>> > Thilina Mahesh Buddhika
>>> > http://blog.thilinamb.com
>>> >
>>> >
>>> > On Wed, Jan 19, 2011 at 10:12 PM, Abid K.  wrote:
>>> >>
>>> >> Hi, I have created a client app using Axis2/Rampart and I'm having
>>> >> difficulties getting it to work with .net/WCF(I think).
>>> >>
>>> >> My axis2.xml config contains (Also tried policy with same results):
>>> >> ...
>>> >>   
>>> >>      
>>> >>        Signature
>>> >>        user
>>> >>        PWCBHandler
>>> >>        client.properties
>>> >>        DirectReference
>>> >>      
>>> >>    
>>> >> ... etc.
>>> >>
>>> >> client.properties:
>>> >>
>>> >>
>>> >> org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
>>> >> org.apache.ws.security.crypto.merlin.keystore.type=pkcs12
>>> >> org.apache.ws.security.crypto.merlin.file=key.pfx
>>> >> org.apache.ws.security.crypto.merlin.keystore.password=password
>>> >>
>>> >>
>>> >> I get the follow error:
>>> >> org.apache.axis2.AxisFault: An error occurred when verifying security
>>> >> for the message.
>>> >>        at
>>> >>
>>> >> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
>>> >>        at
>>> >>
>>> >> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
>>> >>        at
>>> >>
>>> >> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
>>> >>
>>> >> Also get the following in the log:
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] Request body sent
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "HTTP/1.1 500 Internal Server
>>> >> Error[\r][\n]"
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "HTTP/1.1 500 Internal Server
>>> >> Error[\r][\n]"
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Date: Wed, 19 Jan 2011 16:02:39
>>> >> GMT[\r][\n]"
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Server:
>>> >> Microsoft-IIS/6.0[\r][\n]"
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "X-Powered-By: ASP.NET[\r][\n]"
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "X-AspNet-Version:
>>> >> 2.0.50727[\r][\n]"
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Connection: close[\r][\n]"
>>> >> 2011-01-19 16:02:38 [main] [DEBUG] << "Cache-Control: private[\r][\n]"
>>

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

[Carlos Martins (JIRA)]

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, jaxws, kernel
Affects Versions: 1.5.4
 Environment: IBM AIX; Java-1.6; Tomcat 6; Axis2 1.5.4
Reporter: Carlos Martins


Calling a simple method which returns java.util.List causes the server 
to throw the exception
javax.xml.bind.JAXBException: java.util.List is not known to this context.
I followed the issue [AXIS2-3736] and in fact created a small maven application 
with a simple webservice and axis2 1.5.4

package com.audaxys.lease.model.generic;

import java.util.ArrayList;
import java.util.List;

import javax.jws.WebResult;
import javax.jws.WebService;
import javax.xml.ws.ResponseWrapper;

@WebService(name="AppleFinderService", serviceName="AppleFinderService", 
portName="Rpc", targetNamespace="http://com.audaxys.lease/";)
public class AppleFinderImpl implements AppleFinder {

@WebResult(name = "appleListReturn", targetNamespace = 
"http://com.audaxys.lease/";)
@ResponseWrapper(className = 
"com.audaxys.lease.model.generic.AppleListResponse" , 
localName="appleListResponse", targetNamespace="http://com.audaxys.lease/";)
public List getAppleList(String appType) {
List apples = new ArrayList();
Apple a = new Apple();
a.setAppleType("Red");
apples.add(a);
a = new Apple();
a.setAppleType("Green");
apples.add(a);
return apples;
}

public Apple[] getAppleArray(String appType) {
List apples = new ArrayList();
Apple a = new Apple();
a.setAppleType("Red");
apples.add(a);
a = new Apple();
a.setAppleType("Green");
apples.add(a);
Apple[] appleArray = new Apple[apples.size()];
int i=0; 
for(Apple app : apples) {
appleArray[i++] = app;
}
return appleArray;
}

public String obtemUmaString() {
return "uma string";
}

public Apple loadApple(String appType) {
Apple a = new Apple();
a.setAppleType(appType);
return a;
}

public List getStringList(String str) {
List l = new ArrayList();
for(int i=0; i< 10; i++) {
l.add(str);
}
return l;
}

public String[] getStringArray(String str) {
String[] l = new String[10];
for(int i=0; i< 10; i++) {
l[i] = "Red";
}
return l;
}

}


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

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

[Carlos Martins (JIRA)]

 [ 
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 the exception
javax.xml.bind.JAXBException: java.util.List is not known to this context.
I followed the issue *bold*[AXIS2-3736]*bold* and in fact created a small maven 
application with a simple webservice and axis2 1.5.4

{code}
package com.audaxys.lease.model.generic;

import java.util.ArrayList;
import java.util.List;

import javax.jws.WebResult;
import javax.jws.WebService;
import javax.xml.ws.ResponseWrapper;

@WebService(name="AppleFinderService", serviceName="AppleFinderService", 
portName="Rpc", targetNamespace="http://com.audaxys.lease/";)
public class AppleFinderImpl implements AppleFinder {

@WebResult(name = "appleListReturn", targetNamespace = 
"http://com.audaxys.lease/";)
@ResponseWrapper(className = 
"com.audaxys.lease.model.generic.AppleListResponse" , 
localName="appleListResponse", targetNamespace="http://com.audaxys.lease/";)
public List getAppleList(String appType) {
List apples = new ArrayList();
Apple a = new Apple();
a.setAppleType("Red");
apples.add(a);
a = new Apple();
a.setAppleType("Green");
apples.add(a);
return apples;
}

public Apple[] getAppleArray(String appType) {
List apples = new ArrayList();
Apple a = new Apple();
a.setAppleType("Red");
apples.add(a);
a = new Apple();
a.setAppleType("Green");
apples.add(a);
Apple[] appleArray = new Apple[apples.size()];
int i=0; 
for(Apple app : apples) {
appleArray[i++] = app;
}
return appleArray;
}

public String obtemUmaString() {
return "uma string";
}

public Apple loadApple(String appType) {
Apple a = new Apple();
a.setAppleType(appType);
return a;
}

public List getStringList(String str) {
List l = new ArrayList();
for(int i=0; i< 10; i++) {
l.add(str);
}
return l;
}

public String[] getStringArray(String str) {
String[] l = new String[10];
for(int i=0; i< 10; i++) {
l[i] = "Red";
}
return l;
}

}
{code}

  was:
Calling a simple method which returns java.util.List causes the server 
to throw the exception
javax.xml.bind.JAXBException: java.util.List is not known to this context.
I followed the issue [AXIS2-3736] and in fact created a small maven application 
with a simple webservice and axis2 1.5.4

package com.audaxys.lease.model.generic;

import java.util.ArrayList;
import java.util.List;

import javax.jws.WebResult;
import javax.jws.WebService;
import javax.xml.ws.ResponseWrapper;

@WebService(name="AppleFinderService", serviceName="AppleFinderService", 
portName="Rpc", targetNamespace="http://com.audaxys.lease/";)
public class AppleFinderImpl implements AppleFinder {

@WebResult(name = "appleListReturn", targetNamespace = 
"http://com.audaxys.lease/";)
@ResponseWrapper(className = 
"com.audaxys.lease.model.generic.AppleListResponse" , 
localName="appleListResponse", targetNamespace="http://com.audaxys.lease/";)
public List getAppleList(String appType) {
List apples = new ArrayList();
Apple a = new Apple();
a.setAppleType("Red");
apples.add(a);
a = new Apple();
a.setAppleType("Green");
apples.add(a);
return apples;
}

public Apple[] getAppleArray(String appType) {
List apples = new ArrayList();
Apple a = new Apple();
a.setAppleType("Red");
apples.add(a);
a = new Apple();
a.setAppleType("Green");
apples.add(a);
Apple[] appleArray = new Apple[apples.size()];
int i=0; 
for(Apple app : apples) {
appleArray[i++] = app;
}
return appleArray;
}

public String obtemUmaString() {
return "uma string";
}

public Apple loadApple(String appType) {
Apple a = new Apple();
a.setAppleType(appType);
return a;
}

public List getStringList(String str) {
List l = new ArrayList();
for(int i=0; i< 10; i++) {
l.add(str);
}
return l;
}

public String[] getStringArray(String str) {
String[] l = new String[10];
for(int i=0; i< 10; i++) {
l[i] = "Red";
}
return l;
}

}



> java.util.List is not known to this context
> ---
>
> Key: AXIS2-4940
> URL: https://issues.apache.org/jira/browse/AXIS2-4940
> Project: Axis2
>  Issue Typ

Axis2 on Websphere 7 class conflict

[Wally Dennis]

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, which is not valid, caused 
org.apache.axis2.handlers.addressing.AddressingInHandler cannot be cast to 
org.apache.axis2.engine.Handler 
 java.lang.ClassCastException: 
org.apache.axis2.handlers.addressing.AddressingInHandler cannot be cast to 
org.apache.axis2.engine.Handler 

The issue appears to be that the classloader is pulling the 
AddressingInHandler from the org.apache.axis2.jar bundled with Websphere 
and won't load the one in the .mar file.  We have set all of the 
classloader policies to PARENT_LAST and also disabled JAX-WS support in 
Websphere.  The only way we have been able to get past this error is to 
copy the addressing-1.5.3.mar into our WEB-INF/lib directory and change 
the extension to .jar so that the classloader at least loads the right 
code before pulling it from WAS.

Has anyone been able to resolve this or get around it a different 
approach?

Thanks,
Wally



The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 

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

[Carlos Martins (JIRA)]

 [ 
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 demo 
this exception.
Just import to your eclipse workspace and enable maven dependency management.
There is a README file included to explain how to run and test.

> 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, jaxws, kernel
>Affects Versions: 1.5.4
> Environment: IBM AIX; Java-1.6; Tomcat 6; Axis2 1.5.4
>Reporter: Carlos Martins
> Attachments: wstest.zip
>
>
> Calling a simple method which returns java.util.List causes the 
> server to throw the exception
> javax.xml.bind.JAXBException: java.util.List is not known to this context.
> I followed the issue *bold*[AXIS2-3736]*bold* and in fact created a small 
> maven application with a simple webservice and axis2 1.5.4
> {code}
> package com.audaxys.lease.model.generic;
> import java.util.ArrayList;
> import java.util.List;
> import javax.jws.WebResult;
> import javax.jws.WebService;
> import javax.xml.ws.ResponseWrapper;
> @WebService(name="AppleFinderService", serviceName="AppleFinderService", 
> portName="Rpc", targetNamespace="http://com.audaxys.lease/";)
> public class AppleFinderImpl implements AppleFinder {
> @WebResult(name = "appleListReturn", targetNamespace = 
> "http://com.audaxys.lease/";)
> @ResponseWrapper(className = 
> "com.audaxys.lease.model.generic.AppleListResponse" , 
> localName="appleListResponse", targetNamespace="http://com.audaxys.lease/";)
>   public List getAppleList(String appType) {
> List apples = new ArrayList();
> Apple a = new Apple();
> a.setAppleType("Red");
> apples.add(a);
> a = new Apple();
> a.setAppleType("Green");
> apples.add(a);
> return apples;
>   }
> public Apple[] getAppleArray(String appType) {
> List apples = new ArrayList();
> Apple a = new Apple();
> a.setAppleType("Red");
> apples.add(a);
> a = new Apple();
> a.setAppleType("Green");
> apples.add(a);
> Apple[] appleArray = new Apple[apples.size()];
> int i=0; 
> for(Apple app : apples) {
>   appleArray[i++] = app;
> }
> return appleArray;
>   }
> 
> public String obtemUmaString() {
>   return "uma string";
> }
> public Apple loadApple(String appType) {
> Apple a = new Apple();
> a.setAppleType(appType);
> return a;
> }
> 
> public List getStringList(String str) {
>   List l = new ArrayList();
>   for(int i=0; i< 10; i++) {
>   l.add(str);
>   }
>   return l;
> }
> public String[] getStringArray(String str) {
>   String[] l = new String[10];
>   for(int i=0; i< 10; i++) {
>   l[i] = "Red";
>   }
>   return l;
> }
> }
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Axis2 1.6 release plan

[Ruwan Linton]

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, but
still you need them to be separate releases going insync at least for this
release.

Ruwan

On Tue, Jan 25, 2011 at 10:10 PM, Sanjiva Weerawarana  wrote:

> 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 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 look at Neethi and Wooden state.
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>> On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen <
>>> andreas.veit...@gmail.com> wrote:
>>>
 We need to figure out what releases we need from upstream projects.
 Right now the trunk has the following snapshot dependencies:

1.2.11-SNAPSHOT
3.0.0-SNAPSHOT
1.0-SNAPSHOT

 We definitely need a new Axiom release, but this is not a problem
 because the code is in a releasable state. I can take care of this.

 The question is still open for Neethi and Woden.

 Andreas

 On Tue, Jan 25, 2011 at 02:43, Ruwan Linton 
 wrote:
 > Folks,
 > After a set of hackathons on Axis2 trunk it is sort of at a stable
 sate for
 > the 1.6 release. I predict that if we start now we should be able to
 get the
 > first release candidate in the first week of february.
 > Any volunteers to be the Release Manager for this release? and also
 any
 > critical fixes to be included into the 1.6 release?
 > Your thoughts are welcome.
 > Thanks,
 > Ruwan
 >
 > --
 > Ruwan Linton
 > Software Architect & Product Manager
 > WSO2 Inc.; http://wso2.org
 >
 > Lean . Enterprise . Middleware
 >
 > phone: +1 408 754 7388 ext 51789
 > email: ru...@wso2.com; cell: +94 77 341 3097
 > blog: http://blog.ruwan.org
 > linkedin: http://www.linkedin.com/in/ruwanlinton
 > google: http://www.google.com/profiles/ruwan.linton
 > tweet: http://twitter.com/ruwanlinton
 >

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


>>>
>>>
>>> --
>>> Ruwan Linton
>>> Software Architect & Product Manager
>>> WSO2 Inc.; http://wso2.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> phone: +1 408 754 7388 ext 51789
>>> email: ru...@wso2.com; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>> google: http://www.google.com/profiles/ruwan.linton
>>> tweet: http://twitter.com/ruwanlinton
>>>
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2; http://wso2.com/
> Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Member; Sahana Software Foundation; http://www.sahanafoundation.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>
>


-- 
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
Software Architect & Product Manager, WSO2 Inc.; http://wso2.org

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: Axis2 1.6 release plan

[Ruwan Linton]

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 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 stable sate
>> for the 1.6 release. I predict that if we start now we should be able to get
>> the first release candidate in the first week of february.
>>
>> Any volunteers to be the Release Manager for this release? and also any
>> critical fixes to be included into the 1.6 release?
>>
>> Your thoughts are welcome.
>>
>> Thanks,
>> Ruwan
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2; http://wso2.com/
> Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Member; Sahana Software Foundation; http://www.sahanafoundation.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>
>


-- 
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
Software Architect & Product Manager, WSO2 Inc.; http://wso2.org

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton