Bug 724510 (BRMS-456) - ClassCastException when deploying jboss-brms-server.war
Summary: ClassCastException when deploying jboss-brms-server.war
Keywords:
Status: CLOSED WONTFIX
Alias: BRMS-456
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Deployment
Version: 5.1.0.ER4
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ---
: future
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-24 09:46 UTC by Petr Široký
Modified: 2011-06-13 18:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Fedora 13 x86_64 java 1.6.0_21 (Sun)
Last Closed: 2011-06-13 18:37:28 UTC
Type: Bug


Attachments (Terms of Use)
server.log (83.88 KB, text/plain)
2010-11-24 09:47 UTC, Petr Široký
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-456 0 Blocker Closed ClassCastException when deploying jboss-brms-server.war 2014-05-19 06:49:57 UTC

Description Petr Široký 2010-11-24 09:46:28 UTC
Steps to Reproduce: 1. Download and unzip brms-standalone-5.1.0-ER4
2. Copy directory jboss-as-web/tools/jboss-brms-server.war to jboss-as-web/server/default/deploy
3. Start server (./run.sh in jboss-as-web/bin directory)
securitylevel_name: Public

The ClassCastException is thrown when deploying jboss-brms-server.war. 

[ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource [beans.xml]; nested exception is 
java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl cannot be cast to javax.xml.parsers.DocumentBuilderFactory

Comment 1 Petr Široký 2010-11-24 09:47:14 UTC
Server log file attached.

Comment 2 Petr Široký 2010-11-24 09:47:14 UTC
Attachment: Added: server.log


Comment 3 John Graham 2011-06-13 18:37:28 UTC
For a previous release ER build.


Note You need to log in before you can comment on or make changes to this bug.