Rainer,

I just attached a jar to ww-1392, it has the code, and the batch file I was using to test it. 2 things about it, first, I can't get tiger to format the output xml (there is a bug in tiger...6296446....there must be a workaround), the second one is that apt has a bug parsing the cmd line parameter in tiger (6258929...workaround in the code).

regards,
musachy

Rainer Hermanns wrote:
Musachy,
can you send me over your tld processor stuff?
Best would be to attach it to the jira ticket (WW-1392).

tia,
Rainer

After 2 hours trying to make apt run from ant in a generic way, I found
out that ant 1.7 has an AptTask. I guess I will borrow that class until
struts upgrades to 1.7(RC1 right now).

musachy

Musachy Barroso wrote:
Rene,

Let me know when you get this done, I have apt ready.

musachy

Rene Gielen wrote:
When we started the taglib generation in ww2, we had to tweak the
xdoclet templates and a little bit of code because the meta
information had to be in the component sources rather than the
Tag-classes. Because of the dual use of the components (fm-support),
the real logic sits there while the Tag classes are simple wrappers.
Also I remenber there were some small issues with html artifact
generation. We could not get xdoclet to go without tweaking it.

Maybe Konstantin could bring some light into whether standard xd2
taglib doclet would deliver this flexibility. Also, the idea of using
real annotations, while doing generation with xd2, does not sound
that bad, if it would help us to get things out the door more quickly.

BTW, I did not find much on apt based tld generation, too ...

Regards,
Rene


If the xdoclet 2 project already has a taglib module,
I'd rather use that.  Is there any technical reason we would need to
have our own custom taglib generation module?

Don

Konstantin Priblouda wrote:

--- Don Brown <[EMAIL PROTECTED]> wrote:


Surely, we can't be the first project interested

in

using annotations to generate taglib tld's?  Is there any other

solution

out there we can leverage?

Hi Don,  you have several options out of the box:
1. XD2 has working taglib module, maven2 plugin,

and

fresh version of qdox parser (1.6.1) is said to

work

with 1.5 sources - just add plugin invocation to

your

pom.xml

If you like to go for annotations, there is

posibility

to create metadata provider which would pull the

same

metadata from  annotations instead of @tags and
utilize the same templates.
regards,

----[ Konstantin Pribluda http://www.pribluda.de

]----------------

Still using XDoclet 1.x?  XDoclet 2 is released and

of production quality.

check it out: http://xdoclet.codehaus.org





______________________________________________________
______________________________

Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail

beta.

http://new.mail.yahoo.com



------------------------------------------------------
---------------

To unsubscribe, e-mail:

[EMAIL PROTECTED]

For additional commands, e-mail:

[EMAIL PROTECTED]

------------------------------------------------------
---------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]



---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=49702&messageID=102084#102084



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to