xdoclet-plugins-interest — General list for XDoclet plugin writers and users

[xdoclet-plugins-interest] [jira] Commented: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml

[Konstantin P. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168734#action_168734 ] 

Konstantin Pribluda commented on XDP-240:
-----------------------------------------

current workaround would be to implement javax.ejb.* in leaf classes

current logic determining whether to generate classes definitely needs attention
( patches as always welcome ) 

> EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: XDP-240
>                 URL: http://jira.codehaus.org/browse/XDP-240
>             Project: XDoclet 2 Plugins
>          Issue Type: Bug
>          Components: ejb
>    Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
>         Environment: JDK 1.5
> ANT 1.7
>            Reporter: Konstantin Kasatkin
>            Priority: Critical
>         Attachments: xdoclet2.zip
>
>
> It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
> XDoclet1 really did that, because I remember that I personally set this issue against project team.
> I have an 2 super classes for the EJB and a super interface for EJB Interface looking like
> public abstract class AbstractSessionBean implements SessionBean {...}
> public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {
> ...some business methods with xdoclet declarations...
> /**
>      * @ejb.interface-method
>      * @ejb.transaction-method type="Supports"
> */
>     public void additionalMethods () { ... implementation ... }
> }
> public interface AsyncPipes extends Serializable {
>     public void additionalMethods();
> }
> EJB class is declared as:
> /*
> * @ejb.bean ...
> * @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> *                local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
> */
> public class ImportEJB extends AsyncPipesImpl {
>     ... implementation ...
> }
> When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.
> Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.
> Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-241) EJB Plugin doesn't parse EJB super

