[Axis2] Access a resource inside of a Axis2 archive

Hi I've a Axis2 archive file (.aar) which contains several libraries in the /lib folder. In my *PortSkeleton class I'm looking for a way to load a properties file that is in one of this libs. I tried with this.getClass().getResource("my.properties") (also with "lib/my.properties") without success

Re: [Axis2]linking wsdl binding transport and Axis2 transports

Hi Srinath! This is a random thought occur to me when I am working on some system here. Please comment :) Comment : +1 :) Even though we have done the hard work of making the transports pluggable we have not make it final by linking the wsdl transports define in the binding with our transpor

Re: [axis2] ws-addr test cases

Sanjiva Weerawarana wrote: > Ooops wrong link: >http://www.w3.org/2002/ws/addr/testsuite/ > > Sanjiva. > It still offends me that WS-A can consider themselves nearly ready to be final and yet they only have a few draft test cases. For example, where is their wsa:To header with a ? string

Re: [axis2] ws-addr test cases

Hey Steve: > Ooops wrong link: > http://www.w3.org/2002/ws/addr/testsuite/ It still offends me that WS-A can consider themselves nearly ready to be final and yet they only have a few draft test cases. For example, where is their wsa:To header with a ? string in http://ex.org/url?name=

Re: [Axis2]linking wsdl binding transport and Axis2 transports

Hi Glen; +1 and yes .. dynamic invocations are one of the other things we need to do for Axis2 clients Thanks Srinath On 10/24/05, Glen Daniels <[EMAIL PROTECTED]> wrote: > Hi Srinath! > > > This is a random thought occur to me when I am working on some system > > here. Please comment :) > > Comme

Re: [axis2] Dispatchers

