webwork-devel Mailing List for WebWork (Page 7)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

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

Modified Files:
	loginfo 
Log Message:
enable syncmail

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

Modified Files:
	loginfo 
Log Message:
no message

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

Modified Files:
	syncmail 
Log Message:
no message

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

Modified Files:
	loginfo 
Log Message:
added syncmail line

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

Added Files:
	syncmail 
Log Message:
syncmail 3.20 from
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailmain/CVSROOT/syncmail

thx. i'll give this a try.

----- Original Message -----
From: "Scott Farquhar" <sc...@at...>
To: <web...@li...>
Sent: Thursday, May 02, 2002 7:53 PM
Subject: [Webwork-devel] CVS Emails

> I few things I have noticed regarding the cvs emails:
>
> - They copy the class name on the email.  Ie this morning Matt committed
> "CHANGES.txt" and then "cha...@us..." was copied on
> the email.  I have seen this on all CVS emails in at least month.
>
> - Inclusion of the diff message in the cvs email.  Many other cvs lists
> also include the diff of the file in the cvs email.  Perhaps is has been
> turned off to save bandwidth, but I find it very useful to see what has
> changed in files without having to update & diff each file manually.
>
> I think both the above can be resolved by installing the latest version
> of syncmail on the servers:
>
>    http://sourceforge.net/docman/display_doc.php?docid=772&group_id=1
>
> Any thoughts?
>
> Cheers,
> Scott
> --
> Scott Farquhar :: sc...@at...
>
> Atlassian :: http://www.atlassian.com
>       Supporting YOUR J2EE World
>
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Webwork-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-devel
>
>

I few things I have noticed regarding the cvs emails:

- They copy the class name on the email.  Ie this morning Matt committed 
"CHANGES.txt" and then "cha...@us..." was copied on 
the email.  I have seen this on all CVS emails in at least month.

- Inclusion of the diff message in the cvs email.  Many other cvs lists 
also include the diff of the file in the cvs email.  Perhaps is has been 
turned off to save bandwidth, but I find it very useful to see what has 
changed in files without having to update & diff each file manually.

I think both the above can be resolved by installing the latest version 
of syncmail on the servers:

   http://sourceforge.net/docman/display_doc.php?docid=772&group_id=1

Any thoughts?

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

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

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

Modified Files:
	CHANGES.txt 
Log Message:
update

Update of /cvsroot/webwork/webwork/src/etc
In directory usw-pr-cvs1:/tmp/cvs-serv27649

Added Files:
	skeleton-project.zip 
Log Message:
Added a skeleton project for people to quickly setup a webwork project
for those that are interested.

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

Modified Files:
	faq.xml 
Log Message:
added the faq to the mail archive. it was accidentally removed

Update of /cvsroot/webwork/webwork/src/main/webwork
In directory usw-pr-cvs1:/tmp/cvs-serv24915

Modified Files:
	log4j.properties 
Log Message:
update

Update of /cvsroot/webwork/webwork/src/main/webwork/util
In directory usw-pr-cvs1:/tmp/cvs-serv24635

Modified Files:
	ValueStack.java 
Log Message:
made all logging debug for now since taglib was causing 
log statements to print

Update of /cvsroot/webwork/webwork/src/main/webwork/examples
In directory usw-pr-cvs1:/tmp/cvs-serv24097

Modified Files:
	FormTest.java 
Log Message:
uncomment a commented section

Hello,

I'm trying to implement the tabbedpane inside an application but
i 'm meeting problem.I 've studied the sample inside webwork, that's to say 
tabbedpane.jsp and the class TabbedPaneTest, it works fine in the exemple
context.

I ve created a classe Account with a method doing the set up of
the tabbedpaned as done in the sample but
 all the time i get an exception : 

The jsp code is : 
.....
<p><webwork:tabbedpane contentName="'Tabs1'"/></p>

.....
The java code inside the class:

    static Set getData()
    {
        Map tmpMap = new HashMap();
        tmpMap.put( "bal1", "bal1.jsp" );
        tmpMap.put( "bal2", "bal2.jsp" );
        tmpMap.put( "bal3", "bal3.jsp" );
        return tmpMap.entrySet();
    }

    public Vector getTabs1() { return tabs1; }
    public Vector tabs1 = new Vector( getData() );
....

After it builts the page i get this messages from the BEA WebLogic server:

02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)]
findValue() for: query="'RIGHT'"
segment(s) {[id="RIGHT" type="0" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)]
findValue() for: query="'Tabs1'"
segment(s) {[id="Tabs1" type="0" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)]
findValue() for: query="Tabs1"
segment(s) {[id="Tabs1" type="8" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)] value for
[Tabs1] is null.
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)]
findValue() for: query="."
segment(s) {[id="null" type="3" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)]
findValue() for: query="."
segment(s) {[id="null" type="3" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)]
findValue() for: query="com.pdt.e
banking.webapp.wwactions.admin.Account@7f5227"
segment(s) {[id="com.pdt.ebanking.webapp.wwactions.admin.Account@7f5227"
type="8" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)] value for
[com.pdt.ebanking.webap
p.wwactions.admin.Account@7f5227] is null.
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp (ValueStack)]
findValue() for: query="'center'"

