From: <[EMAIL PROTECTED]> > "Konstantin > Piroumian" To: <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> Subject: Re: Action XSP > >From: "Artur Bialecki" <[EMAIL PROTECTED]> > > >> > >> Actions are great, however it would be nice If > >> I could dynamically create them with XSP so in > >> my sitemap I have: > >> <map:action > >> name="my-action" > >> src="/actions/my-action.xsp" > >> logger="action.my-action" > >> /> > >> > >> Where my-action.xsp gets trasfomed to java using > >> some action.xsl, builtin and custom logicsheets. > >> > >> Cocoon already has everything I need other than the > >> action.xsl. > > >Are you looking for this: > >xml-cocoon2\src\java\org\apache\cocoon\components\language\markup\xsp\java\ a > >ction.xsl ? > > >> > >> How would I go about adding this functionality? > >> Where do I start? > > >May I ask a question? Why do you need an XSP based action? IMHO, actions > >should be pure Java classes that perform some programmatic logic and you > >have Generators for XML generation, based on the result from actions. > > >Are there any real use-cases? > > >Konstantin > > > What about dynamically generating a form action from XML/XSP? Currently in > XMLForm you must create your own action to change "controller" behavior (i.e. > how navigation works and other stuff). What if you have hundreds (thousands) of > forms with different controllers? What if you build 20 different forms every > day? Wouldn't it be easier to describe these controllers in xml/xsp than in > java? This could even be part of some larger abstract form description which > would also describe data model in xml/xsp. From larger abstraction would come > bean.java and wizard.java? Model, view, and controller would all be described > in xml. Think markup developers rather than programmers/engineers. > > Am I being crazy here?
No, you're Ok ;) You are talking much about the things that we're discussing a while ago about the controller, flow control, etc. The main two ideas were: to use some XML description of the flow and to use scripting language for that (like Schecoon). That time we couldn't come to a consensus about the best approach. >From my point of view I can say, that now I see a very good usage for XSP actions (and even XSP without Cocoon with some other flow x-language). Konstantin > > --Michael > > > > > Thanks, > > > > Artur... > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
