This content has been marked as final.
Show 3 replies
-
1. Re: Role of the Database in Nukes
julien1 Jan 29, 2004 3:19 PM (in response to mcscottmc)"cooper" wrote:
the module/block to be persistent must be created with the persistent value set to true (in the constructor)
1.it syncs with the DB : if the attribute is not in the DB, then it is written with the actual value in the XML setting, otherwise it is taken from the DB and loaded.
2.nukes_services is used for dynamic block creation (index.html?module=block) here you can create blocks. this module has still osme issues :-( but it works a bit. We have to fix that. -
2. Re: Role of the Database in Nukes
mcscottmc Jan 29, 2004 4:12 PM (in response to mcscottmc)"mcscottmc" wrote:
Thanks for the info, Julien.
Here is an update for anyone following this thread:
I edited the jboss-service.xml in the nukes.sar to make the MenuBlock persistent. This is useful if you would like to add links to the menu. To make the MenuBlock persistent, I added a boolean parameter to the constructor. When I restarted JBoss, the MenuBlock's attributes were added to the database and any changes I made in the JMX console were persisted.
Does anyone know of any way to do what I just did rather than rebuilding the entire nukes.ear? It seems like overkill to do that, but it is looking more and more like maintaining my own jboss-service.xml in the nukes.sar is the way to go.
-Scott -
3. Re: Role of the Database in Nukes
julien1 Jan 29, 2004 4:26 PM (in response to mcscottmc)"cooper" wrote:
you did the right way.
ideally all blocks should be persisted in the database OR be specified in the block module, so it would be entirely customizable : add / remove blocks