[JBoss Portal] - Catalog Portlet enhancements for navigation
by reisdk
Does anyone know of an enhanced Catalog Portlet for Portal 2.4?
We are developing a Portal using JBoss Portal 2.4 on JBoss AS 4.0.5 that is more like a tree navigation to get to content or external systems. The site will go 3 or 4 levels deep in menus and needs to be bi-lingual. We also want it to be "out-of-the-box" as much as possible. The shortcomings we see to the Catalog portlet are:
- no navigation provided back up the tree - you must use the back button (does history not parent) or tabs (back to the beginning)
- the order of the "choices" (pages) can not be selected
- the choices move around because the current choice moves to the top
- the choices are not localizable (through resource bundles)
I saw the Jira on the Navigation Portlet (to add tab order and resource key) so we could use a similar thing here. I just wanted to check to see if anyone has done any of these enhancements already before we go diving in.
Thanks.
-Deb Reis
Unisys Corp
Malvern, PA
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002398#4002398
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002398
19 years, 3 months
[EJB 3.0] - Transactions over multiple session beans
by literadix
Hi all !
I have allrwdy postet this question to the Oreilly's book forum, but can not figure out how construct the following:
I have multiple Entities (Entity1, Entity2, ..., EntityN) and have put on top of each entity a session bean (Entity1Dao, Entity2Dao, ..., EntityNDao). What I want to do is to hadle an update of entity1, entity2, entityn within one single transaction.
Any exception during entity management should mark the just running transaction for rollback, so when an exception occured within Entity2Dao no data from Entity1 should persist. After the command flow has end, I would like to commit all changes (transaction commit).
Is there any public example or some nice lad who can give me any source code how to manage this? If possible, I would like avoid to use stateful beans . The base code for my entity DAOs is like this:
| public abstract class GenericDaoImpl<T extends GenericDatabaseObject, PK extends Serializable> implements GenericDao<T, PK> {
|
| /** EntityManager */
| @PersistenceContext(type=PersistenceContextType.TRANSACTION)
| EntityManager manager;
|
| @TransactionAttribute(TransactionAttributeType.REQUIRED )
| public void save(T instance) {
| System.out.println(manager);
| manager.persist(instance);
| }
|
| @TransactionAttribute(TransactionAttributeType.REQUIRED )
| public void delete(T persistentObject) {
| manager.remove(persistentObject);
| }
|
|
|
|
|
| and the sub class for two specific session beans is as in following example:
|
| @Stateless(name = "AddressDao")
| @Remote(AddressDao.class)
| @Local(AddressDao.class)
| public class AddressDaoImpl extends GenericDaoImpl<Address, Long> implements AddressDao {
| // ...
| }
|
| @Stateless(name = "BookDao")
| @Remote(BookDao.class)
| @Local(BookDao.class)
| public class BookDaoImpl extends GenericDaoImpl<Book, Long> implements BookDao {
| // ...
| }
|
I am using the latest JBOSS 4.0.5 and EJB3R9 and PersistenceContextType.TRANSACTION for the EntityManager.
Thank you very much,
Maciej A. Bednarz
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002397#4002397
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002397
19 years, 3 months