Thanks for the information Dave.  I don't know much about the jar 
conflict you describe -- it could be a bug or just an item that needs to 
be documented on the wiki.  I'll let Andy, Alan or Vince respond -- I'm 
sure they have an inkling here.

In the meantime (so it won't be forgotten), I would suggest you file a 
bug report on this here (like New Issue -- upper right of the navigation):

http://code.google.com/p/openbluedragon/issues/list

If it's not a bug, then can be moved to be documented instead.  Thanks 
for snooping about and providing a possible reason on what needed to be 
done to get things working correctly.

Best,
.Peter

Dave said the following on 07/27/2009 06:59 PM:
> Good Morning,
>
> I've been playing with openbd1.1, JBoss 4.2.3 and Apache 2.2 on centOS
> 5.3 without any issues in a development environment with a view to
> migrating to either openBD or Railo in production from Coldfusion 7.
>
> There are plenty of posts in various blogs regarding Railo and JBoss
> 5.x and removing various jar files from ./WEB-INF/lib to deploy Railo
> successfully.
>
> Today I thought I'd throw openbd1.1.war (extracted) into the deploy
> folder of JBoss 5.1 and see what happens.  As expected the deployment
> failed with the error
>
> 2009-07-28 17:40:24,552 ERROR [org.apache.catalina.core.ContainerBase.
> [jboss.web
> ].[localhost].[/bluedragon]] (main) StandardWrapper.Throwable
> java.lang.LinkageError: loader constraint violation: when resolving
> method "java
> x.xml.parsers.DocumentBuilder.parse(Lorg/xml/sax/InputSource;)Lorg/w3c/
> dom/Docum
> ent;" the class loader (instance of org/jboss/classloader/spi/base/
> BaseClassLoad
> er) of the current class, com/naryx/tagfusion/xmlConfig/
> xmlConfigManager, and th
> e class loader (instance of <bootloader>) for resolved class, javax/
> xml/parsers/
> DocumentBuilder, have different Class objects for the type org/xml/sax/
> InputSour
> ce used in the signature
>         at com.naryx.tagfusion.xmlConfig.xmlConfigManager.<init>
> (Unknown Source)
>         at
> com.naryx.tagfusion.xmlConfig.xmlConfigManagerFactory.createXmlConfig
> Manager(Unknown Source)
>         at com.naryx.tagfusion.cfm.engine.cfEngine.<init>(Unknown
> Source)
>         at com.naryx.tagfusion.cfm.engine.cfEngine.init(Unknown
> Source)
>         at com.naryx.tagfusion.cfm.cfServlet.init(Unknown Source)
>         at org.apache.catalina.core.StandardWrapper.loadServlet
> (StandardWrapper.
> java:1048)
>         at org.apache.catalina.core.StandardWrapper.load
> (StandardWrapper.java:95
> 0)
>         at org.apache.catalina.core.StandardContext.loadOnStartup
> (StandardContex
> t.java:4122)
>         at org.apache.catalina.core.StandardContext.start
> (StandardContext.java:4
> 421)
>
> I've search google for posts containing openbd and JBoss 5.x without
> much luck.
>
> After looking at the JBoss server.log file I thought I'd rename the ./
> WEB-INF/lib/xmlrpc-1.2-b1.jar (some sort of xml parser) to xmlrpc-1.2-
> b1.jar.off to see if this was the cause of the failed deployment.
>
> Restarted JBoss and openBD1.1 deployed without any errors and I was
> able to browse the demo files and administrator pages without any
> issues.
>
> I'd just like to say that I'm new to JBoss so I thought it would be a
> good idea to ask a few questions:
>
> 1. Should I stay away from JBoss 5.x and continue down the path of
> JBoss 4.2.3?
> 2. Will removing this file cause issues down the track if JBoss 5.1
> was chosen as the AS
> 3. I've deployed Coldfusion 7 to a 3 node JBoss 4.2.3 cluster using
> Apache 2.2.x as the load balancer in a development environment, and
> would now like to replace CF7 with openbd1.1 - Has anyone tried the
> same with openBD?  I'd be interested in sharing config settings etc.
>
> Thanks in advance
>
> Dave.
>
> >
>   


--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official site @ http://www.openbluedragon.org/

!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to