webwork-user Mailing List for WebWork (Page 10)
Brought to you by:
baldree,
rickardoberg
Menu
▾
▴
webwork-user — WebWork users mailing list
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(24) |
Dec
(194) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(70) |
Feb
(133) |
Mar
(193) |
Apr
(114) |
May
(141) |
Jun
(176) |
Jul
(334) |
Aug
(418) |
Sep
(329) |
Oct
(209) |
Nov
(296) |
Dec
(122) |
| 2002 |
Jan
(123) |
Feb
(61) |
Mar
(115) |
Apr
(149) |
May
(124) |
Jun
(69) |
Jul
(80) |
Aug
(22) |
Sep
(1) |
Oct
(4) |
Nov
(3) |
Dec
|
| 2003 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
|
May
(1) |
Jun
(5) |
Jul
(4) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Sean H. <sea...@di...> - 2002-05-20 15:30:42
|
I'm having problems running the webwork 1.0.3 samples on orion 1.5.4. When trying to run the 'http://localhost/webwork/tests/exprformtest!default.action' test, I get the following 500 error: java.lang.NullPointerException at webwork.util.ValueStack.getStack(ValueStack.java:63) at webwork.view.taglib.WebWorkBodyTagSupport.getStack(WebWorkBodyTagSupport.jav a:47) at webwork.view.taglib.ui.ComponentTag.release(ComponentTag.java:148) at /tests/exprformtest.jsp._jspService(/tests/exprformtest.jsp.java:106)... I get similar problems with other examples - all relating to accessing the ValueStack. I'm assuming that this is an Orion-specific problem. Would appreciate some help - thanks in advance, Sean |
|
From: notyy <no...@vi...> - 2002-05-20 07:30:50
|
aGksYWxsDQogICAgSSBhbSBuZXcgdG8gd2Vid29yayAsYW5kIHRyeWluZyB0byBidWlsZCBhIHdl YiBhcHBsaWNhdGlvbiB3aXRoIGl0Lg0KICAgIEkgZGlkbid0IHVzZSB3ZWJ3b3JrIHVpIHRhZ2xp YiB0byBwcmVzZW50IHRoZSByZXN1bHQsSSB1c2UgVmFsdWVTdGFjayBpbnN0ZWFkLg0KICAgIHdo ZW4gc29tZSBwYXJhbWV0ZXJzIHBvc3QgdG8gYW4gQWN0aW9uLCB0aGUgYWN0aW9uKGNvbnRyb2xs ZXIpIHByb2Nlc3MgaXQsdGhlbiB0aGUgZGlzcGF0Y2hlciBwdXNoIHRoZSBBY3Rpb24gaW50byB0 aGUgVmFsdWVTdGFjaw0KYW5kIGZvcndvcmQgdG8gdGhlIHJlc3VsdCBqc3AuIFRoZSByZXN1bHQg anNwIHRoZW4gcG9wIHRoZSBBY3Rpb24gb3V0LGFuZCBnZXQgc29tZSBkYXRhIGZyb20gaXQuDQog ICAgc28sIEluIGZhY3QgLEknbSB1c2luZyB0aGUgQWN0aW9uIGFzIHRoZSBtb2RlbCBmb3IgdGhh dCBqc3AgcGFnZS4gDQogICAgSSBhbSB3b25kZXJpbmcgd2hldGhlciBJIGFtIHVzaW5nIHdlYndv cmsgY29ycmVjdGx5Lg0K |
|
From: Mike Cannon-B. <mi...@at...> - 2002-05-20 00:19:52
|
+1 Extra filters just make it harder for users to setup! KISS :) -mike On 20/5/02 10:05 AM, "Matt Baldree" (ma...@sm...) penned the words: > I assume you mean moving the filter logic in the ServletDispatcher and wrap > the request there. I'll take a look. > > -Matt > > ----- Original Message ----- > From: "Patrick Lightbody" <pli...@ho...> > To: "Matt Baldree" <ma...@sm...>; "Webwork-User" > <web...@li...> > Sent: Sunday, May 19, 2002 6:55 PM > Subject: Re: [Webwork-user] multipart support > > >> I don't understand why you can't just make the ServletDispatcher figure > out >> if the request is multipart and if so act accordingly? Why not make the >> entire thing transparent and also still avoid using filters unless >> absolutely necessary. I know most implementations can do filters now, so >> that's not the issue, but the more transparent this feature is, the > better! >> Just my two cents... >> >> -Pat >> >> ----- Original Message ----- >> From: "Matt Baldree" <ma...@sm...> >> To: "Webwork-User" <web...@li...> >> Sent: Saturday, May 18, 2002 11:51 AM >> Subject: [Webwork-user] multipart support >> >> >>> I added multipart support to WW. I looked at a couple of approaches at >>> solving this problem and settled in using a filter to wrap the request. > I >>> thought this was the cleanest, less obtrusive solution. You have the >> ability >>> to choose between Jason's multipart parse (watch the license) and Pell's >> by >>> setting a new property setting "webwork.multipart.parser". You can > always >>> add your own parser and adapter if you like. See "Multipart Request > Test" >>> for more details. >>> >>> -Matt >>> >>> >>> >>> _______________________________________________________________ >>> Hundreds of nodes, one monster rendering program. >>> Now that's a super model! Visit http://clustering.foundries.sf.net/ >>> >>> _______________________________________________ >>> Webwork-user mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webwork-user >>> >> >> > > > > _______________________________________________________________ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > _______________________________________________ > Webwork-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-user |
|
From: Matt B. <ma...@sm...> - 2002-05-20 00:05:20
|
I assume you mean moving the filter logic in the ServletDispatcher and wrap the request there. I'll take a look. -Matt ----- Original Message ----- From: "Patrick Lightbody" <pli...@ho...> To: "Matt Baldree" <ma...@sm...>; "Webwork-User" <web...@li...> Sent: Sunday, May 19, 2002 6:55 PM Subject: Re: [Webwork-user] multipart support > I don't understand why you can't just make the ServletDispatcher figure out > if the request is multipart and if so act accordingly? Why not make the > entire thing transparent and also still avoid using filters unless > absolutely necessary. I know most implementations can do filters now, so > that's not the issue, but the more transparent this feature is, the better! > Just my two cents... > > -Pat > > ----- Original Message ----- > From: "Matt Baldree" <ma...@sm...> > To: "Webwork-User" <web...@li...> > Sent: Saturday, May 18, 2002 11:51 AM > Subject: [Webwork-user] multipart support > > > > I added multipart support to WW. I looked at a couple of approaches at > > solving this problem and settled in using a filter to wrap the request. I > > thought this was the cleanest, less obtrusive solution. You have the > ability > > to choose between Jason's multipart parse (watch the license) and Pell's > by > > setting a new property setting "webwork.multipart.parser". You can always > > add your own parser and adapter if you like. See "Multipart Request Test" > > for more details. > > > > -Matt > > > > > > > > _______________________________________________________________ > > Hundreds of nodes, one monster rendering program. > > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > > > _______________________________________________ > > Webwork-user mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webwork-user > > > > |
|
From: Patrick L. <pli...@ho...> - 2002-05-19 23:55:32
|
I don't understand why you can't just make the ServletDispatcher figure out if the request is multipart and if so act accordingly? Why not make the entire thing transparent and also still avoid using filters unless absolutely necessary. I know most implementations can do filters now, so that's not the issue, but the more transparent this feature is, the better! Just my two cents... -Pat ----- Original Message ----- From: "Matt Baldree" <ma...@sm...> To: "Webwork-User" <web...@li...> Sent: Saturday, May 18, 2002 11:51 AM Subject: [Webwork-user] multipart support > I added multipart support to WW. I looked at a couple of approaches at > solving this problem and settled in using a filter to wrap the request. I > thought this was the cleanest, less obtrusive solution. You have the ability > to choose between Jason's multipart parse (watch the license) and Pell's by > setting a new property setting "webwork.multipart.parser". You can always > add your own parser and adapter if you like. See "Multipart Request Test" > for more details. > > -Matt > > > > _______________________________________________________________ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > _______________________________________________ > Webwork-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-user > |
|
From: Matt B. <ma...@sm...> - 2002-05-18 18:52:12
|
I added multipart support to WW. I looked at a couple of approaches at solving this problem and settled in using a filter to wrap the request. I thought this was the cleanest, less obtrusive solution. You have the ability to choose between Jason's multipart parse (watch the license) and Pell's by setting a new property setting "webwork.multipart.parser". You can always add your own parser and adapter if you like. See "Multipart Request Test" for more details. -Matt |
|
From: Rickard <ri...@dr...> - 2002-05-17 14:23:57
|
Harvey Kandola wrote: > I created my own theme/skin/template and made the change to my > webwork.properties file to point towards my template directory: >=20 > webwork.ui.theme=3Dmy_skin >=20 > But I then also have to change all my JSP pages in order to use this ne= w > theme: >=20 > <link rel=3D"stylesheet" type=3D"text/css" href=3D"template/standard/st= yles.css" > title=3D"Style"> > <link rel=3D"stylesheet" type=3D"text/css" href=3D"template/my_skin/sty= les.css" > title=3D"Style"> >=20 > Is there any way of changing the theme name centrally (i.e. > webwork.properties file) instead of having to change all of my JSP page= s as > well? Use SiteMesh (www.opensymphony.com). /Rickard --=20 Rickard =D6berg |
|
From: Harvey K. <ha...@ka...> - 2002-05-17 13:34:17
|
I created my own theme/skin/template and made the change to my webwork.properties file to point towards my template directory: webwork.ui.theme=my_skin But I then also have to change all my JSP pages in order to use this new theme: <link rel="stylesheet" type="text/css" href="template/standard/styles.css" title="Style"> <link rel="stylesheet" type="text/css" href="template/my_skin/styles.css" title="Style"> Is there any way of changing the theme name centrally (i.e. webwork.properties file) instead of having to change all of my JSP pages as well? Thanks. Harvey. |
|
From: <ma...@sm...> - 2002-05-16 22:29:51
|
Throw Tomcat 4.0.3 away and get 4.0.4bx. 4.0.2 and 4.0.3 has classloader bugs. -Matt On Thu, 16 May 2002, "Dave Maher" wrote > > Hi WW group - > > I have Tomcat 4.0.3 and WW 1.0.3. I dropped the webwork.war into my webapps > folder and ensured log4j.jar was in tomcat_home/lib. > > However, upon launching Tomcat, I get this error. There are no other webapps > besides ROOT deployed. > > ============================================== > Starting service Tomcat-Standalone > Apache Tomcat/4.0.3 > PARSE error at line 1 column 1 > org.xml.sax.SAXParseException: The markup in the document preceding the root > element must be well-formed > Starting service Tomcat-Apache > Apache Tomcat/4.0.3 > ============================================== > > > and I gingerly try the first example out: > > http://localhost:8080/webwork/tests/expr.jsp > > and get a 500 error. > > ============================================== > org.apache.jasper.JasperException: No such tag bean in the tag library > imported with prefix webwork > at > org.apache.jasper.compiler.TagLibraries.isUserDefinedTag(TagLibraries.java:97) > ============================================== > > > Would appreciate help, > Thanks in advance, > > Darren Michaels > > > > _________________________________________________________________ > Chat with friends online, try MSN Messenger: http://messenger.msn.com > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Webwork-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-user |
|
From: Dave M. <t0a...@ho...> - 2002-05-16 21:21:56
|
Hi WW group - I have Tomcat 4.0.3 and WW 1.0.3. I dropped the webwork.war into my webapps folder and ensured log4j.jar was in tomcat_home/lib. However, upon launching Tomcat, I get this error. There are no other webapps besides ROOT deployed. ============================================== Starting service Tomcat-Standalone Apache Tomcat/4.0.3 PARSE error at line 1 column 1 org.xml.sax.SAXParseException: The markup in the document preceding the root element must be well-formed Starting service Tomcat-Apache Apache Tomcat/4.0.3 ============================================== and I gingerly try the first example out: http://localhost:8080/webwork/tests/expr.jsp and get a 500 error. ============================================== org.apache.jasper.JasperException: No such tag bean in the tag library imported with prefix webwork at org.apache.jasper.compiler.TagLibraries.isUserDefinedTag(TagLibraries.java:97) ============================================== Would appreciate help, Thanks in advance, Darren Michaels _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com |
|
From: <ma...@sm...> - 2002-05-16 15:47:43
|
I've branched 1.0.3 "branch-release-1-0-3" so new features should be committed to the HEAD which will become 1.1 release. I will manage 1.0.3 for bug fixes that are needed before 1.1 release. -Matt On Thu, 16 May 2002, "Jason Carreira" wrote > > When / Where should new features (probably different enough that we don't want them in the 1.0.x tree) be checked in? > > > -----Original Message----- > > From: ma...@sm... [mailto:ma...@sm...] > > Sent: Thursday, May 16, 2002 11:35 AM > > To: web...@li... > > Subject: [Webwork-user] release 1.0.3 > > > > > > WebWork 1.0.3 was just released. This release includes > > support for escaping HTML via property tag so all UI > > tags now escape HTML. In addition, it includes > > important bug fixes that surfaced using WW in a > > WebLogic environment. Finally, a FAQ was added for > > JBoss. See CHANGES.txt for more details. > > > > Things to look forward to. WebWork project will soon > > utilize JIRA (http://www.atlassian.com/software/jira/) > > for its issue tracking system and not SF. This system > > is far better and will provide you with the ability to > > cast your vote on features that should be included, > > etc. Also, support for multipart content type is soon > > coming. > > > > Stay tune for more. > > > > -Matt > > > > > > > > _______________________________________________________________ > > > > Have big pipes? SourceForge.net is looking for download > > mirrors. We supply > > the hardware. You get the recognition. Email Us: > > ban...@so... > > _______________________________________________ > > Webwork-user mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webwork-user > > |
|
From: Jason C. <jas...@no...> - 2002-05-16 15:41:47
|
When / Where should new features (probably different enough that we = don't want them in the 1.0.x tree) be checked in? > -----Original Message----- > From: ma...@sm... [mailto:ma...@sm...] > Sent: Thursday, May 16, 2002 11:35 AM > To: web...@li... > Subject: [Webwork-user] release 1.0.3 >=20 >=20 > WebWork 1.0.3 was just released. This release includes > support for escaping HTML via property tag so all UI > tags now escape HTML. In addition, it includes > important bug fixes that surfaced using WW in a > WebLogic environment. Finally, a FAQ was added for > JBoss. See CHANGES.txt for more details. >=20 > Things to look forward to. WebWork project will soon > utilize JIRA (http://www.atlassian.com/software/jira/) > for its issue tracking system and not SF. This system > is far better and will provide you with the ability to > cast your vote on features that should be included, > etc. Also, support for multipart content type is soon > coming.=20 >=20 > Stay tune for more. >=20 > -Matt >=20 >=20 >=20 > _______________________________________________________________ >=20 > Have big pipes? SourceForge.net is looking for download=20 > mirrors. We supply > the hardware. You get the recognition. Email Us:=20 > ban...@so... > _______________________________________________ > Webwork-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-user >=20 |
|
From: <ma...@sm...> - 2002-05-16 15:35:25
|
WebWork 1.0.3 was just released. This release includes support for escaping HTML via property tag so all UI tags now escape HTML. In addition, it includes important bug fixes that surfaced using WW in a WebLogic environment. Finally, a FAQ was added for JBoss. See CHANGES.txt for more details. Things to look forward to. WebWork project will soon utilize JIRA (http://www.atlassian.com/software/jira/) for its issue tracking system and not SF. This system is far better and will provide you with the ability to cast your vote on features that should be included, etc. Also, support for multipart content type is soon coming. Stay tune for more. -Matt |
|
From: Rickard <ri...@dr...> - 2002-05-16 15:12:07
|
Vaishakhi Ajmera wrote: > I have written quite a few jsp pages calling methods on actions and hav= e > found that webwork prefixes them with a 'get' before calling them. Henc= e I > have all the methods in my actions that I want to make available to my = views > start with 'get'. > However I now want to have my action implement an interface that has me= thods > not starting with 'get' and wondered if my views will be able to call t= hem. > I do not know how to do that. > Has anyone else done that and if so, how. Try and see what happens. It should work fine by just using the method=20 name as is. I.e. if your method is "foo" then use "foo" as property name. /Rickard --=20 Rickard =D6berg |
|
From: Vaishakhi A. <vai...@ar...> - 2002-05-16 14:46:33
|
No I haven't, I have written quite a few jsp pages calling methods on actions and have found that webwork prefixes them with a 'get' before calling them. Hence I have all the methods in my actions that I want to make available to my views start with 'get'. However I now want to have my action implement an interface that has methods not starting with 'get' and wondered if my views will be able to call them. I do not know how to do that. Has anyone else done that and if so, how. Thanks Vaishakhi ----- Original Message ----- From: "Rickard" <ri...@dr...> To: "Vaishakhi Ajmera" <vai...@ar...> Cc: <web...@li...> Sent: Thursday, May 16, 2002 2:15 AM Subject: Re: [Webwork-user] Method not starting with get > Vaishakhi Ajmera wrote: > > hello, > > I wanted to know if my view can call only those methods from my actions > > that start with a 'get' or not. > > Have you tried? > > /Rickard > |
|
From: Rickard <ri...@dr...> - 2002-05-16 11:48:28
|
Bill Burton wrote: >>It should be trivial to write a servlet filter that overloads >>request.getAttribute() and delegates to the stack before doing the >>normal stuff. The semantics of that may get a little iffy, but at least >>it would provide super-trivial access to the WW valuestack. >=20 > It's too bad JSTL doesn't provide a way to do this internally where you > could implement your own version of PageContent.findAttribute similar t= o > what you did for the Velocity implementation. Yeah, but the filter thingy should do the trick though. Not very hard to=20 do, so.. /Rickard --=20 Rickard =D6berg |
|
From: Rickard <ri...@dr...> - 2002-05-16 11:48:24
|
Vaishakhi Ajmera wrote: > hello, > I wanted to know if my view can call only those methods from my actions > that start with a 'get' or not. Have you tried? /Rickard |
|
From: Vaishakhi A. <vai...@ar...> - 2002-05-15 21:07:07
|
hello, I wanted to know if my view can call only those methods from my actions = that start with a 'get' or not.=20 If not, I would love to see an example to a method starting without a = 'get' being called. Any help will be appreciated. Thanks=20 Vaishakhi Ajmera |
|
From: Bill B. <bi...@pr...> - 2002-05-15 20:37:07
|
Hello,
Rickard wrote:
>=20
> Bill Burton wrote:
> > Other objects are only available on WW's ValueStack which JSTL can't
> > directly access. So to make them available you have to copy the obje=
ct of
> > interest off the VS and save a reference to it in the request, etc. =
Don't
> > know of any way to do this with WW tags, but the following scriptlet
> > should work:
> > <% request.setAttribute("user",
> > ValueStack.getStack(request).findValue(".")); %>
>=20
> which equals this with WW tags:
> <webwork:property value=3D"." id=3D"user">
> ...use JSTL here...
> </webwork:property>
Cool!
> It should be trivial to write a servlet filter that overloads
> request.getAttribute() and delegates to the stack before doing the
> normal stuff. The semantics of that may get a little iffy, but at least
> it would provide super-trivial access to the WW valuestack.
It's too bad JSTL doesn't provide a way to do this internally where you
could implement your own version of PageContent.findAttribute similar to
what you did for the Velocity implementation.
> /Rickard
>=20
> --
> Rickard =D6berg
-Bill
|
|
From: <ma...@sm...> - 2002-05-15 13:35:04
|
you don't need an action loaded for this. it will first try to use the action on the stack, if it can't find your bundle, then it will load ActionSupport and use it to find your bundle. -Matt On Wed, 15 May 2002, "Harvey Kandola" wrote > > Matt, > > Thanks for your response. > > As for using i18n tag, am I correct in assuming that this will place > a resource bundle on the value stack as long as the resource bundle > has a corresponding action class? > > What happens if a JSP does not have a corresponding action class? > All I want to do is to have global resource files that can be used on > any JSP page to access localised resource items as follows: > > <webwork:text name="'blah'"/> > > There will be cases where JSP's don't have action classes but still > need to access resource bundles... > > Thanks. > Harvey. > > > > <ma...@sm...> wrote in message > news:200...@ma..... > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Webwork-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-user |
|
From: Harvey K. <ha...@ka...> - 2002-05-15 09:46:35
|
Matt, Thanks for your response. As for using i18n tag, am I correct in assuming that this will place a resource bundle on the value stack as long as the resource bundle has a corresponding action class? What happens if a JSP does not have a corresponding action class? All I want to do is to have global resource files that can be used on any JSP page to access localised resource items as follows: <webwork:text name="'blah'"/> There will be cases where JSP's don't have action classes but still need to access resource bundles... Thanks. Harvey. <ma...@sm...> wrote in message news:200...@ma..... |
|
From: Rickard <ri...@dr...> - 2002-05-15 05:49:55
|
Bill Burton wrote:
> Other objects are only available on WW's ValueStack which JSTL can't
> directly access. So to make them available you have to copy the object=
of
> interest off the VS and save a reference to it in the request, etc. Do=
n't
> know of any way to do this with WW tags, but the following scriptlet
> should work:
> <% request.setAttribute("user",
> ValueStack.getStack(request).findValue(".")); %>
which equals this with WW tags:
<webwork:property value=3D"." id=3D"user">
...use JSTL here...
</webwork:property>
It should be trivial to write a servlet filter that overloads=20
request.getAttribute() and delegates to the stack before doing the=20
normal stuff. The semantics of that may get a little iffy, but at least=20
it would provide super-trivial access to the WW valuestack.
/Rickard
--=20
Rickard =D6berg
|
|
From: Bill B. <bi...@pr...> - 2002-05-15 04:55:34
|
Hello Ryan,
> Ryan LeCompte wrote:
>
> Hello,
>
> Is there any way to utilize the new JSTL (JSP Standard Tag Libraries) in
> the WebWork framework?
Yes, if you're willing to write a little "glue" code.
If your Actions and Beans use the "id" attribute in the WebWork tags, you
should be able to access them directly from the JSTL Expression Language.
Other objects are only available on WW's ValueStack which JSTL can't
directly access. So to make them available you have to copy the object of
interest off the VS and save a reference to it in the request, etc. Don't
know of any way to do this with WW tags, but the following scriptlet
should work:
<% request.setAttribute("user",
ValueStack.getStack(request).findValue(".")); %>
which returns a reference to the current object on the ValueStack saving
it into the request. This effectively gives the object an id of "user."
Then you should then be able to access the object in JSTL something like:
<c:out value="${user.email}"/>
Hope this helps,
-Bill
> Thanks.
>
> Ryan LeCompte
> rm...@ul...
> http://www.ull.edu/~rml7669
>
|
|
From: <ma...@sm...> - 2002-05-14 21:45:10
|
It is on our TODO list to look into this. On Tue, 14 May 2002, "Ryan LeCompte" wrote > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML><HEAD> > <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> > <META content="MSHTML 5.50.4807.2300" name=GENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY bgColor=#ffffff> > <DIV><FONT face=Arial size=2></FONT> </DIV> > <DIV><FONT face=Arial size=2>Hello,</FONT></DIV> > <DIV><FONT face=Arial size=2></FONT> </DIV> > <DIV><FONT face=Arial size=2></FONT> </DIV> > <DIV><FONT face=Arial size=2>Is there any way to utilize the new JSTL (JSP > Standard Tag Libraries) in the WebWork framework?</FONT></DIV> > <DIV><FONT face=Arial size=2></FONT> </DIV> > <DIV><FONT face=Arial size=2>Thanks.</FONT></DIV> > <DIV><FONT face=Arial size=2></FONT> </DIV> > <DIV><FONT face=Arial size=2>Ryan LeCompte</FONT></DIV> > <DIV><FONT face=Arial size=2><A > href="mailto:rm...@ul...">rm...@ul...</A></FONT></DIV> > <DIV><FONT face=Arial size=2><A > href="http://www.ull.edu/~rml7669">http://www.ull.edu/~rml7669</A></FONT></DIV> > <DIV> </DIV></BODY></HTML> |
|
From: <ma...@sm...> - 2002-05-14 21:41:02
|
You have a couple of options. 1. You can use i18n tag and load a bundle to be used. 2. or, WW will walk the inheritence tree of an action looking for the resource bundle if your action extends ActionSupport. So, you can have a resource bundle for ActionSupport and if all your actions extend this then this resource bundle will be called unless you offer a more specific bundle for you class. -Matt On Tue, 14 May 2002, "Harvey Kandola" wrote > > How can you specify global resource bundle files that can be used/accessed > by all JSP's? > > The examples that ship with WW show FormTest.jsp using > FormTest.properties... > > Thanks. > > > > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Webwork-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-user |
3279 messages has been excluded from this view by a project administrator.
