webwork-devel — WebWork development

[Webwork-devel] CVS update: webwork

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork
In directory usw-pr-cvs1:/tmp/cvs-serv6550

Modified Files:
	TODO.txt 
Log Message:
added items for looking into using Jakarta commons-logging and 
need for unit tests for BeanUtil and ValueStack

[Webwork-devel] broswer detection

[Toby H. <tob...@in...>]

Hi everyone,

Is there any built-in browser detection stuff in WebWork?

Cheers,
Toby Hede




----- Original Message -----
From: <ma...@sm...>
To: <web...@li...>;
<web...@li...>
Cc: <web...@li...>
Sent: Tuesday, April 16, 2002 5:28 AM
Subject: [Webwork-user] rc - next release features


> Ok, here is a final summary of potential new WW
> features for the next release. I have indicated who
> mentioned each feature so we can go back to them for
> more information if needed.
>
> Have I left any features out? Should any feature be
> removed? What do you believe are a *must* for the next
> release? Do you have any feature(s) you would like to
> work on or take ownership of? If you have any revisions
> or comments, please reply.
>
> I will commit this summary as TODO.txt to the root of
> CVS.
>
> -Matt
>
> - Documentation
> 1. Better velocity documentation. [suggested by Matt]
> 2. A more detailed section describing the view mapping
> focusing on using actions.xml and views.properties with
> an example containing all the goodies (commands,
> aliases, hierarchical aspects etc.) and describing the
> main differences between them. [suggested by Paolo]
> 3. A detailed description on the single items and
> configuration of the webwork.properties should be done
> (based on the default.properties) [suggested by Paolo]
> 4. Client Action documentation [suggested by Mike]
> 5. Splitting documentation into a RedBook and a
> reference. [suggested by Peter]
>
> - Core
> 6. Ability to chain actions [suggested by Pat]
> 7. XSLT should be enhanced slightly to be really
> useful. We need some XSLT java extension for
> URL-escaping and so on. [suggested by Billy]
> 8. Ability to receive multi-part content -
> AttachmentAware? [suggested by Mike]
> 9. Ability to reuse the same action - i.e.
> I've also got a SessionActionFactory that I built a
> while back that will reuse the same action by saving it
> and pulling it from the session, which makes things
> like multi-page forms easy, because you don't have to
> keep passing the data along as hidden fields, etc.
> [suggested by Jason]
> 10. Support for Java Server Faces [suggested by Rickard]
> 11. Support for Java Standard Tag Library [suggested by
> Rickard]
> 12. Support for Portlet API [suggested by Rickard]
> 13. Ability to have more than one servlet dispatcher
> (need more info) [suggested by Rickard]
> 14. Revaluate the standard configuration scheme
> [suggested by Rickard]
> 15. Management console - some configuration tool would
> be nice. [suggested by Low]
> 16. Security model/framework [suggested by Low]
> 17. Include i18n in ValidationEditorSupport. [suggested
> by Paolo]
> 18. Factor out HTTP stuff out of the dispatcher.
> [suggested by Sven]
>
> - Tags
> Existing tags
> 19. Convert to XHTML [suggested by Matt]
> 20. Provide escape support. [suggested by Taavi]
>
> Contrib tags
> 21. Mike offered the inclusion of Jira tags in the
> library where they made sense.
>
> New tags
> 22. VXML (voice XML) [suggested by Matt]
> 23. WML [suggested by Matt]
>
> - Velocity
> 24. More velocity macros, etc. [suggested by Matt]
>
> - Examples/Tests
> 25. More Swing/Client side examples [suggested by Pat]
> 26. SVG example [suggested by Billy]
>
> - Misc
> 27. Bug fixes
> 28. Instrument/profile code - where is our bottlenecks?
> how well does WW scale? [suggested by Matt]
> 29. Logging - overhaul debug statements to use proper
> logging levels - debug, info, etc.[suggested by Matt]
> 30. Nightly builds [suggested by Matt]
> 31. JUnit test cases [suggested by Billy]
> 32. Tool integration - DreamWeaver integration for the
> ui tag. [suggested by Low](Low)
> 33. Reloadable actions [suggested by Bill]
> 34. Reloadable configuration(s) [suggested by Bill]
> 35. Include contrib work from other people [suggested
> by Fran=E7ois]
>
> - Incorporating new view technologies
> 36. Flash [suggested by Rickard]
> 37. Apache Axis (SOAP) [suggested by Matt]
>
>
>
> _______________________________________________
> Webwork-user mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-user
>

