[ti] generation of config files through annotations or xdoclet tags

[Rich Feit <ri...@gmail.com>]

Don,

Thanks for getting the patch from http://issues.apache.org/bugzilla/show_bug.cgi?id=36607 in so quickly.

Here are some notes about this, for general consumption:
    - This checkin provides build-time support for generation of the XDoclet config files using either annotations (apt) or tags (xdoclet).

    - Runtime generation should be a near-term goal, to enable a nice iterative dev experience (simply refreshing the page causes recompilation/regeneration, as Don has described).

    - There are now three sample apps (wars):
         * wars/samples: apt-based.  After 'maven war', deploy wars/samples/target/struts-ti.
         * wars/samples-xdoclet: xdoclet-based.  After 'maven war', deploy wars/samples/target/struts-ti-xdoclet.
         * wars/samples-jsf: apt-based.  After 'maven war', deploy wars/samples/target/struts-ti-jsf.

    - Currently, both apt and xdoclet builds are done through maven goals (see 'build-pageflows-apt' and 'build-pageflows-xdoclet' in /maven.xml).  Ultimately we will need to provide user-consumable ant scripts (or just doc the necessary calls to our ant targets).

    - James, I'd love it if you'd take a look at the maven work I did to make sure it's legit.

    - 3 obvious next steps:
        * unit tests
        * hook in XWork config generation at runtime in iterative dev mode
        * begin (finally) integration, e.g., moving page flow onto XWork interceptors/validation.

Rich


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [ti] generation of config files through annotations or xdoclet tags

[Don Brown <mr...@twdata.org>]

Very cool!  If you have a chance and haven't already, update the wiki status 
page.  Thanks again for the hard work,

Don

Rich Feit wrote:
> Don,
> 
> Thanks for getting the patch from http://issues.apache.org/bugzilla/show_bug.cgi?id=36607 in so quickly.
> 
> Here are some notes about this, for general consumption:
>     - This checkin provides build-time support for generation of the XDoclet config files using either annotations (apt) or tags (xdoclet).
> 
>     - Runtime generation should be a near-term goal, to enable a nice iterative dev experience (simply refreshing the page causes recompilation/regeneration, as Don has described).
> 
>     - There are now three sample apps (wars):
>          * wars/samples: apt-based.  After 'maven war', deploy wars/samples/target/struts-ti.
>          * wars/samples-xdoclet: xdoclet-based.  After 'maven war', deploy wars/samples/target/struts-ti-xdoclet.
>          * wars/samples-jsf: apt-based.  After 'maven war', deploy wars/samples/target/struts-ti-jsf.
> 
>     - Currently, both apt and xdoclet builds are done through maven goals (see 'build-pageflows-apt' and 'build-pageflows-xdoclet' in /maven.xml).  Ultimately we will need to provide user-consumable ant scripts (or just doc the necessary calls to our ant targets).
> 
>     - James, I'd love it if you'd take a look at the maven work I did to make sure it's legit.
> 
>     - 3 obvious next steps:
>         * unit tests
>         * hook in XWork config generation at runtime in iterative dev mode
>         * begin (finally) integration, e.g., moving page flow onto XWork interceptors/validation.
> 
> Rich
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org