i did get this error:
java.lang.NoSuchMethodError:
org.apache.commons.collections.IteratorUtils.emptyIterator()Lorg/apache/
commons/collections/ResettableIterator;
org.apache.commons.configuration.PropertyConverter.toIterator(PropertyCo
nverter.java:632)
So there was a commons-collections deployed somewhere, but probably an
older version...that!s the jboss classloader,it is not exclusive to the
deployed app but more or less acts on a first come first serve basis, so
some app had allready grapped the IteratorUtils of the older archive and
now it's number one in the class repository. If you move a library from
your app to server/default/lib it climbs in hierachy in jboss(so far
what I remember of the JBoss Classloader)
The other thing I did, was to comment out the plexus logmanager
component in application.xml so that continuum now logs to server.log
(logging seems to be a bit of a mistery in continuum with this always
empty $appserver.base/logs directory anyway)
I did not have to apply your patch with CommonsConfigurationRegistry
cause the *.pom file of my repository point to an older version where
the original application.xml entry is still valid...
-----Original Message-----
From: Thierry Lach [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 2:56 PM
To: [email protected]
Subject: Re: JBoss Support
It appears that JBoss 4.0.5.GA (which I'm using) includes
commons-collections.jar in the lib directory, and according to the
manifest it is version 3.1. I'll add your comment to the instructions
page.
Did you have to change application.xml because of the plexus
configuration issue?
Also - what sort of error were you getting (I want to provide that on
the web page also)?
On 2/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> a bit different than Thierry's solution (on JBoss 4.0.1SP1): I had to
> move commons-collections-3.0.jar from continuum.war/WEB-INF/lib to
> JBOSS_HOME/server/default/lib. Now I see the create admin page at last
> ;-)
>
> Knowing the JBoss classloading system a bit, I will probably run into
> some classloading issues on a hot deploy too..
>
> -----Original Message-----
> From: Thierry Lach [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 15, 2007 9:58 PM
> To: [email protected]
> Subject: Re: JBoss Support
>
> SUCCESS!
>
> OK it looks like the root cause is the inability to find class
> org.codehaus.plexus.registry.CommonsConfigurationRegistry. I think
> the correct class name should be
> org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.
> since that is what is contained in the plexus-registry-commons jar.
> I've changed the implementation name in the file
> continuum-webapp/src/main/resources/META-INF/plexus/application.xml
> and it seems to work now - I've been able to configure it and am now
> running a
> maven1 build. I'll update the patch sometime this evening to include
> the change to application.xml.
>
>
> On 2/15/07, Thierry Lach <[EMAIL PROTECTED]> wrote:
> >
> > Yep - my rejoicing was a little premature it seems. War deploy
> > seems to behave fine but the website itself doesn't get up and run.
> >
> > On 2/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
> > >
> > > allright here we go:
> > > with these two datasources things start moving the right direction
> > >
> >
> > <snip/>
> >
> > -----Original Message-----
> > > From: Hilco Wijbenga [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, February 15, 2007 6:39 PM
> > > To: [email protected]
> > > Subject: Re: JBoss Support
> > >
> > > On 2/15/07, Thierry Lach <[EMAIL PROTECTED] > wrote:
> > > > Can you post the contents of your derby-ds.xml file please? I'm
> > > > guessing that the example I used for the Continuum+on_JBoss
> > > > example isn't correct enough for continuum.
> > >
> > > See http://docs.codehaus.org/display/MAVENUSER/Archiva+on+JBoss
> > >
> > > There used to be something similar for Continuum. I think your
> > > JNDI name is wrong; all the silly stuff (comp/env/jdbc/) will be
> > > added by
>
> > > JBoss ... IIRC, it's been a while. :-)
> > >
> >
> >
>