[Webwork-devel] CVS update: webwork/src/resources/web/template/css

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork/src/resources/web/template/css
In directory usw-pr-cvs1:/tmp/cvs-serv22960

Modified Files:
	checkbox.jsp combobox.jsp label.jsp password.jsp radiomap.jsp 
	select.jsp selectcascading.jsp selectgroupmap.jsp 
	selectmap.jsp text.jsp textarea.jsp 
Log Message:
removed absolute reference to controlheader and controlfooter

[Webwork-devel] CVS update: webwork/src/resources/web/template/standard

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork/src/resources/web/template/standard
In directory usw-pr-cvs1:/tmp/cvs-serv22915

Modified Files:
	checkbox.jsp combobox.jsp label.jsp password.jsp radiomap.jsp 
	select.jsp selectcascading.jsp selectgroupmap.jsp 
	selectmap.jsp text.jsp textarea.jsp 
Log Message:
removed absolute reference to controlheader and controlfooter

[Webwork-devel] One more addition for the feature list

[Patrick L. <pli...@ho...>]

Has anyone been looking in to WebWork support with the JSTL and/or JSP 1.3? 
The expression language in there looks pretty familiar....

-Pat

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

Re: [Webwork-devel] Servlet 2.2 support

[Scott F. <sc...@at...>]

Todd,

HttpServletResponseWrapper is not dependant on anything else in 2.3 
AFAIK, so you could probably include it in your webwork.jar file.

Else you could just rewrite IncludeTag.ServletResponseWrapperInclude to 
implement HttpServletResponse.  You will be up and going with the 2.2 
spec in no time.

Cheers,
Scott

Hough, Todd wrote:
> I'm stuck with the Servlet 2.2 spec for awhile but I'd like to use 
> WebWork.  So I compiled the source using my version 2.2 servlet.jar to 
> check how much code was 2.3 specific.  Everything was fine except for 
> the following errors:
> 
> Information:  6 errors
> Information:  7 warnings
> C:\Projects\RnD\WebWork\src\webwork\dispatcher\TestDispatcher.java
>     Error:  line (14) cannot resolve symbol class HttpServletRequestWrapper
>     Error:  line (83) cannot resolve symbol class HttpServletRequestWrapper
>     Error:  line (45) setRequest(javax.servlet.http.HttpServletRequest) 
> in webwork.action.ActionContext cannot be applied to 
> (webwork.dispatcher.TestDispatcher.TestRequestWrapper)
> 
> C:\Projects\RnD\WebWork\src\webwork\view\taglib\IncludeTag.java
>     Error:  line (14) cannot resolve symbol class 
> HttpServletResponseWrapper
>     Error:  line (193) cannot resolve symbol class 
> HttpServletResponseWrapper
>     Error:  line (50) 
> include(javax.servlet.ServletRequest,javax.servlet.ServletResponse) in 
> javax.servlet.RequestDispatcher cannot be applied to 
> (javax.servlet.ServletRequest,webwork.view.taglib.IncludeTag.ServletResponseWrapperInclude)
> 
> I don't see anything else using TestDispatcher but ComponentTag uses 
> IncludeTag and pretty much everything in webwork.view.taglib.ui uses 
> ComponentTag.  I noticed that 
> webwork.view.velocity.WebWorkUtil.include() doesn't use any 2.3 classes 
> or methods.  Is it doing the same thing as IncludeTag? 
> 
> Would you consider working from the 2.2 spec?  Is there anything in 
> WebWork that's impossible to do with the 2.2 spec?  Are there any 
> statistics about 2.3 adoption rates?  Believe me I'd love to use the 
> latest spec but it takes a lot of coordination and testing to upgrade 
> server software where I work.
> 
> Thanks for your hard work producing a quality product.
> 
> Todd
> 


