Re: [Ejbca-develop] Schema confusion

[Tomas G. <to...@pr...>]

This off-course also means that <abstract-schema-name> can be changed 
without affecting current installations. For example if any new 
container would require so for easiest possible deployment (i.e. if any 
new container models the actual schema after abstract-schema-name).

Cheers,
Tomas

Tomas Gustavsson wrote:
> 
> <abstract-schema-name> in ejb-jar.xml is only abstract and used in 
> EJB-QL, it does not define the actual database table. The table created 
> by JBoss is named after <ejb-name> and is AdminGroupData, there is no 
> table AdminGroupDataBean in the database, hence the session bean selects 
> from AdminGroupData.
> 
> EJB-QL refers the the abstract-schema-name which is not the same as the 
> actual table-name. The mapping betweeb abstract-schema-name and 
> table-name is defined by the container and can be overridden by 
> container-specific configuration files (see for instance 
> weblogic-cmp-rdbms-jar.xml files). The default table name in JBoss is 
> the same as the <ejb-name>.
> 
> You can name abstract-schema-name anything you like though this is not 
> recommended off-course. The deployment descriptors in ejbca is modelled 
> (copied) after the book 'Mastering Enterprise JavaBeans' Second edition 
> by Ed Roman, Scott Ambler and Tyler Jewell.
> 
> The database schema is as you say named after <ejb-name>, which is 
> AdminGroupData in this case. No migration script is therefore needed I 
> believe.
> 
> Cheers,
> Tomas
> 
> Stephane Bailliez wrote:
> 
>> I'm a bit confused about the schema:
>>
>> In Authorization, the Entity bean AdminGroupDataBean defines a 
>> schema-name
>> AdminGroupDataBean
>> finders do perform queries on AdminGroupDataBean
>>
>> In the session bean however, I can see a sql query that work on
>> 'AdminGroupData'.
>>
>>
>> ps: On a related note, naming convention implies that the schema name
>> associated to <component-name>Bean should be <component-name> which is
>> semantically more correct than a table named xxxBean, once everything 
>> will
>> be somewhat clean, it means that we would need to write a migration 
>> script.
>>
>> Stephane
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by the new InstallShield X.
>>
>>> From Windows to Linux, servers to mobile, InstallShield X is the one
>>
>> installation-authoring solution that does it all. Learn more and
>> evaluate today! http://www.installshield.com/Dev2Dev/0504
>> _______________________________________________
>> Ejbca-develop mailing list
>> Ejb...@li...
>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> 
>> From Windows to Linux, servers to mobile, InstallShield X is the one
> 
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop