I did some dependency cleanup in upstream dependencies (Axis2 and
Rampart) and probably the TCP transport is no longer a transitive
dependency of Synapse. We need to decide if we want to bundle it with
Synapse (in which case it should be added as a dependency to the
distribution) or not (in which case we should comment it out in the
axis2.xml).

Andreas

On Tue, Mar 17, 2009 at 10:09, Hiranya Jayathilaka <[email protected]> wrote:
> OK. Apparently some changes are made to the parent POM in the trunk.  The
> parent POM refers to  a set of specific transport jars now. And TCP
> transport jar is not specified as a dependency. So I guess we need to add
> that.
>
> Thanks,
> Hiranya
>
> On Tue, Mar 17, 2009 at 2:33 PM, Hiranya Jayathilaka <[email protected]>
> wrote:
>>
>> Usually when the Synapse trunk is built axis2-transport-tcp jar falls into
>> the lib directory. I don't think anything changed drastically in our POM to
>> prevent this jar from being downloaded. Could it be due to a change outside
>> Synapse?
>>
>> Thanks,
>> Hiranya
>>
>> On Tue, Mar 17, 2009 at 2:30 PM, Charith Wickramarachchi
>> <[email protected]> wrote:
>>>
>>> Asanka I was wondering what is the correct way of resolving it ?is it
>>> putting TCP transport as a dependency or making the client depend only http
>>> transport in the default  case ?
>>>
>>> thank you,
>>> Charith
>>>
>>>
>>> On Tue, Mar 17, 2009 at 2:24 PM, Asanka Abeysinghe <[email protected]>
>>> wrote:
>>>>
>>>> I do get the same issue in the trunk.
>>>> - Asanka
>>>> Hiranya Jayathilaka wrote:
>>>>
>>>> That's odd. I haven't encountered this situation ever with the trunk. I
>>>> believe axis2-transports dependency is in the parent POM which should take
>>>> care of adding all the necessary transports jars. Is anybody else
>>>> experiencing the same problem?
>>>>
>>>> Thanks,
>>>> Hiranya
>>>>
>>>> On Tue, Mar 17, 2009 at 1:52 PM, Charith Wickramarachchi
>>>> <[email protected]> wrote:
>>>>>
>>>>> HI devs,
>>>>>
>>>>> while trying to run the Synapse sample client in synapse trunk as
>>>>> follows
>>>>>
>>>>>  ant stockquote
>>>>> -Daddurl=http://localhost:8280/axis2/services/StockQuoteProxy
>>>>>
>>>>> i got a ClassNotfound exception
>>>>>
>>>>>      [java] org.apache.axis2.deployment.DeploymentException:
>>>>> org.apache.axis2.transport.tcp.TCPTransportSender
>>>>>      [java]     at
>>>>> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:694)
>>>>>      [java]     at
>>>>> org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:121)
>>>>>      [java]     at
>>>>> org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:707)
>>>>>      [java]     at
>>>>> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116)
>>>>>      [java]     at
>>>>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
>>>>>      [java]     at
>>>>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:206)
>>>>>      [java]     at
>>>>> samples.userguide.StockQuoteClient.executeClient(Unknown Source)
>>>>>      [java]     at samples.userguide.StockQuoteClient.main(Unknown
>>>>> Source)
>>>>>      [java] Caused by: java.lang.ClassNotFoundException:
>>>>> org.apache.axis2.transport.tcp.TCPTransportSender
>>>>>
>>>>> this is because the axis2 tcp transport jar is missing in the class
>>>>> path
>>>>> and they are not defined in the parent pom
>>>>>
>>>>> this can be solved by adding these jars to the classpath (by defining
>>>>> in the pom)
>>>>>
>>>>> thanks you,
>>>>>
>>>>> Charith
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Charith Dhanushka Wickramarachchi
>>>>> http://charithwiki.blogspot.com/
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Charith Dhanushka Wickramarachchi
>>> http://charithwiki.blogspot.com/
>>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to