On Mon, 2005-06-20 at 00:49, Nick Hus wrote:
> My bean is in the package cam.config and the name of the bean class,
> CommentsBean. So the full name of my class bean is
> cam.config.CommentsBean.class.
>
> The ebj name is Comments, specified by @ejb.bean name="Comments".
>
> Here is the contents of the file that I am trying to merge:
>
> <entity>
> <load-groups>
> <load-group>
> <load-group-name>Locking</load-group-name>
> <field-name>lastUpdated</field-name>
> </load-group>
> </load-groups>
> <optimistic-locking>
> <group-name>Locking</group-name>
> </optimistic-locking>
> </entity>
>
>
> I've loaded the above xml content into a file with the name
> jbosscmp-jdbc-Workflows.xml and jbosscmp-jdbc-WorkflowsBean.xml.
> Neither worked. I've placed these files in the directory
> mergeDir/cam/config.
>
> I am using Eclipse JBOSS IDE. The Jboss version is 4.0.1. In the Jboss
> xdoclet subtask:
> I've specified version 4.0, and the mergeDir name of mergedDir.
>
> I do appreciate your help. I've looked carefully through the archives
> and I've found messages relating to merging of jbosscmp-jdbc.xml, but
> they were not helpful to me. Sorry. An example would be helpful if
> someone can provide it, or tell me what I am doing wrong.
Given that you said your bean has the ejb name "Comments", have you
tried using "jbosscmp-jdbc-Comments.xml" as the filename rather than
"jbosscmp-jdbc-Workflows.xml"?
Also, I believe the jbosscmp-jdbc-{0}.xml merge point appears inside the
<entity> element already, so you should probably remove those else
you'll get them repeated and the generated file will be invalid.
If you use that particular merge point, however, you'll also have to
specify any <cmp-field> and <query> elements in your merge file in
addition to the load groups as those also appear inside the
corresponding <XDtMerge:merge> template tags (and merge files replace
everything inside the tags).
The <optimistic-locking> bit may not work either, if an <unknown-pk> or
<entity-command> tag gets generated. Those elements appear outside of
the merge point's tags, so you could end up with optimistic-locking
appearing before them instead of after them, which would again make the
file invalid. If neither of those elements are being generated, you'll
get away with it.
Is there some reason you can't just use @jboss.load-group and
@jboss.optimistic-locking tags to generate these entries, rather than
the merge file?
Andrew.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
xdoclet-user mailing list
xdoclet-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
