Hunter Kelly wrote:
There seems to be a bug in nested ZCLasses. I think the action property for factories of nested ZClasses is being set incorrectly.
Simple recipe:
Create a new product ("FooProd") Create a ZCLass that is an Object Manager, let's say "Foo". In that ZClass, create another ZClass ("Bar"). In the Subobjects menu of FooClass, add File and Foo, just for comparison's sake.
Create an instance of Foo somewhere. On it's contents page, trying to add a Bar is totally broken.
Here's the relevant bit of generated HTML:
<TABLE ALIGN="LEFT"> <TR> <TD VALIGN="MIDDLE"> To add a new item, select an item type <NOSCRIPT>and click "Add"</NOSCRIPT>. </TD> </TR> <TR> <TD VALIGN="MIDDLE"> <FORM ACTION="http://opal:8080/FooInst/" METHOD="GET"> <SELECT NAME=":method" ONCHANGE="location.href=this.options[this.selectedIndex].value"> <OPTION value="manage_workspace" DISABLED>Available Objects <OPTION value="BarClass_factory">Bar <OPTION value="manage_addProduct/OFSP/fileAdd">File <OPTION value="manage_addProduct/FooProd/FooClass_factory">Foo </SELECT> <NOSCRIPT><INPUT TYPE="SUBMIT" VALUE=" Add "></NOSCRIPT> </FORM> </TD> </TR> </TABLE>
For Bar, I am assuming that the value should be something like value="manage_addProduct/FooProd/FooClass/BarClass_factory"
instead of just value="BarClass_factory"
It's a bug, I think - I added it to the Collector yesterday, and it's also an entry in the Collector from August, if I understood the title correctly.