Chris, I also had to comment out the following dependencies since they get
excluded from .sar anyway, but I get complains from Maven, which cannot find
these jars.

<!--dependency>
      <groupId>jboss</groupId>
      <artifactId>jboss-system</artifactId>
      <version>${jboss-version}</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>jboss</groupId>
      <artifactId>jboss-jmx</artifactId>
      <version>${jboss-version}</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>jboss</groupId>
      <artifactId>jboss-common</artifactId>
      <version>${jboss-version}</version>
      <scope>provided</scope>
    </dependency-->


Chris Custine (Apache) wrote:
> 
> For a quick fix to get the JBoss deployer working with newer ServiceMix
> versions (3.2+), add these lines to the list of exclusions under
> servicemix-core in the pom.xml and rebuild the JBoss deployer:
> 
>         <exclusion>
>           <groupId>org.apache.geronimo.specs</groupId>
>           <artifactId>geronimo-jta_1.1_spec</artifactId>
>         </exclusion>
>         <exclusion>
>           <groupId>commons-logging</groupId>
>           <artifactId>commons-logging-api</artifactId>
>         </exclusion>
> 
> with these additions you can use the JBoss deployer with any of the 3.2
> and
> 3.3 ServiceMix builds by changing the servicemix-version property at the
> top
> of the pom.xml file.
> 
> Thanks,
> Chris
> 
> On Jan 25, 2008 6:24 PM, Chris Custine <[EMAIL PROTECTED]> wrote:
> 
>> I am doing some work on the JBoss deployer and I have fixes ready to make
>> it work with ServiceMix 3.2 and 3.3 (trunk) builds among other things.  I
>> will post more information here when I figure out what to do with the
>> code.
>>
>> Thanks,
>> Chris
>>
>>
>> On Dec 10, 2007 12:20 PM, Andreas Schaefer
>> <[EMAIL PROTECTED]>
>> wrote:
>>
>> > You probably have a class loader issue at hand because the
>> > TransactionManagerDelegate does implement TransactionManager.
>> >
>> > What is happening here is that the class loader for the
>> > TransactionManager is different between JBoss and ServiceMix. Normally
>> > ServiceMix embedded inside JBoss should use the JBoss library because
>> > it is delegating to the parent class loader first but that seems not
>> > to be happening.
>> >
>> > For further investigation you need to print out the class loader of
>> > the ServiceMix TransactionManager with:
>> > TransactionManager.class.getClassLoader() and the class loader of the
>> > TM of JBoss with: tm.getClass().getClassLoader() where 'tm' is the
>> > variable that JBIContainer gets.
>> >
>> > Hope it helps
>> >
>> > Andreas Schaefer
>> > CEO of Madplanet.com Inc.
>> > [EMAIL PROTECTED]
>> >
>> >
>> > On Dec 10, 2007, at 10:37 AM, dipali.kucheria wrote:
>> >
>> > >
>> > > Im trying to integrate ServiceMix 3.2.1 with JBoss 4.2.1 based on
>> > > following
>> > > http://servicemix.apache.org/jboss-integration.html
>> > >
>> > > I managed to build the Jboss Deployer (not without a few maven
>> > > issues) and
>> > > deployed it on Jboss 4.2.1 , only to realise that this was using
>> > > ServiceMix
>> > > 3.1.2 internally and Jboss 4.0.5.
>> > > I rebuilt with
>> > > <servicemix-version>3.2.1</servicemix-version>
>> > > <jboss-version>4.2.1</jboss-version>
>> > >
>> > > and the deployer is giving following error :
>> > >
>> > > 2007-12-10 12:19:05,551 DEBUG
>> > > [org.servicemix.jboss.deployment.JBIService]
>> > > Starting failed org.servicemix:service=JBIService
>> > > java.lang.ClassCastException:
>> > > com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate
>> > >       at
>> > > org
>> > > .apache
>> > > .servicemix
>> > > .jbi.container.JBIContainer.setTransactionManager(JBIContainer.java:
>> > > 794)
>> > >       at
>> > > org
>> > > .servicemix.jboss.deployment.JBIService.startService(JBIService.java:
>> > > 235)
>> > >       at
>> > > org
>> > > .jboss
>> > > .system
>> > > .ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
>> > >       at
>> > > org
>> > > .jboss
>> > > .system
>> > > .ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:
>> > > 245)
>> > >       at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>> > >       at
>> > > sun
>> > > .reflect
>> > > .DelegatingMethodAccessorImpl
>> > > .invoke(DelegatingMethodAccessorImpl.java:25)
>> > >       at java.lang.reflect.Method.invoke(Method.java:585)
>> > >       at
>> > > org
>> > > .jboss
>> > > .mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:
>> > > 155)
>> > >       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
>> > >       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>> > >       at
>> > > org
>> > > .jboss
>> > > .mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>> > >       at org.jboss.mx.server.MBeanServerImpl.invoke(
>> > MBeanServerImpl.java:
>> > > 659)
>> > >       at
>> > > org.jboss.system.ServiceController
>> > > $ServiceProxy.invoke(ServiceController.java:978)
>> > >       at $Proxy0.start(Unknown Source)
>> > >       at org.jboss.system.ServiceController.start(
>> > ServiceController.java:
>> > > 417)
>> > >
>> > > Any pointers ? Anyone who can help me unravel this ?
>> > > --
>> > > View this message in context:
>> >
>> http://www.nabble.com/ServiceMix-3.2.1-with-JBoss-4.2.1-tp14258796s12049p14258796.html
>> > > Sent from the ServiceMix - User mailing list archive at Nabble.com.
>> > >
>> >
>> >
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/ServiceMix-3.2.1-with-JBoss-4.2.1-tp14258796p17408508.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to