webwork-devel Mailing List for WebWork (Page 41)
Brought to you by:
baldree,
rickardoberg
Menu
▾
▴
webwork-devel — WebWork development
You can subscribe to this list here.
| 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
|
|
From: Doug P. <dou...@es...> - 2002-01-09 16:11:37
|
In building the examples, I came across a few instances of old code in the
JSPs:
\src\resources\web\events\autologin.jsp lines 4 & 5:
"property" should be "value"
\src\resources\web\helloworld\brief\login.jsp lines 7, 12 & 14:
"name" should be "value" (5 places)
\src\resources\web\i18n\price.jsp line 2:
"name" should be "value" (1 place)
And these two files are pretty much completely out of date:
\src\resources\web\template\chtml\controlheader.jsp
\src\resources\web\template\chtml\text.jsp
HTH,
Doug
|
|
From: Rickard <ri...@mi...> - 2002-01-09 07:47:23
|
Matt Baldree wrote: > I could see how a bare bones project structure would be helpful for newbies > to WW and web apps in general. What if we provided a bare bones sample > project that would be part of the "dist" target. So as part of the > distribution, this project structure would be built and moved under the > example folder; i.e., example/projects/webapp. Do you think this would work? But what *is* a barebones example? Does it include utilities for best-practice stuff? And what is best-practice anyway, since that depends on the project? There are many tricky issues with doing minimalist stuff. What is minimal?... > I guess one concern would be do we provide a sample bare bones project for > JSP, Velocity, etc. or do we let them work this out for themselves using the > examples and the documentation? That's also a good question. 1/3 JSP, 1/3 Velocity, 1/XSLT :-) But then, what to do when another technology is integrated? *sigh* /Rickard |
|
From: Rickard <ri...@mi...> - 2002-01-09 07:44:52
|
Bill Burton wrote: > Hello, > > Would it make sense to modify the servlet so it takes a Log4J > configuration parameter? Why add a parameter when we already have a configuration strategy for WebWork? Why not use that? > - If not specified, logging is assumed to already be initialized. > - Specify a properties file name > - Specify an XML file name > > If either a properties file or XML file are specified for the parameter, > the appropriate one will be used to initialized Log4J. Works for me. /Rickard -- Rickard Öberg |
|
From: Mike Cannon-B. <mi...@at...> - 2002-01-09 05:37:57
|
Usually Victors ideas are good - this time I think he's spent a little too
much time in the Puerto Rican sun ;)
The concept of a bare bones structure is ok, but the problem is as you
pointed out - what it should actually contain given that people's needs are
so different. (ie maybe it's a full J2EE app, maybe just a WAR, maybe it's
adding WW to an existing WAR)
However I do think having a much 'simpler' sample app is a good idea. I'd
keep all the complex stuff in there that's already there - it's quite good
for reference but very daunting to newbies who aren't sure where to start.
Then make a new 'newbie' WAR that's just a few simple (perhaps a series of)
actions which do form posts and the like, and show off the most common tags
(iterator, property, ui tags etc).
My $0.02.
-mike
On 8/1/02 8:02 PM, "Matt Baldree" <ma...@sm...> wrote:
> I could see how a bare bones project structure would be helpful for newbies
> to WW and web apps in general. What if we provided a bare bones sample
> project that would be part of the "dist" target. So as part of the
> distribution, this project structure would be built and moved under the
> example folder; i.e., example/projects/webapp. Do you think this would work?
> I guess one concern would be do we provide a sample bare bones project for
> JSP, Velocity, etc. or do we let them work this out for themselves using the
> examples and the documentation?
>
> -Matt
>
> ----- Original Message -----
> From: "Victor Salaman" <vsa...@ho...>
> To: <ma...@sm...>; <web...@li...>
> Sent: Monday, January 07, 2002 10:59 PM
> Subject: Re: [Webwork-devel] loading log4j.properties
>
>
>> Matt, that's great... Although my suggestion would be to create a "ant
>> skeleton" target, that builds a bare-bones, no frills webwork dir
> structure.
>> A new user can take this structure and use it to build an app. Out of my
>> evangelizing process, the biggest problem people have encountered is
> setting
>> up initially. By making a skeleton, that burden is removed.
>>
>> /V
>>
>>
>>> From: "Matt Baldree" <ma...@sm...>
>>> To: "Webwork-Developer" <web...@li...>
>>> Subject: [Webwork-devel] loading log4j.properties
>>> Date: Mon, 7 Jan 2002 19:40:40 -0600
>>>
>>> I was working on the JSP documentation and realized we need a
> configuration
>>> document to describe how to configure WW. I wrote this today and added it
>>> to
>>> CVS. One section in configuration talks about configuring WW's logger. I
>>> think the developer should be able to substitute the default
>>> log4j.properties under webwork/ with their own if they so choose. This
>>> means
>>> they could provide a log4j.properties under WEB-INF/classes that WW would
>>> first check before loading its default under webwork/. This allows the
>>> developer a clean log4j.properties substitution without having to
>>> programmatically do it somewhere else. To allow this capability, I
> propose
>>> changing the ServletDispatcher as follows:
>>>
>>> 84c84,92
>>> <
>>
>> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.prope
> r
>>> ties"));
>>> ---
>>>> try
>>>> {
>>>>
>>
>> PropertyConfigurator.configure(classLoader.getResource("log4j.properties"))
> ;
>>>> log.info("Custom log4j property file loaded.");
>>>> } catch (Exception e)
>>>> {
>>>>
>>
>> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.prope
> r
>>> ties"));
>>>> log.info("Default log4j property file loaded.");
>>>> }
>>>
>>> Thoughts?
>>>
>>> -Matt
>>>
>>>
>>>
>>> _______________________________________________
>>> Webwork-devel mailing list
>>> Web...@li...
>>> https://lists.sourceforge.net/lists/listinfo/webwork-devel
>>
>>
>>
>>
>> _________________________________________________________________
>> Join the world's largest e-mail service with MSN Hotmail.
>> http://www.hotmail.com
>>
>>
>> _______________________________________________
>> Webwork-devel mailing list
>> Web...@li...
>> https://lists.sourceforge.net/lists/listinfo/webwork-devel
>>
>>
>
> _______________________________________________
> Webwork-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-devel
Sent using the Entourage X Test Drive.
|
|
From: Mike Cannon-B. <mi...@at...> - 2002-01-09 05:31:06
|
Bill,
Yes - this does make a lot of sense to me and I think I suggested it a while
back (see ServletLoggingDispatcher or something close ;)). It's a trivial
code edition to add an init-param to the dispatcher servlet with the name of
the log4j config file. (If the file ends .xml, use DOMConfigurator,
otherwise use the PropertiesConfigurator).
This is the most elegant solution I think. By default this turns logging off
though (ie no init parameter) which is OK by me. If others don't want this,
perhaps have the string "none" be special to mean turn logging off?
-mike
8/1/02 3:48 PM, "Bill Burton" <bi...@pr...> wrote:
> Hello,
>
> Would it make sense to modify the servlet so it takes a Log4J
> configuration parameter?
>
> - If not specified, logging is assumed to already be initialized.
> - Specify a properties file name
> - Specify an XML file name
>
> If either a properties file or XML file are specified for the parameter,
> the appropriate one will be used to initialized Log4J.
>
> -Bill
>
> Mike Cannon-Brookes wrote:
>>
>> Matt,
>>
>> I brought this up a while ago because I have a
>> different issue. I always use xml configuration files
>> in log4j (easier to manipulate, generate etc) and
>> there's no way to do that.
>>
>> What I'd suggest is abstract the log loading into
>> separate class that's easily extendable. The default
>> behaviour as below is good, and also if log4j is
>> already configured it should not touch it at all. (I
>> configure logging at the EAR level).
>>
>> -mike
>>
>> --- Matt Baldree <ma...@sm...> wrote:
>>> I was working on the JSP documentation and realized
>>> we need a configuration
>>> document to describe how to configure WW. I wrote
>>> this today and added it to
>>> CVS. One section in configuration talks about
>>> configuring WW's logger. I
>>> think the developer should be able to substitute the
>>> default
>>> log4j.properties under webwork/ with their own if
>>> they so choose. This means
>>> they could provide a log4j.properties under
>>> WEB-INF/classes that WW would
>>> first check before loading its default under
>>> webwork/. This allows the
>>> developer a clean log4j.properties substitution
>>> without having to
>>> programmatically do it somewhere else. To allow this
>>> capability, I propose
>>> changing the ServletDispatcher as follows:
>>>
>>> 84c84,92
>>> <
>>>
>> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
>>> ties"));
>>> ---
>>>> try
>>>> {
>>>>
>>>
>> PropertyConfigurator.configure(classLoader.getResource("log4j.properties"));
>>>> log.info("Custom log4j property file
>>> loaded.");
>>>> } catch (Exception e)
>>>> {
>>>>
>>>
>> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
>>> ties"));
>>>> log.info("Default log4j property file
>>> loaded.");
>>>> }
>>>
>>> Thoughts?
>>>
>>> -Matt
>
> _______________________________________________
> Webwork-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-devel
Sent using the Entourage X Test Drive.
|
|
From: Bill B. <bi...@pr...> - 2002-01-09 05:15:50
|
Hello,
Would it make sense to modify the servlet so it takes a Log4J
configuration parameter?
- If not specified, logging is assumed to already be initialized.
- Specify a properties file name
- Specify an XML file name
If either a properties file or XML file are specified for the parameter,
the appropriate one will be used to initialized Log4J.
-Bill
Mike Cannon-Brookes wrote:
>
> Matt,
>
> I brought this up a while ago because I have a
> different issue. I always use xml configuration files
> in log4j (easier to manipulate, generate etc) and
> there's no way to do that.
>
> What I'd suggest is abstract the log loading into
> separate class that's easily extendable. The default
> behaviour as below is good, and also if log4j is
> already configured it should not touch it at all. (I
> configure logging at the EAR level).
>
> -mike
>
> --- Matt Baldree <ma...@sm...> wrote:
> > I was working on the JSP documentation and realized
> > we need a configuration
> > document to describe how to configure WW. I wrote
> > this today and added it to
> > CVS. One section in configuration talks about
> > configuring WW's logger. I
> > think the developer should be able to substitute the
> > default
> > log4j.properties under webwork/ with their own if
> > they so choose. This means
> > they could provide a log4j.properties under
> > WEB-INF/classes that WW would
> > first check before loading its default under
> > webwork/. This allows the
> > developer a clean log4j.properties substitution
> > without having to
> > programmatically do it somewhere else. To allow this
> > capability, I propose
> > changing the ServletDispatcher as follows:
> >
> > 84c84,92
> > <
> >
> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> > ties"));
> > ---
> > > try
> > > {
> > >
> >
> PropertyConfigurator.configure(classLoader.getResource("log4j.properties"));
> > > log.info("Custom log4j property file
> > loaded.");
> > > } catch (Exception e)
> > > {
> > >
> >
> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> > ties"));
> > > log.info("Default log4j property file
> > loaded.");
> > > }
> >
> > Thoughts?
> >
> > -Matt
|
|
From: Victor S. <sa...@us...> - 2002-01-09 02:07:41
|
Update of /cvsroot/webwork/webwork/src/main/webwork/action In directory usw-pr-cvs1:/tmp/cvs-serv14546/webwork/action Modified Files: ActionSupport.java Log Message: If an exception ocurred in a CommandDrivenAction it would always return an InvocationTargetException, this has now been fixed. |
|
From: Matt B. <ma...@sm...> - 2002-01-09 01:02:26
|
I could see how a bare bones project structure would be helpful for newbies
to WW and web apps in general. What if we provided a bare bones sample
project that would be part of the "dist" target. So as part of the
distribution, this project structure would be built and moved under the
example folder; i.e., example/projects/webapp. Do you think this would work?
I guess one concern would be do we provide a sample bare bones project for
JSP, Velocity, etc. or do we let them work this out for themselves using the
examples and the documentation?
-Matt
----- Original Message -----
From: "Victor Salaman" <vsa...@ho...>
To: <ma...@sm...>; <web...@li...>
Sent: Monday, January 07, 2002 10:59 PM
Subject: Re: [Webwork-devel] loading log4j.properties
> Matt, that's great... Although my suggestion would be to create a "ant
> skeleton" target, that builds a bare-bones, no frills webwork dir
structure.
> A new user can take this structure and use it to build an app. Out of my
> evangelizing process, the biggest problem people have encountered is
setting
> up initially. By making a skeleton, that burden is removed.
>
> /V
>
>
> >From: "Matt Baldree" <ma...@sm...>
> >To: "Webwork-Developer" <web...@li...>
> >Subject: [Webwork-devel] loading log4j.properties
> >Date: Mon, 7 Jan 2002 19:40:40 -0600
> >
> >I was working on the JSP documentation and realized we need a
configuration
> >document to describe how to configure WW. I wrote this today and added it
> >to
> >CVS. One section in configuration talks about configuring WW's logger. I
> >think the developer should be able to substitute the default
> >log4j.properties under webwork/ with their own if they so choose. This
> >means
> >they could provide a log4j.properties under WEB-INF/classes that WW would
> >first check before loading its default under webwork/. This allows the
> >developer a clean log4j.properties substitution without having to
> >programmatically do it somewhere else. To allow this capability, I
propose
> >changing the ServletDispatcher as follows:
> >
> >84c84,92
> ><
>
>PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.prope
r
> >ties"));
> >---
> > > try
> > > {
> > >
>
>PropertyConfigurator.configure(classLoader.getResource("log4j.properties"))
;
> > > log.info("Custom log4j property file loaded.");
> > > } catch (Exception e)
> > > {
> > >
>
>PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.prope
r
> >ties"));
> > > log.info("Default log4j property file loaded.");
> > > }
> >
> >Thoughts?
> >
> >-Matt
> >
> >
> >
> >_______________________________________________
> >Webwork-devel mailing list
> >Web...@li...
> >https://lists.sourceforge.net/lists/listinfo/webwork-devel
>
>
>
>
> _________________________________________________________________
> Join the world's largest e-mail service with MSN Hotmail.
> http://www.hotmail.com
>
>
> _______________________________________________
> Webwork-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-devel
>
>
|
|
From: Matt B. <ma...@sm...> - 2002-01-09 00:45:42
|
For now I made the proposed change but I agree with your point. I need to
finish the JSP doc and I will look at this next.
-Matt
----- Original Message -----
From: "Mike Cannon-Brookes" <boo...@ya...>
To: "Matt Baldree" <ma...@sm...>; "Webwork-Developer"
<web...@li...>
Sent: Monday, January 07, 2002 10:16 PM
Subject: Re: [Webwork-devel] loading log4j.properties
> Matt,
>
> I brought this up a while ago because I have a
> different issue. I always use xml configuration files
> in log4j (easier to manipulate, generate etc) and
> there's no way to do that.
>
> What I'd suggest is abstract the log loading into
> separate class that's easily extendable. The default
> behaviour as below is good, and also if log4j is
> already configured it should not touch it at all. (I
> configure logging at the EAR level).
>
> -mike
>
> --- Matt Baldree <ma...@sm...> wrote:
> > I was working on the JSP documentation and realized
> > we need a configuration
> > document to describe how to configure WW. I wrote
> > this today and added it to
> > CVS. One section in configuration talks about
> > configuring WW's logger. I
> > think the developer should be able to substitute the
> > default
> > log4j.properties under webwork/ with their own if
> > they so choose. This means
> > they could provide a log4j.properties under
> > WEB-INF/classes that WW would
> > first check before loading its default under
> > webwork/. This allows the
> > developer a clean log4j.properties substitution
> > without having to
> > programmatically do it somewhere else. To allow this
> > capability, I propose
> > changing the ServletDispatcher as follows:
> >
> > 84c84,92
> > <
> >
>
PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> > ties"));
> > ---
> > > try
> > > {
> > >
> >
>
PropertyConfigurator.configure(classLoader.getResource("log4j.properties"));
> > > log.info("Custom log4j property file
> > loaded.");
> > > } catch (Exception e)
> > > {
> > >
> >
>
PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> > ties"));
> > > log.info("Default log4j property file
> > loaded.");
> > > }
> >
> > Thoughts?
> >
> > -Matt
> >
> >
> >
> > _______________________________________________
> > Webwork-devel mailing list
> > Web...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/webwork-devel
>
>
> __________________________________________________
> Do You Yahoo!?
> Send FREE video emails in Yahoo! Mail!
> http://promo.yahoo.com/videomail/
>
>
|
|
From: matt b. <ba...@us...> - 2002-01-09 00:43:57
|
Update of /cvsroot/webwork/webwork/src/main/webwork/dispatcher In directory usw-pr-cvs1:/tmp/cvs-serv30715 Modified Files: ServletDispatcher.java Log Message: changed to look for a custom log4j before default |
|
From: Rickard <ri...@mi...> - 2002-01-08 08:18:02
|
Matt Baldree wrote:
> I was working on the JSP documentation and realized we need a configuration
> document to describe how to configure WW. I wrote this today and added it to
> CVS. One section in configuration talks about configuring WW's logger. I
> think the developer should be able to substitute the default
> log4j.properties under webwork/ with their own if they so choose. This means
> they could provide a log4j.properties under WEB-INF/classes that WW would
> first check before loading its default under webwork/. This allows the
> developer a clean log4j.properties substitution without having to
> programmatically do it somewhere else. To allow this capability, I propose
> changing the ServletDispatcher as follows:
>
> 84c84,92
> <
> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> ties"));
> ---
>
>> try
>> {
>>
>>
> PropertyConfigurator.configure(classLoader.getResource("log4j.properties"));
>
>> log.info("Custom log4j property file loaded.");
>> } catch (Exception e)
>> {
>>
>>
> PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> ties"));
>
>> log.info("Default log4j property file loaded.");
>> }
>>
>
> Thoughts?
This sounds like a good first step, then accompanied with what Mike
proposed.
/Rickard
--
Rickard Öberg
|
|
From: Victor S. <vsa...@ho...> - 2002-01-08 04:59:57
|
Matt, that's great... Although my suggestion would be to create a "ant
skeleton" target, that builds a bare-bones, no frills webwork dir structure.
A new user can take this structure and use it to build an app. Out of my
evangelizing process, the biggest problem people have encountered is setting
up initially. By making a skeleton, that burden is removed.
/V
>From: "Matt Baldree" <ma...@sm...>
>To: "Webwork-Developer" <web...@li...>
>Subject: [Webwork-devel] loading log4j.properties
>Date: Mon, 7 Jan 2002 19:40:40 -0600
>
>I was working on the JSP documentation and realized we need a configuration
>document to describe how to configure WW. I wrote this today and added it
>to
>CVS. One section in configuration talks about configuring WW's logger. I
>think the developer should be able to substitute the default
>log4j.properties under webwork/ with their own if they so choose. This
>means
>they could provide a log4j.properties under WEB-INF/classes that WW would
>first check before loading its default under webwork/. This allows the
>developer a clean log4j.properties substitution without having to
>programmatically do it somewhere else. To allow this capability, I propose
>changing the ServletDispatcher as follows:
>
>84c84,92
><
>PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
>ties"));
>---
> > try
> > {
> >
>PropertyConfigurator.configure(classLoader.getResource("log4j.properties"));
> > log.info("Custom log4j property file loaded.");
> > } catch (Exception e)
> > {
> >
>PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
>ties"));
> > log.info("Default log4j property file loaded.");
> > }
>
>Thoughts?
>
>-Matt
>
>
>
>_______________________________________________
>Webwork-devel mailing list
>Web...@li...
>https://lists.sourceforge.net/lists/listinfo/webwork-devel
_________________________________________________________________
Join the worlds largest e-mail service with MSN Hotmail.
http://www.hotmail.com
|
|
From: Mike Cannon-B. <boo...@ya...> - 2002-01-08 04:16:29
|
Matt,
I brought this up a while ago because I have a
different issue. I always use xml configuration files
in log4j (easier to manipulate, generate etc) and
there's no way to do that.
What I'd suggest is abstract the log loading into
separate class that's easily extendable. The default
behaviour as below is good, and also if log4j is
already configured it should not touch it at all. (I
configure logging at the EAR level).
-mike
--- Matt Baldree <ma...@sm...> wrote:
> I was working on the JSP documentation and realized
> we need a configuration
> document to describe how to configure WW. I wrote
> this today and added it to
> CVS. One section in configuration talks about
> configuring WW's logger. I
> think the developer should be able to substitute the
> default
> log4j.properties under webwork/ with their own if
> they so choose. This means
> they could provide a log4j.properties under
> WEB-INF/classes that WW would
> first check before loading its default under
> webwork/. This allows the
> developer a clean log4j.properties substitution
> without having to
> programmatically do it somewhere else. To allow this
> capability, I propose
> changing the ServletDispatcher as follows:
>
> 84c84,92
> <
>
PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> ties"));
> ---
> > try
> > {
> >
>
PropertyConfigurator.configure(classLoader.getResource("log4j.properties"));
> > log.info("Custom log4j property file
> loaded.");
> > } catch (Exception e)
> > {
> >
>
PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
> ties"));
> > log.info("Default log4j property file
> loaded.");
> > }
>
> Thoughts?
>
> -Matt
>
>
>
> _______________________________________________
> Webwork-devel mailing list
> Web...@li...
>
https://lists.sourceforge.net/lists/listinfo/webwork-devel
__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
|
|
From: Matt B. <ma...@sm...> - 2002-01-08 01:41:24
|
I was working on the JSP documentation and realized we need a configuration
document to describe how to configure WW. I wrote this today and added it to
CVS. One section in configuration talks about configuring WW's logger. I
think the developer should be able to substitute the default
log4j.properties under webwork/ with their own if they so choose. This means
they could provide a log4j.properties under WEB-INF/classes that WW would
first check before loading its default under webwork/. This allows the
developer a clean log4j.properties substitution without having to
programmatically do it somewhere else. To allow this capability, I propose
changing the ServletDispatcher as follows:
84c84,92
<
PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
ties"));
---
> try
> {
>
PropertyConfigurator.configure(classLoader.getResource("log4j.properties"));
> log.info("Custom log4j property file loaded.");
> } catch (Exception e)
> {
>
PropertyConfigurator.configure(classLoader.getResource("webwork/log4j.proper
ties"));
> log.info("Default log4j property file loaded.");
> }
Thoughts?
-Matt
|
|
From: matt b. <ba...@us...> - 2002-01-08 01:39:14
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv5165 Modified Files: index.xml Added Files: configuration.xml Log Message: added configuration doc |
|
From: Philipp M. <llu...@us...> - 2002-01-06 20:11:00
|
Update of /cvsroot/webwork/webwork/src/resources/web/WEB-INF In directory usw-pr-cvs1:/tmp/cvs-serv7220/resources/web/WEB-INF Modified Files: web.xml Log Message: Changes suggested by Aslak Hellesoy: Replaced empty load-on_startup element with <load-on_startup>1</...> in web.xml Added Doctype declaration to application.xml |
|
From: Philipp M. <llu...@us...> - 2002-01-06 20:11:00
|
Update of /cvsroot/webwork/webwork/src/resources/ear/META-INF In directory usw-pr-cvs1:/tmp/cvs-serv7220/resources/ear/META-INF Modified Files: application.xml Log Message: Changes suggested by Aslak Hellesoy: Replaced empty load-on_startup element with <load-on_startup>1</...> in web.xml Added Doctype declaration to application.xml |
|
From: <asl...@ne...> - 2002-01-06 17:59:22
|
I have two issues about the webwork samples: 1) webwork/src/resources/web/WEB-INF/web.xml According to the DTD, the load-on_startup element is not accepted by WLS. (Although the DTD says it can be empty. This is ctually a WLS bug, but it wouldn't do any harm to change it to: <load-on_startup>1</load-on_startup> 2) src/resources/ear/META-INF/application.xml The XML and DTD declarations are missing: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'> WLS refuses this file without those declarations. Could you change this in CVS? Regards, Aslak |
|
From: Philipp M. <llu...@us...> - 2002-01-06 16:53:50
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv32563 Modified Files: velocity.xml Log Message: Updated with path from webwork-devel mailing list. Thanks again, Dan. |
|
From: Dan B. <da...@ch...> - 2002-01-06 07:46:16
|
I made some things clearer and removed some blatant errors (thanks Salaman).. I'll add some more advanced stuff over then next few days.... as I figure it out :) If someone who has not used velocity with webwork would try to get the example in this doc running and let me know anything thats not clear enough, i would appreciate it. |
|
From: matt b. <ba...@us...> - 2002-01-05 02:32:30
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv15156 Modified Files: velocity.xml Log Message: update - thanks Dan |
|
From: Kjetil H.P. <kje...@mo...> - 2002-01-04 21:19:28
|
This one is old, I've updated this file locally and I'll post the new stuff + sample code as soon as I get my machine up from a terrible "christmas chrash" ;) You can have a go at it again then. /kjetilhp ----- Original Message ----- From: "Dan Bachelder" <ch...@ch...> To: <web...@li...> Sent: Friday, January 04, 2002 5:05 PM Subject: [Webwork-devel] [PATCH] - validation.xml > I think i made this patch right... "cvs diff -u validation.xml" > > no new content... just reading it and fixed a few readability and spelling issues... > > > > > |
|
From: Dan B. <ch...@ch...> - 2002-01-04 18:11:21
|
I noticed on the "Documentation Update" email the other day that no one was signed up todo velocity docs.. and there is really nothing in CVS now... so here is a start at it... I'm just getting going with webwork, so please forgive any ommisions or incorrect statements.. |
|
From: Dan B. <ch...@ch...> - 2002-01-04 16:05:07
|
I think i made this patch right... "cvs diff -u validation.xml" no new content... just reading it and fixed a few readability and spelling issues... |
|
From: matt b. <ba...@us...> - 2002-01-03 23:42:36
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv1038 Modified Files: baseclasses.xml build.xml community.xml expr.xml exprref.xml features.xml jsp.xml jspref.xml validation.xml valuestack.xml xslt.xml Log Message: modified look and feel to be consistent across sections |
34982 messages has been excluded from this view by a project administrator.
