You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <te...@gmail.com> on 2006/01/05 15:30:23 UTC
Struts/WebWork Merger Tasks (was Q)
Apparently "Q" happens too :)
On 1/5/06, Ted Husted <te...@gmail.com> wrote:
> I'm recapping our ApacheCon presnetation at the NE JUG next week,
> along with Jason's Javapolis presentation. I'll get updated copies of
> both presentations up on the Struts University wiki.
>
> * http://StrutsUniversity.org/Presentations
>
> As I understand it, the general plan at this point is:
>
> 0. Encourage everyone to become involved in both projects
> 1. Ship WebWork 2.2 final
> 2. Resolve any incubator issues in the Open Symphony CVS
> 3. Vote on the accepting the code, and clear the IP with the Incubator
> 4. Import the donated code into the Struts repository
> 5. Develop Struts Action 1.x to 2.x migration tools
> 6. Develop a MailReader for WW 2.2
> 7. Migrate Struts features as desired (chain support, wildcards, etc)
> 8. Develop a migration guide, for both applications and developers
> 9. Release Struts Action 2.0.0 when ready
>
> Of course, some steps can be asychronous. Some of us are already
> working on #3-#6, for example. A few thoughts on #3 are on the wiki
> page,
>
> * http://wiki.apache.org/struts/StrutsAction2
>
> and Don Brown and Rich Feit have started on the infrastructure for the
> Conversion Wizard in the sandbox/ti/phase1/jars/legacy directory.
>
> * http://svn.apache.org/viewcvs.cgi/struts/sandbox/trunk/ti/phase1/jars/legacy/
>
> As to #0 and #1, it looks like the code is ready for the next WW2.2
> RC, but the community is thinking that they need more documentation
> first, so that this can be the best WW release ever.
>
> * http://forums.opensymphony.com/thread.jspa?threadID=12094
>
> WebWork has also started to rework their slate of example
> applications. [Sounds familiar, don't it :)]
>
> * http://forums.opensymphony.com/thread.jspa?threadID=11830
>
> As to #4, there's been a back-and-forth about retaining history from
> external projects, but the current thinking seems to be that it's OK
> to import history from other open source projects. Film at 11.
>
> As to #6, I've updated the MailReader for Struts Action 1.3. I working
> on an Action 1.x training course right now.
>
> * http://StrutsUniversity.org/MailReader+Training+Course
>
> As soon as that is done, I'll get back to creating a version with both
> Struts Action 1.3 and WebWork 2.2 versions of the MailReader in the
> same application, so we can compare apples to apples. I'd also like to
> rework the course for Action 2.x (as well as Shale).
>
> -Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Patrick Lightbody <pl...@gmail.com>.
Ah, they look exactly like PropertySets: http://www.opensymphony.com/
propertyset. PropertySets can have memory/map implementations (like a
DynaBean) or can have persistence implementations (EJB, JDBC, etc).
Yeah, I think adding support would be _really_ easy.
Patrick
On Jan 5, 2006, at 2:36 PM, Don Brown wrote:
> http://jakarta.apache.org/commons/beanutils/commons-beanutils-1.7.0/
> docs/api/org/apache/commons/beanutils/DynaBean.html
>
> DynaBeans aren't really a Map (but they may use one internally for
> storage, and require a backing DynaClass to define their structure
> and data types.
>
> Don
>
> Patrick Lightbody wrote:
>> Pardon my ignorance, but is there some link that describes what
>> DynaBeans are? Currently WW's ValueStack is able to populate Map
>> structures if they are in the value stack. Ie: foo.action?bar=baz
>> will call map.setBar("baz") if a Map is in the stack.
>> On Jan 5, 2006, at 2:17 PM, Don Brown wrote:
>>> Good question. DynaBeans might still be valuable if you use
>>> them further down in your application or generally prefer
>>> working with Map-type structures. If they are only used to
>>> avoid having to write forms, then, correct, they won't be of
>>> much use in XWork.
>>>
>>> If folks don't think Action 2.0 should support DynaBeans in
>>> core, I'm fine leaving them in the legacy package, which
>>> supports the ability to run ActionForms and DynaActionForms
>>> unmodified in Action 2.
>>>
>>> Don
>>>
>>> Laurie Harper wrote:
>>>
>>>> Ex-party sidebar: how much value do DyanBeans add in WW given
>>>> that, if I understand correctly, it can already work directly
>>>> with POJOs? The thing that dyna action forms are there to
>>>> avoid (writing boilerplate action forms) isn't needed in WW is it?
>>>> L.
>>>> Don Brown wrote:
>>>>
>>>>> Off the top of my head:
>>>>>
>>>>> - Wildcards
>>>>> - Chain command executed from Interceptor (like ChainInterceptor)
>>>>> - Chain command executed as Action (an alternate
>>>>> implementation of ActionInvoker)
>>>>> - DynaBean support in ognl
>>>>> - Package properties support (debatable)
>>>>>
>>>>> Don
>>>>>
>>>>> Patrick Lightbody wrote:
>>>>>
>>>>>> Duh, sorry about that. It's been a slow day :)
>>>>>>
>>>>>> Can we talk about more about #7? I think #7 is where the
>>>>>> majority of the time (debate time or development time) will
>>>>>> be spent. What items do you guys have in mind?
>>>>>>
>>>>>> Patrick
>>>>>>
>>>>>> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>>>>>>
>>>>>>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>>>>>>
>>>>>>>> I know there are a few features (probably more) that we'd
>>>>>>>> like to
>>>>>>>> bring forward from Struts Action 1.x to 2.x that aren't in
>>>>>>>> WebWork
>>>>>>>> already. For example, the wildcard support in configuration.
>>>>>>>>
>>>>>>>> Where does that fit in? This current schedule looks like
>>>>>>>> 2.0.0 would
>>>>>>>> be basically WebWork 2.2 + migration tools. Is the plan to
>>>>>>>> add the
>>>>>>>> extra features, like wildcards, to Struts Action 2.1? I'm
>>>>>>>> find with
>>>>>>>> either, but my understanding was that we'd do additional
>>>>>>>> development
>>>>>>>> between WW 2.2 and SAF 2.0.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> That would be item # 7.
>>>>>>>
>>>>>>>> 7. Migrate Struts features as desired (chain support,
>>>>>>>> wildcards, etc)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> We're going to need at least two phases of development
>>>>>>> between WW 2.2
>>>>>>> and SAF 2.0.0.
>>>>>>>
>>>>>>> First, we need to replace the LGPL dependencies and resolve
>>>>>>> any other
>>>>>>> IP/Incubator issues (Item #2).
>>>>>>>
>>>>>>> Second, we would add any missing features, like
>>>>>>> wildcardmappings (Item #7).
>>>>>>>
>>>>>>> Of course, some of this will be asynchronous. Don and Rich
>>>>>>> are doing
>>>>>>> some early work on tools now, but those would change as we
>>>>>>> add missing
>>>>>>> features.
>>>>>>>
>>>>>>> -T.
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> -- ---
>>>>>>> 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
>>>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> 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
>>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Don Brown <mr...@twdata.org>.
http://jakarta.apache.org/commons/beanutils/commons-beanutils-1.7.0/docs/api/org/apache/commons/beanutils/DynaBean.html
DynaBeans aren't really a Map (but they may use one internally for storage, and
require a backing DynaClass to define their structure and data types.
Don
Patrick Lightbody wrote:
> Pardon my ignorance, but is there some link that describes what
> DynaBeans are? Currently WW's ValueStack is able to populate Map
> structures if they are in the value stack. Ie: foo.action?bar=baz will
> call map.setBar("baz") if a Map is in the stack.
>
> On Jan 5, 2006, at 2:17 PM, Don Brown wrote:
>
>> Good question. DynaBeans might still be valuable if you use them
>> further down in your application or generally prefer working with
>> Map-type structures. If they are only used to avoid having to write
>> forms, then, correct, they won't be of much use in XWork.
>>
>> If folks don't think Action 2.0 should support DynaBeans in core, I'm
>> fine leaving them in the legacy package, which supports the ability
>> to run ActionForms and DynaActionForms unmodified in Action 2.
>>
>> Don
>>
>> Laurie Harper wrote:
>>
>>> Ex-party sidebar: how much value do DyanBeans add in WW given that,
>>> if I understand correctly, it can already work directly with POJOs?
>>> The thing that dyna action forms are there to avoid (writing
>>> boilerplate action forms) isn't needed in WW is it?
>>> L.
>>> Don Brown wrote:
>>>
>>>> Off the top of my head:
>>>>
>>>> - Wildcards
>>>> - Chain command executed from Interceptor (like ChainInterceptor)
>>>> - Chain command executed as Action (an alternate implementation of
>>>> ActionInvoker)
>>>> - DynaBean support in ognl
>>>> - Package properties support (debatable)
>>>>
>>>> Don
>>>>
>>>> Patrick Lightbody wrote:
>>>>
>>>>> Duh, sorry about that. It's been a slow day :)
>>>>>
>>>>> Can we talk about more about #7? I think #7 is where the majority
>>>>> of the time (debate time or development time) will be spent. What
>>>>> items do you guys have in mind?
>>>>>
>>>>> Patrick
>>>>>
>>>>> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>>>>>
>>>>>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>>>>>
>>>>>>> I know there are a few features (probably more) that we'd like to
>>>>>>> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
>>>>>>> already. For example, the wildcard support in configuration.
>>>>>>>
>>>>>>> Where does that fit in? This current schedule looks like 2.0.0
>>>>>>> would
>>>>>>> be basically WebWork 2.2 + migration tools. Is the plan to add the
>>>>>>> extra features, like wildcards, to Struts Action 2.1? I'm find with
>>>>>>> either, but my understanding was that we'd do additional
>>>>>>> development
>>>>>>> between WW 2.2 and SAF 2.0.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> That would be item # 7.
>>>>>>
>>>>>>> 7. Migrate Struts features as desired (chain support,
>>>>>>> wildcards, etc)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> We're going to need at least two phases of development between WW
>>>>>> 2.2
>>>>>> and SAF 2.0.0.
>>>>>>
>>>>>> First, we need to replace the LGPL dependencies and resolve any
>>>>>> other
>>>>>> IP/Incubator issues (Item #2).
>>>>>>
>>>>>> Second, we would add any missing features, like wildcardmappings
>>>>>> (Item #7).
>>>>>>
>>>>>> Of course, some of this will be asynchronous. Don and Rich are doing
>>>>>> some early work on tools now, but those would change as we add
>>>>>> missing
>>>>>> features.
>>>>>>
>>>>>> -T.
>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>> ---
>>>>>> 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
>>>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>
>
> ---------------------------------------------------------------------
> 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
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Patrick Lightbody <pl...@gmail.com>.
Pardon my ignorance, but is there some link that describes what
DynaBeans are? Currently WW's ValueStack is able to populate Map
structures if they are in the value stack. Ie: foo.action?bar=baz
will call map.setBar("baz") if a Map is in the stack.
On Jan 5, 2006, at 2:17 PM, Don Brown wrote:
> Good question. DynaBeans might still be valuable if you use them
> further down in your application or generally prefer working with
> Map-type structures. If they are only used to avoid having to
> write forms, then, correct, they won't be of much use in XWork.
>
> If folks don't think Action 2.0 should support DynaBeans in core,
> I'm fine leaving them in the legacy package, which supports the
> ability to run ActionForms and DynaActionForms unmodified in Action 2.
>
> Don
>
> Laurie Harper wrote:
>> Ex-party sidebar: how much value do DyanBeans add in WW given
>> that, if I understand correctly, it can already work directly with
>> POJOs? The thing that dyna action forms are there to avoid
>> (writing boilerplate action forms) isn't needed in WW is it?
>> L.
>> Don Brown wrote:
>>> Off the top of my head:
>>>
>>> - Wildcards
>>> - Chain command executed from Interceptor (like ChainInterceptor)
>>> - Chain command executed as Action (an alternate implementation
>>> of ActionInvoker)
>>> - DynaBean support in ognl
>>> - Package properties support (debatable)
>>>
>>> Don
>>>
>>> Patrick Lightbody wrote:
>>>
>>>> Duh, sorry about that. It's been a slow day :)
>>>>
>>>> Can we talk about more about #7? I think #7 is where the
>>>> majority of the time (debate time or development time) will be
>>>> spent. What items do you guys have in mind?
>>>>
>>>> Patrick
>>>>
>>>> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>>>>
>>>>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>>>>
>>>>>> I know there are a few features (probably more) that we'd like to
>>>>>> bring forward from Struts Action 1.x to 2.x that aren't in
>>>>>> WebWork
>>>>>> already. For example, the wildcard support in configuration.
>>>>>>
>>>>>> Where does that fit in? This current schedule looks like 2.0.0
>>>>>> would
>>>>>> be basically WebWork 2.2 + migration tools. Is the plan to add
>>>>>> the
>>>>>> extra features, like wildcards, to Struts Action 2.1? I'm find
>>>>>> with
>>>>>> either, but my understanding was that we'd do additional
>>>>>> development
>>>>>> between WW 2.2 and SAF 2.0.
>>>>>
>>>>>
>>>>>
>>>>> That would be item # 7.
>>>>>
>>>>>> 7. Migrate Struts features as desired (chain support,
>>>>>> wildcards, etc)
>>>>>
>>>>>
>>>>>
>>>>> We're going to need at least two phases of development between
>>>>> WW 2.2
>>>>> and SAF 2.0.0.
>>>>>
>>>>> First, we need to replace the LGPL dependencies and resolve any
>>>>> other
>>>>> IP/Incubator issues (Item #2).
>>>>>
>>>>> Second, we would add any missing features, like
>>>>> wildcardmappings (Item #7).
>>>>>
>>>>> Of course, some of this will be asynchronous. Don and Rich are
>>>>> doing
>>>>> some early work on tools now, but those would change as we add
>>>>> missing
>>>>> features.
>>>>>
>>>>> -T.
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> 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
>>>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Don Brown <mr...@twdata.org>.
Good question. DynaBeans might still be valuable if you use them further down
in your application or generally prefer working with Map-type structures. If
they are only used to avoid having to write forms, then, correct, they won't be
of much use in XWork.
If folks don't think Action 2.0 should support DynaBeans in core, I'm fine
leaving them in the legacy package, which supports the ability to run
ActionForms and DynaActionForms unmodified in Action 2.
Don
Laurie Harper wrote:
> Ex-party sidebar: how much value do DyanBeans add in WW given that, if I
> understand correctly, it can already work directly with POJOs? The thing
> that dyna action forms are there to avoid (writing boilerplate action
> forms) isn't needed in WW is it?
>
> L.
>
> Don Brown wrote:
>
>> Off the top of my head:
>>
>> - Wildcards
>> - Chain command executed from Interceptor (like ChainInterceptor)
>> - Chain command executed as Action (an alternate implementation of
>> ActionInvoker)
>> - DynaBean support in ognl
>> - Package properties support (debatable)
>>
>> Don
>>
>> Patrick Lightbody wrote:
>>
>>> Duh, sorry about that. It's been a slow day :)
>>>
>>> Can we talk about more about #7? I think #7 is where the majority of
>>> the time (debate time or development time) will be spent. What items
>>> do you guys have in mind?
>>>
>>> Patrick
>>>
>>> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>>>
>>>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>>>
>>>>> I know there are a few features (probably more) that we'd like to
>>>>> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
>>>>> already. For example, the wildcard support in configuration.
>>>>>
>>>>> Where does that fit in? This current schedule looks like 2.0.0 would
>>>>> be basically WebWork 2.2 + migration tools. Is the plan to add the
>>>>> extra features, like wildcards, to Struts Action 2.1? I'm find with
>>>>> either, but my understanding was that we'd do additional development
>>>>> between WW 2.2 and SAF 2.0.
>>>>
>>>>
>>>>
>>>> That would be item # 7.
>>>>
>>>>> 7. Migrate Struts features as desired (chain support, wildcards,
>>>>> etc)
>>>>
>>>>
>>>>
>>>> We're going to need at least two phases of development between WW 2.2
>>>> and SAF 2.0.0.
>>>>
>>>> First, we need to replace the LGPL dependencies and resolve any other
>>>> IP/Incubator issues (Item #2).
>>>>
>>>> Second, we would add any missing features, like wildcardmappings
>>>> (Item #7).
>>>>
>>>> Of course, some of this will be asynchronous. Don and Rich are doing
>>>> some early work on tools now, but those would change as we add missing
>>>> features.
>>>>
>>>> -T.
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>>
>
>
> ---------------------------------------------------------------------
> 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
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Laurie Harper <la...@holoweb.net>.
Ex-party sidebar: how much value do DyanBeans add in WW given that, if I
understand correctly, it can already work directly with POJOs? The thing
that dyna action forms are there to avoid (writing boilerplate action
forms) isn't needed in WW is it?
L.
Don Brown wrote:
> Off the top of my head:
>
> - Wildcards
> - Chain command executed from Interceptor (like ChainInterceptor)
> - Chain command executed as Action (an alternate implementation of
> ActionInvoker)
> - DynaBean support in ognl
> - Package properties support (debatable)
>
> Don
>
> Patrick Lightbody wrote:
>> Duh, sorry about that. It's been a slow day :)
>>
>> Can we talk about more about #7? I think #7 is where the majority of
>> the time (debate time or development time) will be spent. What items
>> do you guys have in mind?
>>
>> Patrick
>>
>> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>>
>>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>>
>>>> I know there are a few features (probably more) that we'd like to
>>>> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
>>>> already. For example, the wildcard support in configuration.
>>>>
>>>> Where does that fit in? This current schedule looks like 2.0.0 would
>>>> be basically WebWork 2.2 + migration tools. Is the plan to add the
>>>> extra features, like wildcards, to Struts Action 2.1? I'm find with
>>>> either, but my understanding was that we'd do additional development
>>>> between WW 2.2 and SAF 2.0.
>>>
>>>
>>> That would be item # 7.
>>>
>>>> 7. Migrate Struts features as desired (chain support, wildcards, etc)
>>>
>>>
>>> We're going to need at least two phases of development between WW 2.2
>>> and SAF 2.0.0.
>>>
>>> First, we need to replace the LGPL dependencies and resolve any other
>>> IP/Incubator issues (Item #2).
>>>
>>> Second, we would add any missing features, like wildcardmappings
>>> (Item #7).
>>>
>>> Of course, some of this will be asynchronous. Don and Rich are doing
>>> some early work on tools now, but those would change as we add missing
>>> features.
>>>
>>> -T.
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Don Brown <mr...@twdata.org>.
Patrick Lightbody wrote:
> OK. There are a lot of things we want to do with WW that may or may not
> have to be done to support these things. My personal list includes:
>
> - cleaning up configuration code
> - cleaning up ActionContext/ActionInvocation/ActionProxy confusion
>
> Would you imagine those would be included in SAF 2.0, or would we defer
> most of what would have been WW 2.3 over to SAF 2.1?
I think we should defer. I'd still like to get an alpha release out by March
assuming WW 2.2 ships soon. Also hopefully soon, we'll start using JIRA so we
can manage our roadmap better and start getting releases out every few months....
Still dreaming,
Don
>
> On Jan 5, 2006, at 12:21 PM, Don Brown wrote:
>
>> Off the top of my head:
>>
>> - Wildcards
>> - Chain command executed from Interceptor (like ChainInterceptor)
>> - Chain command executed as Action (an alternate implementation of
>> ActionInvoker)
>> - DynaBean support in ognl
>> - Package properties support (debatable)
>>
>> Don
>>
>> Patrick Lightbody wrote:
>>
>>> Duh, sorry about that. It's been a slow day :)
>>> Can we talk about more about #7? I think #7 is where the majority
>>> of the time (debate time or development time) will be spent. What
>>> items do you guys have in mind?
>>> Patrick
>>> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>>>
>>>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>>>
>>>>> I know there are a few features (probably more) that we'd like to
>>>>> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
>>>>> already. For example, the wildcard support in configuration.
>>>>>
>>>>> Where does that fit in? This current schedule looks like 2.0.0 would
>>>>> be basically WebWork 2.2 + migration tools. Is the plan to add the
>>>>> extra features, like wildcards, to Struts Action 2.1? I'm find with
>>>>> either, but my understanding was that we'd do additional development
>>>>> between WW 2.2 and SAF 2.0.
>>>>
>>>>
>>>>
>>>> That would be item # 7.
>>>>
>>>>> 7. Migrate Struts features as desired (chain support, wildcards,
>>>>> etc)
>>>>
>>>>
>>>>
>>>> We're going to need at least two phases of development between WW 2.2
>>>> and SAF 2.0.0.
>>>>
>>>> First, we need to replace the LGPL dependencies and resolve any other
>>>> IP/Incubator issues (Item #2).
>>>>
>>>> Second, we would add any missing features, like wildcardmappings
>>>> (Item #7).
>>>>
>>>> Of course, some of this will be asynchronous. Don and Rich are doing
>>>> some early work on tools now, but those would change as we add missing
>>>> features.
>>>>
>>>> -T.
>>>>
>>>> -------------------------------------------------------------------- -
>>>> 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
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Patrick Lightbody <pl...@gmail.com>.
OK. There are a lot of things we want to do with WW that may or may
not have to be done to support these things. My personal list includes:
- cleaning up configuration code
- cleaning up ActionContext/ActionInvocation/ActionProxy confusion
Would you imagine those would be included in SAF 2.0, or would we
defer most of what would have been WW 2.3 over to SAF 2.1?
On Jan 5, 2006, at 12:21 PM, Don Brown wrote:
> Off the top of my head:
>
> - Wildcards
> - Chain command executed from Interceptor (like ChainInterceptor)
> - Chain command executed as Action (an alternate implementation of
> ActionInvoker)
> - DynaBean support in ognl
> - Package properties support (debatable)
>
> Don
>
> Patrick Lightbody wrote:
>> Duh, sorry about that. It's been a slow day :)
>> Can we talk about more about #7? I think #7 is where the majority
>> of the time (debate time or development time) will be spent. What
>> items do you guys have in mind?
>> Patrick
>> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>>
>>>> I know there are a few features (probably more) that we'd like to
>>>> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
>>>> already. For example, the wildcard support in configuration.
>>>>
>>>> Where does that fit in? This current schedule looks like 2.0.0
>>>> would
>>>> be basically WebWork 2.2 + migration tools. Is the plan to add the
>>>> extra features, like wildcards, to Struts Action 2.1? I'm find with
>>>> either, but my understanding was that we'd do additional
>>>> development
>>>> between WW 2.2 and SAF 2.0.
>>>
>>>
>>> That would be item # 7.
>>>
>>>> 7. Migrate Struts features as desired (chain support,
>>>> wildcards, etc)
>>>
>>>
>>> We're going to need at least two phases of development between WW
>>> 2.2
>>> and SAF 2.0.0.
>>>
>>> First, we need to replace the LGPL dependencies and resolve any
>>> other
>>> IP/Incubator issues (Item #2).
>>>
>>> Second, we would add any missing features, like wildcardmappings
>>> (Item #7).
>>>
>>> Of course, some of this will be asynchronous. Don and Rich are doing
>>> some early work on tools now, but those would change as we add
>>> missing
>>> features.
>>>
>>> -T.
>>>
>>> --------------------------------------------------------------------
>>> -
>>> 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
>
>
> ---------------------------------------------------------------------
> 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
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Don Brown <mr...@twdata.org>.
Off the top of my head:
- Wildcards
- Chain command executed from Interceptor (like ChainInterceptor)
- Chain command executed as Action (an alternate implementation of ActionInvoker)
- DynaBean support in ognl
- Package properties support (debatable)
Don
Patrick Lightbody wrote:
> Duh, sorry about that. It's been a slow day :)
>
> Can we talk about more about #7? I think #7 is where the majority of
> the time (debate time or development time) will be spent. What items do
> you guys have in mind?
>
> Patrick
>
> On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
>
>> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>>
>>> I know there are a few features (probably more) that we'd like to
>>> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
>>> already. For example, the wildcard support in configuration.
>>>
>>> Where does that fit in? This current schedule looks like 2.0.0 would
>>> be basically WebWork 2.2 + migration tools. Is the plan to add the
>>> extra features, like wildcards, to Struts Action 2.1? I'm find with
>>> either, but my understanding was that we'd do additional development
>>> between WW 2.2 and SAF 2.0.
>>
>>
>> That would be item # 7.
>>
>>> 7. Migrate Struts features as desired (chain support, wildcards, etc)
>>
>>
>> We're going to need at least two phases of development between WW 2.2
>> and SAF 2.0.0.
>>
>> First, we need to replace the LGPL dependencies and resolve any other
>> IP/Incubator issues (Item #2).
>>
>> Second, we would add any missing features, like wildcardmappings
>> (Item #7).
>>
>> Of course, some of this will be asynchronous. Don and Rich are doing
>> some early work on tools now, but those would change as we add missing
>> features.
>>
>> -T.
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Patrick Lightbody <pl...@gmail.com>.
Duh, sorry about that. It's been a slow day :)
Can we talk about more about #7? I think #7 is where the majority of
the time (debate time or development time) will be spent. What items
do you guys have in mind?
Patrick
On Jan 5, 2006, at 12:05 PM, Ted Husted wrote:
> On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
>> I know there are a few features (probably more) that we'd like to
>> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
>> already. For example, the wildcard support in configuration.
>>
>> Where does that fit in? This current schedule looks like 2.0.0 would
>> be basically WebWork 2.2 + migration tools. Is the plan to add the
>> extra features, like wildcards, to Struts Action 2.1? I'm find with
>> either, but my understanding was that we'd do additional development
>> between WW 2.2 and SAF 2.0.
>
> That would be item # 7.
>
>> 7. Migrate Struts features as desired (chain support, wildcards,
>> etc)
>
> We're going to need at least two phases of development between WW 2.2
> and SAF 2.0.0.
>
> First, we need to replace the LGPL dependencies and resolve any other
> IP/Incubator issues (Item #2).
>
> Second, we would add any missing features, like wildcardmappings
> (Item #7).
>
> Of course, some of this will be asynchronous. Don and Rich are doing
> some early work on tools now, but those would change as we add missing
> features.
>
> -T.
>
> ---------------------------------------------------------------------
> 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
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Ted Husted <te...@gmail.com>.
On 1/5/06, Patrick Lightbody <pl...@gmail.com> wrote:
> I know there are a few features (probably more) that we'd like to
> bring forward from Struts Action 1.x to 2.x that aren't in WebWork
> already. For example, the wildcard support in configuration.
>
> Where does that fit in? This current schedule looks like 2.0.0 would
> be basically WebWork 2.2 + migration tools. Is the plan to add the
> extra features, like wildcards, to Struts Action 2.1? I'm find with
> either, but my understanding was that we'd do additional development
> between WW 2.2 and SAF 2.0.
That would be item # 7.
> 7. Migrate Struts features as desired (chain support, wildcards, etc)
We're going to need at least two phases of development between WW 2.2
and SAF 2.0.0.
First, we need to replace the LGPL dependencies and resolve any other
IP/Incubator issues (Item #2).
Second, we would add any missing features, like wildcardmappings (Item #7).
Of course, some of this will be asynchronous. Don and Rich are doing
some early work on tools now, but those would change as we add missing
features.
-T.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Patrick Lightbody <pl...@gmail.com>.
I know there are a few features (probably more) that we'd like to
bring forward from Struts Action 1.x to 2.x that aren't in WebWork
already. For example, the wildcard support in configuration.
Where does that fit in? This current schedule looks like 2.0.0 would
be basically WebWork 2.2 + migration tools. Is the plan to add the
extra features, like wildcards, to Struts Action 2.1? I'm find with
either, but my understanding was that we'd do additional development
between WW 2.2 and SAF 2.0.
On Jan 5, 2006, at 11:37 AM, Don Brown wrote:
> Looks good to me.
>
> Don
>
> Ted Husted wrote:
>> Apparently "Q" happens too :)
>> On 1/5/06, Ted Husted <te...@gmail.com> wrote:
>>> I'm recapping our ApacheCon presnetation at the NE JUG next week,
>>> along with Jason's Javapolis presentation. I'll get updated
>>> copies of
>>> both presentations up on the Struts University wiki.
>>>
>>> * http://StrutsUniversity.org/Presentations
>>>
>>> As I understand it, the general plan at this point is:
>>>
>>> 0. Encourage everyone to become involved in both projects
>>> 1. Ship WebWork 2.2 final
>>> 2. Resolve any incubator issues in the Open Symphony CVS
>>> 3. Vote on the accepting the code, and clear the IP with the
>>> Incubator
>>> 4. Import the donated code into the Struts repository
>>> 5. Develop Struts Action 1.x to 2.x migration tools
>>> 6. Develop a MailReader for WW 2.2
>>> 7. Migrate Struts features as desired (chain support, wildcards,
>>> etc)
>>> 8. Develop a migration guide, for both applications and developers
>>> 9. Release Struts Action 2.0.0 when ready
>>>
>>> Of course, some steps can be asychronous. Some of us are already
>>> working on #3-#6, for example. A few thoughts on #3 are on the wiki
>>> page,
>>>
>>> * http://wiki.apache.org/struts/StrutsAction2
>>>
>>> and Don Brown and Rich Feit have started on the infrastructure
>>> for the
>>> Conversion Wizard in the sandbox/ti/phase1/jars/legacy directory.
>>>
>>> * http://svn.apache.org/viewcvs.cgi/struts/sandbox/trunk/ti/
>>> phase1/jars/legacy/
>>>
>>> As to #0 and #1, it looks like the code is ready for the next WW2.2
>>> RC, but the community is thinking that they need more documentation
>>> first, so that this can be the best WW release ever.
>>>
>>> * http://forums.opensymphony.com/thread.jspa?threadID=12094
>>>
>>> WebWork has also started to rework their slate of example
>>> applications. [Sounds familiar, don't it :)]
>>>
>>> * http://forums.opensymphony.com/thread.jspa?threadID=11830
>>>
>>> As to #4, there's been a back-and-forth about retaining history from
>>> external projects, but the current thinking seems to be that it's OK
>>> to import history from other open source projects. Film at 11.
>>>
>>> As to #6, I've updated the MailReader for Struts Action 1.3. I
>>> working
>>> on an Action 1.x training course right now.
>>>
>>> * http://StrutsUniversity.org/MailReader+Training+Course
>>>
>>> As soon as that is done, I'll get back to creating a version with
>>> both
>>> Struts Action 1.3 and WebWork 2.2 versions of the MailReader in the
>>> same application, so we can compare apples to apples. I'd also
>>> like to
>>> rework the course for Action 2.x (as well as Shale).
>>>
>>> -Ted.
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts/WebWork Merger Tasks (was Q)
Posted by Don Brown <mr...@twdata.org>.
Looks good to me.
Don
Ted Husted wrote:
> Apparently "Q" happens too :)
>
> On 1/5/06, Ted Husted <te...@gmail.com> wrote:
>
>>I'm recapping our ApacheCon presnetation at the NE JUG next week,
>>along with Jason's Javapolis presentation. I'll get updated copies of
>>both presentations up on the Struts University wiki.
>>
>>* http://StrutsUniversity.org/Presentations
>>
>>As I understand it, the general plan at this point is:
>>
>> 0. Encourage everyone to become involved in both projects
>> 1. Ship WebWork 2.2 final
>> 2. Resolve any incubator issues in the Open Symphony CVS
>> 3. Vote on the accepting the code, and clear the IP with the Incubator
>> 4. Import the donated code into the Struts repository
>> 5. Develop Struts Action 1.x to 2.x migration tools
>> 6. Develop a MailReader for WW 2.2
>> 7. Migrate Struts features as desired (chain support, wildcards, etc)
>> 8. Develop a migration guide, for both applications and developers
>> 9. Release Struts Action 2.0.0 when ready
>>
>>Of course, some steps can be asychronous. Some of us are already
>>working on #3-#6, for example. A few thoughts on #3 are on the wiki
>>page,
>>
>>* http://wiki.apache.org/struts/StrutsAction2
>>
>>and Don Brown and Rich Feit have started on the infrastructure for the
>>Conversion Wizard in the sandbox/ti/phase1/jars/legacy directory.
>>
>>* http://svn.apache.org/viewcvs.cgi/struts/sandbox/trunk/ti/phase1/jars/legacy/
>>
>>As to #0 and #1, it looks like the code is ready for the next WW2.2
>>RC, but the community is thinking that they need more documentation
>>first, so that this can be the best WW release ever.
>>
>>* http://forums.opensymphony.com/thread.jspa?threadID=12094
>>
>>WebWork has also started to rework their slate of example
>>applications. [Sounds familiar, don't it :)]
>>
>>* http://forums.opensymphony.com/thread.jspa?threadID=11830
>>
>>As to #4, there's been a back-and-forth about retaining history from
>>external projects, but the current thinking seems to be that it's OK
>>to import history from other open source projects. Film at 11.
>>
>>As to #6, I've updated the MailReader for Struts Action 1.3. I working
>>on an Action 1.x training course right now.
>>
>>* http://StrutsUniversity.org/MailReader+Training+Course
>>
>>As soon as that is done, I'll get back to creating a version with both
>>Struts Action 1.3 and WebWork 2.2 versions of the MailReader in the
>>same application, so we can compare apples to apples. I'd also like to
>>rework the course for Action 2.x (as well as Shale).
>>
>>-Ted.
>
>
> ---------------------------------------------------------------------
> 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