[Axis2]How module versioning works

[Srinath Perera <he...@gmail.com>]

Hi All;

How does the Module visioning works? How should I name my modules and
how should I engage them? (recent commit suddenly break my module
loading with a null pointer). I think it should be transparent to
people who do not use them

I am sure  there must be a mailing list discussion on the module
versioning and rationale for it's need? I can not find it in the list.
can some one point me to it.

Thanks
Srinath

java.lang.NullPointerException
	at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:991)
	at java.lang.Float.parseFloat(Float.java:394)
	at org.apache.axis2.util.Utils.isLatest(Utils.java:313)
	at org.apache.axis2.util.Utils.calculateDefaultModuleVersion(Utils.java:294)
	at org.apache.axis2.deployment.DeploymentEngine.load(DeploymentEngine.java:499)
	at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:59)
	at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:33)
	at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:49)
	at edu.indiana.extreme.lead.ws.Axis2WSDL4JBasedWebServiceInvoker.invoke(Axis2WSDL4JBasedWebServiceInvoker.java:279)
	at SecuirtyInvocationTest1.doInvocation(SecuirtyInvocationTest1.java:64)
	at SecuirtyInvocationTest1.testsecuirtyCallWithSync(SecuirtyInvocationTest1.java:19)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at junit.framework.TestCase.runTest(TestCase.java:154)
	at junit.framework.TestCase.runBare(TestCase.java:127)
	at junit.framework.TestResult$1.protect(TestResult.java:106)
	at junit.framework.TestResult.runProtected(TestResult.java:124)
	at junit.framework.TestResult.run(TestResult.java:109)
	at junit.framework.TestCase.run(TestCase.java:118)
	at junit.framework.TestSuite.runTest(TestSuite.java:208)
	at junit.framework.TestSuite.run(TestSuite.java:203)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)



--
============================
Srinath Perera:
   http://www.cs.indiana.edu/~hperera/
   http://www.bloglines.com/blog/hemapani

Re: [Axis2]How module versioning works

[Eran Chinthaka <ch...@opensource.lk>]

Hi Srinath,

Seems you are bit relax these days to help us with Axis2 ;-)

Srinath Perera wrote:

>Hi All;
>
>How does the Module visioning works? How should I name my modules and
>how should I engage them? 
>
You can name modules as myModuleName-x.x.x.mar, where all x are numbers.
But SNAPSHOT is considered special case, so you can name your module as
myModule-x.x.x-SNAPHOT.mar.

How you engage module is,

ServiceClient.engageModule(new QName("myModuleName")); // this will
pickup the default or the latest module deployed, or
ServiceClient.engageModule(new QName("myModuleName-x.x.x"))

>(recent commit suddenly break my module
>loading with a null pointer). I think it should be transparent to
>people who do not use them.
>
>  
>
It is transparent to the users.

>I am sure  there must be a mailing list discussion on the module
>versioning and rationale for it's need? I can not find it in the list.
>can some one point me to it.
>  
>
http://marc.theaimsgroup.com/?l=axis-dev&m=113011143509962&w=2

-- Chinthaka