-
1. Re: problems with latest snapshot
yyi2133 Jul 28, 2004 3:16 AM (in response to yyi2133)hmmm... I managed my self to solve the "servlet" problem placing the servlet.jar in some directory and modifying the libraries.ent file... but now I have problems with some other "missing classes" from JBoss JMX core...
It sounds strage... something like the JBOSS_HOME is not recognized and used... but it's there! always there... and I've never had problems building all the other snapshots....
any idea? -
2. Re: problems with latest snapshot
yyi2133 Jul 28, 2004 3:27 AM (in response to yyi2133)Here again :-)
now, searching in the forum for some JBOSS_HOME issue I've found a post about JBoss version and Nukes.
Is it true that Nukes works only on JBoss 3.2.3?
We have Jboss 3.2.5 in production now... is it possible to compile it with Jboss3.2.3 and make it work with a 3.2.5? ... or when it will be available in the 3.2.5? (3.2.3 is no longer available from the site) -
3. Re: problems with latest snapshot
julien1 Jul 28, 2004 4:27 AM (in response to yyi2133)we should upgrade nukes 1.1 to 3.2.5, otherwise it works only with 3.2.3
-
4. Re: problems with latest snapshot
starmanrg Jul 28, 2004 9:14 AM (in response to yyi2133)I was trying Nukes 1.0 with JB3.2.3 for a department intranet. I'm now evaluating JB4.0/Hibernate for a new enterprise architecture.
I was thinking of using Nukes as a web platform to develop a vertical slice of our application, to be a proof of concept for the new architecture. Will Nukes 1.1 run with JBoss 4.0?
Starman -
5. Re: problems with latest snapshot
julien1 Jul 28, 2004 9:22 AM (in response to yyi2133)nukes 2.0 (under developement) will
-
6. Re: problems with latest snapshot
jae77 Jul 28, 2004 11:40 AM (in response to yyi2133)"cooper" wrote:
we should upgrade nukes 1.1 to 3.2.5, otherwise it works only with 3.2.3
i looked at this the other day, and the biggest issue is that the org.jboss.mx.interceptor.Invocation class no longer exists. i tried to change it to use the org.jboss.mx.server.Invocation class, but i keep getting null pointer exceptions when deploying.
here are the rest of the changes i made as well:org.jboss.nukes.component NukesBuilder - convert MBeanAttributeInterceptor to ModelMBeanAttributeInterceptor - synced ModelMBeanConstants variable names org.jboss.nukes.handler NukesImpl - added stubbed impls for missing methods - removed throws exception from setCharacterEncoding org.jboss.nukes.utils Tools.java - removed jdom import statements org.jboss.nukes.system JDBCPersistenceManager - synced ModelMBeanConstants variable names
i'm not sure what the direction for this should be given work on nukes 2.0 is occurring.
on a side note, i'm in the process of moving back to nyc and starting a new job, so (most likely) i won't be able to put in any time on this until the beginning of september.