[Installation, Configuration & DEPLOYMENT] - Multiple enterprise app instances...
by davesb
Not sure if this is the right forum, but....
I am designing an enterprise app which, at the moment, is simply an EAR containing an EJB and a Web module. The EJB jar contains JPA entities and a persistence.xml file pointing to a JNDI datasource. That datasource is defined under server/default/deploy/ right now. This is all good, but I have a requirement to be able to deploy multiple instances of this application on the same server (under different URLs). Each instance needs to be able to connect to a different datasource. At the moment, this is the only difference although there could be other differences in the future (like instance specific message queues for example).
Is it possible to deploy the full EAR just once and then, for other instances, just deploy a "configuration" which would include different datasource details?
When this app goes into production there's going to be at least 30 instances to start with, so I really don't want to have to do that many full deployments.
Any suggestions warmly appreciated!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107689#4107689
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107689
18 years, 5 months
[JBoss Portal] - org.hibernate.NonUniqueResultException: query did not return
by prns
I had deployed a portlet on portal server, Now created user suppose "jboss"on portal server. Logged in as jboss user and clicked on EDIT button of my portlet window,
On "save" it executes required code of my portlet application, but throws exception.
Please find the stackTrace below.
org.hibernate.NonUniqueResultException: query did not return a unique result: 2
at org.hibernate.impl.AbstractQueryImpl.uniqueElement(AbstractQueryImpl.java:765)
at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:756)
at org.jboss.portal.core.impl.model.instance.InstanceImpl.invoke(InstanceImpl.java:249)
at org.jboss.portal.core.command.RenderWindowCommand.execute(RenderWindowCommand.java:109)
at org.jboss.portal.core.command.ControllerCommand.dispatch(ControllerCommand.java:84)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:141)
at org.jboss.portal.core.aspects.controller.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:168)
On checking database.script for hypersonic , found it creates 2 enteries for user "jboss", not sure why?
If anyone has idea on it how to fix it.Please let me know.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107685#4107685
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107685
18 years, 5 months
[JBoss Seam] - Re: Exadel, JBoss and Seam
by sysmat
"tnfink" wrote : "petemuir" wrote : "lisaanm" wrote : the team should provide a short integration guide for RichFaces-Seam
| |
| | AFAIK you would set up a project as if for ajax4jsf (seam-gen will do this for you :) and just drop the richfaces jar into WEB-INF/lib
|
| we tried this. But it only worked with simple components (e.g., the separator). If we bound the suggestion box to a Seam managed bean, we encountered class loading problems. We then put the jars from richfaces, ajaf4jsf, and oscache into the root of the EAR and added them as Java-modules. This solved the problems.
|
| We tested the suggestion box, the data table, and the panel and everything worked fine. The skins seem to be missing and the documentation is a little bit sparse.
| But all in all, it is usable now and it can only become better :-)
I put jars into ear and register them as java moduls and I always get error at deployment:
javax.faces.FacesException: org.ajax4jsf.renderkit.ChameleonRenderKitFactory
What that means.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107670#4107670
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107670
18 years, 5 months