Deploy the sample app JPetStore to Macromedia JRun4 Problem

[sunfmin]

When I deploy the sample app JPetStore to Macromedia JRun4 , I got the following error. but work fine in Jakarta Tomcat 4.1.30
can anyone tell me what's wrong with it. and How can I solve it? thanks.

08/23 14:52:49 info [axis] Initializing servlet 'remoting'
08/23 14:52:49 info [axis] Framework servlet 'remoting' init
08/23 14:52:49 user Initializing WebApplicationContext for servlet 'remoting'
08/23 14:52:49 error [axis] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlMap' defined in resource [/WEB-INF/dataAccessContext-local.xml] of ServletContext: Initialization of bean failed; nested exception is java.lang.VerifyError: (class: com/ibatis/db/sqlmap/XmlSqlMapBuilder, method: buildFragmentList signature: (Lorg/jdom/Element;)Ljava/util/List;) Incompatible object argument for function call
java.lang.VerifyError: (class: com/ibatis/db/sqlmap/XmlSqlMapBuilder, method: buildFragmentList signature: (Lorg/jdom/Element;)Ljava/util/List;) Incompatible object argument for function call
	at org.springframework.orm.ibatis.SqlMapFactoryBean.afterPropertiesSet(SqlMapFactoryBean.java:75)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:987)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:284)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:204)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:198)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:135)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:217)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:284)
	at org.springframework.web.context.support.XmlWebApplicationContext.refresh(XmlWebApplicationContext.java:131)
	at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:156)
	at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:97)
	at org.springframework.web.context.ContextLoaderServlet.init(ContextLoaderServlet.java:80)
	at javax.servlet.GenericServlet.init(GenericServlet.java:258)
	at jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.java:1204)
	at jrun.servlet.WebApplicationService.preloadServlets(WebApplicationService.java:762)
	at jrun.servlet.WebApplicationService.postStart(WebApplicationService.java:257)
	at jrun.deployment.DeployerService.initModules(DeployerService.java:711)
	at jrun.deployment.DeployerService.createWatchedDeployment(DeployerService.java:242)
	at jrun.deployment.DeployerService.deploy(DeployerService.java:430)
	at jrun.deployment.DeployerService.checkWatchedDirectories(DeployerService.java:179)
	at jrun.deployment.DeployerService.run(DeployerService.java:891)
	at jrunx.scheduler.SchedulerService.invokeRunnable(SchedulerService.java:223)
	at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:348)
	at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:451)
	at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:294)
	at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

[mraible]

It looks to me like JRun has a version of JDOM that conflicts with Spring. Maybe you can replace it with the one that Spring uses?

[sunfmin]

It is located in jrun.jar,It is so funny that JRun4 include jdom in it's jar.
then how can I separate it? thanks.

jrun.jar
    ├─allaire
    ├─com
    ├─images
    ├─javax
    ├─jrun
    ├─jrunx
    ├─META-INF
    ├─net
    └─org
        ├─apache
        ├─jdom
        ├─mozilla
        ├─omg
        ├─w3c
        └─xml

[Colin Sampaleanu]

That's a pretty nasty thing for them to do.

Assuming JRun does have the ability to load classes it needs from something like a lib dir, what's stopping you from just editing the jar file (with a zip archive maniulator) and removing the files, then dropping in an up to date JDOM?

Regards,

[sunfmin]

Looks like it is the only way I can do that.
ok. thanks.

[Juergen Hoeller]

It looks to me like JRun has a version of JDOM that conflicts with Spring. Maybe you can replace it with the one that Spring uses?

Actually, it's iBATIS SQL Maps 1.3.1 that requires JDOM, not Spring itself. Note that SQL Maps 2.0 doesn't require JDOM anymore.

Velocity depends on JDOM too, if I recall correctly. In any case, JRun really shouldn't bundle JDOM in its server jar...

Juergen

[Colin Sampaleanu]

FWIW, the upgrade form iBatis SQL Maps 1.0 to 2.0, which would also get rid of this issue, is very simple and mechanical, although relatively tedious if you have a lot of mapping files and code, since most maps and code will be touched unless you run in the compatibility mode. But the process is straightforward, and not-error prone since since everything in 1.0 has an equivalent in 2.0.

Regards,