You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Deepal Jayasinghe <de...@opensource.lk> on 2007/01/16 14:49:41 UTC
[Axis2] Axis2 1.2 release plan
Hi All;
We released Axis2 1.1.1 few days ago and now its time to think about the
next major release (Axis2 1.2). Before doing that we have big item left
in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
on doing that on this week (I may try this time :( ).
In Axis2 release I would like to see following features in the release
in addition to the JIRAs in the JIRA list.
- WSDL 2.0 fully support
- POJO - annotation
- REST Annotation
- JAX-WS integration
- JAX-WS -annotation
- Un-wrapping (Response)
- ADB - missing schema support
- Move security and Sawan module from Axis2 trunk
- Maven2 support
- JASON support
- Binary serialization
- Geronimo Integration
- Jax-ws option for code gen (Jaxbri as the db)
- Custom File cache mechanism
- Multiple services support in code gen (WSDL with multiple services)
- HTTP code generation (both WSDL 1.1 and 2.0)
- i18n support
- Fix/update helper mode
I would like to suggest 31st of March as the release date and going
backward from that date , we need to release first RC on 28th Feb and
cut the branch on the same date. So the release dates will be ;
- 28th Feb cut the branch for 1.2 release
- 28th Feb Release Axis2 1.2 RC1
- 15th March Release Axis2 RC2 (depending on the RC1 state)
- Rename RC2 or RC1 as Axis2 1.2
To have the above mentioned feature list and to cope with the mentioned
date it is very much essential to have community support. One other
thing if we unable to get all the above mentioned feature by 28th Feb
then we will be releasing Axis2 1.2 with whatever the features we have
at that time.
About JAX-WS integration and JAX-WS annotation , please update the
mailing list whether we will be able to have those feature in the
release or not.
Please comment and suggest if I have miss any features that you think is
necessary , or if I have add any feature which are not necessary.
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Axis2 1.2 release plan
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Chathura ;
Yes , thats a good idea and we definitely add that feature into the list .
Thanks
Deepal
> Hi Deepal et al,
>
> Is it possible to bring in jetty in place of SimpleAxisServer for 1.2
> release. I suppose the work is already done in WSO2's WSAS. May be we
> could make a request to WSO2 to donate the code. It would be a big
> leap for long running asynchronous application, for which
> SimpleAxisServer is a bad candidate(for any production system for that
> matter). It would help Sandesha2 project as well.
>
> Thanks
> Chathura
>
>
>
> On 1/16/07, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> Hi Deepal and all,
>
> Great list. Anyway, I hope I can comment on this plan, even though I
> won't be able contribute much, in terms of coding, to the next release.
>
> I have a small doubt whether all these are doable within 6 weeks, but I
> assume you have planned well. Anyway isn't it better to identify most
> critical features, as a minimum to be satisfied?
>
> > Hi All;
>
> > We released Axis2 1.1.1 few days ago and now its time to think about the
> > next major release (Axis2 1.2). Before doing that we have big item left
> > in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
> > on doing that on this week (I may try this time :( ).
>
> > In Axis2 release I would like to see following features in the release
> > in addition to the JIRAs in the JIRA list.
> > - WSDL 2.0 fully support
> For this I think you might want to consider merging the branch Keith is
> now working. I think this is bit tricky as most of the WSDL 1.1 features
> are broken in that branch. Keith correct me if I am wrong.
>
> > - POJO - annotation
> > - REST Annotation
> Hmm, cool feature. I hope this will help our annotations fans a lot. We
> have a very good REST support, but not exposed well enough and this will
> help to overcome that.
>
> > - JAX-WS integration
> > - JAX-WS -annotation
> > - Un-wrapping (Response)
> > - ADB - missing schema support
> > - Move security and Sawan module from Axis2 trunk
> > - Maven2 support
>
> I hope documentation on using Maven2 with Axis2 will also be updated
> (created), with this move.
>
> Other than that, +1 for the release plan. I hope you will be the release
> manager for this release :)
>
> -- Chinthaka
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Axis2 1.2 release plan
Posted by Chathura Herath <ch...@gmail.com>.
Hi Deepal et al,
Is it possible to bring in jetty in place of SimpleAxisServer for 1.2
release. I suppose the work is already done in WSO2's WSAS. May be we
could make a request to WSO2 to donate the code. It would be a big
leap for long running asynchronous application, for which
SimpleAxisServer is a bad candidate(for any production system for that
matter). It would help Sandesha2 project as well.
Thanks
Chathura
On 1/16/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Deepal and all,
>
> Great list. Anyway, I hope I can comment on this plan, even though I
> won't be able contribute much, in terms of coding, to the next release.
>
> I have a small doubt whether all these are doable within 6 weeks, but I
> assume you have planned well. Anyway isn't it better to identify most
> critical features, as a minimum to be satisfied?
>
> > Hi All;
> >
> > We released Axis2 1.1.1 few days ago and now its time to think about the
> > next major release (Axis2 1.2). Before doing that we have big item left
> > in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
> > on doing that on this week (I may try this time :( ).
> >
> > In Axis2 release I would like to see following features in the release
> > in addition to the JIRAs in the JIRA list.
> > - WSDL 2.0 fully support
> For this I think you might want to consider merging the branch Keith is
> now working. I think this is bit tricky as most of the WSDL 1.1 features
> are broken in that branch. Keith correct me if I am wrong.
>
> > - POJO - annotation
> > - REST Annotation
> Hmm, cool feature. I hope this will help our annotations fans a lot. We
> have a very good REST support, but not exposed well enough and this will
> help to overcome that.
>
> > - JAX-WS integration
> > - JAX-WS -annotation
> > - Un-wrapping (Response)
> > - ADB - missing schema support
> > - Move security and Sawan module from Axis2 trunk
> > - Maven2 support
>
> I hope documentation on using Maven2 with Axis2 will also be updated
> (created), with this move.
>
> Other than that, +1 for the release plan. I hope you will be the release
> manager for this release :)
>
> - -- Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFrZiXjON2uBzUhh8RAhnxAJ9mHj+zY0iQlaqxZ3TXGl5JH6btyQCdH8O8
> j7aGnr4bNgcMcbmeHsXYUXU=
> =byxr
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Axis2 1.2 release plan
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Deepal and all,
Great list. Anyway, I hope I can comment on this plan, even though I
won't be able contribute much, in terms of coding, to the next release.
I have a small doubt whether all these are doable within 6 weeks, but I
assume you have planned well. Anyway isn't it better to identify most
critical features, as a minimum to be satisfied?
> Hi All;
>
> We released Axis2 1.1.1 few days ago and now its time to think about the
> next major release (Axis2 1.2). Before doing that we have big item left
> in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
> on doing that on this week (I may try this time :( ).
>
> In Axis2 release I would like to see following features in the release
> in addition to the JIRAs in the JIRA list.
> - WSDL 2.0 fully support
For this I think you might want to consider merging the branch Keith is
now working. I think this is bit tricky as most of the WSDL 1.1 features
are broken in that branch. Keith correct me if I am wrong.
> - POJO - annotation
> - REST Annotation
Hmm, cool feature. I hope this will help our annotations fans a lot. We
have a very good REST support, but not exposed well enough and this will
help to overcome that.
> - JAX-WS integration
> - JAX-WS -annotation
> - Un-wrapping (Response)
> - ADB - missing schema support
> - Move security and Sawan module from Axis2 trunk
> - Maven2 support
I hope documentation on using Maven2 with Axis2 will also be updated
(created), with this move.
Other than that, +1 for the release plan. I hope you will be the release
manager for this release :)
- -- Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFrZiXjON2uBzUhh8RAhnxAJ9mHj+zY0iQlaqxZ3TXGl5JH6btyQCdH8O8
j7aGnr4bNgcMcbmeHsXYUXU=
=byxr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Axis2 1.2 release plan
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Deepal and all,
Great list. Anyway, I hope I can comment on this plan, even though I
won't be able contribute much, in terms of coding, to the next release.
I have a small doubt whether all these are doable within 6 weeks, but I
assume you have planned well. Anyway isn't it better to identify most
critical features, as a minimum to be satisfied?
> Hi All;
>
> We released Axis2 1.1.1 few days ago and now its time to think about the
> next major release (Axis2 1.2). Before doing that we have big item left
> in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
> on doing that on this week (I may try this time :( ).
>
> In Axis2 release I would like to see following features in the release
> in addition to the JIRAs in the JIRA list.
> - WSDL 2.0 fully support
For this I think you might want to consider merging the branch Keith is
now working. I think this is bit tricky as most of the WSDL 1.1 features
are broken in that branch. Keith correct me if I am wrong.
> - POJO - annotation
> - REST Annotation
Hmm, cool feature. I hope this will help our annotations fans a lot. We
have a very good REST support, but not exposed well enough and this will
help to overcome that.
> - JAX-WS integration
> - JAX-WS -annotation
> - Un-wrapping (Response)
> - ADB - missing schema support
> - Move security and Sawan module from Axis2 trunk
> - Maven2 support
I hope documentation on using Maven2 with Axis2 will also be updated
(created), with this move.
Other than that, +1 for the release plan. I hope you will be the release
manager for this release :)
- -- Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFrZiXjON2uBzUhh8RAhnxAJ9mHj+zY0iQlaqxZ3TXGl5JH6btyQCdH8O8
j7aGnr4bNgcMcbmeHsXYUXU=
=byxr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
[Axis2] RE:RE: RE: Axis2 1.2 release plan
Posted by falom <fa...@yahoo.com.cn>.
Hi Paul,
BTW, I've also tried to change the jms axis2.xml config to use geronimo's org.activemq.jndi.ActiveMQInitialContextFactory instead of org.apache.activemq.jndi.ActiveMQInitialContextFactory, i got same noclassfound exception.
falom
falom <fa...@yahoo.com.cn> wrote： Hi Paul,
I installed axis2 war in both tomcat and geronimo.
First I managed to test axis2 jms transport in tomcat connecting to standalone activemq broker by deploying one service using servicelifecycle to start up the jmslistener.
BUT when i deploy the same service in geronimo, while trying connect to the activemq broker within geronimo, i got following exception attached, seems like problem related to classloader, or something else which i am really stuck with(BTW, i have put necessary activemq jars in every possible folders i can think of under geronimo and axis2 war, same exception all the time), please help!
Also I'd very much like to look more into Synapse and related jms soap samples, which i know is a more robust pattern to bridge jms and web services. But i need to first solve this problem in geronimo first.
falom
22:46:30,709 INFO [JMSActiveEchoServiceLifeCycle] JMSActiveEchoServiceLifeCycle startUp called.
22:46:30,719 ERROR [JMSListener] Error connecting to JMS connection factory : TopicConnectionFactory
javax.naming.NoInitialContextException: Cannot instantiate class: org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.apache.activemq.jndi.ActiveMQInitialContextFactory in classloader default/axis211/1164548268298/war]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createInitialContext(JMSConnectionFactory.java:133)
at org.apache.axis2.transport.jms.JMSConnectionFactory.connect(JMSConnectionFactory.java:122)
at org.apache.axis2.transport.jms.JMSListener.initializeConnectionFactories(JMSListener.java:244)
at org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:104)
at org.apache.axis2.jms2.JMSActiveEchoServiceLifeCycle.startUp(JMSActiveEchoServiceLifeCycle.java:56)
at org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass(ServiceBuilder.java:354)
at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:136)
at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:91)
at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:133)
at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:528)
at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:227)
at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:174)
at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:88)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176)
at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:67)
at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:337)
at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31)
at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:192)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:313)
at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$f3376869.addContext(<generated>)
at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:438)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540)
at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:508)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$d98215e2.startConfiguration(<generated>)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
Paul Fremantle <pz...@gmail.com> wrote： Falom
We have tested Axis2 JMS with ActiveMQ. In fact I've done some really
nice examples with Synapse where we bridge ActiveMQ into SOAP.
Do you have any specific integration requirements?
Paul
On 1/17/07, falom wrote:
> Hi Deepal,
>
> It will be great to have geronimo integration for 1.2 release. Particularly
> i'm interest to see if axis2 jms support can be integrated with geronimo
> activemq broker, which will make axis2 much more powerful in aspect of
> efficient handling async business requirements.
>
> falom
>
> Deepal Jayasinghe wrote：
> Hi All;
>
> We released Axis2 1.1.1 few days ago and now its time to think about the
> next major release (Axis2 1.2). Before doing that we have big item left
> in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
> on doing that on this week (I may try this time :( ).
>
> In Axis2 release I would like to see following features in the release
> in addition to the JIRAs in the JIRA list.
> - WSDL 2.0 fully support
> - POJO - annotation
> - REST Annotation
> - JAX-WS integration
> - JAX-WS -annotation
> - Un-wrapping (Response)
> - ADB - missing schema support
> - Move security and Sawan module from Axis2 trunk
> - Maven2 support
> - JASON support
> - Binary serialization
> - Geronimo Integration
> - Jax-ws option for code gen (Jaxbri as the db)
> - Custom File cache mechanism
> - Multiple services support in code gen (WSDL with multiple services)
> - HTTP code generation (both WSDL 1.1 and 2.0)
> - i18n support
> - Fix/update helper mode
>
> I would like to suggest 31st of March as the release date and going
> backward from that date , we need to release first RC on 28th Feb and
> cut the branch on the same date. So the release dates will be ;
>
> - 28th Feb cut the branch for 1.2 release
> - 28th Feb Release Axis2 1.2 RC1
> - 15th March Release Axis2 RC2 (depending on the RC1 state)
> - Rename RC2 or RC1 as Axis2 1.2
>
> To have the above mentioned feature list and to cope with the mentioned
> date it is very much essential to have community support. One other
> thing if we unable to get all the above mentioned feature by 28th Feb
> then we will be releasing Axis2 1.2 with whatever the features we have
> at that time.
>
> About JAX-WS integration and JAX-WS annotation , please update the
> mailing list whether we will be able to have those feature in the
> release or not.
>
> Please comment and suggest if I have miss any features that you think is
> necessary , or if I have add any feature which are not necessary.
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------
Mp3疯狂搜-新歌热歌高速下
[Axis2] RE: RE: Axis2 1.2 release plan
Posted by falom <fa...@yahoo.com.cn>.
Hi Paul,
I installed axis2 war in both tomcat and geronimo.
First I managed to test axis2 jms transport in tomcat connecting to standalone activemq broker by deploying one service using servicelifecycle to start up the jmslistener.
BUT when i deploy the same service in geronimo, while trying connect to the activemq broker within geronimo, i got following exception attached, seems like problem related to classloader, or something else which i am really stuck with(BTW, i have put necessary activemq jars in every possible folders i can think of under geronimo and axis2 war, same exception all the time), please help!
Also I'd very much like to look more into Synapse and related jms soap samples, which i know is a more robust pattern to bridge jms and web services. But i need to first solve this problem in geronimo first.
falom
22:46:30,709 INFO [JMSActiveEchoServiceLifeCycle] JMSActiveEchoServiceLifeCycle startUp called.
22:46:30,719 ERROR [JMSListener] Error connecting to JMS connection factory : TopicConnectionFactory
javax.naming.NoInitialContextException: Cannot instantiate class: org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.apache.activemq.jndi.ActiveMQInitialContextFactory in classloader default/axis211/1164548268298/war]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createInitialContext(JMSConnectionFactory.java:133)
at org.apache.axis2.transport.jms.JMSConnectionFactory.connect(JMSConnectionFactory.java:122)
at org.apache.axis2.transport.jms.JMSListener.initializeConnectionFactories(JMSListener.java:244)
at org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:104)
at org.apache.axis2.jms2.JMSActiveEchoServiceLifeCycle.startUp(JMSActiveEchoServiceLifeCycle.java:56)
at org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass(ServiceBuilder.java:354)
at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:136)
at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:91)
at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:133)
at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:528)
at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:227)
at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:174)
at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:88)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176)
at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:67)
at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:337)
at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31)
at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:192)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:313)
at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$f3376869.addContext(<generated>)
at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:438)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540)
at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:508)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$d98215e2.startConfiguration(<generated>)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
Paul Fremantle <pz...@gmail.com> wrote： Falom
We have tested Axis2 JMS with ActiveMQ. In fact I've done some really
nice examples with Synapse where we bridge ActiveMQ into SOAP.
Do you have any specific integration requirements?
Paul
On 1/17/07, falom wrote:
> Hi Deepal,
>
> It will be great to have geronimo integration for 1.2 release. Particularly
> i'm interest to see if axis2 jms support can be integrated with geronimo
> activemq broker, which will make axis2 much more powerful in aspect of
> efficient handling async business requirements.
>
> falom
>
> Deepal Jayasinghe wrote：
> Hi All;
>
> We released Axis2 1.1.1 few days ago and now its time to think about the
> next major release (Axis2 1.2). Before doing that we have big item left
> in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
> on doing that on this week (I may try this time :( ).
>
> In Axis2 release I would like to see following features in the release
> in addition to the JIRAs in the JIRA list.
> - WSDL 2.0 fully support
> - POJO - annotation
> - REST Annotation
> - JAX-WS integration
> - JAX-WS -annotation
> - Un-wrapping (Response)
> - ADB - missing schema support
> - Move security and Sawan module from Axis2 trunk
> - Maven2 support
> - JASON support
> - Binary serialization
> - Geronimo Integration
> - Jax-ws option for code gen (Jaxbri as the db)
> - Custom File cache mechanism
> - Multiple services support in code gen (WSDL with multiple services)
> - HTTP code generation (both WSDL 1.1 and 2.0)
> - i18n support
> - Fix/update helper mode
>
> I would like to suggest 31st of March as the release date and going
> backward from that date , we need to release first RC on 28th Feb and
> cut the branch on the same date. So the release dates will be ;
>
> - 28th Feb cut the branch for 1.2 release
> - 28th Feb Release Axis2 1.2 RC1
> - 15th March Release Axis2 RC2 (depending on the RC1 state)
> - Rename RC2 or RC1 as Axis2 1.2
>
> To have the above mentioned feature list and to cope with the mentioned
> date it is very much essential to have community support. One other
> thing if we unable to get all the above mentioned feature by 28th Feb
> then we will be releasing Axis2 1.2 with whatever the features we have
> at that time.
>
> About JAX-WS integration and JAX-WS annotation , please update the
> mailing list whether we will be able to have those feature in the
> release or not.
>
> Please comment and suggest if I have miss any features that you think is
> necessary , or if I have add any feature which are not necessary.
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------
Mp3疯狂搜-新歌热歌高速下
Re: [Axis2] RE: Axis2 1.2 release plan
Posted by Paul Fremantle <pz...@gmail.com>.
Falom
We have tested Axis2 JMS with ActiveMQ. In fact I've done some really
nice examples with Synapse where we bridge ActiveMQ into SOAP.
Do you have any specific integration requirements?
Paul
On 1/17/07, falom <fa...@yahoo.com.cn> wrote:
> Hi Deepal,
>
> It will be great to have geronimo integration for 1.2 release. Particularly
> i'm interest to see if axis2 jms support can be integrated with geronimo
> activemq broker, which will make axis2 much more powerful in aspect of
> efficient handling async business requirements.
>
> falom
>
> Deepal Jayasinghe <de...@opensource.lk> wrote：
> Hi All;
>
> We released Axis2 1.1.1 few days ago and now its time to think about the
> next major release (Axis2 1.2). Before doing that we have big item left
> in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
> on doing that on this week (I may try this time :( ).
>
> In Axis2 release I would like to see following features in the release
> in addition to the JIRAs in the JIRA list.
> - WSDL 2.0 fully support
> - POJO - annotation
> - REST Annotation
> - JAX-WS integration
> - JAX-WS -annotation
> - Un-wrapping (Response)
> - ADB - missing schema support
> - Move security and Sawan module from Axis2 trunk
> - Maven2 support
> - JASON support
> - Binary serialization
> - Geronimo Integration
> - Jax-ws option for code gen (Jaxbri as the db)
> - Custom File cache mechanism
> - Multiple services support in code gen (WSDL with multiple services)
> - HTTP code generation (both WSDL 1.1 and 2.0)
> - i18n support
> - Fix/update helper mode
>
> I would like to suggest 31st of March as the release date and going
> backward from that date , we need to release first RC on 28th Feb and
> cut the branch on the same date. So the release dates will be ;
>
> - 28th Feb cut the branch for 1.2 release
> - 28th Feb Release Axis2 1.2 RC1
> - 15th March Release Axis2 RC2 (depending on the RC1 state)
> - Rename RC2 or RC1 as Axis2 1.2
>
> To have the above mentioned feature list and to cope with the mentioned
> date it is very much essential to have community support. One other
> thing if we unable to get all the above mentioned feature by 28th Feb
> then we will be releasing Axis2 1.2 with whatever the features we have
> at that time.
>
> About JAX-WS integration and JAX-WS annotation , please update the
> mailing list whether we will be able to have those feature in the
> release or not.
>
> Please comment and suggest if I have miss any features that you think is
> necessary , or if I have add any feature which are not necessary.
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> ________________________________
> 抢注雅虎免费邮箱-3.5G容量，20M附件！
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
[Axis2] RE: Axis2 1.2 release plan
Posted by falom <fa...@yahoo.com.cn>.
Hi Deepal,
It will be great to have geronimo integration for 1.2 release. Particularly i'm interest to see if axis2 jms support can be integrated with geronimo activemq broker, which will make axis2 much more powerful in aspect of efficient handling async business requirements.
falom
Deepal Jayasinghe <de...@opensource.lk> wrote：
Hi All;
We released Axis2 1.1.1 few days ago and now its time to think about the
next major release (Axis2 1.2). Before doing that we have big item left
in our hand is to merge Axis2 trunk and 1.1 branch. So we need to plan
on doing that on this week (I may try this time :( ).
In Axis2 release I would like to see following features in the release
in addition to the JIRAs in the JIRA list.
- WSDL 2.0 fully support
- POJO - annotation
- REST Annotation
- JAX-WS integration
- JAX-WS -annotation
- Un-wrapping (Response)
- ADB - missing schema support
- Move security and Sawan module from Axis2 trunk
- Maven2 support
- JASON support
- Binary serialization
- Geronimo Integration
- Jax-ws option for code gen (Jaxbri as the db)
- Custom File cache mechanism
- Multiple services support in code gen (WSDL with multiple services)
- HTTP code generation (both WSDL 1.1 and 2.0)
- i18n support
- Fix/update helper mode
I would like to suggest 31st of March as the release date and going
backward from that date , we need to release first RC on 28th Feb and
cut the branch on the same date. So the release dates will be ;
- 28th Feb cut the branch for 1.2 release
- 28th Feb Release Axis2 1.2 RC1
- 15th March Release Axis2 RC2 (depending on the RC1 state)
- Rename RC2 or RC1 as Axis2 1.2
To have the above mentioned feature list and to cope with the mentioned
date it is very much essential to have community support. One other
thing if we unable to get all the above mentioned feature by 28th Feb
then we will be releasing Axis2 1.2 with whatever the features we have
at that time.
About JAX-WS integration and JAX-WS annotation , please update the
mailing list whether we will be able to have those feature in the
release or not.
Please comment and suggest if I have miss any features that you think is
necessary , or if I have add any feature which are not necessary.
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------
抢注雅虎免费邮箱-3.5G容量，20M附件！