-- 
Scott Farquhar :: sc...@at...

Atlassian :: http://www.atlassian.com
      Supporting YOUR J2EE World

[Webwork-devel] Servlet 2.2 support

[Hough, T. <Mat...@Ma...>]

I'm stuck with the Servlet 2.2 spec for awhile but I'd like to use WebWork.
So I compiled the source using my version 2.2 servlet.jar to check how much
code was 2.3 specific.  Everything was fine except for the following errors:

Information:  6 errors
Information:  7 warnings
C:\Projects\RnD\WebWork\src\webwork\dispatcher\TestDispatcher.java
    Error:  line (14) cannot resolve symbol class HttpServletRequestWrapper
    Error:  line (83) cannot resolve symbol class HttpServletRequestWrapper
    Error:  line (45) setRequest(javax.servlet.http.HttpServletRequest) in
webwork.action.ActionContext cannot be applied to
(webwork.dispatcher.TestDispatcher.TestRequestWrapper)
C:\Projects\RnD\WebWork\src\webwork\view\taglib\IncludeTag.java
    Error:  line (14) cannot resolve symbol class HttpServletResponseWrapper
    Error:  line (193) cannot resolve symbol class
HttpServletResponseWrapper
    Error:  line (50)
include(javax.servlet.ServletRequest,javax.servlet.ServletResponse) in
javax.servlet.RequestDispatcher cannot be applied to
(javax.servlet.ServletRequest,webwork.view.taglib.IncludeTag.ServletResponse
WrapperInclude)

I don't see anything else using TestDispatcher but ComponentTag uses
IncludeTag and pretty much everything in webwork.view.taglib.ui uses
ComponentTag.  I noticed that webwork.view.velocity.WebWorkUtil.include()
doesn't use any 2.3 classes or methods.  Is it doing the same thing as
IncludeTag?  

Would you consider working from the 2.2 spec?  Is there anything in WebWork
that's impossible to do with the 2.2 spec?  Are there any statistics about
2.3 adoption rates?  Believe me I'd love to use the latest spec but it takes
a lot of coordination and testing to upgrade server software where I work.

Thanks for your hard work producing a quality product.

Todd

[Webwork-devel] CVS update: webwork

[Maurice C. P. <mau...@us...>]

Update of /cvsroot/webwork/webwork
In directory usw-pr-cvs1:/tmp/cvs-serv13694

Added Files:
	.classpath .project 
Log Message:
added metadata for Eclipse users

[Webwork-devel] CVS update: webwork/src/lib

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork/src/lib
In directory usw-pr-cvs1:/tmp/cvs-serv14896

Modified Files:
	saxon.jar 
Log Message:
updated to 6.5.2

[Webwork-devel] CVS update: webwork/src/docs

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork/src/docs
In directory usw-pr-cvs1:/tmp/cvs-serv14389

Modified Files:
	faq.xml 
Log Message:
added faq on checking out code behind a firewall with CVS

[Webwork-devel] CVS update: webwork

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork
In directory usw-pr-cvs1:/tmp/cvs-serv14268

Added Files:
	TODO.txt 
Log Message:
no message

[Webwork-devel] rc - next release features

[<ma...@sm...>]

Ok, here is a final summary of potential new WW
features for the next release. I have indicated who
mentioned each feature so we can go back to them for
more information if needed.

Have I left any features out? Should any feature be
removed? What do you believe are a *must* for the next
release? Do you have any feature(s) you would like to
work on or take ownership of? If you have any revisions
or comments, please reply.

I will commit this summary as TODO.txt to the root of
CVS.=20

-Matt

- Documentation
1. Better velocity documentation. [suggested by Matt]
2. A more detailed section describing the view mapping
focusing on using actions.xml and views.properties with
an example containing all the goodies (commands,
aliases, hierarchical aspects etc.) and describing the
main differences between them. [suggested by Paolo]
3. A detailed description on the single items and
configuration of the webwork.properties should be done
(based on the default.properties) [suggested by Paolo]
4. Client Action documentation [suggested by Mike]
5. Splitting documentation into a RedBook and a
reference. [suggested by Peter]