[Konstantin K. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168728#action_168728 ] 

Konstantin Kasatkin commented on XDP-241:
-----------------------------------------

Please correct the Issue heading, I accidently pressed Enter key and submited it unedited:(

I ment "EJB Plugin incorrectly parses @ejb.interface extends tag value"

> EJB Plugin doesn't parse EJB super 
> -----------------------------------
>
>                 Key: XDP-241
>                 URL: http://jira.codehaus.org/browse/XDP-241
>             Project: XDoclet 2 Plugins
>          Issue Type: Bug
>          Components: ejb
>    Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
>            Reporter: Konstantin Kasatkin
>
> EJB Doclet Plugin processes @ejb.interface extends attribute.
> If I declare @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> (with no space between class declaration) all works fine. But when I add a space
> before or after comma, Plugin doesn't trim space and consider class name as
> "<space>javax.ejb.EJBObject" and in the generated code it adds javax.ejb.EJBObject twice
> because it thinks that it two different classes "<space>javax.ejb.EJBObject" and "javax.ejb.EJBObject". 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Created: (XDP-241) EJB Plugin doesn't parse EJB super

[Konstantin K. (JIRA) <ji...@co...>]

EJB Plugin doesn't parse EJB super 
-----------------------------------

                 Key: XDP-241
                 URL: http://jira.codehaus.org/browse/XDP-241
             Project: XDoclet 2 Plugins
          Issue Type: Bug
          Components: ejb
    Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.5, 1.0.4
            Reporter: Konstantin Kasatkin


EJB Doclet Plugin processes @ejb.interface extends attribute.
If I declare @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
(with no space between class declaration) all works fine. But when I add a space
before or after comma, Plugin doesn't trim space and consider class name as
"<space>javax.ejb.EJBObject" and in the generated code it adds javax.ejb.EJBObject twice
because it thinks that it two different classes "<space>javax.ejb.EJBObject" and "javax.ejb.EJBObject". 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml

[Konstantin K. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168726#action_168726 ] 

Konstantin Kasatkin commented on XDP-240:
-----------------------------------------

If I add my superclasses into processed source fileset I get very messy result,
xDoclet begins to generate interfaces for superclasses, in one word all goes worse than without adding:(

> EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: XDP-240
>                 URL: http://jira.codehaus.org/browse/XDP-240
>             Project: XDoclet 2 Plugins
>          Issue Type: Bug
>          Components: ejb
>    Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
>         Environment: JDK 1.5
> ANT 1.7
>            Reporter: Konstantin Kasatkin
>            Priority: Critical
>         Attachments: xdoclet2.zip
>
>
> It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
> XDoclet1 really did that, because I remember that I personally set this issue against project team.
> I have an 2 super classes for the EJB and a super interface for EJB Interface looking like
> public abstract class AbstractSessionBean implements SessionBean {...}
> public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {
> ...some business methods with xdoclet declarations...
> /**
>      * @ejb.interface-method
>      * @ejb.transaction-method type="Supports"
> */
>     public void additionalMethods () { ... implementation ... }
> }
> public interface AsyncPipes extends Serializable {
>     public void additionalMethods();
> }
> EJB class is declared as:
> /*
> * @ejb.bean ...
> * @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> *                local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
> */
> public class ImportEJB extends AsyncPipesImpl {
>     ... implementation ...
> }
> When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.
> Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.
> Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml

[Konstantin P. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168373#action_168373 ] 

Konstantin Pribluda commented on XDP-240:
-----------------------------------------

Supplied example  excludes abstract base class from file set feed to xdoclet:

     <fileset dir="src">
        <include name="**/*EJB.java"/>
      </fileset>         

Thus it will never see it. 

As for your last comment - this belongs in separate issue 

> EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: XDP-240
>                 URL: http://jira.codehaus.org/browse/XDP-240
>             Project: XDoclet 2 Plugins
>          Issue Type: Bug
>          Components: ejb
>    Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
>         Environment: JDK 1.5
> ANT 1.7
>            Reporter: Konstantin Kasatkin
>            Priority: Critical
>         Attachments: xdoclet2.zip
>
>
> It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
> XDoclet1 really did that, because I remember that I personally set this issue against project team.
> I have an 2 super classes for the EJB and a super interface for EJB Interface looking like
> public abstract class AbstractSessionBean implements SessionBean {...}
> public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {
> ...some business methods with xdoclet declarations...
> /**
>      * @ejb.interface-method
>      * @ejb.transaction-method type="Supports"
> */
>     public void additionalMethods () { ... implementation ... }
> }
> public interface AsyncPipes extends Serializable {
>     public void additionalMethods();
> }
> EJB class is declared as:
> /*
> * @ejb.bean ...
> * @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> *                local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
> */
> public class ImportEJB extends AsyncPipesImpl {
>     ... implementation ...
> }
> When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.
> Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.
> Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml

[Konstantin K. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168120#action_168120 ] 

Konstantin Kasatkin commented on XDP-240:
-----------------------------------------

I've just found one more issue in processing @ejb.interface extends attribute.
If I declare @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
(with no space between class declaration) all works fine. But when I add a space
before or after comma, Plugin doesn't trim space and consider clal name as
"<space>javax.ejb.EJBObject" and in the generated code it adds javax.ejb.EJBObject twice
because it thinks that it two different classes "<space>javax.ejb.EJBObject" and "javax.ejb.EJBObject".

> EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: XDP-240
>                 URL: http://jira.codehaus.org/browse/XDP-240
>             Project: XDoclet 2 Plugins
>          Issue Type: Bug
>          Components: ejb
>    Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
>         Environment: JDK 1.5
> ANT 1.7
>            Reporter: Konstantin Kasatkin
>            Priority: Critical
>         Attachments: xdoclet2.zip
>
>
> It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
> XDoclet1 really did that, because I remember that I personally set this issue against project team.
> I have an 2 super classes for the EJB and a super interface for EJB Interface looking like
> public abstract class AbstractSessionBean implements SessionBean {...}
> public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {
> ...some business methods with xdoclet declarations...
> /**
>      * @ejb.interface-method
>      * @ejb.transaction-method type="Supports"
> */
>     public void additionalMethods () { ... implementation ... }
> }
> public interface AsyncPipes extends Serializable {
>     public void additionalMethods();
> }
> EJB class is declared as:
> /*
> * @ejb.bean ...
> * @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> *                local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
> */
> public class ImportEJB extends AsyncPipesImpl {
>     ... implementation ...
> }
> When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.
> Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.
> Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml

[Konstantin K. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168119#action_168119 ] 

Konstantin Kasatkin commented on XDP-240:
-----------------------------------------

Some additional comments about attachment.
Archive xdoclet2.zip contains java source including xdoclet tags code for processing
and Atn build script.

Also it contains xdoclet1-generated.zip archive that 
is a result of processing the same source code by xdoclet1 framework.
It is an example for EJB plugin how it should really work.

> EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: XDP-240
>                 URL: http://jira.codehaus.org/browse/XDP-240
>             Project: XDoclet 2 Plugins
>          Issue Type: Bug
>          Components: ejb
>    Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
>         Environment: JDK 1.5
> ANT 1.7
>            Reporter: Konstantin Kasatkin
>            Priority: Critical
>         Attachments: xdoclet2.zip
>
>
> It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
> XDoclet1 really did that, because I remember that I personally set this issue against project team.
> I have an 2 super classes for the EJB and a super interface for EJB Interface looking like
> public abstract class AbstractSessionBean implements SessionBean {...}
> public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {
> ...some business methods with xdoclet declarations...
> /**
>      * @ejb.interface-method
>      * @ejb.transaction-method type="Supports"
> */
>     public void additionalMethods () { ... implementation ... }
> }
> public interface AsyncPipes extends Serializable {
>     public void additionalMethods();
> }
> EJB class is declared as:
> /*
> * @ejb.bean ...
> * @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> *                local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
> */
> public class ImportEJB extends AsyncPipesImpl {
>     ... implementation ...
> }
> When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.
> Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.
> Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml

[Konstantin K. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168118#action_168118 ] 

Konstantin Kasatkin commented on XDP-240:
-----------------------------------------

111

> EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: XDP-240
>                 URL: http://jira.codehaus.org/browse/XDP-240
>             Project: XDoclet 2 Plugins
>          Issue Type: Bug
>          Components: ejb
>    Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
>         Environment: JDK 1.5
> ANT 1.7
>            Reporter: Konstantin Kasatkin
>            Priority: Critical
>         Attachments: xdoclet2.zip
>
>
> It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
> XDoclet1 really did that, because I remember that I personally set this issue against project team.
> I have an 2 super classes for the EJB and a super interface for EJB Interface looking like
> public abstract class AbstractSessionBean implements SessionBean {...}
> public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {
> ...some business methods with xdoclet declarations...
> /**
>      * @ejb.interface-method
>      * @ejb.transaction-method type="Supports"
> */
>     public void additionalMethods () { ... implementation ... }
> }
> public interface AsyncPipes extends Serializable {
>     public void additionalMethods();
> }
> EJB class is declared as:
> /*
> * @ejb.bean ...
> * @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> *                local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
> */
> public class ImportEJB extends AsyncPipesImpl {
>     ... implementation ...
> }
> When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.
> Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.
> Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Created: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml

[Konstantin K. (JIRA) <ji...@co...>]

EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
------------------------------------------------------------------------------------------------------------

                 Key: XDP-240
                 URL: http://jira.codehaus.org/browse/XDP-240
             Project: XDoclet 2 Plugins
          Issue Type: Bug
          Components: ejb
    Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.5, 1.0.4
         Environment: JDK 1.5
ANT 1.7
            Reporter: Konstantin Kasatkin
            Priority: Critical
         Attachments: xdoclet2.zip

It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
XDoclet1 really did that, because I remember that I personally set this issue against project team.

I have an 2 super classes for the EJB and a super interface for EJB Interface looking like

public abstract class AbstractSessionBean implements SessionBean {...}

public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {

...some business methods with xdoclet declarations...
/**
     * @ejb.interface-method
     * @ejb.transaction-method type="Supports"
*/
    public void additionalMethods () { ... implementation ... }
}

public interface AsyncPipes extends Serializable {

    public void additionalMethods();
}


EJB class is declared as:

/*
* @ejb.bean ...
* @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
*                local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
*/
public class ImportEJB extends AsyncPipesImpl {
    ... implementation ...
}

When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.

Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.

Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[Grégory J. (J. <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158648#action_158648 ] 

Grégory Joseph commented on XDP-239:
------------------------------------

JBUM, they're not (or should not be) in random order, but in the order in which they're parsed in the code. In the same spirit as "tag your code to document or generate artifacts out of it", the order in which attributes are declared in your classes (c/sh)ould be meaningful. Inheritance breaks that, unfortunately.

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>         Attachments: TaglibPlugin.java.patch
>
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[xdoclet-plugins-interest] [jira] Commented: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[JBUM (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158650#action_158650 ] 

JBUM commented on XDP-239:
--------------------------

Sorry about the confusion.  I do not mean "random" but it "seemed" to be random at first before I realized it was in the inheritance order - current class first, then its immediate super class, then the next super class, etc.

Yeah, there is no clear cut behavior that'll fit everyones use case.  What I would really love to see is a separation of inherited attributes, similar to Javadocs, but that's not part of the TLD schema - just wishful thinking.

Anyways, let me know what you guys decide.  I'm currently using a modified version of the 1.0.4 version of the TaglibPlugin code that lists the attributes in alphabetical order (or at least in the context of Java Strings).

It would be great if the next rev (1.0.5?) could have this built-in - configurable or not.

Thanks!

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>         Attachments: TaglibPlugin.java.patch
>
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[JBUM (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158624#action_158624 ] 

JBUM commented on XDP-239:
--------------------------

FYI, my patch does not implement the flag (sort) that I was requesting.  Currently, in its state, it will always sort.

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>         Attachments: TaglibPlugin.java.patch
>
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Updated: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[JBUM (JIRA) <ji...@co...>]

     [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

JBUM updated XDP-239:
---------------------

    Attachment: TaglibPlugin.java.patch

Hope this works for you guys...

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>         Attachments: TaglibPlugin.java.patch
>
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[JBUM (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158622#action_158622 ] 

JBUM commented on XDP-239:
--------------------------

Gregory,

I tend to agree that we should also preserve the inheritance order for people who'd like to see them that way.

Could we possibly have a flag (perhaps something called "sort") on the <component> element of the ant task for TaglibPlugin?  By default we can do what's there out of the box.  If sort="true", we can sort the attributes.

The reason why I wanted this is because we produce TLD Docs out of our TLDs and it's very hard to constantly search for attributes when they are in random order.

I will attach a patch for my changes (my first time trying this with SVN). 

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[Grégory J. (J. <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158589#action_158589 ] 

Grégory Joseph commented on XDP-239:
------------------------------------

I for one would be against this - that the inherited attributes are in the wrong place, I'd agree and would probably like them better on top, but otherwise, i'd rather have the tld declare the attributes in the same order as my code - which also influences generated documentation, and as such allows me to put the more important/relevant attributes first.

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[xdoclet-plugins-interest] [jira] Assigned: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[Konstantin P. (JIRA) <ji...@co...>]

     [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Pribluda reassigned XDP-239:
---------------------------------------

    Assignee: Konstantin Pribluda

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[Konstantin P. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158497#action_158497 ] 

Konstantin Pribluda commented on XDP-239:
-----------------------------------------

If you dare to provide a patch,  this issue can be solved more quickly.

> Ability to order all taglib attributes in alphabetical order in generated TLD
> -----------------------------------------------------------------------------
>
>                 Key: XDP-239
>                 URL: http://jira.codehaus.org/browse/XDP-239
>             Project: XDoclet 2 Plugins
>          Issue Type: Improvement
>          Components: web
>    Affects Versions: 1.0.4
>         Environment: Unbuntu 8.04 and JBoss
>            Reporter: JBUM
>            Assignee: Konstantin Pribluda
>
> Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.
> It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.
> It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.
> It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Created: (XDP-239) Ability to order all taglib attributes in alphabetical order in generated TLD

[JBUM (JIRA) <ji...@co...>]

Ability to order all taglib attributes in alphabetical order in generated TLD
-----------------------------------------------------------------------------

                 Key: XDP-239
                 URL: http://jira.codehaus.org/browse/XDP-239
             Project: XDoclet 2 Plugins
          Issue Type: Improvement
          Components: web
    Affects Versions: 1.0.4
         Environment: Unbuntu 8.04 and JBoss
            Reporter: JBUM


Currently, all the inherited attributes of a taglib get listed in the TLD just fine.  However, the inherited ones come at the bottom of the attributes entries for a particular tag and not sorted along with the entire set.

It appears the plugin is using an Arraylist to add attributes and it displays them essentially in that order.

It would be nice to store them so that you retrieve them by alphabetical order of the attribute names.

It would make it much nicer to read the TLD and easier to search for things.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-237) Not able to create struts.xml for struts2 framework using xdoclet-2

[Konstantin P. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157850#action_157850 ] 

Konstantin Pribluda commented on XDP-237:
-----------------------------------------

This is standart way to escape potentially dangerous xml content
( and urls are potentially dangerous, because they can contain
symbols illegal in xml  - like ampersands )

this escape is removed by xml parsers, so struts2 would not see it
at all.

And it is actually xwork, which does action invocation for struts-2
( remember, that struts 2 is relabelew webwork2, and uses xwork ) 

So, plugin is xwork plugin, though now it used to generate struts.xml 

> Not able to create struts.xml for struts2 framework using xdoclet-2 
> --------------------------------------------------------------------
>
>                 Key: XDP-237
>                 URL: http://jira.codehaus.org/browse/XDP-237
>             Project: XDoclet 2 Plugins
>          Issue Type: Test
>            Reporter: ravishankar
>            Assignee: Konstantin Pribluda
>             Fix For: 1.0.5
>
>
> Using xdoclet 1.2.3 we were able to generate the code for struts 1.x framework like struts-config.xml using xdoclet.
> We want to create struts.xml file with all action mapping details from our action classes but we are not able to do it.
> <project name="GlobalBuildProperties" basedir=".">
> 	<property file="build.properties" />
> 	<property name="output.location" value="${project.base}/dist" />
>         <property name="jdev.home" value="C:/JDeveloper" />
>         <property name="codegenerator" value="${jdev.home}/jdev/mywork/CodeGenerator" />
> 	
> 	<!-- Runtime JAR locations for compilation -->
> 	<property name="j2ee.runtime.location" value="${jdev.home}/j2ee/home/lib" />
> 	<property name="struts.runtime.location" value="C:/JDeveloper/jdev/mywork/CodeGenerator/lib/Struts2_Library/Struts2_Library" />
> 	<property name="xdoclet.runtime.location" value="C:/xdoclet2/xdoclet-plugins-dist-1.0.4-bin/xdoclet-plugins-dist-1.0.4/lib" />
> 	<taskdef name="xd" classname="org.xdoclet.ant.XDocletTask">
> 		<classpath>
> 			<fileset dir="${xdoclet.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${j2ee.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${struts.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 		</classpath>
> 	</taskdef>
> </project>
> ============
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="XDocletBuildDemo" basedir=".">
>  <import file="build-properties.xml"/>
>  <target name="run.xdoclet">
>   <xd>
>    <!-- defines the file handled by xdoclet2 -->
>    <fileset dir="${codegenerator}/CodeGenerator/src">
>     <include name="**/*.java"/>
>    </fileset>
>    <!-- defines the processing of a plugin -->
>    <component 
>               classname="org.xdoclet.plugin.struts.StrutsConfigXMLPlugin" 
>               destdir="${project.base}" validate="false" filename="struts.xml"/>
>   <component  classname="org.xdoclet.plugin.xwork.XWorkXMLPlugin" 
>               destdir="${project.base}" package="com.infosys" filename="struts.xml" extends="webwork-default"
>               />              
>   </xd>
>  </target>
> </project>
> But the file is not getting generated.
> created a simple action class
> import com.opensymphony.xwork2.ActionSupport;
> public class HelloAction extends ActionSupport
> {
>     private String message;
>     public String getMessage()
>     {
>         return message;
>     }
>     public void setMessage(String message)
>     {
>         this.message = message;
>     }
>     public String execute() throws Exception
>     {
>         setMessage("Hello! Welcome in the world of Struts2.");
>         
>         return SUCCESS;
>     }
> }
> Please give me a sample of how to create struts.xml file using xdoclet-2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-237) Not able to create struts.xml for struts2 framework using xdoclet-2

[ravishankar (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157829#action_157829 ] 

ravishankar commented on XDP-237:
---------------------------------

so you want to say that even if the code is generated in the following format

*result name="error"><![CDATA[test.jsp]]></result>*

it is not an issue and it will be properly mapped during runtime to *test.jsp*

one more thing I would like to know is that if there is a specific plugin for generating struts.xml file instead of using xwork.xml plugin.

> Not able to create struts.xml for struts2 framework using xdoclet-2 
> --------------------------------------------------------------------
>
>                 Key: XDP-237
>                 URL: http://jira.codehaus.org/browse/XDP-237
>             Project: XDoclet 2 Plugins
>          Issue Type: Test
>            Reporter: ravishankar
>            Assignee: Konstantin Pribluda
>             Fix For: 1.0.5
>
>
> Using xdoclet 1.2.3 we were able to generate the code for struts 1.x framework like struts-config.xml using xdoclet.
> We want to create struts.xml file with all action mapping details from our action classes but we are not able to do it.
> <project name="GlobalBuildProperties" basedir=".">
> 	<property file="build.properties" />
> 	<property name="output.location" value="${project.base}/dist" />
>         <property name="jdev.home" value="C:/JDeveloper" />
>         <property name="codegenerator" value="${jdev.home}/jdev/mywork/CodeGenerator" />
> 	
> 	<!-- Runtime JAR locations for compilation -->
> 	<property name="j2ee.runtime.location" value="${jdev.home}/j2ee/home/lib" />
> 	<property name="struts.runtime.location" value="C:/JDeveloper/jdev/mywork/CodeGenerator/lib/Struts2_Library/Struts2_Library" />
> 	<property name="xdoclet.runtime.location" value="C:/xdoclet2/xdoclet-plugins-dist-1.0.4-bin/xdoclet-plugins-dist-1.0.4/lib" />
> 	<taskdef name="xd" classname="org.xdoclet.ant.XDocletTask">
> 		<classpath>
> 			<fileset dir="${xdoclet.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${j2ee.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${struts.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 		</classpath>
> 	</taskdef>
> </project>
> ============
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="XDocletBuildDemo" basedir=".">
>  <import file="build-properties.xml"/>
>  <target name="run.xdoclet">
>   <xd>
>    <!-- defines the file handled by xdoclet2 -->
>    <fileset dir="${codegenerator}/CodeGenerator/src">
>     <include name="**/*.java"/>
>    </fileset>
>    <!-- defines the processing of a plugin -->
>    <component 
>               classname="org.xdoclet.plugin.struts.StrutsConfigXMLPlugin" 
>               destdir="${project.base}" validate="false" filename="struts.xml"/>
>   <component  classname="org.xdoclet.plugin.xwork.XWorkXMLPlugin" 
>               destdir="${project.base}" package="com.infosys" filename="struts.xml" extends="webwork-default"
>               />              
>   </xd>
>  </target>
> </project>
> But the file is not getting generated.
> created a simple action class
> import com.opensymphony.xwork2.ActionSupport;
> public class HelloAction extends ActionSupport
> {
>     private String message;
>     public String getMessage()
>     {
>         return message;
>     }
>     public void setMessage(String message)
>     {
>         this.message = message;
>     }
>     public String execute() throws Exception
>     {
>         setMessage("Hello! Welcome in the world of Struts2.");
>         
>         return SUCCESS;
>     }
> }
> Please give me a sample of how to create struts.xml file using xdoclet-2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-237) Not able to create struts.xml for struts2 framework using xdoclet-2

[Konstantin P. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157756#action_157756 ] 

Konstantin Pribluda commented on XDP-237:
-----------------------------------------

There is no such setting, so if you are really like to get rid of cdata wrapping,
you will have to grab sources of module, change  jelly template and recompile it

but be aware, that resulting mappings may be wrong then

> Not able to create struts.xml for struts2 framework using xdoclet-2 
> --------------------------------------------------------------------
>
>                 Key: XDP-237
>                 URL: http://jira.codehaus.org/browse/XDP-237
>             Project: XDoclet 2 Plugins
>          Issue Type: Test
>            Reporter: ravishankar
>            Assignee: Konstantin Pribluda
>             Fix For: 1.0.5
>
>
> Using xdoclet 1.2.3 we were able to generate the code for struts 1.x framework like struts-config.xml using xdoclet.
> We want to create struts.xml file with all action mapping details from our action classes but we are not able to do it.
> <project name="GlobalBuildProperties" basedir=".">
> 	<property file="build.properties" />
> 	<property name="output.location" value="${project.base}/dist" />
>         <property name="jdev.home" value="C:/JDeveloper" />
>         <property name="codegenerator" value="${jdev.home}/jdev/mywork/CodeGenerator" />
> 	
> 	<!-- Runtime JAR locations for compilation -->
> 	<property name="j2ee.runtime.location" value="${jdev.home}/j2ee/home/lib" />
> 	<property name="struts.runtime.location" value="C:/JDeveloper/jdev/mywork/CodeGenerator/lib/Struts2_Library/Struts2_Library" />
> 	<property name="xdoclet.runtime.location" value="C:/xdoclet2/xdoclet-plugins-dist-1.0.4-bin/xdoclet-plugins-dist-1.0.4/lib" />
> 	<taskdef name="xd" classname="org.xdoclet.ant.XDocletTask">
> 		<classpath>
> 			<fileset dir="${xdoclet.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${j2ee.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${struts.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 		</classpath>
> 	</taskdef>
> </project>
> ============
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="XDocletBuildDemo" basedir=".">
>  <import file="build-properties.xml"/>
>  <target name="run.xdoclet">
>   <xd>
>    <!-- defines the file handled by xdoclet2 -->
>    <fileset dir="${codegenerator}/CodeGenerator/src">
>     <include name="**/*.java"/>
>    </fileset>
>    <!-- defines the processing of a plugin -->
>    <component 
>               classname="org.xdoclet.plugin.struts.StrutsConfigXMLPlugin" 
>               destdir="${project.base}" validate="false" filename="struts.xml"/>
>   <component  classname="org.xdoclet.plugin.xwork.XWorkXMLPlugin" 
>               destdir="${project.base}" package="com.infosys" filename="struts.xml" extends="webwork-default"
>               />              
>   </xd>
>  </target>
> </project>
> But the file is not getting generated.
> created a simple action class
> import com.opensymphony.xwork2.ActionSupport;
> public class HelloAction extends ActionSupport
> {
>     private String message;
>     public String getMessage()
>     {
>         return message;
>     }
>     public void setMessage(String message)
>     {
>         this.message = message;
>     }
>     public String execute() throws Exception
>     {
>         setMessage("Hello! Welcome in the world of Struts2.");
>         
>         return SUCCESS;
>     }
> }
> Please give me a sample of how to create struts.xml file using xdoclet-2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-237) Not able to create struts.xml for struts2 framework using xdoclet-2

[ravishankar (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157750#action_157750 ] 

ravishankar commented on XDP-237:
---------------------------------

So please let me know what needs to be done so that my generated struts.xml structure looks like this

<action name="struts2Action" class="com.infosys.struts2Action">
<result name="success"/>
<result name="error">test.jsp</result>
</action>
and not

<action name="struts2Action" class="com.infosys.struts2Action">
<result name="success"/>
<result name="error"><![CDATA[test.jsp]]></result>
</action>

> Not able to create struts.xml for struts2 framework using xdoclet-2 
> --------------------------------------------------------------------
>
>                 Key: XDP-237
>                 URL: http://jira.codehaus.org/browse/XDP-237
>             Project: XDoclet 2 Plugins
>          Issue Type: Test
>            Reporter: ravishankar
>            Assignee: Konstantin Pribluda
>             Fix For: 1.0.5
>
>
> Using xdoclet 1.2.3 we were able to generate the code for struts 1.x framework like struts-config.xml using xdoclet.
> We want to create struts.xml file with all action mapping details from our action classes but we are not able to do it.
> <project name="GlobalBuildProperties" basedir=".">
> 	<property file="build.properties" />
> 	<property name="output.location" value="${project.base}/dist" />
>         <property name="jdev.home" value="C:/JDeveloper" />
>         <property name="codegenerator" value="${jdev.home}/jdev/mywork/CodeGenerator" />
> 	
> 	<!-- Runtime JAR locations for compilation -->
> 	<property name="j2ee.runtime.location" value="${jdev.home}/j2ee/home/lib" />
> 	<property name="struts.runtime.location" value="C:/JDeveloper/jdev/mywork/CodeGenerator/lib/Struts2_Library/Struts2_Library" />
> 	<property name="xdoclet.runtime.location" value="C:/xdoclet2/xdoclet-plugins-dist-1.0.4-bin/xdoclet-plugins-dist-1.0.4/lib" />
> 	<taskdef name="xd" classname="org.xdoclet.ant.XDocletTask">
> 		<classpath>
> 			<fileset dir="${xdoclet.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${j2ee.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${struts.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 		</classpath>
> 	</taskdef>
> </project>
> ============
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="XDocletBuildDemo" basedir=".">
>  <import file="build-properties.xml"/>
>  <target name="run.xdoclet">
>   <xd>
>    <!-- defines the file handled by xdoclet2 -->
>    <fileset dir="${codegenerator}/CodeGenerator/src">
>     <include name="**/*.java"/>
>    </fileset>
>    <!-- defines the processing of a plugin -->
>    <component 
>               classname="org.xdoclet.plugin.struts.StrutsConfigXMLPlugin" 
>               destdir="${project.base}" validate="false" filename="struts.xml"/>
>   <component  classname="org.xdoclet.plugin.xwork.XWorkXMLPlugin" 
>               destdir="${project.base}" package="com.infosys" filename="struts.xml" extends="webwork-default"
>               />              
>   </xd>
>  </target>
> </project>
> But the file is not getting generated.
> created a simple action class
> import com.opensymphony.xwork2.ActionSupport;
> public class HelloAction extends ActionSupport
> {
>     private String message;
>     public String getMessage()
>     {
>         return message;
>     }
>     public void setMessage(String message)
>     {
>         this.message = message;
>     }
>     public String execute() throws Exception
>     {
>         setMessage("Hello! Welcome in the world of Struts2.");
>         
>         return SUCCESS;
>     }
> }
> Please give me a sample of how to create struts.xml file using xdoclet-2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Closed: (XDP-237) Not able to create struts.xml for struts2 framework using xdoclet-2

[Konstantin P. (JIRA) <ji...@co...>]

     [ http://jira.codehaus.org/browse/XDP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Pribluda closed XDP-237.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.5

> Not able to create struts.xml for struts2 framework using xdoclet-2 
> --------------------------------------------------------------------
>
>                 Key: XDP-237
>                 URL: http://jira.codehaus.org/browse/XDP-237
>             Project: XDoclet 2 Plugins
>          Issue Type: Test
>            Reporter: ravishankar
>            Assignee: Konstantin Pribluda
>             Fix For: 1.0.5
>
>
> Using xdoclet 1.2.3 we were able to generate the code for struts 1.x framework like struts-config.xml using xdoclet.
> We want to create struts.xml file with all action mapping details from our action classes but we are not able to do it.
> <project name="GlobalBuildProperties" basedir=".">
> 	<property file="build.properties" />
> 	<property name="output.location" value="${project.base}/dist" />
>         <property name="jdev.home" value="C:/JDeveloper" />
>         <property name="codegenerator" value="${jdev.home}/jdev/mywork/CodeGenerator" />
> 	
> 	<!-- Runtime JAR locations for compilation -->
> 	<property name="j2ee.runtime.location" value="${jdev.home}/j2ee/home/lib" />
> 	<property name="struts.runtime.location" value="C:/JDeveloper/jdev/mywork/CodeGenerator/lib/Struts2_Library/Struts2_Library" />
> 	<property name="xdoclet.runtime.location" value="C:/xdoclet2/xdoclet-plugins-dist-1.0.4-bin/xdoclet-plugins-dist-1.0.4/lib" />
> 	<taskdef name="xd" classname="org.xdoclet.ant.XDocletTask">
> 		<classpath>
> 			<fileset dir="${xdoclet.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${j2ee.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${struts.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 		</classpath>
> 	</taskdef>
> </project>
> ============
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="XDocletBuildDemo" basedir=".">
>  <import file="build-properties.xml"/>
>  <target name="run.xdoclet">
>   <xd>
>    <!-- defines the file handled by xdoclet2 -->
>    <fileset dir="${codegenerator}/CodeGenerator/src">
>     <include name="**/*.java"/>
>    </fileset>
>    <!-- defines the processing of a plugin -->
>    <component 
>               classname="org.xdoclet.plugin.struts.StrutsConfigXMLPlugin" 
>               destdir="${project.base}" validate="false" filename="struts.xml"/>
>   <component  classname="org.xdoclet.plugin.xwork.XWorkXMLPlugin" 
>               destdir="${project.base}" package="com.infosys" filename="struts.xml" extends="webwork-default"
>               />              
>   </xd>
>  </target>
> </project>
> But the file is not getting generated.
> created a simple action class
> import com.opensymphony.xwork2.ActionSupport;
> public class HelloAction extends ActionSupport
> {
>     private String message;
>     public String getMessage()
>     {
>         return message;
>     }
>     public void setMessage(String message)
>     {
>         this.message = message;
>     }
>     public String execute() throws Exception
>     {
>         setMessage("Hello! Welcome in the world of Struts2.");
>         
>         return SUCCESS;
>     }
> }
> Please give me a sample of how to create struts.xml file using xdoclet-2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-237) Not able to create struts.xml for struts2 framework using xdoclet-2

[Konstantin P. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157699#action_157699 ] 

Konstantin Pribluda commented on XDP-237:
-----------------------------------------

CDATA is the normal way to escape potentially illegal XML content 
( no, it does not harm S2, it is removed by parser transparently )

urls are potentially incompatible and may contain  characters illegal in xml
elements - that's why we put them in cdata sections

> Not able to create struts.xml for struts2 framework using xdoclet-2 
> --------------------------------------------------------------------
>
>                 Key: XDP-237
>                 URL: http://jira.codehaus.org/browse/XDP-237
>             Project: XDoclet 2 Plugins
>          Issue Type: Test
>            Reporter: ravishankar
>            Assignee: Konstantin Pribluda
>             Fix For: 1.0.5
>
>
> Using xdoclet 1.2.3 we were able to generate the code for struts 1.x framework like struts-config.xml using xdoclet.
> We want to create struts.xml file with all action mapping details from our action classes but we are not able to do it.
> <project name="GlobalBuildProperties" basedir=".">
> 	<property file="build.properties" />
> 	<property name="output.location" value="${project.base}/dist" />
>         <property name="jdev.home" value="C:/JDeveloper" />
>         <property name="codegenerator" value="${jdev.home}/jdev/mywork/CodeGenerator" />
> 	
> 	<!-- Runtime JAR locations for compilation -->
> 	<property name="j2ee.runtime.location" value="${jdev.home}/j2ee/home/lib" />
> 	<property name="struts.runtime.location" value="C:/JDeveloper/jdev/mywork/CodeGenerator/lib/Struts2_Library/Struts2_Library" />
> 	<property name="xdoclet.runtime.location" value="C:/xdoclet2/xdoclet-plugins-dist-1.0.4-bin/xdoclet-plugins-dist-1.0.4/lib" />
> 	<taskdef name="xd" classname="org.xdoclet.ant.XDocletTask">
> 		<classpath>
> 			<fileset dir="${xdoclet.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${j2ee.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${struts.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 		</classpath>
> 	</taskdef>
> </project>
> ============
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="XDocletBuildDemo" basedir=".">
>  <import file="build-properties.xml"/>
>  <target name="run.xdoclet">
>   <xd>
>    <!-- defines the file handled by xdoclet2 -->
>    <fileset dir="${codegenerator}/CodeGenerator/src">
>     <include name="**/*.java"/>
>    </fileset>
>    <!-- defines the processing of a plugin -->
>    <component 
>               classname="org.xdoclet.plugin.struts.StrutsConfigXMLPlugin" 
>               destdir="${project.base}" validate="false" filename="struts.xml"/>
>   <component  classname="org.xdoclet.plugin.xwork.XWorkXMLPlugin" 
>               destdir="${project.base}" package="com.infosys" filename="struts.xml" extends="webwork-default"
>               />              
>   </xd>
>  </target>
> </project>
> But the file is not getting generated.
> created a simple action class
> import com.opensymphony.xwork2.ActionSupport;
> public class HelloAction extends ActionSupport
> {
>     private String message;
>     public String getMessage()
>     {
>         return message;
>     }
>     public void setMessage(String message)
>     {
>         this.message = message;
>     }
>     public String execute() throws Exception
>     {
>         setMessage("Hello! Welcome in the world of Struts2.");
>         
>         return SUCCESS;
>     }
> }
> Please give me a sample of how to create struts.xml file using xdoclet-2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[xdoclet-plugins-interest] [jira] Commented: (XDP-237) Not able to create struts.xml for struts2 framework using xdoclet-2

[ravishankar (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/XDP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157659#action_157659 ] 

ravishankar commented on XDP-237:
---------------------------------

Any updates on why ""><![CDATA[test.xml]]>" is getting generated and how can it be removed.

> Not able to create struts.xml for struts2 framework using xdoclet-2 
> --------------------------------------------------------------------
>
>                 Key: XDP-237
>                 URL: http://jira.codehaus.org/browse/XDP-237
>             Project: XDoclet 2 Plugins
>          Issue Type: Test
>            Reporter: ravishankar
>            Assignee: Konstantin Pribluda
>
> Using xdoclet 1.2.3 we were able to generate the code for struts 1.x framework like struts-config.xml using xdoclet.
> We want to create struts.xml file with all action mapping details from our action classes but we are not able to do it.
> <project name="GlobalBuildProperties" basedir=".">
> 	<property file="build.properties" />
> 	<property name="output.location" value="${project.base}/dist" />
>         <property name="jdev.home" value="C:/JDeveloper" />
>         <property name="codegenerator" value="${jdev.home}/jdev/mywork/CodeGenerator" />
> 	
> 	<!-- Runtime JAR locations for compilation -->
> 	<property name="j2ee.runtime.location" value="${jdev.home}/j2ee/home/lib" />
> 	<property name="struts.runtime.location" value="C:/JDeveloper/jdev/mywork/CodeGenerator/lib/Struts2_Library/Struts2_Library" />
> 	<property name="xdoclet.runtime.location" value="C:/xdoclet2/xdoclet-plugins-dist-1.0.4-bin/xdoclet-plugins-dist-1.0.4/lib" />
> 	<taskdef name="xd" classname="org.xdoclet.ant.XDocletTask">
> 		<classpath>
> 			<fileset dir="${xdoclet.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${j2ee.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 			<fileset dir="${struts.runtime.location}">
> 				<include name="**/*.jar" />
> 			</fileset>
> 		</classpath>
> 	</taskdef>
> </project>
> ============
> <?xml version="1.0" encoding="UTF-8" ?>
> <project name="XDocletBuildDemo" basedir=".">
>  <import file="build-properties.xml"/>
>  <target name="run.xdoclet">
>   <xd>
>    <!-- defines the file handled by xdoclet2 -->
>    <fileset dir="${codegenerator}/CodeGenerator/src">
>     <include name="**/*.java"/>
>    </fileset>
>    <!-- defines the processing of a plugin -->
>    <component 
>               classname="org.xdoclet.plugin.struts.StrutsConfigXMLPlugin" 
>               destdir="${project.base}" validate="false" filename="struts.xml"/>
>   <component  classname="org.xdoclet.plugin.xwork.XWorkXMLPlugin" 
>               destdir="${project.base}" package="com.infosys" filename="struts.xml" extends="webwork-default"
>               />              
>   </xd>
>  </target>
> </project>
> But the file is not getting generated.
> created a simple action class
> import com.opensymphony.xwork2.ActionSupport;
> public class HelloAction extends ActionSupport
> {
>     private String message;
>     public String getMessage()
>     {
>         return message;
>     }
>     public void setMessage(String message)
>     {
>         this.message = message;
>     }
>     public String execute() throws Exception
>     {
>         setMessage("Hello! Welcome in the world of Struts2.");
>         
>         return SUCCESS;
>     }
> }
> Please give me a sample of how to create struts.xml file using xdoclet-2 plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira