Re: [Springframework-developer] spring xdoclet module

[Craig W. <cr...@ha...>]

I initially added the Spring tags. What's there is the result of what I
was using on a project, but nothing else. It has been my intent to go back
and look for opportunities to enhance it, but I simply haven't had the
time.

I think that there's a lot of opportunity here, especially WRT to creating
tags for controllers. I'm thinking that instead of using @spring.bean to
declare a controller, you might have @spring.controller which abstracts
away all of the stuff that goes along with a controller. Likewise, you've
identified some opportunities with remoting.

All of this is good stuff, but as I mentioned, my other priorities have
prevented me from revisiting this stuff. You should certainly feel free to
submit enhancement ideas in JIRA and perhaps someone could get around to
implementing your ideas. Or you could even submit patches.

>
>   are there any plans to add further enhancements to the xdoclet module
> for
> spring? is it even "maintained" by anyone involved directly w/ spring?
>
>   i feel that the @spring.bean tag is somewhat limiting because it does
> not
> let me define a class name, and instead just assumes that it should
> create an entry for that class. while this is true most of the time, in
> instances where i might be using a MultiActionController, it'd be nice
> if i could specify the MethodNameResolver configuration in the same
> class since the two are directly related.
>
>   there are also other minor additions, such as being able to generate
> remote interfaces from business interfaces when using remoting (i
> already achieve this through a simple doclet template), creating
> "standard" tags for some bean definitions (ie: jaxrpc proxy)  that i
> feel would be great additions. is anyone else interested in these types
> of enhancements?
>
> --
> -jae