- Core
6. Ability to chain actions [suggested by Pat]
7. XSLT should be enhanced slightly to be really
useful. We need some XSLT java extension for
URL-escaping and so on. [suggested by Billy]
8. Ability to receive multi-part content -
AttachmentAware? [suggested by Mike]
9. Ability to reuse the same action - i.e.
I've also got a SessionActionFactory that I built a
while back that will reuse the same action by saving it
and pulling it from the session, which makes things
like multi-page forms easy, because you don't have to
keep passing the data along as hidden fields, etc.
[suggested by Jason]
10. Support for Java Server Faces [suggested by Rickard]
11. Support for Java Standard Tag Library [suggested by
Rickard]
12. Support for Portlet API [suggested by Rickard]
13. Ability to have more than one servlet dispatcher
(need more info) [suggested by Rickard]
14. Revaluate the standard configuration scheme
[suggested by Rickard]
15. Management console - some configuration tool would
be nice. [suggested by Low]
16. Security model/framework [suggested by Low]
17. Include i18n in ValidationEditorSupport. [suggested
by Paolo]
18. Factor out HTTP stuff out of the dispatcher.
[suggested by Sven]

- Tags
Existing tags
19. Convert to XHTML [suggested by Matt]
20. Provide escape support. [suggested by Taavi]

Contrib tags
21. Mike offered the inclusion of Jira tags in the
library where they made sense.

New tags
22. VXML (voice XML) [suggested by Matt]
23. WML [suggested by Matt]

- Velocity
24. More velocity macros, etc. [suggested by Matt]

- Examples/Tests
25. More Swing/Client side examples [suggested by Pat]
26. SVG example [suggested by Billy]

- Misc
27. Bug fixes
28. Instrument/profile code - where is our bottlenecks?
how well does WW scale? [suggested by Matt]
29. Logging - overhaul debug statements to use proper
logging levels - debug, info, etc.[suggested by Matt]
30. Nightly builds [suggested by Matt]
31. JUnit test cases [suggested by Billy]
32. Tool integration - DreamWeaver integration for the
ui tag. [suggested by Low](Low)
33. Reloadable actions [suggested by Bill]
34. Reloadable configuration(s) [suggested by Bill]
35. Include contrib work from other people [suggested
by Fran=E7ois]

- Incorporating new view technologies
36. Flash [suggested by Rickard]
37. Apache Axis (SOAP) [suggested by Matt]
=0D

[Webwork-devel] saxon

[<fbe...@py...>]

Note that saxon 6.5.2 has been released and includes bug fixes.
http://sourceforge.net/project/shownotes.php?release_id=84276

May be webwork's cvs repository should be updated to include version 6.5.2
of saxon.

Cheers,
___________________________
François Beauregard, b.ing.
Vice-président
Recherche et développement
Pyxis Technologies
www.pyxis-tech.com

T : (450) 681-9094, poste 102
F : (450) 681-5758
fbe...@py...

[Webwork-devel] Re: features request: reloadable Actions/Beans

[Bill B. <bi...@pr...>]

Hello,

Here's another enhancement suggestion: Reloadable Actions and Beans.

I'm working on a project now interfacing WW with a third party
application.  However, it takes a long time for the web app to restart
after making changes to Actions or Beans.  So it would be nice if it were
possible if Actions and Beans were reloadable.

Another, similar enhancement would be to support reloading the action and
view mappings without a restart.

-Bill

ma...@sm... wrote:
> 
> I wanted to initiate a discussion for next release
> features, requirements people feel are important for
> WW. I hope collectively, we can come up with a good
> list which we can prioritize and delegate. So here goes.

[Webwork-devel] Re: [Webwork-user] IntelliJ

[Patrick L. <pli...@ho...>]

In the ant build properties in IDEA you can specify the system properties. 
However, I recall that the latest build of the EAP version doesn't seem to 
utilize those properties like it should. What version are you using?

