This was fixed in beta2. I had the old beta1 jars in the same libdir.
Forgot that beta2 changed the jar naming conventions.
chris
----- Original Message -----
From: "Chris Trawick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 08, 2003 12:34 PM
Subject: [Xdoclet-user] BMP and value-object compose
> I have had success using value-object compose with CMP beans, I'm having
> trouble getting it to work for DAO-backed BMP beans. There's got to be
> something wrong with what I'm doing, because I could not find any
> CMP-specific code in the value-object stuff. I'm using 1.2.0-beta1.
Tried
> it with beta2 with same result.
>
> Here's one snippet:
>
> <code>
> // at the class level
> * @ejb.value-object name="UserAccess" match="access"
>
> // at the method level
> /**
> * @ejb.interface-method
> * @ejb.value-object match="access"
> *
> compose="net.cultured.site.security.vo.UserRoleValue"
> * compose-name="UserRoles"
> *
> members="net.cultured.site.security.interfaces.UserRoleLocal"
> * members-name="UserRole"
> * relation="external"
> * type="Collection"
> */
> public Collection getUserRoles() throws NamingException, FinderException {
> return UserRoleUtil.getLocalHome().findByUserID(userID);
> }
> </code>
>
> The header was pretty much stolen from the CMP-enabled version of this,
> which was in turn pretty much stolen from the feature docs. The problem
is
> that XDoclet is not generating the appropriate add/remove/update methods
in
> the BMP interface. It does the get*Value methods just fine though.
>
> I turned debugging on and traced it through the
> <XDtEjbValueObj:forAllRelations> (entity-value.xdt) tag to the message
just
> before the generate() fall-through ("Type Collection or Set" and
> relationInterface, in ValueObjectTagsHandler.java), so it did properly
> recognize this as a value-object relation. The only other test in that
> template between the <XDtEjbValueObj:forAllRelations> and the
> add/remove/update methods is a <XDtMethod:ifHasMethodTag
> tagName="ejb:value-object" paramName="type">. Unfortunately, this test
does
> not produce any messages, so I don't know what it thinks it's seeing. The
> parameter is there though.
>
> I have a funny feeling that there's something obvious here that I'm
missing.
> May I borrow your eyes?
>
> chris
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> xdoclet-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
