Dmitri Colebatch wrote:
> On Tue, 4 Sep 2001, Rickard [iso-8859-1] �berg wrote:
> > "Messy" was my thought. Why do you need it? Why is it a requirement?
>
> for the situations where you have one servlet and multiple views of that
> servlet that depend on different configurations - unless I'm missing a
> really obvious way to do that, I typically have a init-param that is the
> name of the jsp to use, so I'd need another servlet tag.
So.. you mean you have one servlet, which redirects to multiple JSP's.
And you want to be able to use the same servlet with multiple JSP's.
Right?
If so, I'd recommend that you look at WebWork :-) It allows you to do
that, but much simpler :-)
BTW, I am working on a WebWork configuration doclet Right This Minute.
XDoclet is really cool...
> (o: that was my reaction too... I obviously didn't do as good a job of
> explaining it as the initial requester, but... the interface is generated
> yes, but if you have a heap of clients that call that interface, then you
> want your refactoring tool to update their code... but it cant, because
> the refactoring tool isn't responsible for the remote (or
> local) interface...
>
> hope I've done a better job explaining (o:
Ok, ok, I see. You want pre-compilation checking of interfaces, and also
to be able to refactor the clients in a nice fashion. True, that's a
valid reason, generation or no generation.
/Rickard
--
Rickard �berg
Software Development Specialist
xlurc - Xpedio Link�ping Ubiquitous Research Center
Author of "Mastering RMI"
Email: [EMAIL PROTECTED]
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
