On Tue, Jun 9, 2009 at 2:38 PM, Andreas Veithen <andreas.veit...@gmail.com>wrote:
> Amila, > > I would also like to point out that: > - there is a mex-xxx-impl.jar; > - the MAR file is not deployed to the (local|snapshot) Maven repository; > - the Maven build (and the type of artifacts) is not consistent > between mex, addressing, mtompolicy, etc. > > So we should agree on a consistent way to build the MARs and apply > that to all of them. +1 > > > One additional question: in which circumstances do you need the > mex-xxx.jar in the classpath without deploying it as a module? Generally any mar file can put to the class path and use it. This is useful in client side. Users can engage modules with out creating a configuration context object and a repository. thanks, Amila. > > > Regards, > > Andreas > > On Tue, Jun 9, 2009 at 08:31, Amila > Suriarachchi<amilasuriarach...@gmail.com> wrote: > > hi, > > > > It seems like both mex-xxx.jar and mex-xxx.mar files have the same > content. > > > > Since mex-xxx.jar file contains a module.xml file it tries to deploy as a > > module when the server starts up. > > I think we need to remove module.xml part from the jar file. > > > > thanks, > > Amila. > > > > -- > > Amila Suriarachchi > > WSO2 Inc. > > blog: http://amilachinthaka.blogspot.com/ > > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