-Pat


>From: François Beauregard <fbe...@py...>
>Reply-To: <fbe...@py...>
>To: <web...@li...>
>CC: <web...@li...>
>Subject: [Webwork-user] IntelliJ
>Date: Wed, 10 Apr 2002 09:06:58 -0400
>
>Yesterday I decided to give a first try at IntelliJ.
>Since WebWork has an already defined project for IntelliJ, I decided to
>start with this.
>
>When I invoke the dist target from within the IDE the style task fails 
>cause
>it tries to work with xalan instead of saxon.
>From build.bat, this is done using
>: 
>-Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryI
>mpl
>
>How do we fix this in IntelliJ?
>
>Cheers,
>___________________________
>François Beauregard, b.ing.
>Vice-président
>Recherche et développement
>Pyxis Technologies
>www.pyxis-tech.com
>
>T : (450) 681-9094, poste 102
>F : (450) 681-5758
>fbe...@py...
>


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

RE: [Webwork-user] Re: [Webwork-devel] IntelliJ

[<fbe...@py...>]

Thank you very much for the quick answer.
Everything was almost done.
The problem is that the path for saxon is not relative.
Therefore if you work in a different directory than C:\projects\webwork you
get the failure.

The only way I have found to make it location independant is to use the
include project classpath option.

I modified the .ipr file to have three entries in the additionalClassPath
section of the buildFile section.
See the following excerpt of the new project file.

    <buildFile url="file://$PROJECT_DIR$/src/build/build.xml">

      ...

      <additionalClassPath>
        <entry path="$PROJECT_DIR$\lib\crimson.jar" />
        <entry path="$PROJECT_DIR$\lib\jaxp.jar" />
        <entry path="$PROJECT_DIR$\src\lib\saxon.jar" />
      </additionalClassPath>

      ...

    </buildFile>

This works but the next time you use IntelliJ, $PROJECT_DIR$ gets converted
to an absolute path value.

Cheers,
___________________________
François Beauregard, b.ing.
Vice-président
Recherche et développement
Pyxis Technologies
www.pyxis-tech.com

T : (450) 681-9094, poste 102
F : (450) 681-5758
fbe...@py...

-----Original Message-----
From: web...@li...
[mailto:web...@li...]On Behalf Of Scott
Farquhar
Sent: April 10, 2002 10:35 AM
To: fbe...@py...
Cc: web...@li...;
web...@li...
Subject: [Webwork-user] Re: [Webwork-devel] IntelliJ


AFAIK you can do this by right clicking in your "Ant Build" window, and
choose "build properties".  From there you can add properties to the
build file.

Cheers,
Scott

François Beauregard wrote:
> Yesterday I decided to give a first try at IntelliJ.
>
> Since WebWork has an already defined project for IntelliJ, I decided to
> start with this.
>
>
>
> When I invoke the dist target from within the IDE the style task fails
> cause it tries to work with xalan instead of saxon.
>
>  From build.bat, this is done using :
> -Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryI
mpl
>
>
>
> How do we fix this in IntelliJ?
>
>
>
> Cheers,
> ___________________________
> *François Beauregard, b.ing.*
> Vice-président
> Recherche et développement
> *Pyxis* *Technologies*
> www.pyxis-tech.com <http://www.pyxis-tech.com/>
>
> T : (450) 681-9094, poste 102
> F : (450) 681-5758
> fbe...@py... <mailto:fbe...@py...>
>
>
>


--
Scott Farquhar :: sc...@at...

Atlassian :: http://www.atlassian.com
      Supporting YOUR J2EE World



_______________________________________________
Webwork-user mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webwork-user

Re: [Webwork-devel] IntelliJ

[Scott F. <sc...@at...>]

AFAIK you can do this by right clicking in your "Ant Build" window, and=20
choose "build properties".  From there you can add properties to the=20
build file.

Cheers,
Scott

