Greetings,
I would like to know what diferences (advantages/disadvantages) exist
between using a relation and using a value-object?
I recently made this interface method to represent a relation but I also
inserted an optional value-object method.
/**
* @ejb.interface-method
* view-type="local"
* @ejb.relation
* name="service_TO_primitive"
* role-name="service_CALLS_primitive"
* cascade-delete="no"
* target-ejb="Primitive"
* target-role-name="primitive_IS_CALLED_BY_service"
* target-cascade-delete="no"
* target-multiple="no"
* @ejb.value-object
* aggregate="pt.ptinovacao.nginpro.uif.ejb.access.PrimitiveValue"
* aggregate-name="primitive"
* relation="external"
* @jboss.relation
* related-pk-field="primitiveId"
* fk-column="primitive_id"
*/
public abstract PrimitiveLocal getPrimitive();
public abstract void setPrimitive(PrimitiveLocal primitive);
The only thing I can manage here is that in a relation I may have a
delete cascade and in a value-object I'm unable to define it. So, can
any of you briefly show me what uses are reasonable to use with one
method or the other?
NOTE: the performance issue is very important to me!
thanks,
Pedro Salazar.
--
-PS
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