segment(s) {[id="center" type="0" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp
/template/standard/tabbedpane.jsp (ValueStack)]
 findValue() for: query="'webwork.util.Counter'"
segment(s) {[id="webwork.util.Counter" type="0" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp
/template/standard/tabbedpane.jsp (ValueStack)]
 findValue() for: query="'first'"
segment(s) {[id="first" type="0" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp
/template/standard/tabbedpane.jsp (ValueStack)]
 findValue() for: query="0"
segment(s) {[id="null" type="12" values="0"]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp
/template/standard/tabbedpane.jsp (ValueStack)]
 findValue() for: query="'last'"
segment(s) {[id="last" type="0" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp
/template/standard/tabbedpane.jsp (ValueStack)]
 findValue() for: query="content/size"
segment(s) {[id="content" type="8" values=""]
[id="size" type="8" values=""]}
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp
/template/standard/tabbedpane.jsp (ValueStack)]
 value for [content/size] is null.
02.05.2002 16:24:00 [/html/accountEditTabbedpane.jsp
/template/standard/tabbedpane.jsp (BeanUtil)] E
rror executing read method for last on webwork.util.Counter
java.lang.NullPointerException
        at webwork.util.BeanUtil.setValue(BeanUtil.java:363)

May be someone have already met this problem and can provide any advertises.

Ludovic.

On doing a search on google I came across this 
mail to news converter which mirrors the webwork
mailinglist to a news server
news://news.gmane.org/ 

if someone don't want to use a news reader it can also be viewed
with a nice webinterface
http://news.gmane.org/thread.php?group=gmane.comp.java.webwork.devel
http://news.gmane.org/thread.php?group=gmane.comp.java.webwork.user

Hope this is of comman interest..

Cheers
-Paolo

Hey

I just noticed that this list isn't dead. I haven't received any emails=20
for the past two weeks, so I thought that just nothing was happening. A=20
quick scan in the archives says otherwise, and the reason I haven't seen=20
any of it is that TMC decided to turn off my email without telling me.=20
C'est la vie.

Anyway, I'll try to catch up through the archives. Sorry for this.

/Rickard

--=20
Rickard =D6berg

I think 6, action chaining, is the most important thing on this list. =
(MHO)

> -----Original Message-----
> From: Matt Baldree [mailto:ma...@sm...]
> Sent: Sunday, April 28, 2002 11:35 PM
> To: Webwork-Developer; Webwork-User
> Subject: [Webwork-user] feature prioritization?
>=20
>=20
> I wanted to throw out a feature prioritization strawman and=20
> see what people
> thought. I did not list the Java Spec API support like Java=20
> Server Faces and
> others since these are not released at this time. Here is=20
> what I believe are
> priorities. This list doesn't mean other items cannot be=20
> worked on before
> these but rather serves as a temperature gauge to see what=20
> people would like
> released for 1.1.
>=20
> [Priority]
> 20
> 8
> 29
> 9
> 6
> 19
> 28
>=20
> -Matt
>=20
>=20
> [From TODO.txt]
> - Documentation
> 1. Better velocity documentation. [suggested by Matt]
> 2. A more detailed section describing the view mapping=20
> focusing on using
> actions.xml and views.properties with an example containing=20
> 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.=20
> [suggested by
> Peter]
>=20
> - Core
> 6. Ability to chain actions [suggested by Pat]
> 7. XSLT should be enhanced slightly to be really useful. We=20
> need some XSLT
> java extension for URL-escaping and so on. [suggested by Billy]
> 8. Ability to receive multi-part content - AttachmentAware?=20
> [suggested by
> Mike]
> 9. Ability to reuse the same action - i.e.
> I've also got a SessionActionFactory that I built a while=20
> back that will
> reuse the same action by saving it and pulling it from the=20
> session, which
> makes things like multi-page forms easy, because you don't=20
> 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=20
> nice. [suggested
> by Low]
>    15.1 Consider implementing this as an Eclipse plugin
> 16. Security model/framework [suggested by Low]
> 17. Include i18n in ValidationEditorSupport. [suggested by Paolo]
> 18. Factor out HTTP stuff out of the=20
> ActionFactory/ActionContext. [suggested
> by Sven]
>=20
> - Tags
> Existing tags
> 19. Convert to XHTML [suggested by Matt]
> 20. Provide escape support. [suggested by Taavi]
>=20
> Contrib tags
> 21. Mike offered the inclusion of Jira tags in the library=20
> where they made
> sense.
>=20
> New tags
> 22. VXML (voice XML) [suggested by Matt]
> 23. WML [suggested by Matt]
>=20
> - Velocity
> 24. More velocity macros, etc. [suggested by Matt]
>=20
> - Examples/Tests
> 25. More Swing/Client side examples [suggested by Pat]
> 26. SVG example [suggested by Billy]
>=20
> - Misc
> 27. (done - mostly) Bug fixes
> 28. Instrument/profile code - where is our bottlenecks? how=20
> well does WW
> scale? [suggested by Matt]
>    28.1. Are there any memory leaks from the value stack? Do=20
> the objects in
> the stack get reclaimed properly?
> 29. Logging - overhaul debug statements to use proper logging levels -
> debug, info, etc.[suggested by Matt]
>    29.1. Investigate using Jakarta commons-logging (allows=20
> transparent use
> of a logger both
>    log4j and jdk1.4 logger
> 30. Nightly builds [suggested by Matt]
> 31. JUnit test cases [suggested by Billy]
>    31.1 Need unit tests for BeanUtil and ValueStack (should=20
> test for all
> expression scenarios)
> 32. Tool integration - DreamWeaver integration for the ui=20
> 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]
>=20
> - Incorporating new view technologies
> 36. Flash [suggested by Rickard]
> 37. Apache Axis (SOAP) [suggested by Matt]
>=20
>=20
>=20
>=20
> _______________________________________________
> Webwork-user mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-user
>=20

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

Modified Files:
	TODO.txt 
Log Message:
no message

I wanted to throw out a feature prioritization strawman and see what people
thought. I did not list the Java Spec API support like Java Server Faces and
others since these are not released at this time. Here is what I believe are
priorities. This list doesn't mean other items cannot be worked on before
these but rather serves as a temperature gauge to see what people would like
released for 1.1.

[Priority]
20
8
29
9
6
19
28

-Matt

[From TODO.txt]
- 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]
   15.1 Consider implementing this as an Eclipse plugin
16. Security model/framework [suggested by Low]
17. Include i18n in ValidationEditorSupport. [suggested by Paolo]
18. Factor out HTTP stuff out of the ActionFactory/ActionContext. [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. (done - mostly) Bug fixes
28. Instrument/profile code - where is our bottlenecks? how well does WW
scale? [suggested by Matt]
   28.1. Are there any memory leaks from the value stack? Do the objects in
the stack get reclaimed properly?
29. Logging - overhaul debug statements to use proper logging levels -
debug, info, etc.[suggested by Matt]
   29.1. Investigate using Jakarta commons-logging (allows transparent use
of a logger both
   log4j and jdk1.4 logger
30. Nightly builds [suggested by Matt]
31. JUnit test cases [suggested by Billy]
   31.1 Need unit tests for BeanUtil and ValueStack (should test for all
expression scenarios)
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çois]

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

I was investigating Eclipse and reading about its plugin architecture and
wanted to toss up an idea. But first a little background. Eclipse is IBM's
$40M donation to the Open Source community. It is designed "for building
integrated development environments (IDEs) that can be used to create
applications as diverse as web sites, embedded Java TM programs, C++
programs, and Enterprise JavaBeans TM.".  Its principal role is to provide a
seamless integration platform for tools. It achieves this in part from its
ability to support plugins.

I propose that we develop a WW management console plugin for Eclipse
platform. This will fulfill a few requests on the TODO list - management
console, better client action documentation, and more swing/client examples.
Plus, the fact that Eclipse is gaining popularity fast does not hurt either.

Thoughts?

-Matt

Update of /cvsroot/webwork/webwork/src/build
In directory usw-pr-cvs1:/tmp/cvs-serv26347

Modified Files:
	build.xml 
Log Message:
rev up

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

Modified Files:
	index.xml 
Log Message:
added rev

Update of /cvsroot/webwork/webwork/lib/pdf
In directory usw-pr-cvs1:/tmp/cvs-serv26527

Modified Files:
	html-to-pdf-settings.book 
Log Message:
updated

WebWork 1.0.2 was released which includes numerous bug fixes and FAQ for
installing the WAR on WebLogic 6.1 and 7.0. See the CHANGES.txt for more
details.

-Matt

Update of /cvsroot/webwork/webwork/src/resources/web/WEB-INF/classes
In directory usw-pr-cvs1:/tmp/cvs-serv17529

Modified Files:
	log4j.properties 
Log Message:
updated

2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (316)	Dec (117)
2002	Jan (197)	Feb (229)	Mar (293)	Apr (177)	May (84)	Jun (40)	Jul (43)	Aug	Sep	Oct	Nov	Dec

webwork-devel Mailing List for WebWork (Page 7)

webwork-devel — WebWork development