[nat101]

I tried a simple ‘Hello’ ejb. After XDoclet gens all the sources (nice!) I am left with a taglib.tld with the following error flag on it:

The content of element type “taglib” is incomplete, it must match “(tlib-version,jsp-version,short-name,uri?,display-name?,small-icon?,large-icon?,description?,validator?,listener*,tag+)”.

And here is the complete contents of the file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN" "http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd">

<taglib>

   <tlib-version>1.0</tlib-version>
   <jsp-version>1.2</jsp-version>
   <short-name>j2ee</short-name>

</taglib>

Thanks;
-nat

[Riyad Kalla]

nat,
You’re missing atleast 1 <tag> entry (end of message, tag+).

Although I’m not clear why the ejb doclet is giving you a tld file… let me ask our XDoclet guy.

[nat101]

@support-rkalla wrote:

Although I’m not clear why the ejb doclet is giving you a tld file… let me ask our XDoclet guy.

Oh. That gave me a hint. I went to project properties>MyEclipse XDoclet and removed ‘standard web’ xdoclet configuration, leaving only ‘standard ejb’ as the only config, and indeed xdoclet does not attempt to write the tld file. So, no more problem.

Questions.
1) Even though ‘standard web’ was defined, this should not have happened. True?

2) Why let us define xdoclet configs that are inaprropiate for a given project?

3) Why doesn’t MyEclipse automatically define the standrd xdoclet configs required for a given project type.

Thanks;
-nat

[Greg]

Nat,

1) There must be some subtasks in the tld generation that start a stubbed out tld file and when there is no xdoclet input files it just leaves the stubbed file. This is an oversight on the xdoclet module writers part. Of course the easy solution is to not have the subdoclet task defined as you figured out.

2) Just for simplicity. If we tried to be too smart and “validate” the configuration, more often than not we would mis-understand how a user wants to configure their xdoclet settings and we would be causing them more work.

3) This is a good idea for EJB projects. I can think of alot of web project cases where xdoclet is never used. But for EJB projects, xdoclet is essentail.

Thank you for your feekback, and we will review your suggestions as we continue to improve MyEclipse Xdoclet support.

[nat101]

I am impressed with your open/honest [and listening] atitude.
Thank you much.
-nat

[Author]

Posts