Fran=E7ois Beauregard wrote:
> Yesterday I decided to give a first try at IntelliJ.
>=20
> Since WebWork has an already defined project for IntelliJ, I decided to=
=20
> start with this.
>=20
> =20
>=20
> When I invoke the dist target from within the IDE the style task fails=20
> cause it tries to work with xalan instead of saxon.
>=20
>  From build.bat, this is done using :=20
> -Djavax.xml.transform.TransformerFactory=3Dcom.icl.saxon.TransformerFac=
toryImpl
>=20
> =20
>=20
> How do we fix this in IntelliJ?
>=20
> =20
>=20
> Cheers,
> ___________________________
> *Fran=E7ois Beauregard, b.ing.*
> Vice-pr=E9sident
> Recherche et d=E9veloppement
> *Pyxis* *Technologies*
> www.pyxis-tech.com <http://www.pyxis-tech.com/>
>=20
> T : (450) 681-9094, poste 102
> F : (450) 681-5758
> fbe...@py... <mailto:fbe...@py...>
>=20
> =20
>=20


--=20
Scott Farquhar :: sc...@at...

Atlassian :: http://www.atlassian.com
      Supporting YOUR J2EE World

[Webwork-devel] IntelliJ

[<fbe...@py...>]

Yesterday I decided to give a first try at IntelliJ.
Since WebWork has an already defined project for IntelliJ, I decided to
start with this.

When I invoke the dist target from within the IDE the style task fails cause
it tries to work with xalan instead of saxon.
From build.bat, this is done using
: -Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryI
mpl

How do we fix this in IntelliJ?

Cheers,
___________________________
François Beauregard, b.ing.
Vice-président
Recherche et développement
Pyxis Technologies
www.pyxis-tech.com

T : (450) 681-9094, poste 102
F : (450) 681-5758
fbe...@py...

[Webwork-devel] How to use WebWorks

[Diann P. <di...@fr...>]

I have JDK 1.4.0 and I read that you can use WebWorks without an =
Application Server, but how.

I have tried to follow the instructions but I cannot get the guist of =
it.

Any help would be appreciated.

Rolf Pfotenhauer
email: ro...@st...

[Webwork-devel] CVS update: webwork/src/resources/web/tests

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork/src/resources/web/tests
In directory usw-pr-cvs1:/tmp/cvs-serv10565

Modified Files:
	formtest.jsp 
Log Message:
added a select back in that was mistakenly removed

[Webwork-devel] CVS update: webwork/src/docs

[matt b. <ba...@us...>]

Update of /cvsroot/webwork/webwork/src/docs
In directory usw-pr-cvs1:/tmp/cvs-serv4191

Modified Files:
	community.xml faq.xml 
Log Message:
added info about contributing

RE: [Webwork-devel] DRAFT 4 - next release features/requirements

[<fbe...@py...>]

1.
Some people have been using WW for a while and have done some independent
work.
It may be interesting to include some of this stuff in WW.
Wouldn't it be nice that a process would be in place so that people could
submit their independent work, it would be evaluated by a steering comitee
and included in WW.

2.
In a eXtreme Programming like fashion, it would interesting to split next
release into iterations and then specify target dates for each iteration.

Cheers,
___________________________
François Beauregard, b.ing.
Vice-président
Recherche et développement
Pyxis Technologies
www.pyxis-tech.com

T : (450) 681-9094, poste 102
F : (450) 681-5758
fbe...@py...

-----Original Message-----
From: web...@li...
[mailto:web...@li...]On Behalf Of Matt
Baldree
Sent: April 6, 2002 8:03 AM
To: web...@li...;
web...@li...
Subject: [Webwork-devel] DRAFT 4 - next release features/requirements


4th draft of possible next release feature/requirements based on what people
have posted. I've also listed the person that requested the
feature/requirement based on memory. Could be wrong? Looks like we have a
pretty good list. I'll wait for revisions and then I propose that my next
post be for inclusion/exclusion/prioritization.

 Documentation
1. Better velocity documentation (Matt)
2. A more detailed section describing the view mapping focusing on using
actions.xml and views.properties with an example containing all the goodies
(commands, aliases, hierarchical aspects etc.) and describing the main
differences between them. (Paolo)
3. A detailed description on the single items and configuration of the
webwork.properties should be done (based on the default.properties) (Paolo)
4. Client Action documentation (Mike)
5. Splitting documentation into a RedBook and a reference. (Peter)

 Enhancements
