Generally in order to "clear" the DB entries for deployments of a certain page you have to notice that the tag <if-exists> has the value "overwrite" and not "keep".
If it is overwrite then redeployment of your webapp will reinitialize that page or portal with all the children which are configured in the deployed -object.xml
Anyway FYI:
one portal can have * pages,
one page can have * pages,
one page also can have * windows,
one portlet instance can have * windows,
one portlet name can have * portlet instances.
Hope this helps
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149999#4149999
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149999
"scooter4j" wrote : I had correctly set up the queue correctly using the JNDIName attribute - and after starting JBoss the queue showed up in the Administration console as expected.... so I'm confident my queue was set up correctly.
|
| The link below indicates that this (MDB deployer not "seeing" the destination queue) is a recognized bug in JBoss when using EJB3:
| http://jira.jboss.org/jira/browse/EJBTHREE-541?page=all
|
|
Can you post the contents of the xml file in which you have configured your queue? Also, where have you place this file and what have you named it? As for the bug that you pointed to, i don't think that should affect users of JBoss-4.2.x.
P.S: While posting the logs or xml content or code, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149984#4149984
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149984
