[Installation, Configuration & DEPLOYMENT] - Problem with JAXB when upgrading to JBoss 4.2.2
by ssinger
I'm having a problem and I am ripping my hair out trying to resolve!
We have an application that uses JSXB to marshall XML objects. We're using "jaxb-rt-1.0-ea.jar" and we include the JAR file in the application and in the CLASSPATH. Works perfectly in 4.0.4.
I'm trying to get the application up in 4.2.2GA, and I get the following error:
java.lang.NoSuchFieldError: INITIAL_COLOR
javax.xml.bind.ValidatableObject.(ValidatableObject.java:32)
javax.xml.bind.MarshallableObject.(MarshallableObject.java:54)
javax.xml.bind.MarshallableRootElement.(MarshallableRootElement.java:97)
This type of thing almost always happens when there is a mismatch between the classes it is compiled against as opposed to run against. However, I checked, and these classes exist only in "jaxb-rt-1.0-ea.jar" and nowhere else within JBoss. "jaxb-rt-1.0-ea.jar" is still inthe application, and in the CLASSPATH.
Anybody have any idea what might be happening? Hopefully, it's just something dumb I'm doing.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168806#4168806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168806
17 years, 8 months
[JBoss Tools (users)] - Re: jboss-seam.jar is packaged into jboss-seam.jar when adde
by skirilo
The problem seems to me comes from this exception. Probably Seam publisher classes (like JstPublisher) are not even initialized. Does anybody have such problem?
!ENTRY org.eclipse.wst.server.core 4 0 2008-08-05 20:14:37.687
!MESSAGE Error calling delegate setupLaunchConfiguration() GlassFish V2
!STACK 0
java.lang.NullPointerException
at org.eclipse.jst.server.generic.internal.xml.Resolver.skipToProperty(Resolver.java:103)
at org.eclipse.jst.server.generic.internal.xml.Resolver.resolvePropertiesFromCache(Resolver.java:90)
at org.eclipse.jst.server.generic.internal.xml.Resolver.resolveProperties(Resolver.java:68)
at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.getStartClassName(GenericServerBehaviour.java:259)
at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.setupLaunchConfiguration(GenericServerBehaviour.java:354)
at org.eclipse.wst.server.core.internal.Server.setupLaunchConfiguration(Server.java:1419)
at org.eclipse.wst.server.core.internal.Server.getLaunchConfiguration(Server.java:1462)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:2637)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:2590)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:260)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168801#4168801
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168801
17 years, 8 months
[EJB/JBoss] - Re: Annoying log warning:
by jonathanztaub
I was able to reproduce this - it basically happens when I rollback a transaction. There are some files created under %JBOSS_HOME%\server\default\data\tx-object-store. I'm not sure whether this is JMS related at all.
However, I still don't quite understand what the problem is and the logs are quite annoying. I searched elsewhere on the internet, and found other people running into this logging statement, but none had any pointers as to what the problem is.
Perhaps, and correct me if I'm wrong, XA has to do with 2pc, and having a JMS transaction resource with a database (JDBC) causes some issues. I'll try creating a database insert failure and a rollback inside another bean, which is outside the scope of JMS, and see whether the problem manifests itself there as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168796#4168796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168796
17 years, 8 months
[Installation, Configuration & DEPLOYMENT] - Re: Deploying ZIP/JAR files issue
by PeterJ
The location of the file is no exactly what I would expect:
C:/build-capri/eds-server/deploy/Raw+Data+Load/dataload/xml/1996_update.zip
Typically, the directory structure is server/xxx/deploy. Did you update the URLlist, and if so, what did youy update it to?
Also, this part of the path is suspect: Raw+Data+Load. Is this really "Raw Data Load", with spaces? If so, either move the ZIP file into a path without space or rename the directory so it no longer has spaces. Spaces in paths can give some Java libraries fits. (If the directory really does contain the plus signs, try removing them and see if it helps.)
The sources are available from the same web page where you downloaded the binary.
Finally, what version of JBossAS are you using.
By the way, Jaikiran asked you to run the jar utility to ensure that the ZIP file was readable. In the past we have encountered people who use various other utilities (such a WinRAR) to create ZIP files and those files were incompatible with Java.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168790#4168790
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168790
17 years, 8 months