1. More velocity macros, etc. (Matt)
2. WML tags (Matt)
3. XHTML tags (possible move our existing tags to be XHTML compliant) (Matt)
4. VXML tags (Matt)
5. Ability to chain actions (Pat)
6. XSLT should be enhanced slightly to be really useful. We need some XSLT
java extension for URL-escaping and so on. (Billy)
7. Ability to receive multi-part content - AttachmentAware? (Mike)
8. Ability to reuse the same action - i.e.
I've also got a SessionActionFactory that I built a while back that will
reuse the same action by saving it and pulling it from the session, which
makes things like multi-page forms easy, because you don't have to keep
passing the data along as hidden fields, etc. (Jason)
9. Support for Java Server Faces (Rickard)
10. Support for Java Standard Tag Library (Rickard)
11. Support for Portlet API (Rickard)
12. Ability to have more than one servlet dispatcher (need more info)
(Rickard)
13. Revaluate the standard configuration scheme (Rickard)
14. Management console - some configuration tool would be nice. (Low)
15. Security model/framework (Low)

 Examples/Tests
1. More Swing/Client side examples (Pat)

 Misc
1. Bug list
2. Feature list
3. Instrument/profile code - where is our bottlenecks? how well does WW
scale? (Matt)
4. Logging - overhaul debug statements to use proper logging levels - debug,
info, etc.(Matt)
5. Nightly builds (Matt)
6. Tool integration - DreamWeaver integration for the ui tag. (Low)

 Incorporating new view technologies
1. Flash (Rickard)
2. Apache Axis (SOAP) (Matt)

 -Matt




_______________________________________________
Webwork-devel mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webwork-devel

[Webwork-devel] DRAFT 4 - next release features/requirements

[Matt B. <ma...@sm...>]

4th draft of possible next release feature/requirements based on what people
have posted. I've also listed the person that requested the
feature/requirement based on memory. Could be wrong? Looks like we have a
pretty good list. I'll wait for revisions and then I propose that my next
post be for inclusion/exclusion/prioritization.

 Documentation
1. Better velocity documentation (Matt)
2. A more detailed section describing the view mapping focusing on using
actions.xml and views.properties with an example containing all the goodies
(commands, aliases, hierarchical aspects etc.) and describing the main
differences between them. (Paolo)
3. A detailed description on the single items and configuration of the
webwork.properties should be done (based on the default.properties) (Paolo)
4. Client Action documentation (Mike)
5. Splitting documentation into a RedBook and a reference. (Peter)

 Enhancements
1. More velocity macros, etc. (Matt)
2. WML tags (Matt)
3. XHTML tags (possible move our existing tags to be XHTML compliant) (Matt)
4. VXML tags (Matt)
5. Ability to chain actions (Pat)
6. XSLT should be enhanced slightly to be really useful. We need some XSLT
java extension for URL-escaping and so on. (Billy)
7. Ability to receive multi-part content - AttachmentAware? (Mike)
8. Ability to reuse the same action - i.e.
I've also got a SessionActionFactory that I built a while back that will
reuse the same action by saving it and pulling it from the session, which
makes things like multi-page forms easy, because you don't have to keep
passing the data along as hidden fields, etc. (Jason)
9. Support for Java Server Faces (Rickard)
10. Support for Java Standard Tag Library (Rickard)
11. Support for Portlet API (Rickard)
12. Ability to have more than one servlet dispatcher (need more info)
(Rickard)
13. Revaluate the standard configuration scheme (Rickard)
14. Management console - some configuration tool would be nice. (Low)
15. Security model/framework (Low)

 Examples/Tests
1. More Swing/Client side examples (Pat)

 Misc
1. Bug list
2. Feature list
3. Instrument/profile code - where is our bottlenecks? how well does WW
scale? (Matt)
4. Logging - overhaul debug statements to use proper logging levels - debug,
info, etc.(Matt)
5. Nightly builds (Matt)
6. Tool integration - DreamWeaver integration for the ui tag. (Low)

 Incorporating new view technologies
