On 10/1/07, Dinesh Shahane <[EMAIL PROTECTED]> wrote:
>
> The dependency is due to programmatic startup of ActiveMQ broker. We need
> it
> for SOAP/JMS and JMS binding tests unless we require the broker to be
> started manually from the command line.
>
>
> > -----Original Message-----
> > From: Simon Laws [mailto:[EMAIL PROTECTED]
> > Sent: Monday, October 01, 2007 11:36 AM
> > To: [email protected]
> > Subject: Re: Strange behavior with helloworld-ws-service and it's
> ActiveMQ
> > dependency.
> >
> > On 10/1/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> > >
> > > Simon Laws wrote:
> > > > On 9/28/07, Dinesh Shahane <[EMAIL PROTECTED]> wrote:
> > > >
> > > >> I saw this error when I was trying to build just this module but it
> > > went
> > > >> away when I did a full build.
> > > >>
> > > >> I do see another error now at runtime (NoClassDefFound) in this
> > module.
> > > It
> > > >> could be due to scope=test
> > > >>
> > > >> Helloworld-ws-service/pom.xml
> > > >>
> > > >>         <dependency>
> > > >>             <groupId>org.apache.activemq</groupId>
> > > >>             <artifactId>apache-activemq</artifactId>
> > > >>             <version>4.1.1</version>
> > > >>             <scope>test</scope>
> > > >>         </dependency>
> > > >>
> > > >> It works fine once I change the scope to runtime.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: Luciano Resende [mailto:[EMAIL PROTECTED]
> > > >>> Sent: Friday, September 28, 2007 9:54 AM
> > > >>> To: tuscany-dev
> > > >>> Subject: Strange behavior with helloworld-ws-service and it's
> > ActiveMQ
> > > >>> dependency.
> > > >>>
> > > >>> Anyone seeing this :
> > > >>>
> > > >>> [INFO] Compilation failure
> > > >>>
> > > >>>
> > >
> D:\dev\Opensource\Apache\Tuscany\source\java\sca\samples\helloworld-ws-
> > > >>> service\src\main\java\helloworld\HelloWorldJmsServer.java:[22,34]
> > > >>> package org.apache.activemq.
> > > >>> broker does not exist
> > > >>>
> > > >>>
> > >
> D:\dev\Opensource\Apache\Tuscany\source\java\sca\samples\helloworld-ws-
> > > >>> service\src\main\java\helloworld\HelloWorldJmsServer.java:[33,8]
> > > >>> cannot find symbol
> > > >>> symbol  : class BrokerService
> > > >>> location: class helloworld.HelloWorldJmsServer
> > > >>>
> > > >>>
> > >
> D:\dev\Opensource\Apache\Tuscany\source\java\sca\samples\helloworld-ws-
> > > >>> service\src\main\java\helloworld\HelloWorldJmsServer.java:[33,35]
> > > >>> cannot find symbol
> > > >>> symbol  : class BrokerService
> > > >>> location: class helloworld.HelloWorldJmsServer
> > > >>>
> > > >>>
> > > >>> It's strange, as I do see the ActiveMQ jar and the offending class
> > in
> > > >>> place.
> > > >>>
> > > >>> --
> > > >>> Luciano Resende
> > > >>> Apache Tuscany Committer
> > > >>> http://people.apache.org/~lresende
> > > >>> http://lresende.blogspot.com/
> > > >>>
> > > >>>
> --------------------------------------------------------------------
> > -
> > > >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > >>> For additional commands, e-mail: [EMAIL PROTECTED]
> > > >>>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > >> For additional commands, e-mail: [EMAIL PROTECTED]
> > > >>
> > > >> I'm seeing this this morning but this is the first time. Been
> > > >>
> > > > compiling/running OK over the last few days with these JMS changes.
> I
> > > had to
> > > > change the ActiveMQ dependency to a "provided" dependency to get
> past
> > > it.
> > > > This seems right as there are compile time dependencies on some
> > ActiveMQ
> > > > classes. I don't understand how it was working before though.
> > > >
> > > > Simon
> > > >
> > > >
> > >
> > > My 2c, if I'm going to use just SOAP/HTTP in an application I probably
> > > won't want to carry a dependency on ActiveMQ, so it would be better to
> > > not have this dependency...
> > >
> > > I've not followed this too closely, but didn't we enable support for
> > > SOAP/JMS recently? couldn't that change have triggered this?
> > >
> > > --
> > > Jean-Sebastien
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > > Yes, that's what introduced the dependency. We need to take a look at
> > the
> > code to see if we can remove the dependency except in the case that you
> > have
> > selected the JMS transport.
> >
> > Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> So I think Dinesh is right. I.e. the dependency is only required in the
tests as the MQ broker is being started. What is a little confusing is that
there is a warning where Axis is complaining that the JMS transport is not
completely configured in the case that JMS is not being used. Not related to
a dependency on ActiveMQ but gives the impression that it is missconfigured

Simon

Reply via email to