[JBoss Portal] - Placing portlet_instances.xml in a central place ...
by rohit000
Hi,
Seems like creating portlet instances from a central place (like portal-object.xml) is not supported.
Can anyone please confirm this ?
However, this looks to be a required feature which can provide proper separation of concern between portlet developer and deployer, especially if you don't want to use admin console (say you want to deploy the portal in 5 different boxes and doing the configuration job through admin console is not a choice) for creating portlet instances.
Allowing portlet_instances.xml only in the same .war file which has the portlet.xml does not give enough separation where the portal deployer can decide how many portlet instances (for a given portlet) he needs to create and how he would like to set different preferences for them. In the current version of jboss portal (2.6.4) the deployer needs to change the same only by going into respective .war files of the portlets.
Any takers ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151882#4151882
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151882
18 years, 1 month
[EJB/JBoss] - Re: Atomic process in Local SSB -Urgent !!!!!!!
by kahzoo
anonymous wrote : One thing that worries me with Synchronization is that Synch is on whole bean and not the methods :).
|
| Now I need to have more than one Stateful session bean.
|
I'm sorry, but I'm failing to understand what your concern is.
Are you saying that you have to split the logic in two different beans?
That is not the case, and you can implement the logic in one stateful session bean(, in which you will have both your business method and the synchronization methods). You just call the business method and the synchronization methods will be automatically called at appropriate points of the CMT transaction.
If StatefulSessionBean/SessionSynchronization is not satisfactory, the other option would be to switch from CMT to BMT (bean-managed transaction).
With BMT, you need to do the transaction demarcation (begin, commit, rolback) yourself, but since your bean will know the outcome of the transaction, it can decide to write/do-not-write data in the file accordingly.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151876#4151876
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151876
18 years, 1 month