Oops. Meant to send it to the list.
-- Forwarded message --
To: Mike Kienenberger [EMAIL PROTECTED]
On 8/10/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 7/19/06, Hubert Rabago [EMAIL PROTECTED] wrote:
Is there a way to wrap all calls to methods called by h:something
Is there a way to wrap all calls to methods called by h:something
actionListener=/ attributes? Something like
ActionListener.processAction(ActionEvent) does for h:something
action=/ methods?
thanks,
Hubert
Is there a way to intercept any and all exceptions in JSF within its
lifecycle? When we searched for clues, the only ones we found were
handling errors using JSP error pages, after FacesServlet has
completed.
What we'd like to do is have one class handle all exceptions that our
managed beans
On 5/8/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 5/7/06, Hubert Rabago [EMAIL PROTECTED] wrote:
It's the documentation for this:
//This is an emulation of the action link being clicked.
hform[form+':'+target].value=form+':'+target;
I want to know how the author knew
On 5/5/06, Craig McClanahan [EMAIL PROTECTED] wrote:
My question actually isn't about an alternate way to do it, but rather
where is it stated that giving a particular hidden field some
particular value will result in some particular JSF behavior?
How did the author know that setting this
Anyone?
On 4/28/06, Hubert Rabago [EMAIL PROTECTED] wrote:
I was looking at the sample application in
http://www.jsftutorials.net/interface/jsf-popup.html.
In it, the author has this form:
h:form id=placeList
h:commandLink id=find action=showPlace value=/
/h:form
He has some Javascript
:
This wiki page contains some informations about JavaScript and Faces [1]
HTH,
Matthias
[1] http://wiki.apache.org/myfaces/JavascriptWithJavaServerFaces
On 4/29/06, Hubert Rabago [EMAIL PROTECTED] wrote:
I was looking at the sample application in
http://www.jsftutorials.net/interface/jsf
Sounds like a job for t:aliasBean [1]. Wrap your snippet with an
alias bean and you can change the backing bean being referenced in the
snippet.
Hubert
[1] http://myfaces.apache.org/tomahawk/aliasBean.html
If it's a large snippet, should it still be called a snippet? :)
On 5/3/06, Michael
I was looking at the sample application in
http://www.jsftutorials.net/interface/jsf-popup.html.
In it, the author has this form:
h:form id=placeList
h:commandLink id=find action=showPlace value=/
/h:form
He has some Javascript that essentially sets the value of the command
link equal to
On 4/19/06, Adam Winer [EMAIL PROTECTED] wrote:
And what if your custom validator needs an attribute other than those
specified in that one tag? That's a no go.
That's why I added the s:validatorVar tag. Your custom validator
can now have its own parameters.
On 4/19/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
validators into one tag. They should be in separate tags.
That's not a bad idea.
I'm not sure about this, but doesn't this describe the existing
Tomahawk validators (creditCard, email, regExp)?
yeah, there are separate tags
).
I wouldn't mind that.
Hubert
[1] http://www.themaninblue.com/writing/perspective/2005/10/05/form/form4.htm
On 4/19/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: Hubert Rabago [EMAIL PROTECTED]
On 4/19/06, Gary VanMatre wrote:
It'd be OK to have a convenience tag - like
On 4/14/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 4/14/06, Werner Punz [EMAIL PROTECTED] wrote:
I think what the original poster wanted was to have the entire form and
event handling based on get
If that is indeed what the original poster wanted, then I hope the original
poster will
On 4/14/06, Adam Winer [EMAIL PROTECTED] wrote:
On 4/14/06, Hubert Rabago [EMAIL PROTECTED] wrote:
Without something like NonFacesRequestServlet, the request goes
directly to the JSP and bypasses managed beans. That was my
understanding. Jacob says I'm wrong, and I was wondering
Ok, thanks. I just wanted to make sure I didn't miss something
obvious, or something not so obvious.
Oh wait a sec. How *would* you do it? I mean, what's a better way
than NonFacesRequestServlet? Can you explain to a noob like me, or
maybe point to me to a URL?
You say along the same lines
Adam,
Was this for me? I'm sorry, I can never tell because there's no
context. If it is, then yes, I know about the NonFacesRequestServlet
[1], and Shale's remoting support [2]. Both of those of course build
on the framework. I posed the question based on Jacob's statement
that seem to imply
If my page uses a data table, and that data table has command links or
other input controls in it, does that limit it to the request scope?
A teammate of mine says we can't switch certain beans to request scope
because it uses data tables and those will stop working if we do.
thanks,
Hubert
Jacob Hookom, in discussing JSF myths [1], claims that:
Also, JSF can handle GET requests just as easily as other frameworks.
Because of JSF's
managed bean (IoC container), you can do the same kinds of things as
you can with
WebWork -- from parameter assignment to backing beans. An example is
Sorry, typo.
I meant to ask: If my page uses a data table, and that data table has
command links or other input controls in it, does that limit it to the
*session* scope?
thanks,
Hubert
On 4/13/06, Hubert Rabago [EMAIL PROTECTED] wrote:
If my page uses a data table, and that data table has
Thanks, Adam, we'll try this out.
Hubert
On 4/13/06, Adam Brod [EMAIL PROTECTED] wrote:
Yes, you can use request-scoped backing beans with dataTable. I would
recommend that you use the t:saveState component to simplify your life.
See Action listeners and actions for my commands on
On 3/24/06, Werner Punz [EMAIL PROTECTED] wrote:
Greg Reddin wrote:
If you'/re starting from scratch with no knowledge of Tiles, I'd
recommend starting with Facelets or Clay. I have no experience with
either, but, as has been pointed out already, they are native JSF
technologies, whereas
On 3/24/06, Werner Punz [EMAIL PROTECTED] wrote:
You have to define the ajax call in the original renderer with a content
div or any other element content element, of the component and then
render the html in the ajax cycle, and
then on the html level replace the content holders inner html
, Shale Clay can work in a JSP mode.
On 3/24/06, Hubert Rabago [EMAIL PROTECTED] wrote:
On 3/24/06, Werner Punz [EMAIL PROTECTED] wrote:
Greg Reddin wrote:
If you'/re starting from scratch with no knowledge of Tiles, I'd
recommend starting with Facelets or Clay. I have no experience
almost didn't see it.
Thanks for this info. I guess I'll start bugging Gary now.
Hubert
On 3/24/06, Hubert Rabago [EMAIL PROTECTED] wrote:
From what I understand, Facelets doesn't work with JSP. Neither does
Clay. Are there alternatives to Tiles that I can use with JSF that
work with JSP
Take a look at http://wiki.apache.org/myfaces/InvokingJsfPagesWithStandardUrls
Hubert
On 3/23/06, Vladimir Coutinho [EMAIL PROTECTED] wrote:
How could I call a jsf page from a jsp page passing a property form a
backing bean?
--
Vladimir M Coutinho
You have to surround your plain HTML with f:verbatim tags.
t:div id=div1 rendered=false
f:verbatimBlah blah blah/f:verbatim
h:inputText id=it1 value=text/
/t:div
Hubert
On 3/23/06, Costa Basil [EMAIL PROTECTED] wrote:
If I have:
t:div id=div1 rendered=false
Blah blah blah
Actually I did finally get it to work. I used it in the filter I
described on http://marc.theaimsgroup.com/?l=myfaces-userm=114183050209635w=2
It turns out I was getting some conflicts because I had a nightly
build of Commons EL on my war's lib directory.
Hubert
On 3/14/06, Udo Schnurpfeil
Oh, and Thanks for responding, Udo!
Hubert
On 3/14/06, Hubert Rabago [EMAIL PROTECTED] wrote:
Actually I did finally get it to work. I used it in the filter I
described on
http://marc.theaimsgroup.com/?l=myfaces-userm=114183050209635w=2
It turns out I was getting some conflicts because I
I took a different approach. My filter calls methods which are
specifically written with the awareness that they will be called as a
non-faces request. The intention is to avoid confusion over what
state is available when the method is triggered. This would be useful
for URLs that can be
Can I do that? Is that means I have to rewrite all validator in My
Faces implementation?
Why rewrite? Reuse! Take a look at Shale's Commons Validator [1]
support. The messages are controlled by a properties file you can
customize, and you can even specify a unique message for a particular
I'm working on a servlet based on the code in NonFacesRequestServlet.
I read the example in
http://wiki.apache.org/myfaces/InvokingJsfPagesWithStandardUrls. At
the point where it says put your initialization stuff here it shows
using either a VariableResolver (VR) or a ValueBinding (VB) to
The correct mailing list subscription address is
[EMAIL PROTECTED] , without the s at the end of
user.
Hubert
On 1/11/06, xzuma [EMAIL PROTECTED] wrote:
I would appreciate the pointers to the resource to get started with
using Shale within JSF (I specifically am interested in dynamic
32 matches
Mail list logo
