[Beginner's Corner] - Caching objects
by David Bailey
David Bailey [http://community.jboss.org/people/edwardpig] created the discussion
"Caching objects"
To view the discussion, visit: http://community.jboss.org/message/643075#643075
--------------------------------------------------------------
I've written a proof-of-concept session bean which wraps some legacy Java code. The POC seems to be doing what we want it to do, and now it's time to make the bean production-ready.
Each instance of the bean loads configuration from an XML document. There are several dozen XML documents available; the decision about which XML document is loaded depends on what we want the particular bean instance to do.
For the POC, I have simply dropped the XML documents in the servlet 'WEB-INF' directory. At runtime, my POC servlet obtains the appropriate XML document from the ServletContext as an InputStream, and hands the InputStream to the session bean. However, the XML documents in question can be up to a few MB in size, so we don't want to parse them repeatedly. I think there are two requirements for how we would like to handle things:
1) Load and parse each XML document into an in-memory DOM tree at startup, and retain that DOM tree collection in memory 'forever' (until JBoss shuts down).
2) These XML documents rarely change --- in fact, they may *never* change --- but it should still be possible to update them if necessary.
So one question I have is: what is the best way to achieve the loading at startup and in-memory caching? For my POC, I put a static Map in my bean which held references to each DOM, but that's not optimal because the XML isn't parsed at JBoss startup/bean deployment, and the static Map goes away if the bean ClassLoader is ever garbage collected.
Another question I have is: Where should the source XML documents reside? I don't think delivering them in the WEB-INF directory of my web app is a good idea, because I want to be able to update the XML without redeploying the web app. Perhaps I should parse each DOM tree, then store the whole tree as a CLOB in my database?
Suggestions are appreciated.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/643075#643075]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[Snowdrop] - petclinic project deployment issue with jboss7
by Richard Louapre
Richard Louapre [http://community.jboss.org/people/richard.louapre] created the discussion
"petclinic project deployment issue with jboss7"
To view the discussion, visit: http://community.jboss.org/message/643046#643046
--------------------------------------------------------------
Hi,
I followed the instructions from http://community.jboss.org/blogs/mariusb/2011/07/13/spring-and-jboss-as7-... this blog
But the deployment in jboss7 failed with the error message:
07:30:17,917 INFO [org.jboss.as.server.deployment] (pool-2-thread-2) Content added at location D:\Download\Java\JBoss\jboss-as-7.0.2.Final\standalone\data\content\7fc87bc5dd5eb9e451cee831e13453be9d94491b\content
07:30:18,006 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) Starting deployment of "petclinic.war"
07:30:20,615 INFO [org.jboss.as.jpa] (MSC service thread 1-9) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to petclinic.war
07:30:21,287 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-15) MSC00001: Failed to start service jboss.deployment.unit."petclinic.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."petclinic.war"
.INSTALL: Failed to process phase INSTALL of deployment "petclinic.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: only one persistence provider can be packaged with an application [oracle.toplink.essentials.PersistenceProvider, oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider, org.apache.openjpa.persistence.PersistenceProviderImpl, org.hibernate.ejb.HibernatePersistence]
at org.jboss.as.jpa.processor.PersistenceProviderProcessor.deploy(PersistenceProviderProcessor.java:65)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
... 5 more
I also tried to get the complete modified example for https://github.com/mbogoevici/spring-samples/tree/as7-blog github but I have the same deployment issue.
How can I solve this issue?
Thanks,
Richard.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/643046#643046]
Start a new discussion in Snowdrop at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months