The problem is that the *-object.xml file are used to populate the portal database, and the runtime portal layout, including the pages and portlets in the portal, is maintained in that database. When you used the admin portal to remove them, they were removed from the database. The next time you started the portal, the *-object.xml file were read again and the database populated again. Thus removing the *-object.xml files at that point will not do anything because the database has been populated. You have to remove the pages/portlets using the admin portal and remove the *-object.xml files at the same time to keep the pages from reappearing.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252643#4252643
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252643
Creating the durable subscriptions beforehand and then having later subscribers use them is the only thing I could come up with. But you will need to know how many potential subscribers you will have. If you create too few durable subscriptions, some subscribers will not get the messages. If you create too many, the messages will hang around forever.
This really sounds like a job for a MDB and a SLSB. The MDB subscribes to the topic and places all messages in a database. When a new client comes up, it connects to the topic to get future messages and asks the SLSB for the historical messages.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252638#4252638
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252638
