Hi Deepal, For our project, we need an option allowing the set the classloader to look for the libs in the aar files first rather than in web-inf/lib. Currently, if a WS in the AAR needs a lib and this one is in WEB-INF/lib AND in the AAR, the one in WEB-INF/lib is picked up, so this lib can't find a ressource in the aar. I sent a post some times ago that you replied:
[quote] > Hi all Axis2 users, > I have a question about classloading in Axis2: > If I have a JAR in WEB-INF/lib folder of the WAR and in the lib folder > of my .aar service archive, which one will be loaded by Axis2 when a > WebService calls a class in this JAR? > If Axis2 loads the one in the war archive, will the files in the aar > still be loadable by the JAR in the WAR? Well, that is one of the bug in Axis2 class loader and there is a JIRA as well . We wanted to fix that for 1.3 , somehow we didnt do that. I will fix that soon and make the feature available in nightly build [/quote] I would really need this evolution! Thanks in advance, Pierre Deepal Jayasinghe wrote: > > Hi Devs and Users, > > I saw a number of users asking about the next release of Axis2 , so I > think its good time to think about that. We did our last release on > August , looking at the mailing list and JIRA I can assume that the > release is very stable release. However in the meantime we have few > items that we need to implement that we discussed over the mailing list > for the next release. And there are a few bug fixes and new features > that users have ask about , so taking all those into account how about > doing a release on end of February ? > > So in the release I would like to see following list of items > - Support for RPC-Encoded > - Full support for JAX-WS > - Enhance NIO transport support > - Discuss and implement dynamic phase rule support > - Fix the issues we found at MS PlugFest > - Anything else ..... ?? > > In addition to that we need to identify the issues that we are going to > fix in next release , for that I would like ask Axis2 users to go and > create a JIRA or change the priority of JIRA if they want some issues or > features (s)he like to see in next release. In the meantime if someone > think to fix some particular issue for next release then please go and > mark the issue as blocker. But please do not just mark issue as blocker > provide some useful information specifying what do you think its is > important. > > So let's target Axis2 1.4 on end of February , and here is my +1 for the > release. > > -Deepal > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-Axis2--Release-plan-and-road-map-for-Axis2-1.4-release-tp14411346p14434060.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
