Menu edit?

[milesparker]

OK, back to the orginal query. Am I missing something else when it comes to editing menus?

If I click on a menu to edit, I get the name and so on, and then the message:

"No specific block customization"

I'm thinking that there should be somewhere to edit menu structure that I am not seeing? Or do I need to edit an .xml file directly?

(Server has no more errors, but a few loader related warnings, e.g.:

2004-07-09 17:48:14,578 WARN [org.jboss.web.tomcat.tc4.EmbeddedTomcatService] Unable to invoke setDelegate on class loader:org.jboss.web.tomcat.tc4.WebCtxLoader$ENCLoader@1be2893
)

[milesparker]

Anyone? Even a hint? Kind of dead in the water here.

[julien1]

Yes, that menu does not have yet the code hooks to allow self editing in the block menu. So you must indeed edit the XML deployment descriptor of the MBean.

[milesparker]

"cooper" wrote:
Yes, that menu does not have yet the code hooks to allow self editing in the block menu. So you must indeed edit the XML deployment descriptor of the MBean.

Cool, that's what I needed to know..

[milesparker]

Hmm..ok, it appears I need a little more direction here. I tired editing

JBOSS_HOME/server/default/nukes/menu-block-service.xml

and the JBoss console reports:

13:46:20,968 INFO [MainDeployer] Deployed package: file:/F:/Java/jboss-3.2.3RC1
/server/default/nukes/menu-block-service.xml

However, nothing changes on the page, even after a restart. I've tried editing everything form the menu title, to adding menu items, and so on. :-(

[skully]

I do not know if this will help, but I too had to modify the Menu block. I changed the service.xml and added permissions for new menu items, but they wouldn't show up. I even undeployed and redeployed the entire works, but they still wouldn't show up until I modified the module and block security in the JBoss jmx-console.
I guess JBoss doesn't read the xml every time?

[milesparker]

"Skully" wrote:
I do not know if this will help, but I too had to modify the Menu block. I changed the service.xml and added permissions for new menu items, but they wouldn't show up. I even undeployed and redeployed the entire works, but they still wouldn't show up until I modified the module and block security in the JBoss jmx-console.
I guess JBoss doesn't read the xml every time?

thanks..

Well, I know that it notices that the file is touched, but perhaps there is antoher piece I am missing...

How do I "modified the module and block security in the JBoss jmx-console"?

[milesparker]

wtf...the menu-block-service.xml doesn't seem to have anything to do w/ what actually shows up in the menu -- when I edit the title form the block editor, it updates somewhere, but not service.xml. arghh...

[sgwood]

For each module and theme, there are values in the nukes_services_attributes table in the database that are inserted from the MBean descriptor the first time the MBean is run.

If you really want to have updated attributes come from the MBean descriptor, delete the relevant rows and restart Nukes. If the attributes must always come from the MBean descriptor, and thus cannot be updated via the UI, then remove the constructor tag on the MBean descriptor.


Sherman

[milesparker]

"sgwood" wrote:

If you really want to have updated attributes come from the MBean descriptor, delete the relevant rows and restart Nukes. If the attributes must always come from the MBean descriptor, and thus cannot be updated via the UI, then remove the constructor tag on the MBean descriptor.
Sherman

Well, gee that would have been a nice thing to do w/ the menu-block-service.xml then! :-D beginning to seem to me that perhaps Nukes isn't quite ready for civilian use, as it were.

Anyway..thx, Sherman.

[jae77]

if you don't see the functionality you want, write it yourself and submit a patch. that's one of the many beauties of open source.

[milesparker]

But that attitude isn't going to work unless the basics are there -- you should be able to use it to do useful things in a straightforward way out of the box. My point was that perhaps the Constructor flag shouldn't have been set, given that the only way to edit menus is to edit the .xml? Having to delete (undocumented) database rows in order to update a menu is not quite straightforward. :-) Perhaps it would seem more normal if I had experience with the JBoss platform.

Anyway at this point I'll prob. stick w/ it, 'cause I'm past the worst of the learning curve and it is quite powerful.