You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Irantha <ir...@wso2.com> on 2008/12/15 08:57:50 UTC
commons-transport jar not included in axis2-SNAPSHOT-bin.zip
When I tried to run axis2server.bat from extracted axis2-SNAPSHOT-bin.zip
(created with: mvn -Drelease install). I got ClassNotFoundException:
org.apache.axis2.transport.tcp.TCPT
ransportSender.
I had to manually copy axis2-transports-SNAPSHOT.jar from commons-transport
build to AXIS2_HOME/lib.
Don't we need to include commons-transport jar with axis2 release artifacts?
Thanks,
Irantha
[FATAL] [SimpleAxisServer] Shutting down. Error starting SimpleAxisServer
org.apache.axis2.deployment.DeploymentException:
org.apache.axis2.transport.tcp.
TCPTransportSender
at
org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders
(AxisConfigBuilder.java:694)
at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConf
igBuilder.java:121)
at
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguratio
n(DeploymentEngine.java:707)
at
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfigurati
on(FileSystemConfigurator.java:116)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
ionContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
ionContextFromFileSystem(ConfigurationContextFactory.java:206)
at
org.apache.axis2.transport.SimpleAxis2Server.<init>(SimpleAxis2Server
.java:47)
at
org.apache.axis2.transport.SimpleAxis2Server.main(SimpleAxis2Server.j
ava:98)
Caused by: java.lang.ClassNotFoundException:
org.apache.axis2.transport.tcp.TCPT
ransportSender
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
at
org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders
(AxisConfigBuilder.java:669)
... 7 more
[SimpleAxisServer] Shutting down. Error starting SimpleAxisServer
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Deepal jayasinghe <de...@gmail.com>.
> Transports are configured using parameters added to the corresponding
> <transportReceiver> and <transportSender> elements. If the transport
> is simply added to the classpath, these elements are placed in
> axis2.xml, while in the case of deployment using the transport
> deployer, they must be placed in the META-INF/transport.xml file
> inside the archive. I guess that you don't expect users to unzip the
> transport archive, change transport.xml, rezip it and redeploy it, so
> I must have missed something...
>
Nope I did not mean that. What I was referring here is that if the
transport need some kind of parameter, then we can provide them using
axis2.xml or runtime.
Anyway I understand what you mean, I think the deployer is more useful
custom transport. For the default transport we may have to use axis2.xml
as it is.
I think same argument is valid more module like sandesha and rampart, if
someone want to configure them how do they do ?
Deepal
> Andreas
>
> On Mon, Dec 15, 2008 at 23:51, Deepal Jayasinghe <de...@gmail.com> wrote:
>
>> well it is same as how do you set up services I guess. One thing you
>> could do is you can provide parameters though axis2.xml. Or you can
>> change them at runtime
>> - get the transport sender
>> - get the transport description
>> - add the configuration
>>
>> Deepal
>>
>> On Mon, Dec 15, 2008 at 5:38 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>
>>> Deepal,
>>>
>>> With the existing transport deployer, how do you handle the case of a
>>> transport sender that can be set up without any configuration, but for
>>> which the user might want to set some optional parameters later?
>>>
>>> Andreas
>>>
>>> On Mon, Dec 15, 2008 at 23:02, Deepal Jayasinghe <de...@gmail.com> wrote:
>>>
>>>> Not bad,
>>>> in fact we have some thing called transport deployer (just like
>>>> service deployer) , so if you add the transport deployer into axis2
>>>> and specify the location of transport directory. Then you do not need
>>>> to have any of the transport in axis2.xml. Everything is automatic :D
>>>>
>>>> Deepal
>>>>
>>>> On Mon, Dec 15, 2008 at 4:56 PM, Andreas Veithen
>>>> <an...@gmail.com> wrote:
>>>>
>>>>> I think that the default axis2.xml also refers to the TCP sender. BTW,
>>>>> wouldn't it be interesting to have a lookup mechanism (like JDK 1.4
>>>>> service providers) that automatically adds the transport senders to
>>>>> the Axis configuration? That way the default axis2.xml would work out
>>>>> of the box with all transport senders that are available in the
>>>>> classpath, at least those that don't need configuration.
>>>>>
>>>>> Andreas
>>>>>
>>>>> On Mon, Dec 15, 2008 at 22:30, Glen Daniels <gl...@thoughtcraft.com> wrote:
>>>>>
>>>>>> Deepal Jayasinghe wrote:
>>>>>>
>>>>>>> Well lets add the axis2-transport.jar which has all the transport in it.
>>>>>>>
>>>>>> Hm... Wouldn't it be better to keep the distribution small by default now
>>>>>> that it's so easy to just drop transport jars in? I think we should just
>>>>>> include http and local baked in, and then make it dead easy for people to
>>>>>> download and add the others.
>>>>>>
>>>>>> Optionally we could actually start doing what we talked about at the very
>>>>>> beginning of Axis2, releasing profiled builds - embedded, basic, complete,
>>>>>> etc...
>>>>>>
>>>>>> --Glen
>>>>>>
>>>>>>
>
>
--
Thank you!
http://blogs.deepal.org
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Andreas Veithen <an...@gmail.com>.
Transports are configured using parameters added to the corresponding
<transportReceiver> and <transportSender> elements. If the transport
is simply added to the classpath, these elements are placed in
axis2.xml, while in the case of deployment using the transport
deployer, they must be placed in the META-INF/transport.xml file
inside the archive. I guess that you don't expect users to unzip the
transport archive, change transport.xml, rezip it and redeploy it, so
I must have missed something...
Andreas
On Mon, Dec 15, 2008 at 23:51, Deepal Jayasinghe <de...@gmail.com> wrote:
> well it is same as how do you set up services I guess. One thing you
> could do is you can provide parameters though axis2.xml. Or you can
> change them at runtime
> - get the transport sender
> - get the transport description
> - add the configuration
>
> Deepal
>
> On Mon, Dec 15, 2008 at 5:38 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>> Deepal,
>>
>> With the existing transport deployer, how do you handle the case of a
>> transport sender that can be set up without any configuration, but for
>> which the user might want to set some optional parameters later?
>>
>> Andreas
>>
>> On Mon, Dec 15, 2008 at 23:02, Deepal Jayasinghe <de...@gmail.com> wrote:
>>> Not bad,
>>> in fact we have some thing called transport deployer (just like
>>> service deployer) , so if you add the transport deployer into axis2
>>> and specify the location of transport directory. Then you do not need
>>> to have any of the transport in axis2.xml. Everything is automatic :D
>>>
>>> Deepal
>>>
>>> On Mon, Dec 15, 2008 at 4:56 PM, Andreas Veithen
>>> <an...@gmail.com> wrote:
>>>> I think that the default axis2.xml also refers to the TCP sender. BTW,
>>>> wouldn't it be interesting to have a lookup mechanism (like JDK 1.4
>>>> service providers) that automatically adds the transport senders to
>>>> the Axis configuration? That way the default axis2.xml would work out
>>>> of the box with all transport senders that are available in the
>>>> classpath, at least those that don't need configuration.
>>>>
>>>> Andreas
>>>>
>>>> On Mon, Dec 15, 2008 at 22:30, Glen Daniels <gl...@thoughtcraft.com> wrote:
>>>>> Deepal Jayasinghe wrote:
>>>>>>
>>>>>> Well lets add the axis2-transport.jar which has all the transport in it.
>>>>>
>>>>> Hm... Wouldn't it be better to keep the distribution small by default now
>>>>> that it's so easy to just drop transport jars in? I think we should just
>>>>> include http and local baked in, and then make it dead easy for people to
>>>>> download and add the others.
>>>>>
>>>>> Optionally we could actually start doing what we talked about at the very
>>>>> beginning of Axis2, releasing profiled builds - embedded, basic, complete,
>>>>> etc...
>>>>>
>>>>> --Glen
>>>>>
>>>>
>>>
>>
>
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Deepal Jayasinghe <de...@gmail.com>.
well it is same as how do you set up services I guess. One thing you
could do is you can provide parameters though axis2.xml. Or you can
change them at runtime
- get the transport sender
- get the transport description
- add the configuration
Deepal
On Mon, Dec 15, 2008 at 5:38 PM, Andreas Veithen
<an...@gmail.com> wrote:
> Deepal,
>
> With the existing transport deployer, how do you handle the case of a
> transport sender that can be set up without any configuration, but for
> which the user might want to set some optional parameters later?
>
> Andreas
>
> On Mon, Dec 15, 2008 at 23:02, Deepal Jayasinghe <de...@gmail.com> wrote:
>> Not bad,
>> in fact we have some thing called transport deployer (just like
>> service deployer) , so if you add the transport deployer into axis2
>> and specify the location of transport directory. Then you do not need
>> to have any of the transport in axis2.xml. Everything is automatic :D
>>
>> Deepal
>>
>> On Mon, Dec 15, 2008 at 4:56 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>> I think that the default axis2.xml also refers to the TCP sender. BTW,
>>> wouldn't it be interesting to have a lookup mechanism (like JDK 1.4
>>> service providers) that automatically adds the transport senders to
>>> the Axis configuration? That way the default axis2.xml would work out
>>> of the box with all transport senders that are available in the
>>> classpath, at least those that don't need configuration.
>>>
>>> Andreas
>>>
>>> On Mon, Dec 15, 2008 at 22:30, Glen Daniels <gl...@thoughtcraft.com> wrote:
>>>> Deepal Jayasinghe wrote:
>>>>>
>>>>> Well lets add the axis2-transport.jar which has all the transport in it.
>>>>
>>>> Hm... Wouldn't it be better to keep the distribution small by default now
>>>> that it's so easy to just drop transport jars in? I think we should just
>>>> include http and local baked in, and then make it dead easy for people to
>>>> download and add the others.
>>>>
>>>> Optionally we could actually start doing what we talked about at the very
>>>> beginning of Axis2, releasing profiled builds - embedded, basic, complete,
>>>> etc...
>>>>
>>>> --Glen
>>>>
>>>
>>
>
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Andreas Veithen <an...@gmail.com>.
Deepal,
With the existing transport deployer, how do you handle the case of a
transport sender that can be set up without any configuration, but for
which the user might want to set some optional parameters later?
Andreas
On Mon, Dec 15, 2008 at 23:02, Deepal Jayasinghe <de...@gmail.com> wrote:
> Not bad,
> in fact we have some thing called transport deployer (just like
> service deployer) , so if you add the transport deployer into axis2
> and specify the location of transport directory. Then you do not need
> to have any of the transport in axis2.xml. Everything is automatic :D
>
> Deepal
>
> On Mon, Dec 15, 2008 at 4:56 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>> I think that the default axis2.xml also refers to the TCP sender. BTW,
>> wouldn't it be interesting to have a lookup mechanism (like JDK 1.4
>> service providers) that automatically adds the transport senders to
>> the Axis configuration? That way the default axis2.xml would work out
>> of the box with all transport senders that are available in the
>> classpath, at least those that don't need configuration.
>>
>> Andreas
>>
>> On Mon, Dec 15, 2008 at 22:30, Glen Daniels <gl...@thoughtcraft.com> wrote:
>>> Deepal Jayasinghe wrote:
>>>>
>>>> Well lets add the axis2-transport.jar which has all the transport in it.
>>>
>>> Hm... Wouldn't it be better to keep the distribution small by default now
>>> that it's so easy to just drop transport jars in? I think we should just
>>> include http and local baked in, and then make it dead easy for people to
>>> download and add the others.
>>>
>>> Optionally we could actually start doing what we talked about at the very
>>> beginning of Axis2, releasing profiled builds - embedded, basic, complete,
>>> etc...
>>>
>>> --Glen
>>>
>>
>
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Deepal Jayasinghe <de...@gmail.com>.
Not bad,
in fact we have some thing called transport deployer (just like
service deployer) , so if you add the transport deployer into axis2
and specify the location of transport directory. Then you do not need
to have any of the transport in axis2.xml. Everything is automatic :D
Deepal
On Mon, Dec 15, 2008 at 4:56 PM, Andreas Veithen
<an...@gmail.com> wrote:
> I think that the default axis2.xml also refers to the TCP sender. BTW,
> wouldn't it be interesting to have a lookup mechanism (like JDK 1.4
> service providers) that automatically adds the transport senders to
> the Axis configuration? That way the default axis2.xml would work out
> of the box with all transport senders that are available in the
> classpath, at least those that don't need configuration.
>
> Andreas
>
> On Mon, Dec 15, 2008 at 22:30, Glen Daniels <gl...@thoughtcraft.com> wrote:
>> Deepal Jayasinghe wrote:
>>>
>>> Well lets add the axis2-transport.jar which has all the transport in it.
>>
>> Hm... Wouldn't it be better to keep the distribution small by default now
>> that it's so easy to just drop transport jars in? I think we should just
>> include http and local baked in, and then make it dead easy for people to
>> download and add the others.
>>
>> Optionally we could actually start doing what we talked about at the very
>> beginning of Axis2, releasing profiled builds - embedded, basic, complete,
>> etc...
>>
>> --Glen
>>
>
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Andreas Veithen <an...@gmail.com>.
I think that the default axis2.xml also refers to the TCP sender. BTW,
wouldn't it be interesting to have a lookup mechanism (like JDK 1.4
service providers) that automatically adds the transport senders to
the Axis configuration? That way the default axis2.xml would work out
of the box with all transport senders that are available in the
classpath, at least those that don't need configuration.
Andreas
On Mon, Dec 15, 2008 at 22:30, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Deepal Jayasinghe wrote:
>>
>> Well lets add the axis2-transport.jar which has all the transport in it.
>
> Hm... Wouldn't it be better to keep the distribution small by default now
> that it's so easy to just drop transport jars in? I think we should just
> include http and local baked in, and then make it dead easy for people to
> download and add the others.
>
> Optionally we could actually start doing what we talked about at the very
> beginning of Axis2, releasing profiled builds - embedded, basic, complete,
> etc...
>
> --Glen
>
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Deepal Jayasinghe <de...@gmail.com>.
No problem. :),
yes having small part make the job easier.
Deepal
On Mon, Dec 15, 2008 at 4:30 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Deepal Jayasinghe wrote:
>>
>> Well lets add the axis2-transport.jar which has all the transport in it.
>
> Hm... Wouldn't it be better to keep the distribution small by default now
> that it's so easy to just drop transport jars in? I think we should just
> include http and local baked in, and then make it dead easy for people to
> download and add the others.
>
> Optionally we could actually start doing what we talked about at the very
> beginning of Axis2, releasing profiled builds - embedded, basic, complete,
> etc...
>
> --Glen
>
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Deepal Jayasinghe wrote:
> Well lets add the axis2-transport.jar which has all the transport in it.
Hm... Wouldn't it be better to keep the distribution small by default
now that it's so easy to just drop transport jars in? I think we should
just include http and local baked in, and then make it dead easy for
people to download and add the others.
Optionally we could actually start doing what we talked about at the
very beginning of Axis2, releasing profiled builds - embedded, basic,
complete, etc...
--Glen
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Deepal Jayasinghe <de...@gmail.com>.
Well lets add the axis2-transport.jar which has all the transport in it.
Deepal
On Mon, Dec 15, 2008 at 2:20 PM, Jarek Gawor <jg...@gmail.com> wrote:
> Yes. I added the basic transport modules to the bin distribution
> (local, tcp, and http).
>
> Jarek
>
> On Mon, Dec 15, 2008 at 2:57 AM, Irantha <ir...@wso2.com> wrote:
>> When I tried to run axis2server.bat from extracted axis2-SNAPSHOT-bin.zip
>> (created with: mvn -Drelease install). I got ClassNotFoundException:
>> org.apache.axis2.transport.tcp.TCPT
>> ransportSender.
>>
>> I had to manually copy axis2-transports-SNAPSHOT.jar from commons-transport
>> build to AXIS2_HOME/lib.
>> Don't we need to include commons-transport jar with axis2 release artifacts?
>>
>> Thanks,
>> Irantha
>>
>> [FATAL] [SimpleAxisServer] Shutting down. Error starting SimpleAxisServer
>> org.apache.axis2.deployment.DeploymentException:
>> org.apache.axis2.transport.tcp.
>> TCPTransportSender
>> at
>> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders
>> (AxisConfigBuilder.java:694)
>> at
>> org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConf
>> igBuilder.java:121)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguratio
>> n(DeploymentEngine.java:707)
>> at
>> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfigurati
>> on(FileSystemConfigurator.java:116)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
>> ionContext(ConfigurationContextFactory.java:64)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
>> ionContextFromFileSystem(ConfigurationContextFactory.java:206)
>> at
>> org.apache.axis2.transport.SimpleAxis2Server.<init>(SimpleAxis2Server
>> .java:47)
>> at
>> org.apache.axis2.transport.SimpleAxis2Server.main(SimpleAxis2Server.j
>> ava:98)
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.axis2.transport.tcp.TCPT
>> ransportSender
>> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:169)
>> at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
>> at
>> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders
>> (AxisConfigBuilder.java:669)
>> ... 7 more
>> [SimpleAxisServer] Shutting down. Error starting SimpleAxisServer
>>
>>
>>
>>
>
Re: commons-transport jar not included in axis2-SNAPSHOT-bin.zip
Posted by Jarek Gawor <jg...@gmail.com>.
Yes. I added the basic transport modules to the bin distribution
(local, tcp, and http).
Jarek
On Mon, Dec 15, 2008 at 2:57 AM, Irantha <ir...@wso2.com> wrote:
> When I tried to run axis2server.bat from extracted axis2-SNAPSHOT-bin.zip
> (created with: mvn -Drelease install). I got ClassNotFoundException:
> org.apache.axis2.transport.tcp.TCPT
> ransportSender.
>
> I had to manually copy axis2-transports-SNAPSHOT.jar from commons-transport
> build to AXIS2_HOME/lib.
> Don't we need to include commons-transport jar with axis2 release artifacts?
>
> Thanks,
> Irantha
>
> [FATAL] [SimpleAxisServer] Shutting down. Error starting SimpleAxisServer
> org.apache.axis2.deployment.DeploymentException:
> org.apache.axis2.transport.tcp.
> TCPTransportSender
> at
> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders
> (AxisConfigBuilder.java:694)
> at
> org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConf
> igBuilder.java:121)
> at
> org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguratio
> n(DeploymentEngine.java:707)
> at
> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfigurati
> on(FileSystemConfigurator.java:116)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
> ionContext(ConfigurationContextFactory.java:64)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
> ionContextFromFileSystem(ConfigurationContextFactory.java:206)
> at
> org.apache.axis2.transport.SimpleAxis2Server.<init>(SimpleAxis2Server
> .java:47)
> at
> org.apache.axis2.transport.SimpleAxis2Server.main(SimpleAxis2Server.j
> ava:98)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.axis2.transport.tcp.TCPT
> ransportSender
> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:169)
> at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
> at
> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders
> (AxisConfigBuilder.java:669)
> ... 7 more
> [SimpleAxisServer] Shutting down. Error starting SimpleAxisServer
>
>
>
>