It would be a lot easier helping if you show us some configuration
files and code
Nils-H
On Sat, Apr 19, 2008 at 6:59 AM, aum strut <[EMAIL PROTECTED]> wrote:
> yes you are right
>
> not providing complete information in one mail is really not good
>
> i wil take this in to account in futur
i am not using Spring at all.here is the code for my configuration and
action class
my *Quotation.jsp page* by which i am adding data
<%@ taglib prefix="s" uri="/struts-tags" %>
Quotation Form
Quotation Form
*my action class*
package rai
Hi,
I have a tag ... but I would to show the
element of the list in different page.
Infact the list's elements are the result of a search in a SearchEngine so I
would have the links to page 1 2 3 4 5... and for each page I want view only x
results.
For example,if I have 100 results and I want
you can store in session and retrieve later using
http://struts.apache.org/2.0.11.1/docs/ognl-basics.html
- Original Message -
From: <[EMAIL PROTECTED]>
To: "struts mailing list"
Sent: Saturday, April 19, 2008 7:24 AM
Subject: result in different pages
Hi,
I have a tag ... but I would t
Hi,
how can I show up a colored message when doing
declarative validation via xml file.
I tried to surround the message text by a div, but
then the messages werent shown any longer:
>>>
You must enter your fistname.
<<<
Therefore, I dont know how to color that output string.
Can anyone help me?
From looking at the struts2 architecture, one of the big questions that I can't
find the answer to is how struts/xwork moves objects such as the properties on
an action into the PageContext.
When an interceptor is executing for example, calling
ServletActionContext.getPageContext() will return
Well it depends if you are ALWAYS developing using the same library
versions or not.
Be aware that Struts level of compatibility changes from version to
version: For example, from 2.09 to 2.0.11 imposes several constraints
in its tag library, so you may want to prevent this to be in a common
place.
Hello Adam
On Sat, Apr 19, 2008 at 7:29 PM, Adam Hardy
<[EMAIL PROTECTED]> wrote:
> From looking at the struts2 architecture, one of the big questions that I
> can't find the answer to is how struts/xwork moves objects such as the
> properties on an action into the PageContext.
Actually it's not
Hi konference
I read the article there:
http://struts.apache.org/2.0.9/docs/scope-interceptor.html
and a want use scope interceptor, but it not work my. I dont know exactly,
that i good understand it.
I want save into session model: Employee.
//
In my Action Class I
Ralf Fischer on 19/04/08 18:43, wrote:
On Sat, Apr 19, 2008 at 7:29 PM, Adam Hardy
<[EMAIL PROTECTED]> wrote:
From looking at the struts2 architecture, one of the big questions that I
can't find the answer to is how struts/xwork moves objects such as the
properties on an action into the PageCont
--- Adam Hardy <[EMAIL PROTECTED]> wrote:
> The struts interceptors encompass both the actions and the results, but how
> does struts put the action properties into the pageContext?
It doesn't; it puts the action on the stack. The tags use OGNL to get values
from the stack context, or when using J
Dave Newton on 19/04/08 23:54, wrote:
--- Adam Hardy <[EMAIL PROTECTED]> wrote:
The struts interceptors encompass both the actions and the results, but how
does struts put the action properties into the pageContext?
It doesn't; it puts the action on the stack. The tags use OGNL to get values
f
--- Adam Hardy <[EMAIL PROTECTED]> wrote:
> So you say the StrutsRequestWrapper holds the struts context [...]
No, I'm saying it has access to it via ActionContext.getContext().
> and is accessed somewhere in the Result to pull everything down
> into the PageContext?
I'm not sure what that mea
Dave Newton on 20/04/08 00:23, wrote:
--- Adam Hardy <[EMAIL PROTECTED]> wrote:
So you say the StrutsRequestWrapper holds the struts context [...]
No, I'm saying it has access to it via ActionContext.getContext().
and is accessed somewhere in the Result to pull everything down
into the Page
--- Adam Hardy <[EMAIL PROTECTED]> wrote:
> What you're saying is clear except one thing - in JSTL I can access the
> action. And in JSTL, I'm not calling request.getAttribute() - I'm _not_
doing this:
>
> ${requestScope['myObject']}
>
> I'm just doing this:
>
> ${myObject}
>
> and struts someh
ServletContext attributes 'foo'
#application['foo'] or #application.foo
Access to PageContext for attribute foo
#attr['foo'] or #attr.foo
in WebWork 1.x one could access special named objects (the request scope
attributes to be exact) by using "@foo",
but now special variables are accessed u
16 matches
Mail list logo
