Cannot subscribe to the list
Hi! i`m trying to subscribe to the user@shale.apache.org but i got as reply the following: Technical details of permanent failure: PERM_FAILURE: SMTP Error (state 12): 552 spam score (5.5) exceeded threshold
Re: Which AJAX JSF library is compatible with Shale
Hi! Ajax4Jsf is one of the most used ajax libraries for JSF. There a lot sample apps for ajax4jsf and Shale could be easy added there for sample projects. They have a feature called a4j:include and in my opinion it`ll fit very good to shale dialog. On 11/9/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 11/9/06, Alexandre Touret [EMAIL PROTECTED] wrote: Hello, I m trying to integrate some AJAX enabled JSF libraries with a shale application. I have already tested icefaces and ajax4jsf. Unfortunately, I encounter some troubles with the integration against shale .. Could you share more details about the problems you ran into? Do you know if there are any AJAX - JSF framework (free or not ) which is compatible with shale ? In addition to this question, I'd be interested in the reverse ... which frameworks do you think we (Shale developers) should focus on being compatible with? My intent is to focus on building sample and testing apps with these frameworks, and with a limited amount of time available, I'd like to focus on the ones people care the most about. Thanks in advance for your help! Regards, Alexandre Craig -- Seeing is believing
Re: Problem with Shale Token
Yes you`re right. If I want to show the escape button when only when token validation fails i can check for token message in PhaseListener before render response phase. On 11/9/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 11/9/06, Adrian Mitev [EMAIL PROTECTED] wrote: This was posted in the bug tracker [1]: Craig McClanahan [08/Nov/06 10:38 PM] * It is trivially simple for an application to provide an escape hatch when the user screws up ... create a Cancel button with immediate=true, and this action will get processed *before* Process Validations phase, and therefore will bypass the check performed by the Token component. What do you think about storing attribute in the request when the token validation fails that could help render the Cancel button (if no token error, no cancel button). This idea is certainly technically feasible, if you are willing to rely on an internal implementation detail of how the Token component actually saves its state. However, from a user interface design point of view, wouldn't you *always* want a way to exit in the middle of a wizard dialog that you entered by accident? I'd hate to tell users if you want to exit, just do a refresh so the cancel button shows up :-) Craig PS: There is a bunch of discussion about the token component, and how it should behave, on the bug report ... useful background for this conversation can be found at: http://issues.apache.org/struts/browse/SHALE-287 -- Seeing is believing -- Seeing is believing
Re: Problem with Shale Token
This was posted in the bug tracker [1]: Craig McClanahan [08/Nov/06 10:38 PM] * It is trivially simple for an application to provide an escape hatch when the user screws up ... create a Cancel button with immediate=true, and this action will get processed *before* Process Validations phase, and therefore will bypass the check performed by the Token component. What do you think about storing attribute in the request when the token validation fails that could help render the Cancel button (if no token error, no cancel button). -- Seeing is believing
Re: Problem with Shale Token
Its working if i add the token as last input component it works as
expected. I wrote a few words [1] for the token usage.
[1] http://wiki.apache.org/shale/Token
On 11/7/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi
I second that (Should still be on a wiki page too)
Hermod
-Original Message-
From: Torsten Krah [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 12:35 PM
To: user@shale.apache.org
Subject: RE: Problem with Shale Token
This would be sufficient but i would like to see it in the tlddoc too.
Torsten
Am Dienstag, den 07.11.2006, 06:29 -0500 schrieb
[EMAIL PROTECTED]:
Er, that's not javadoc - that's comments inside the method. If this was moved
to
the javadoc it would be sufficient IMHO.
Quoting [EMAIL PROTECTED]:
Hi
It does if you read the javadoc for org.apache.shale.component.Token in the
validate method:
/**
* pPerform superclass validations, then ensure that the specified
input
* value is acceptable at this point in time./p
*
* @param context codeFacesContext/code for the current request
*/
public void validate(FacesContext context) {
// If any of the other input components in this form triggered
// validation errors, we do NOT want to validate the token component
// here, because that would erase the saved token and prevent the
// subsequent valid resubmit from succeeding.
//
// WARNING - for this test to be successful, the token component
must
// be the last input component child of the parent form to be
// processed
if (context.getMaximumSeverity() != null) {
.
I think that maybe the wiki should mention this also though.
Hermod
-Original Message-
From: Torsten Krah [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 10:47 AM
To: user@shale.apache.org
Subject: Re: Problem with Shale Token
Ok its working.
I did not know until now - that it have to be the last component - i put
it everytime in the front, now it works - the documentation should maybe
tell that.
Torsten
Am Montag, den 06.11.2006, 23:49 -0800 schrieb Craig McClanahan:
On 11/6/06, Torsten Krah [EMAIL PROTECTED] wrote:
Token is broken for myfaces greater than 1.1.1.
Look there: http://issues.apache.org/struts/browse/SHALE-287
Torsten
Am Montag, den 06.11.2006, 13:52 +0200 schrieb Adrian Mitev:
Hi all! I have problem using s:token.
I have form with input fields and required=true. When i leave the
field empty, the page is redisplayed with error message. Then i fill
the field with some text and click on the submit button. There i get
error message from the token component. Any suggestions?
OK, I have done a bunch of further investigation of this problem,
including
a new test app (built against MyFaces 1.1.4 and the current trunk code of
Shale, equivalent to the 20061107 nightly build). As far as I can tell,
the
current code works correctly. I've attached the current version of the
test
application (shale-test-core.war) to the relevant bug report[1]. PLEASE
do
everything you can to cause this app to misbehave with regards to token
processing, so we can shake out any remaining problems. But, I assert,
the
problems with the token component in the Shale 1.0.3 release have been
repaired. If there are positive reports of lack of ability to break the
test app, or no comment at all for a few days, I'm going to close this
issue
as having been fixed.
Craig
[1] http://issues.apache.org/struts/browse/SHALE-287
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB NOR cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the anti virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
--
Seeing is believing
Problem with Shale Token
Hi all! I have problem using s:token. I have form with input fields and required=true. When i leave the field empty, the page is redisplayed with error message. Then i fill the field with some text and click on the submit button. There i get error message from the token component. Any suggestions? -- Seeing is believing
Dialog example web project
Is there sample web project showing how to use shale-dialog? -- Seeing is believing
Not receiving the e-mails from the mailing lists
I`m using gmail and not emails are stored in the Spam folder and i don't have filters. -- Seeing is believing
Shale book
Hi guys! These days i found in emule a pdf called struts-shale.pdf and there was the documentation from the web site. Is this auto generated and is it there something like that for the newest documentation of shale? -- Seeing is believing
Suggestion for AbstractFacesBean
Hi! Useful method for AbstractFacesBean also could be something like
public void gotoView(String viewName) {
if (viewName!= null) {
UIViewRoot newView =
getFacesContext().getApplication().getViewHandler().createView(getFacesContext(),
viewName);
getFacesContext().setViewRoot(viewName);
}
}
and
public void navigate(String fromView,String outcome) {
getFacesContext().getApplication().getNavigationHandler().handleNavigation(getFacesContext(),
fromView, outcome);
}
--
Seeing is believing
Re: Problems with shale-core
Maybe its good idea to provide an example for this feature in the demo web projects. -- Seeing is believing
Re: Suggestion for AbstractFacesBean
Sorry about the typo. I`ve wrote this code in gmail not in IDE :) -- Seeing is believing
Suggestion for AbstractFacesBean
Hi! It is a good idea to add method like addMessageFromBundle that
does something like this:
public void addMessageFromBundle(UIComponent component,String
bundleMessageKey) {
ResourceBundle bundle = null;
try {
bundle = ResourceBundle.getBundle(getFacesContext()
.getApplication().getMessageBundle());
String message = bundle.getString(bundleMessageKey);
error(componeng,message);
} catch (MissingResourceException e) {
e.printStackTrace();
}
}
--
Seeing is believing
Re: Shale Navigation Security... and ServletFilter
This is from http://jsffaq.com. Currentyle the site is down. I`ve
downloaded this article before.
---
Outside the Faces realm, for example in a filter or a servlet, when
the FacesContent.getCurrentInstance() returns null, you can use
FacesContextFactory to reach the FacesContext. This is a method that
allows you to do so:
// You need an inner class to be able to call FacesContext.setCurrentInstance
// since it's a protected method
private abstract static class InnerFacesContext extends FacesContext
{
protected static void setFacesContextAsCurrentInstance(FacesContext
facesContext) {
FacesContext.setCurrentInstance(facesContext);
}
}
private FacesContext getFacesContext(ServletRequest request,
ServletResponse response) {
// Try to get it first
FacesContext facesContext = FacesContext.getCurrentInstance();
if (facesContext != null) return facesContext;
FacesContextFactory contextFactory =
(FacesContextFactory)FactoryFinder.getFactory(FactoryFinder.FACES_CONTEXT_FACTORY);
LifecycleFactory lifecycleFactory =
(LifecycleFactory)FactoryFinder.getFactory(FactoryFinder.LIFECYCLE_FACTORY);
Lifecycle lifecycle =
lifecycleFactory.getLifecycle(LifecycleFactory.DEFAULT_LIFECYCLE);
// Either set a private member servletContext =
filterConfig.getServletContext();
// in you filter init() method or set it here like this:
// ServletContext servletContext =
((HttpServletRequest)request).getSession().getServletContext();
// Note that the above line would fail if you are using any other
protocol than http
// Doesn't set this instance as the current instance of
FacesContext.getCurrentInstance
facesContext = contextFactory.getFacesContext(servletContext,
request, response, lifecycle);
// Set using our inner class
InnerFacesContext.setFacesContextAsCurrentInstance(facesContext);
// set a new viewRoot, otherwise context.getViewRoot returns null
UIViewRoot view =
facesContext.getApplication().getViewHandler().createView(facesContext,
yourOwnID);
facesContext.setViewRoot(view);
return facesContext;
}
--
Seeing is believing
Re: Shale Navigation Security...
Could be the Application Manager useful when implementing authorization and authentication? -- Seeing is believing
Re: ViewController question
Hi again! I`m using Shale 1.0.2 (Alpha) downloaded from this url http://people.apache.org/dist/struts/shale/v1.0.2/ I substituted log.debug with System.out.println but the result is the same. - Seeing is believing
Question about ViewController
Declare your backing bean as a managed-bean, using a managed-bean-name value that can be mapped from the view identifier. (See DefaultViewControllerMapper for the details of the default mapping.) In nearly all circumstances, you will want the bean to be placed in request scope. In which xml should i define the managed-bean and the view its mapped to? -- Seeing is believing
