> I've used the Struts config stuff to generate a struts-config.xml, but the
> problem is that merge points are needed for each action to inject local
> forwards.  Has then been brought up before?  How are folks dealing with
it?

I initially did it, and unless someone has been putting some work into it
whilst I've been awol, its probably fair to say it still needs a bit of
work.

> Generating a struts-config seems like a one-time thing that requires lots
of
> manual intervention after its generated - is that a correct assessment?

it shouldn't... although off the top of my head, I cant recall exactly which
bits might fall into that category.

> After looking at at struts_config_xml.j now and seeing its use of
> @struts:action-forward.  Shouldn't this really be a merge point rather
> than a tag?  Defining JSP's in the Action is munging the
> model-view-controller separation quite a bit.

I'd argue that whilst what you say is correct, the way it is is still in
line with the idea of xdoclet.  Basically coders like coding, not working in
config files.  The way I see it (and note, others probably have diff
opinions), I would want to start a system with xdoclet, and if I was
releasing it in binary, then the config files would be created with some
defaults - an admin could then change them.  but during development, I want
to do it all in one file - the source file.  this does arguably break mvc,
but its at development time, and does so in a way that doesn't prevent you
simply switching to a pure mvc come release time.

> It would get ugly because
> there would need to be a separate local forward file for each action,
unless
> the merging stuff is more flexible and they could be defined in one XML
file
> and get pulled in from that (is that possible?).

you typically would have lots of merge files...   not ideal.

I have just moved house, and will soon be back on deck - and we're about to
get a heap of struts work at work, so I will no doubt be putting some time
in there.

cheers
dim


_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to