Cool -- I think that should be straight forward enough. Of course, when I
started to think a little more sanely about this last night, I decided
that it doesn't look like it really matters whether the id's are indexed
numerically or not, they just need to have some kind of unique identifier
for each element between the files when they reference each other.
-jason
Ara Abrahamian <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
02/06/2002 01:50 AM
Please respond to ara_e_w
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc:
Subject: RE: [Xdoclet-user] Newbie to websphere 4...
> Fair enough. :) Before I dig myself into a hole too far, can
someone
> point out quickly if there is a method that can tell me the current
index
> of a "forAll*" loop in a template? For example, to replicate these
> ibm*.xmi docs exactly, they like to add an 'id' attribute to many of
the
> xml tags, which is suffixed by the component number. Does this
> functionality exist? At first glance, it looks like I might be able
to
> add something like this pretty easily to XDocletTagSupport...
The best way to handle it is to enhance/modify
xdoclet.tags.IdTagsHandler. So in template:
<XDtId:id prefix="CmpEntityBean"/>
And what it does is IdTagsHandler has an ordered hashtable inside. So
every time you call XdtId:id it looks at the hashtable, if something
with that prefix found, then get the value (which is an Integer),
increment it and put it back in. If not found then put one. This way you
don't have to worry about nested i/j/k/etc index variables in template
file and also the logic is hidden from the template and is in java code.
Ara.
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