1. Flash (Rickard)
2. Apache Axis (SOAP) (Matt)

 -Matt

[Webwork-devel] Re: [Webwork-user] DRAFT 3 - next release features/requirements

[Matt B. <ma...@sm...>]

makes sense to me.

----- Original Message -----
From: "Peter Kelley" <yel...@ya...>
To: <web...@li...>
Sent: Friday, April 05, 2002 11:52 PM
Subject: [Webwork-user] DRAFT 3 - next release features/requirements


> Has anybody ever seen the IBM Redbook documentation ? They are a
> practical guide to a software or hardware product. They usually have
> stuff like "We tried to do this and this happened" or "We figured out
> how to use this product feature and here is the sample code". I think
> it would be really cool to have that sort of practical documentation
> for WebWork. The reference documentation could then be seperate. At
> the moment it's all jumbled in there together.
>
> I'd even be prepared to help out once I know a little bit more about the
> product, I helped write 2 Redbooks when I was at IBM.
>
> Good idea ? Bad Idea ? Thoughts ?
>
>
> > 3rd draft of possible next release feature/requirements based on what
people
> > have posted. Right now these are candidate ideas. Once we have a good
list,
> > we can repost for inclusion/exclusion/prioritization, etc.
> >
> > Other ideas?
> >
> > Documentation
> > 1. Better velocity documentation
> > 2. A more detailed section describing the view mapping focusing on using
> > actions.xml and views.properties with an example containing all the
goodies
> > (commands, aliases, hierarchical aspects etc.) and describing the main
> > differences between them.
> > 3. A detailed description on the single items and configuration of the
> > webwork.properties should be done (based on the default.properties)
> > 4. Client Action documentation
> >
> > Enhancements
> > 1. More velocity macros, etc.
> > 2. WML tags
> > 3. XHTML tags (possible move our existing tags to be XHTML compliant)
> > 4. VXML tags
> > 5. Ability to chain actions
> > 6. XSLT should be enhanced slightly to be really useful. We need some
XSLT
> > java extension for URL-escaping and so on.
> > 7. Ability to receive multi-part content - AttachmentAware?
> >
> > Examples/Tests
> > 1. More Swing/Client side examples
> >
> > Misc
> > 1. Bug list
> > 2. Feature list
> > 3. Instrument/profile code - where is our bottlenecks? how well does WW
> > scale?
> > 4. Logging - overhaul debug statements to use proper logging levels -
debug,
> > info, etc.
> > 5. Nightly builds
> >
> > Incorporating new view technologies
> > 1. Flash
> > 2. Apache Axis (SOAP)
> >
> > -Matt
> >
> >
> >
> >
> > _______________________________________________
> > Webwork-user mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webwork-user
>
>
> --
> Peter Kelley
>
>
> _______________________________________________
> Webwork-user mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-user
>
>

Re: [Webwork-devel] Re: DRAFT 3 - next release features/requirements

[Rickard <ri...@dr...>]

Heng Sin Low wrote:

> 1. Management console
> - some configuration tool would be nice.
> 2. Tool integration
> - DreamWeaver integration for the ui tag.
> 3. Debugging tool
> - A value stack inspection tool would be usefull.


You can get that today by using the XSLT view "showtree.xslt".


> 4. SWT client ?
> 5. Security model/framework ?


Yes, this needs to be thought about more.


> 6. Action repository api
> - I think it might be usefull to abstract out the
> storage of action definition and its associated view
> mapping, possibly allowing runtime
> configuration/customization.


Can you expand on this?


> 7. Support for the forth coming portlet api ?


Absolutely!!


> 8. Multi-channel view mapping ?
> - For e.g, define different view for the same action
> base on the output channel type ( xml, wml, html, etc
> )


This can be done by using different action mappings.


> 9. More real world example/usage pattern
> - eCommerce 
> - portal

Portal stuff is in the planning stage.

/Rickard

-- 
Rickard Öberg