GenericSetup type installation disregards schema index specifications

hi all,

i've just today realized that when you use a GS profile to define and install 
your portal types, then AT's install_indexes method never gets called, and 
thus any index specifications in the schema fields will not be honored.

we could fix this, potentially, by overriding the default 
TypeInformationXMLAdapter with one that checks whether or not the object is an 
AT-derived type, calling the install_indexes method if so.  or we could add 
another import step that does something similar (still relying on the 
types.xml file) instead of dovetailing on the TypeInfo registry.  OR we could 
not fix it, and just say that switching to using GS to install your type also 
means that you'll need to take your index declarations out of the AT schema 
and instead put them into the catalog.xml file (and any other config files 
that may exist for custom catalogs).

i'm leaning towards the latter, myself, b/c it's a less AT-specific idiom, and 
because it's not really any harder to create the XML file than it is to put 
the specification in the schema, and b/c moving the index definitions is 
similarly easy.  and b/c it means less work to do.  but i want to know what 
the rest of y'all think, so if you've got an opinion please let it be known.

-r


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642