Hi Glen; I agree on that Dispatcher itself is a handler but the name "Dispatcher" implies different meaning than a handler , it is obvious that a module can configure to put handlers into Dispatch phase we are not avoiding doing that (in fact I did the same thing to a the SypaseToy that I wrot

Re: [axis2] Dispatchers

Hi Deepal: I agree on that Dispatcher itself is a handler Ok. but the name "Dispatcher" implies different meaning than a handler , it is obvious that a module can configure to put handlers into Dispatch phase we are not avoiding doing that (in fact I did the same thing to a the SypaseToy t

[Axis2] ThreadPool inside Axis2

hi all, Axis2 at present implements a very simple ThreadPool concept. If we can come up with a way of using an external thread pool we can let the axis2 users use a more robust ThreadPool of their choice if need be. If an external ThreadPool is not set we can do the same thing that we are doi

Re: [axis2] Dispatchers

Hi Glen, Deepal; I think I am the one who hardcode the dispatchers in the first place. But I am convinced that it is a *bad* thing to do. I am +1 to add them all to the dispatcher phase in the axis2.xml and let them be just Handlers Thanks Srinath On 10/24/05, Glen Daniels <[EMAIL PROTECTED]> wro

Re: [Axis2] ThreadPool inside Axis2

On Mon, 2005-10-24 at 15:44 +0600, Chamil Thanthrimudalige wrote: > hi all, > > Axis2 at present implements a very simple ThreadPool concept. If we can > come up with a way of using an external thread pool we can let the axis2 > users use a more robust ThreadPool of their choice if need be. If a

Re: [Axis2] ThreadPool inside Axis2

Hmm, does this mean we will have no problem in running threads in J2EE environments ? Hmm, if thats the case, this is a good idea. ( this doesn't mean we should pop up threads here and there ;-) ). . The two scenarios we are using threads are in invoke non-blocking case and Async Message Receivers.

[jira] Created: (AXIS2-291) OMStaxWrapper throws unnecessary END_DOCUMENT event

OMStaxWrapper throws unnecessary END_DOCUMENT event --- Key: AXIS2-291 URL: http://issues.apache.org/jira/browse/AXIS2-291 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: om Reporter: Eran Chinthaka

[jira] Commented: (AXIS-1642) axis.development.system doesn't supress stack traces

[ http://issues.apache.org/jira/browse/AXIS-1642?page=comments#action_12355682 ] Chad Wilson commented on AXIS-1642: --- Hmm, revisiting, ignore my last comment - it is incorrect. However, the issue is still prevalent in Axis 1.3 (i.e. axis.development.syste

Re: [Axis2] ThreadPool inside Axis2

On Tue, 2005-10-25 at 07:27 +0600, Eran Chinthaka wrote: > Hmm, does this mean we will have no problem in running threads in J2EE > environments ? Hmm, if thats the case, this is a good idea. ( this > doesn't mean we should pop up threads here and there ;-) ). . Right .. if we have this then in a

Re: [axis2] Dispatchers

On Mon, 2005-10-24 at 12:46 -0400, Glen Daniels wrote: > > What I'm trying to say is that we should NOT hard-code the dispatch > order, we should have it simply exist as configuration in the default > axis2.xml file. +1 .. Deepal what's the advantage of having it fixed programmatically instead

Re: [Axis2] Access a resource inside of a Axis2 archive

Hi Yvess; The correct way is get the ServiceDescription from , MessageContxt and then you can get the correct classloader for that service (which has all you lib files) from serviceDescription ClassLoader cl = sd.getClassLoader(); next you can load the properties you want. Thanks, Deepal ..

Re: [axis2] Dispatchers

Hi see my comments below; Thanks, Deepal ~Future is Open~ - Original Message - From: "Sanjiva Weerawarana" <[EMAIL PROTECTED]> To: Sent: Tuesday, October 25, 2005 9:05 AM Subject: Re: [axis2] Dispatchers On Mon, 2005

Re: Base 64 defualt lenghts....... Re: svn commit: r328264 - in /webservices/axis2/trunk/java/modules/xml: src/org/apache/axis2/om/impl/dom/ src/org/apache/axis2/om/impl/llom/ test/org/apache/axis2/om

Hi Please see my comments below: Thanks, Ruchith On 10/25/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > Hi, > >- Added and commented code in OMTextImpl, to do line wrapping of base64 > content (using 76 >character length) , for others to review, this is > required to support Encrypt, Sign

[Axis2] Service scope

Hi, In Axis1 there is a scope parameter in server-config.wsdd that controls the instantiation of the impl class. Is there an appropriate parameter in Axis2 or on which base the instantiation happens? Thanks Yves

Re: [Axis2] Service scope

Hi ; Still we do not handling that , pls create a JIRA we will fix that in next release. Thanks, Deepal ~Future is Open~ - Original Message - From: "Yves Langisch" <[EMAIL PROTECTED]> To: Sent: Tuesday, October 25, 20

Re: [Axis2] Service scope

Deepal, Thanks, I'll file a JIRA entry. What's the actual behaviour? Per call instantiation? Thanks Yves On Tue, 2005-10-25 at 12:43 +0600, Deepal Jayasinghe wrote: > Hi ; > > Still we do not handling that , pls create a JIRA we will fix that in next > release. > > Thanks, > Deepal > .

[jira] Created: (AXIS2-292) Adding service scope control

Adding service scope control Key: AXIS2-292 URL: http://issues.apache.org/jira/browse/AXIS2-292 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: core Versions: 0.92 Reporter: Yves Langisch There should be a

Re: [Axis2] Access a resource inside of a Axis2 archive

Deepal, Thanks, I'll give it a try. Yves On Tue, 2005-10-25 at 09:21 +0600, Deepal Jayasinghe wrote: > Hi Yvess; > > The correct way is get the ServiceDescription from , MessageContxt and then > you can get the correct classloader for that service (which has all you lib > files) from serviceD

[Axis2] How to get current MessageContext in skeleton class

All, I'm looking for a way to get the current MessageContext in the skeleton class? In Axis2 this could be done with AxisEngine.getCurrentMessageContext(). Thanks Yves