I'll update the skeleton project as soon as the 1.3 is ready, it hasn't
been updated for a while :-)
/kjetilhp
-Original Message-
From: Maurice C.Parker [mailto:maurice;vineyardenterprise.com]
Sent: 12. november 2002 05:58
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Final stretch.
[print, context, focus]
Those three tags are ok, but I'm not sure about the names. Before I had
read about them I thought context did was focus do (i.e. pushing the
result of evaluating a property to the stack).
Any better name suggestions?
This is the really hard part about these tags
How about just 'out' for print? To go along with out.println etc.
On Tuesday, November 12, 2002, at 04:57 AM, Chris Miller wrote:
I'm a little uncomfortable with the names as they currently stand too.
Perhaps the 'context' tag could be renamed 'expose', and then 'focus'
could
become
Am Die, 2002-11-12 um 08.27 schrieb Rickard Öberg:
Those three tags are ok, but I'm not sure about the names. Before I had
read about them I thought context did was focus do (i.e. pushing the
result of evaluating a property to the stack).
Any better name suggestions?
What about 'select'?
What about 'select'?
select should be reserved for a ui tag for select controls imho.
// Anders Hovmöller
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
I think this will have to wait until after 1.3. The alpha release will
happen very soon and hopefully after a couple of quick bug fix rounds we
will be able to release 1.3. After that I'm sure that it will be a high
priority item.
Vedovato Paolo wrote:
Could this taglib performance
ww: current cvs version
app server: wls7.0sp1, orion 1.6.0
using ww:include page=../navigation/header.jsp / fails with following
stacktraces:
orion:
--
javax.servlet.jsp.JspTagException: javax.servlet.ServletException: Not a
valid resource path:/html/access/navigation/header.jsp
at
Paolo,
Could you add the URL you used and your directory structure to this bug
report?
Thanks,
Maurice
Vedovato Paolo wrote:
ww: current cvs version
app server: wls7.0sp1, orion 1.6.0
using ww:include page=../navigation/header.jsp / fails with following
stacktraces:
orion:
--
sure...
after a successful login there's a redirect.jspa?url=welcome.jspa so the url
is
url: http://localhost/app/welcome.jspa and the input view is
/app/html/access/welcome.jsp
see action.xml:
action name=Login alias=login
view name=successredirect.jspa?url=welcome.jspa/view
/action
My two (or three) cents:
the names aren't very important right now, as this stuff is all post-1.3 for
now. My votes would be:
-out or print (ww:out value=foo/bar/)
-push (ww:push value=fooww:out value=bar//ww:push)
-set (ww:set value=foo/bar id=blah/ ww:out value=@blah/)
-Pat
You might well want to pull something off the value stack and put it into
the session or application scope?
-mike
On 13/11/02 9:41 AM, Toby Hede ([EMAIL PROTECTED]) penned the
words:
would the use of a general set also allow variables to be set in contexts
other then the pageContext? (as in
-out or print (ww:out value=foo/bar/)
-push (ww:push value=fooww:out value=bar//ww:push)
-set (ww:set value=foo/bar id=blah/ ww:out value=@blah/)
Yes - these are good names IMHO!
After reading lots of names, print, push and set all seem intuitively to
do
the right things?
Print a
Putting things in a generic scope is done by subclassing ValueStack.
Basically, ValueStack uses the method findInContext(String id) to look for
@foo. So the ServletDispatcher when it runs, registers ServletValueStack
in the ActionContext as _the_ ValueStack to use. Currently the code in
No, you are actually pushing a value on the stack. Look at the code in
PropertyTag. Also, you might want to take a look at ValueStack.findValue to
understand how values are found (there is no such thing as a root).
-Pat
- Original Message -
From: Erik Beeson [EMAIL PROTECTED]
To: [EMAIL
I have spent some time in both PropertyTag and VS sources and something
that has bugged me is this situation:
1: ww:property value=foo/bar
2: ww:property value=../far /
3: /ww:property
Line 2 doesn't print foo/far since foo and bar didn't get pushed to the
stack, just bar located in foo. Has
You're right:
1: ww:property value=foo/bar
2: ww:property value=../far /
3: /ww:property
is different than
1: ww:property value=foo
2: ww:property value=bar
3: ww:property value=../far /
4: /ww:property
5: /ww:property
So the question is: should moving down a path put elements on the
Nono, as I understand it set / takes the current object on top of the
value stack and puts it into the page context (pageContext.setAttribute()).
The ValueStack itself is always stored as a page context attribute :)
What I'm saying is you might want to take a variable OFF the stack, and then
set
17 matches
Mail list logo
