Thanks.  It seems that the offending dependency is Lingo.  When I add the
following two exclusions to the Lingo 1.3 dependency I get past the
NoSuchMethodError problems:

            <exclusions>
                <exclusion>
                    <groupId>geronimo</groupId>
                    <artifactId>geronimo-connector</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>geronimo</groupId>
                    <artifactId>geronimo-transaction</artifactId>
                </exclusion>
            </exclusions>


Unfortunately I now have a different problem with ActiveMQ/TranQL
(ClassCastException), but that's another topic for another thread.

Thanks again for your help with this issue.


--James


gnodet wrote:
> 
> Yes, you can use mvn -X to see (it's not so easy) where the 1.0 geronimo
> jars come from (they are transitive dependencies) and explicitely exclude
> them.
> The problem comes from the fact that the groupId has changed, so that
> maven
> does not recognize that geronimo-connector-1.0.jar and
> geronimo-connector-1.2-beta.jar
> are two different versions of the same jar (you should have only one
> in the classpath).
> 
> On 1/22/07, James Adams <[EMAIL PROTECTED]> wrote:
>>
>> I don't have a dependency for Geronimo in my pom.xml and my assumption is
>> that I'm using whatever Geronimo JARs are specified as dependencies for
>> Jencks 2.0 (plus any other Geronimo dependencies from other projects such
>> as
>> ActiveMQ and TranQL).  When I look at the list of external libraries in
>> my
>> Eclipse project I see the following Geronimo JARs:
>>
>> geronimo-connector-1.0.jar
>> geronimo-connector-1.2-beta.jar
>> geronimo-ejb_2.1_spec-1.0.1.jar
>> geronimo-j2ee-connector_1.5_spec-1.0.jar
>> geronimo-j2ee-management_1.0_spec-1.0.jar
>> geronimo-jms_1.1_spec-1.0.jar
>> geronimo-jta_1.0.1B_spec-1.0.1.jar
>> geronimo-transaction-1.0.jar
>> geronimo-transaction-1.2-beta.jar
>>
>>
>> I'm using the below dependencies in my pom.xml:
>>
>>         <!-- Jencks -->
>>         <dependency>
>>             <groupId>org.jencks</groupId>
>>             <artifactId>jencks</artifactId>
>>             <version>2.0</version>
>>             <scope>runtime</scope>
>>         </dependency>
>>
>>         <!-- TranQL -->
>>         <dependency>
>>             <groupId>org.tranql</groupId>
>>             <artifactId>tranql</artifactId>
>>             <version>1.4-SNAPSHOT</version>
>>         </dependency>
>>         <dependency>
>>             <groupId>org.tranql</groupId>
>>             <artifactId>tranql-connector</artifactId>
>>             <version>1.3-SNAPSHOT</version>
>>         </dependency>
>>
>>         <!-- ActiveMQ -->
>>         <dependency>
>>             <groupId>activemq</groupId>
>>             <artifactId>activemq</artifactId>
>>             <version>4.1.0</version>
>>             <scope>compile</scope>
>>         </dependency>
>>         <dependency>
>>             <groupId>org.apache.activemq</groupId>
>>             <artifactId>activemq-ra</artifactId>
>>             <version>4.1.0-incubator</version>
>>         </dependency>
>>
>>         <!-- Lingo -->
>>         <dependency>
>>             <groupId>org.logicblaze.lingo</groupId>
>>             <artifactId>lingo</artifactId>
>>             <version>1.3</version>
>>         </dependency>
>>
>>
>> Is it possible that another project's Geronimo dependencies are taking
>> precedence in the classpath ahead of the Geronimo JARs needed by the
>> Jencks
>> dependency in my project, and because they're older versions of the JARs
>> then a class will be found in the older JAR but the expected/updated
>> method
>> signature will not be?
>>
>>
>> --James
>>
>>
>>
>> gnodet wrote:
>> >
>> > Which version of geronimo jars do you use ?
>> > You need a version >= 1.2-beta
>> >
>> > On 1/22/07, James Adams <[EMAIL PROTECTED]> wrote:
>> >>
>> >> I have set up my application for Outbound JMS with Jencks 2.0 but I am
>> >> getting a NoSuchMethodError with the Geronimo GenericConnectionManager
>> >> when
>> >> Spring tries to instantiate the connectionManager bean.  Following the
>> >> exception stack trace is the Spring configuration file.  Can anyone
>> >> advise
>> >> me as to what the problem might be?
>> >>
>> >> --James
>> >>
>> >>
> 
> -- 
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Outbound-JMS%3A--NoSuchMethodError%3A-Geronimo%27s-GenericConnectionManager.%3Cinit%3E-tf3060055.html#a8514421
Sent from the jencks - user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to