Re: How to call a method in the backing bean from a JSF page
I am not sure if this is the best way, but one idea that could work is
to create a PhaseListener that acts after the view is restored. In
this phase listener, you could check if the view being restored is the
view for which you want to call your backing bean method. Then, you
could obtain a MessageBinding object for your backing bean expression
and use that to call your method.
Create YourPhaseListener and register it in faces-config.xml:
faces-config
...
lifecycle
phase-listenercom.yourcompany.YourPhaseListener/phase-listener
/lifecycle
/faces-config
public class YourPhaseListener implements PhaseListener {
public void beforePhase(PhaseEvent event) {
// Nothing to do
}
public void afterPhase(PhaseEvent event) {
FacesContext facesContext = event.getFacesContext();
UIViewRoot viewRoot = facesContext.getViewRoot();
String idOfYourPage = ...
if (viewRoot.getId().equals(idOfYourPage)) {
Application application = facesContext.getApplication();
String methodExpression = ...
Class[] params = ...
MethodBinding methodBinding =
application.getMessageBinding(methodExpression, params);
methodBinding.invoke(facesContext, ...);
}
public PhaseId getPhaseId() {
return PhaseId.RESTORE_VIEW;
}
}
Disclaimer: I haven't tried this code so I don't know if it would work
or even compile.
-Ken
On 8/24/05, Saul Qunming Yuan [EMAIL PROTECTED] wrote:
Thanks for your response. I guess I didn't make me clear here. My question
is how to call a method in the backing bean from a JSF page without
rendering out anything to the screen.
Re: confusion on best practices in regard to a VO in BackingBean
thats right I believe Slawek was referring to Rick Hightower. On 8/24/05, Rick Reumann [EMAIL PROTECTED] wrote: On 8/24/05, Slawek [EMAIL PROTECTED] wrote: but Rick says in his article that: view is only jsp page, controler is backing bean and model has business logic I take it by article you mean 'e-mail post' ? I don't think I posted any comments on JSF architecture since I obviously am just learning it myself. -- Rick
Re: How to call a method in the backing bean from a JSF page
but remember that getter may be called few times!
i assume that in order to see your page user must click sth (ex.
somme kind of menu) and i assume that u have action binded to that
click that returs string maped to desired page. so just add call
your method in that action.
Słąwek Sobótka
Thanks for your reply, that makes sense. But won't h:commandLink
render a
link and h:commandButton render a button in the page? I don't want to
display anything on the screen. My purpose is to initiate a call
from the
JSF page to a method in the backing bean when the JSF page loads. I'm
returning an empty string from the method so nothing gets printed
out from
h:outputText.
- Original Message -
From: Ken [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Wednesday, August 24, 2005 9:53 PM
Subject: Re: How to call a method in the backing bean from a JSF page
Try h:commandLink or h:commandButton.
If your method returns a string that doesn't match any
navigation-rule
in your faces-confix.xml then the same page you came from will be
rendered again.
On 8/24/05, Saul Qunming Yuan [EMAIL PROTECTED] wrote:
Hi,
I'm wondering what's the correct way to call a method in the
backing bean
from a JSF page. What I tried is to use h:outputText
value=#{theBackingBean.theMethod} /, the backing bean method
returns
an
empty string, so nothing gets printed out in the page. Which
works, but I
am
not sure this is the correct way to do it.
thanks,
Saul
Render an element whithout reload
Hi everybody, I'd like to know if it's possible to render or not a component (panel for exemple) whitout reloading the page. Like a span and javascript in html for example... Thank's a lot.
Re: Render an element whithout reload
Thank you for your help, but it looks me a little complicated to install for something so simple and basic even if it seems to be very performant. Isn't there any else solution more easy to do this ? Thank's - Original Message - From: Kołoszko Paweł [EMAIL PROTECTED] To: 'MyFaces Discussion' users@myfaces.apache.org Sent: Thursday, August 25, 2005 9:04 AM Subject: RE: Render an element whithout reload Try AJAX. See http://wiki.apache.org/myfaces/AJAX_Framework PK -Original Message- From: Nicolas GENSOLLEN [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 8:56 AM To: MyFaces Discussion Subject: Render an element whithout reload Hi everybody, I'd like to know if it's possible to render or not a component (panel for exemple) whitout reloading the page. Like a span and javascript in html for example... Thank's a lot.
Re: Bypassing validation while still preserving values
Hi Richard, I've been reading your post, but I think I'm missing something... If you set immediate=false, then only two phases will be executed: 1) Restore view 2) Apply request values so, as you correctly say, the model will not be updated, as the Update Model phase is not invoked. But AFAIK one thing is the component and another is the model. I mean, the component must be always updated independently of the value for the immediate attribute, so I don't understand why you loose your component values between requests (maybe it's just a matter of scope, and not really the immediate attribute). Just my 2 cents ;-)2005/8/24, Richard Wallace [EMAIL PROTECTED]: James Reynolds wrote:Ooo! I know this one!I lean heavily on the Core JSF book by Geary Horstmann, there is somegood info on this in the page life cycle in Chapter 7.Specifically, the Immediate Components information on page 292.As you mentioned, theimmediate attribute must be set to true for your components.Theportion I tripped up on was adding context.renderResponse (); at theend of my ValueChangeEvent code for the valueChangeListener.Then, themodel maintained the previous state of my page without firingvalidation.The problem with that is that then the model doesn't get updated when the command link is clicked so on the page they get directed to can'tpreserve the model info cause it was never updated.The situation Ihave in mind is something like:The user loads the page.They enter some contact info.They click on one of the command links.The contact info shouldn't be validated butthe model values should be udpated.If you look at the lifecycle thevalidation occurs before updating the model values.And immediate event handling gets handled before validation.So, if I set the immediateattribute to true it will forward to the quick add page beforevalidating the data or updating the model.So t:saveState will be preserving old information, not the latest info the user entered.JR-Original Message-From: Richard Wallace [mailto:[EMAIL PROTECTED] ]Sent: Wednesday, August 24, 2005 10:14 AMTo: MyFaces DiscussionSubject: Bypassing validation while still preserving valuesHey everyone,I've got a form that has a couple of optional command links on it.They are basically quick add buttons so a user can quickly add things todrop downs if they aren't there.When these quick add buttons areclicked the user is sent to an add page, the user enters the new info and is then redirected back to the original page where the new entry isselected and all the other data is preserved from before they clickedthe quick add button.The backing beans involved are request scoped and the values filled in before clicking the quick add button arepreserved through the process using the t:saveState element.I'm trying to get the validation correct. I want all the form elements to be required when the user clicks the submit button, but when they hitthe quick add link the validation should be bypassed. I thought ofdoing this with the immediate attribute set to true on the quick add command links but if I do that then any data the user entered on thatpage load (contact info type stuff) is lost.So I kind of need tobypass the validation but still update the model values if one of the command links are clicked, but have full validation done when thecommand button is pressed.I was looking at the new OptionalValidation Framework but I'm not sureexactly how to apply it in this case.I mean, what I really want is to have the validation type be none when command links are used and hardotherwise.Any ideas?Thanks,Rich
Re: Spanish accents in Javascript
Thanks. Let me try it ;-)2005/8/25, Matt Blum [EMAIL PROTECTED]:
I understand that. I'm suggesting that, instead of La fórmula es correcta in your properties file, you put La f\u00f3rmula es correcta.
-MattOn 8/24/05, Enrique Medina [EMAIL PROTECTED]
wrote:
Hi Matt,
But the problem is that encoding is generated by JSF when using EL like this:
#{messages.literal1}2005/8/24, Matt Blum [EMAIL PROTECTED]:
You need to use the Unicode encoding for the character, like so:
La f\u00f3rmula es correcta
There's a handy online tool to find the codes for most special characters here:
http://www.saila.com/usage/tips/examples/special_characters.html
-MattOn 8/24/05, Enrique Medina
[EMAIL PROTECTED]
wrote:Hi,
I know this is not a question directly related with MyFaces, but does anybody knows how to solve this problem?
I define my literal strings in a properties file, and then I have
created a custom messages tag that renders the message as an alert of
_javascript_. So when a JSF message is generated, it is rendered as an
alert. My problem is with accents. For example, in the alert window the
text appears like:
La f#243;rmula es correcta
while it should be:
La fórmula es correcta
Is it a matter of escaping the text in _javascript_? Because I have tried the escape() function but with no success...
Re: How to get a look at tobago
Hello! We have set up a public Subversion repository recently at: http://www.atanion.net/repos/asf/tobago/trunk/ Browsing the repository currently doesn't seem to work with IDEA. So you may have to check out manually via svn co http://www.atanion.net/repos/asf/tobago/trunk/ tobago To compile Tobago you need Java 5 and Ant 1.6.5. Just run ant install in the root directory. Afterwards you may want to build one of the examples. Change the directory to example/demo and run ant war There is a readme.txt (http://www.atanion.net/repos/asf/tobago/trunk/readme.txt) in the main directory which summarizes these steps. We also started to generate a web site with Maven 2 to make this kind of information easier to access. But it is not deployed yet... Regards, Arvid Solgrims wrote: Hi, is there a way to access the tobago repository? And if so: what do I need to build tobago? Regards, Stefan Hedtfeld.
AW: AW: AW: problem with JSCookMenu
Hi! It seems that the Sun ONE Appserver doesn't find the resources JSCookMenu.js, MyFacesHack.js, theme.js, theme.css. At the AppServer there's no faces dir and subdirs(the server log is at the end of the mail). After creating the dirs and copying the files into the dirs it works. QUESTION: Is there another way to use jscookmenu in Sun JSF with MyFaces Extension without this awful workaround??? Thx Stefan Gesigora Here's a snip of the server log: [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/JSCookMenu.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/JSCookMenu.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/MyFacesHack.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/MyFacesHack.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.css, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.css (File not found) -Ursprüngliche Nachricht- Von: Helmut Juskewycz [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 24. August 2005 17:49 An: MyFaces Discussion Betreff: Re: AW: AW: problem with JSCookMenu -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hmm i think this is what u need but i not sure: add the extension filter to the web.xml !-- Extensions Filter -- filter filter-nameextensionsFilter/filter-name filter-classorg.apache.myfaces.component.html.util.ExtensionsFilter/filter-class init-param param-nameuploadMaxFileSize/param-name param-value100m/param-value descriptionSet the size limit for uploaded files. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB /description /init-param init-param param-nameuploadThresholdSize/param-name param-value100k/param-value descriptionSet the threshold size - files below this limit are stored in memory, files above this limit are stored on disk. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB /description /init-param !--init-param param-nameuploadRepositoryPath/param-name param-value/temp/param-value descriptionSet the path where the intermediary files will be stored. /description /init-param-- /filter filter-mapping filter-nameextensionsFilter/filter-name url-pattern*.jsf/url-pattern /filter-mapping filter-mapping filter-nameextensionsFilter/filter-name url-pattern/faces/*/url-pattern /filter-mapping Stefan Gesigora wrote: Thanks Helmut for your description! But I can't take the web.xml of the simple example cause I'm using Sun JSF with MyFaces Extension!! I've tried to put some elements of the web.xml of the simple example to my web.xml: org.apache.myfaces.ALLOW_JAVASCRIPT org.apache.myfaces.DETECT_JAVASCRIPT org.apache.myfaces.PRETTY_HTML org.apache.myfaces.AUTO_SCROLL But no jscookmenu were shown (with the nightly build and the modified web.xml!) Any suggestions? Stefan Gesigora -Ursprüngliche Nachricht- Von: Helmut Juskewycz [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 24. August 2005 15:08 An: MyFaces Discussion Betreff: Re: AW: problem with JSCookMenu yes that means you didnt install jscookmenu correct. i told you before that you can define it in the head and so on but when you install the jscookmenu correctly then all works fine. Here again how i did it (i hope i make no mistakes) first: look at your web.xml (take the web.xml from the simple
Re: AW: AW: problem with JSCookMenu
Your question was already answered ;) you need to add this section to the web.xml file - no matter if you use MyFaces or the RI: !-- Extensions Filter -- filter filter-nameextensionsFilter/filter-name filter-classorg.apache.myfaces.component.html.util.ExtensionsFilter/filter-class init-param param-nameuploadMaxFileSize/param-name param-value100m/param-value descriptionSet the size limit for uploaded files. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB /description /init-param init-param param-nameuploadThresholdSize/param-name param-value100k/param-value descriptionSet the threshold size - files below this limit are stored in memory, files above this limit are stored on disk. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB /description /init-param !--init-param param-nameuploadRepositoryPath/param-name param-value/temp/param-value descriptionSet the path where the intermediary files will be stored. /description /init-param-- /filter filter-mapping filter-nameextensionsFilter/filter-name url-pattern*.jsf/url-pattern /filter-mapping filter-mapping filter-nameextensionsFilter/filter-name url-pattern/faces/*/url-pattern /filter-mapping regards, Martin On 8/25/05, Stefan Gesigora [EMAIL PROTECTED] wrote: Hi! It seems that the Sun ONE Appserver doesn't find the resources JSCookMenu.js, MyFacesHack.js, theme.js, theme.css. At the AppServer there's no faces dir and subdirs(the server log is at the end of the mail). After creating the dirs and copying the files into the dirs it works. QUESTION: Is there another way to use jscookmenu in Sun JSF with MyFaces Extension without this awful workaround??? Thx Stefan Gesigora Here's a snip of the server log: [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/JSCookMenu.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/JSCookMenu.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/MyFacesHack.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/MyFacesHack.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.css, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.css (File not found) -Ursprüngliche Nachricht- Von: Helmut Juskewycz [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 24. August 2005 17:49 An: MyFaces Discussion Betreff: Re: AW: AW: problem with JSCookMenu -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hmm i think this is what u need but i not sure: add the extension filter to the web.xml !-- Extensions Filter -- filter filter-nameextensionsFilter/filter-name filter-classorg.apache.myfaces.component.html.util.ExtensionsFilter/filter-class init-param param-nameuploadMaxFileSize/param-name param-value100m/param-value descriptionSet the size limit for uploaded files. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB /description /init-param init-param param-nameuploadThresholdSize/param-name param-value100k/param-value descriptionSet the threshold size - files below this limit are stored in memory, files above
AW: AW: AW: problem with JSCookMenu
Hi! Okay I'm sorry you're right. It works after undeploying and deploying again BUT my jsp is in the following dir: /web/jsps/common/index.jsp The jscookmenu is shown except the pics. The AppServer doesn't find these pics with these paths: /web/jsps/common/jscookmenu/ThemeOffice/spacer.gif /web/jsps/common/jscookmenu/ThemeOffice/blank.gif How can I configure myfaces that it works in this configuration? Stefan Gesigora -Ursprüngliche Nachricht- Von: Martin Marinschek [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 25. August 2005 10:03 An: MyFaces Discussion Betreff: Re: AW: AW: problem with JSCookMenu Your question was already answered ;) you need to add this section to the web.xml file - no matter if you use MyFaces or the RI: !-- Extensions Filter -- filter filter-nameextensionsFilter/filter-name filter-classorg.apache.myfaces.component.html.util.ExtensionsFilter/filter-class init-param param-nameuploadMaxFileSize/param-name param-value100m/param-value descriptionSet the size limit for uploaded files. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB /description /init-param init-param param-nameuploadThresholdSize/param-name param-value100k/param-value descriptionSet the threshold size - files below this limit are stored in memory, files above this limit are stored on disk. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB /description /init-param !--init-param param-nameuploadRepositoryPath/param-name param-value/temp/param-value descriptionSet the path where the intermediary files will be stored. /description /init-param-- /filter filter-mapping filter-nameextensionsFilter/filter-name url-pattern*.jsf/url-pattern /filter-mapping filter-mapping filter-nameextensionsFilter/filter-name url-pattern/faces/*/url-pattern /filter-mapping regards, Martin On 8/25/05, Stefan Gesigora [EMAIL PROTECTED] wrote: Hi! It seems that the Sun ONE Appserver doesn't find the resources JSCookMenu.js, MyFacesHack.js, theme.js, theme.css. At the AppServer there's no faces dir and subdirs(the server log is at the end of the mail). After creating the dirs and copying the files into the dirs it works. QUESTION: Is there another way to use jscookmenu in Sun JSF with MyFaces Extension without this awful workaround??? Thx Stefan Gesigora Here's a snip of the server log: [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/JSCookMenu.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/JSCookMenu.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/MyFacesHack.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/MyFacesHack.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.js, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.js (File not found) [25/Aug/2005:09:37:04] WARNING ( 4088): for host 127.0.0.1 trying to GET /web/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.css, send-file reports: HTTP4142: can't find C:/Sun/AppServer7/domains/domain1/server2/applications/j2ee-modules/web_1/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11248525/ThemeOffice/theme.css (File not found) -Ursprüngliche Nachricht- Von: Helmut Juskewycz [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 24. August 2005 17:49 An: MyFaces Discussion Betreff: Re: AW: AW: problem with JSCookMenu -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hmm i think this is what u need but i not sure: add the extension filter to the web.xml !-- Extensions Filter -- filter filter-nameextensionsFilter/filter-name
Antwort: Re: Bypassing validation while still preserving values
What about immediate=true on the input component?
Antwort: Re: Re: Redirect Tree2 _restoredState
Well its more a ugly hack than a solution, but as long as there are no methods for that in the TreeModel you could mimic the behaviour with customized code form the expandAll() and expandEverything() methods of UITreeData in your backing bean getter method that supplies the TreeModel.
Antwort: Tree2 and actionListeners
Hmm, strange. Are you sure that this is a tree2 specific problem? AFAIK the recent changes in the tree2 should not influence the behaviour of a commandLink. Is the actionListener called at all? Can you determine the phase in which this happens? Does the commandLink behave normally when it is outside of the tree? Do you use input components to display your data (in the dataTable)? [EMAIL PROTECTED] schrieb am 23.08.2005 15:05:18: Hi, Just got the 20050822 build and I have problems with my app (I did not have this problem with the 20050802 build). The problem is as follows. I have a tree2 where each item is a commandLink (with immediate set to true) with an actionListener. A click on a tree item should trigger the repopulation of a dataTable as well as the update of values in other components. Until today this all worked as the actionListener was triggered before the repopulation phase. However with this new build it looks like the immediate attribute is not taken into account, i.e. the repopulation phase in my app is triggered before the event handling Is that a bug or am I doing something wrong? Thanks for your help, Emmanuel
Re: How to call a method in the backing bean from a JSF page
Hi, i think you are looking for somthing like a PhaseListener. You can configure such a Listener in faces.xml. make your listener to return javax.faces.event.PhaseId.RENDER_RESPONSE in getPhaseId() method and the beforePhase() method of your listener is invoked just before rendering. Saul Qunming Yuan wrote: I see. The outputText way is actually what I did. So, is there a way to call a method in the backing bean when/before loading a JSF page? Something like a pre-render method before loading a JSF page? I can do that in the backing bean methods that forward to the JSF page, but there are many places that could forward to that JSF page. That's why I trying to do it in the JSF page itself. thanks -- Don't answer to From: address! Mail to this account are droped if not recieved via mailinglist. To contact me direct create the mail address by concatenating my forename to my senders domain.
Re: RE : RE : RE : inputSuggest : some others improvement to do
Matt Blum wrote: I'm not exactly sure what you mean. The z-index of the suggestion div is set to 100, IIRC. I should probably change that so it's settable via a style sheet, but no matter. The z-index of the iframe is supposed to be programmatically set to that of the suggestion div minus 1, as you say. I am not exactly sure, but I recall vaguely that there was another IE bug (probably number 10.000 or so in this absymality of a browser) regarding a zIndex of 100 try to set it to 99 and check out if it fixes the bug...
Re: Spanish accents in Javascript
I have tried to define my properties file (resource bundle) using Unicode encodings:
combiVariables_ValidacionOK = La f\u00F3rmula es correcta
combiVariables_ValidacionNotOK = La f\u00F3rmula no es correcta
But it still doesn't work :-(2005/8/25, Enrique Medina [EMAIL PROTECTED]:
Thanks. Let me try it ;-)2005/8/25, Matt Blum [EMAIL PROTECTED]:
I understand that. I'm suggesting that, instead of La fórmula es correcta in your properties file, you put La f\u00f3rmula es correcta.
-MattOn 8/24/05, Enrique Medina [EMAIL PROTECTED]
wrote:
Hi Matt,
But the problem is that encoding is generated by JSF when using EL like this:
#{messages.literal1}2005/8/24, Matt Blum [EMAIL PROTECTED]:
You need to use the Unicode encoding for the character, like so:
La f\u00f3rmula es correcta
There's a handy online tool to find the codes for most special characters here:
http://www.saila.com/usage/tips/examples/special_characters.html
-MattOn 8/24/05, Enrique Medina
[EMAIL PROTECTED]
wrote:Hi,
I know this is not a question directly related with MyFaces, but does anybody knows how to solve this problem?
I define my literal strings in a properties file, and then I have
created a custom messages tag that renders the message as an alert of
_javascript_. So when a JSF message is generated, it is rendered as an
alert. My problem is with accents. For example, in the alert window the
text appears like:
La f#243;rmula es correcta
while it should be:
La fórmula es correcta
Is it a matter of escaping the text in _javascript_? Because I have tried the escape() function but with no success...
ERROR HtmlRenderKitImpl:145 - ContentTypeList does not contain a supported content type: multipart/form-data;
Hi All,
We have a JSF Page (main.jsf) which
has a h:form tag and it includes another JSF
page for uploading images as a subview.
When we execute main.jsf we get the
following error . We are using the latest nightly build of myfaces.
ERROR HtmlRenderKitImpl:145
- ContentTypeList does not contain a supported content type: multipart/form-data;
boundary=---7d52ca28a104c0
Main.jsf
h:form
id=styleForm
enctype=multipart/form-data
h:selectOneMenu styleClass=selectBox
id=type value=#{StyleJSP.style.type} required=true
immediate=true
valueChangeListener=#{StyleJSP.styleTypeChange}
f:selectItem
itemValue= itemLabel=#{Message.empty_select_item}
/
/h:selectOneMenu
f:subview
id=style6
c:if
test=${StyleJSP.style.type
== 'MARKER'}
jsp:include
page=/upload.jsp
/
/c:if
/f:subview
/h:form
Thanks and Warm Regards,
Debasish Sahu
Re: ERROR HtmlRenderKitImpl:145 - ContentTypeList does not contain a supported content type: multipart/form-data;
This really isn't an error.
We send text/html back as a content-type in this case anyways.
I will check and get rid of that error message.
regards,
Martin
On 8/25/05, Debasish Sahu [EMAIL PROTECTED] wrote:
Hi All,
We have a JSF Page (main.jsf) which has a h:form tag and it includes
another JSF page for uploading images as a subview.
When we execute main.jsf we get the following error . We are using the
latest nightly build of myfaces.
ERROR HtmlRenderKitImpl:145 - ContentTypeList does not contain a supported
content type: multipart/form-data;
boundary=---7d52ca28a104c0
Main.jsf
h:form id=styleForm enctype=multipart/form-data
h:selectOneMenu styleClass=selectBox id=type
value=#{StyleJSP.style.type} required=true immediate=true
onchange=submit();
valueChangeListener=#{StyleJSP.styleTypeChange}
f:selectItem itemValue=
itemLabel=#{Message.empty_select_item} /
/h:selectOneMenu
f:subview id=style6
c:if test=${StyleJSP.style.type == 'MARKER'}
jsp:include page=/upload.jsp /
/c:if
/f:subview
/h:form
Thanks and Warm Regards,
Debasish Sahu
--
http://www.irian.at
Your JSF powerhouse -
JSF Trainings in English and German
Re: AW: AW: AW: problem with JSCookMenu
Hello, The jscookmenu is shown except the pics. The AppServer doesn't find these pics with these paths: Are you sure it is the fault of the appserver? I have deployed the myfaces example simple.war to a tomcat5.5.9 After starting the container and going to http://localhost:8080/simple with different browsers i got different results. With opera8.1 all is displayed as it should. But with IE6.0 i see the crosses like you. It seems that the javascript is not portabel between browsers. Ciao, Carsten Höhne
Re: Does a doc exist describing the MyFaces features?
A guide with examples of the JSF code, rendered output, and HTML output is here: http://www.exadel.com/tutorial/jsf/jsftags-guide.html It only covers the standard JSF tags Sean Schofield wrote: We're getting there. The simple examples are also a very good show by example approach to learning about the components. We're trying to establish some documentation standards for new components but we have some catching up to do with the old stuff. sean On 8/24/05, Martin Marinschek [EMAIL PROTECTED] wrote: another one: http://myfaces.apache.org/tomahawk/overview.html http://myfaces.apache.org/sandbox/overview.html but there is no comprehensive doc or pdf. regards, Martin On 8/24/05, Dave Brondsema [EMAIL PROTECTED] wrote: Also see the TLD links on http://myfaces.apache.org/javadoc.html Balaji Saranathan wrote: This URL lists various components and features of MyFaces. http://wiki.apache.org/myfaces/ -Original Message- *From:* Rick Reumann [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, August 24, 2005 2:37 PM *To:* MyFaces Discussion *Subject:* Does a doc exist describing the MyFaces features? Someone mentioned using x:dataList in place of JSTL for each. I'm curious, is there a document that shows a list of all the different features MyFaces supplies? I know the MyFaces example app shows a lot (maybe all?), but it would be nice to see all these features and a quick example of usage in a single pdf or doc. (Trust me not complaining if one doesn't exist, was just curious if there was one floating around somewhere). Thanks. -- Rick Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. -- Dave Brondsema Software Developer Cornerstone University -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German -- Dave Brondsema Software Developer Cornerstone University signature.asc Description: OpenPGP digital signature
RE : RE : inputSuggest : some others improvement to do
Title: Message What about the #3 problem ? Is it really the expected behaviour of this component ? Thanks Clément -Message d'origine-De: Clément Maignien Envoyé: mercredi 24 août 2005 11:34À: MyFaces DiscussionObjet: RE : inputSuggest : some others improvement to do Hummm, sorry, the #2 issue is a mistake : I have another page with an inputSuggest with manyitems into and the white space isn't there. So I'm asking why it is displayed on my other page and disappier when I don't addthe inputSuggestin the page ... wierd ... Bye, Clément. -Message d'origine-De: Clément Maignien Envoyé: mercredi 24 août 2005 10:37À: MyFaces DiscussionObjet: s:inputSuggest : some others improvement to do I've noticed some more improvements to make on this sandbox component. I don't know if they really comes from the component itself but I here they are : 1- I have a small JSF page with an s:inputSuggest component and an t:inputDate component under it. When clicking inside the inputSuggest a dropdown box open and displays firsts suggests. The problem is that under IE (not Firefox) the dropdown-box is displayed behind the inputDate, hiding some suggests. 2- It also seems that under Firefox (not IE), the page vertical lenght is increaseddepending on the number of items in the inputSuggest. A white space is displayed under the last element of the page. In my case I try to avoid the use of the page scroller in my webapp pages, and now there is a scroller displayed because of this big white space. Are those problems come from the browsers or the component implementation ? 3- When you click inside the inputSuggest and then click outside without typing anything or choosing an item, I get a value of "-1" in the model. In fact, a new suggest is added to the component with an empty stringas label and -1 as value. Is this the expected behaviour of the inputSuggest component ? Thx, Clément.
Setting error page
Title: Message Hi, I would like to know how to set a JSFerror page that will be displayed instead of the default Tomcat one. Is it possible to redirect the navigation to a specific page when the user session times out ? Thx. Clément
outputText for abbr. text with ellipsis
Hej In some columns of datatables I would like to abbreviate the text when the text has more than x characters. Right now I have a special getter in the beans to return an abbreviated string of a hardcoded length ( str.substring(0,abbreviationLength - 2) + \u2026;). I do not like this, because the length should be configured in the jsf-file by the page-designer. = Does someone know of a JSF-component like h:outputText, which has this feature of abbreviating a text with ellipses? OR is there an obvious way to do this? Thanks ... Rick
Re: Setting error page
Hi, look at Core Java Server Faces - Chapter 12 - How do I customize error pages. Chapter 12 is available online on amazon (under product details) http://www.amazon.com/exec/obidos/tg/detail/-/0131463055/104-2329112-1121569 source code at http://www.horstmann.com/corejsf/ Jozef Clément Maignien wrote: Hi, I would like to know how to set a JSF error page that will be displayed instead of the default Tomcat one. Is it possible to redirect the navigation to a specific page when the user session times out ? Thx. Clément ** __ Informacia od NOD32 1.1201 (20050825) __ Tato sprava bola preverena antivirusovym systemom NOD32. http://www.eset.sk __ Informacia od NOD32 1.1201 (20050825) __ Tato sprava bola preverena antivirusovym systemom NOD32. http://www.eset.sk
Re: Re: Re: Redirect Tree2 _restoredState
What about adding a phase listener to expand the nodes just before rendering? Or as I have suggested before, Shale's prerender method? sean On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well its more a ugly hack than a solution, but as long as there are no methods for that in the TreeModel you could mimic the behaviour with customized code form the expandAll() and expandEverything() methods of UITreeData in your backing bean getter method that supplies the TreeModel.
Re: Spanish accents in Javascript
What does it do now? The same thing as before?
-MattOn 8/25/05, Enrique Medina [EMAIL PROTECTED] wrote:
I have tried to define my properties file (resource bundle) using Unicode encodings:
combiVariables_ValidacionOK = La f\u00F3rmula es correcta
combiVariables_ValidacionNotOK = La f\u00F3rmula no es correcta
But it still doesn't work :-(2005/8/25, Enrique Medina [EMAIL PROTECTED]
:
Thanks. Let me try it ;-)2005/8/25, Matt Blum [EMAIL PROTECTED]:
I understand that. I'm suggesting that, instead of La fórmula es correcta in your properties file, you put La f\u00f3rmula es correcta.
-MattOn 8/24/05, Enrique Medina [EMAIL PROTECTED]
wrote:
Hi Matt,
But the problem is that encoding is generated by JSF when using EL like this:
#{messages.literal1}2005/8/24, Matt Blum [EMAIL PROTECTED]:
You need to use the Unicode encoding for the character, like so:
La f\u00f3rmula es correcta
There's a handy online tool to find the codes for most special characters here:
http://www.saila.com/usage/tips/examples/special_characters.html
-MattOn 8/24/05, Enrique Medina
[EMAIL PROTECTED]
wrote:Hi,
I know this is not a question directly related with MyFaces, but does anybody knows how to solve this problem?
I define my literal strings in a properties file, and then I have
created a custom messages tag that renders the message as an alert of
_javascript_. So when a JSF message is generated, it is rendered as an
alert. My problem is with accents. For example, in the alert window the
text appears like:
La f#243;rmula es correcta
while it should be:
La fórmula es correcta
Is it a matter of escaping the text in _javascript_? Because I have tried the escape() function but with no success...
Re: RE : RE : inputSuggest : some others improvement to do
No, that wouldn't seem to me to be the expected behavior. Sean coded that piece, so I can't be 100% sure, but I'd think the expected behavior should be that, if the user doesn't enter anything (either by picking from the list of suggestions or typing in something not on the list), a null value would be submitted to the model, just as it would be for a normal text box left blank. So, to my mind, that would also be a bug. Sean, any comments? -MattOn 8/25/05, Clément Maignien [EMAIL PROTECTED] wrote: What about the #3 problem ? Is it really the expected behaviour of this component ? Thanks Clément -Message d'origine-De: Clément Maignien Envoyé: mercredi 24 août 2005 11:34À: MyFaces DiscussionObjet: RE : inputSuggest : some others improvement to do Hummm, sorry, the #2 issue is a mistake : I have another page with an inputSuggest with manyitems into and the white space isn't there. So I'm asking why it is displayed on my other page and disappier when I don't addthe inputSuggestin the page ... wierd ... Bye, Clément. -Message d'origine-De: Clément Maignien Envoyé: mercredi 24 août 2005 10:37À: MyFaces DiscussionObjet: s:inputSuggest : some others improvement to do I've noticed some more improvements to make on this sandbox component. I don't know if they really comes from the component itself but I here they are : 1- I have a small JSF page with an s:inputSuggest component and an t:inputDate component under it. When clicking inside the inputSuggest a dropdown box open and displays firsts suggests. The problem is that under IE (not Firefox) the dropdown-box is displayed behind the inputDate, hiding some suggests. 2- It also seems that under Firefox (not IE), the page vertical lenght is increaseddepending on the number of items in the inputSuggest. A white space is displayed under the last element of the page. In my case I try to avoid the use of the page scroller in my webapp pages, and now there is a scroller displayed because of this big white space. Are those problems come from the browsers or the component implementation ? 3- When you click inside the inputSuggest and then click outside without typing anything or choosing an item, I get a value of -1 in the model. In fact, a new suggest is added to the component with an empty stringas label and -1 as value. Is this the expected behaviour of the inputSuggest component ? Thx, Clément.
Re: Questions on required=true attribute
Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message instead of h:message. -Ken sean
Re: Does a doc exist describing the MyFaces features?
A guide with examples of the JSF code, rendered output, and HTML output is here: http://www.exadel.com/tutorial/jsf/jsftags-guide.html It only covers the standard JSF tags Yes but its an excellent summary. sean
RE: Spanish accents in Javascript
I am
currently tackling internationalization issues. My recommendation is to
store your properties file in Latin 1 as it's easier to distribute to
translator/proofreader if you are getting your application professionally
translated. You can use the Native2Ascii ant task to convert the
application resource to unicode at build time.
The
latest version of NetBeans comes with a resource bundle editor which tabulates
resources in different languages and is quite useful.
I am
welcome to any better suggestions as I am still looking at this
problem.
-Original Message-From: Enrique Medina
[mailto:[EMAIL PROTECTED]Sent: Thursday, August 25, 2005 3:56
AMTo: MyFaces DiscussionSubject: Re: Spanish accents in
_javascript_Thanks. Let me try it ;-)
2005/8/25, Matt Blum [EMAIL PROTECTED]:
I
understand that. I'm suggesting that, instead of "La fórmula es
correcta" in your properties file, you put "La f\u00f3rmula es
correcta."
-Matt
On 8/24/05, Enrique
Medina [EMAIL PROTECTED]
wrote:
Hi
Matt,But the problem is that encoding is generated by JSF when
using EL like this:#{messages.literal1}
2005/8/24, Matt Blum [EMAIL PROTECTED]:
You
need to use the Unicode encoding for the character, like so:"La
f\u00f3rmula es correcta"There's a handy online tool to find the
codes for most special characters here:http://www.saila.com/usage/tips/examples/special_characters.html-Matt
On 8/24/05, Enrique Medina [EMAIL PROTECTED]
wrote:
Hi,I
know this is not a question directly related with MyFaces, but does
anybody knows how to solve this problem?I define my literal
strings in a properties file, and then I have created a custom
messages tag that renders the message as an alert of _javascript_. So
when a JSF message is generated, it is rendered as an alert. My
problem is with accents. For example, in the alert window the text
appears like:"La f#243;rmula es correcta"while it
should be:"La fórmula es correcta"Is it a matter of
escaping the text in _javascript_? Because I have tried the escape()
function but with no
success...
Re: RE : RE : inputSuggest : some others improvement to do
inputSuggest is still very rough as var as the JSF part goes. So its entirely possible. I will try and turn my attention to it once we get the release done. Someone should add a JIRA issue for now. sean On 8/25/05, Matt Blum [EMAIL PROTECTED] wrote: No, that wouldn't seem to me to be the expected behavior. Sean coded that piece, so I can't be 100% sure, but I'd think the expected behavior should be that, if the user doesn't enter anything (either by picking from the list of suggestions or typing in something not on the list), a null value would be submitted to the model, just as it would be for a normal text box left blank. So, to my mind, that would also be a bug. Sean, any comments? -Matt On 8/25/05, Clément Maignien [EMAIL PROTECTED] wrote: What about the #3 problem ? Is it really the expected behaviour of this component ? Thanks Clément -Message d'origine- De : Clément Maignien Envoyé : mercredi 24 août 2005 11:34 À : MyFaces Discussion Objet : RE : inputSuggest : some others improvement to do Hummm, sorry, the #2 issue is a mistake : I have another page with an inputSuggest with many items into and the white space isn't there. So I'm asking why it is displayed on my other page and disappier when I don't add the inputSuggest in the page ... wierd ... Bye, Clément. -Message d'origine- De : Clément Maignien Envoyé : mercredi 24 août 2005 10:37 À : MyFaces Discussion Objet : s:inputSuggest : some others improvement to do I've noticed some more improvements to make on this sandbox component. I don't know if they really comes from the component itself but I here they are : 1- I have a small JSF page with an s:inputSuggest component and an t:inputDate component under it. When clicking inside the inputSuggest a dropdown box open and displays firsts suggests. The problem is that under IE (not Firefox) the dropdown-box is displayed behind the inputDate, hiding some suggests. 2- It also seems that under Firefox (not IE), the page vertical lenght is increased depending on the number of items in the inputSuggest. A white space is displayed under the last element of the page. In my case I try to avoid the use of the page scroller in my webapp pages, and now there is a scroller displayed because of this big white space. Are those problems come from the browsers or the component implementation ? 3- When you click inside the inputSuggest and then click outside without typing anything or choosing an item, I get a value of -1 in the model. In fact, a new suggest is added to the component with an empty string as label and -1 as value. Is this the expected behaviour of the inputSuggest component ? Thx, Clément.
Re: How to call a method in the backing bean from a JSF page
On 8/24/05, Saul Qunming Yuan [EMAIL PROTECTED] wrote: Thanks for your response. I guess I didn't make me clear here. My questionis how to call a method in the backing bean from a JSF page withoutrendering out anything to the screen. I would suggest using Shale with JSF. Use the Shale jars and then have your backing bean implement a ViewController (I just extend AbstractViewController), and then you'll have several nice methods you can override. One is called prerender(). So if you map this backingbean to the correct path, for example fooBar, when fooBar.jsp is called the prerender method is invoked. That's the ultra simplified explanation and since I'm new to this, others (Craig) will probably elaborate more. It's really useful though for exactly what you want. -- Rick
Re: Re: Re: Redirect Tree2 _restoredState
Do you mean that my tree backing bean should implement the PhaseListener interface and be registered as a phase listener, so before render I could call the expandAll() method from the UITreeData?2005/8/25, Sean Schofield [EMAIL PROTECTED]: What about adding a phase listener to expand the nodes just beforerendering?Or as I have suggested before, Shale's prerender method? seanOn 8/25/05, [EMAIL PROTECTED][EMAIL PROTECTED] wrote: Well its more a ugly hack than a solution, but as long as there are no methods for that in the TreeModel you could mimic the behaviour with customized code form the expandAll() and expandEverything() methods of UITreeData in your backing bean getter method that supplies the TreeModel.
Re: Spanish accents in Javascript
Hi Zhai,
How do I specify my properties file to be Latin 1?2005/8/25, Zhai, Warren [IT] [EMAIL PROTECTED]:
I am
currently tackling internationalization issues. My recommendation is to
store your properties file in Latin 1 as it's easier to distribute to
translator/proofreader if you are getting your application professionally
translated. You can use the Native2Ascii ant task to convert the
application resource to unicode at build time.
The
latest version of NetBeans comes with a resource bundle editor which tabulates
resources in different languages and is quite useful.
I am
welcome to any better suggestions as I am still looking at this
problem.
-Original Message-From: Enrique Medina
[mailto:[EMAIL PROTECTED]]Sent: Thursday, August 25, 2005 3:56
AMTo: MyFaces DiscussionSubject: Re: Spanish accents in
_javascript_Thanks. Let me try it ;-)
2005/8/25, Matt Blum [EMAIL PROTECTED]:
I
understand that. I'm suggesting that, instead of La fórmula es
correcta in your properties file, you put La f\u00f3rmula es
correcta.
-Matt
On 8/24/05, Enrique
Medina [EMAIL PROTECTED]
wrote:
Hi
Matt,But the problem is that encoding is generated by JSF when
using EL like this:#{messages.literal1}
2005/8/24, Matt Blum [EMAIL PROTECTED]:
You
need to use the Unicode encoding for the character, like so:La
f\u00f3rmula es correctaThere's a handy online tool to find the
codes for most special characters here:http://www.saila.com/usage/tips/examples/special_characters.html
-Matt
On 8/24/05, Enrique Medina [EMAIL PROTECTED]
wrote:
Hi,I
know this is not a question directly related with MyFaces, but does
anybody knows how to solve this problem?I define my literal
strings in a properties file, and then I have created a custom
messages tag that renders the message as an alert of _javascript_. So
when a JSF message is generated, it is rendered as an alert. My
problem is with accents. For example, in the alert window the text
appears like:La f#243;rmula es correctawhile it
should be:La fórmula es correctaIs it a matter of
escaping the text in _javascript_? Because I have tried the escape()
function but with no
success...
I know annoying when someone posts a stacktrace, but any help ?
I feel stupid posting this, but his stack trace doesn't seem to help me
pinpoint why my navigation to a follow up page after a backingbean
method is invoked is not working. (I've checked the spelling this time,
and the employeeForm.jsp is in the root dir)...
navigation-rule
navigation-case
from-outcomesuccess/from-outcome
to-view-id/employeeForm.jsp/to-view-id
/navigation-case
/navigation-rule
Method that is' being called:
public String retrieveEmployeeAction() {
log.debug(in retrieveEmployeeAction());
//get Employee from backend
this.name = Rover;
this.age = new Integer(25);
return success;
}
After the above method fires, I get the nice 500 errorI have no idea why. (Couple notes... the
backing bean method first called is returning success and
employeeForm.jsp is spelled correctly and does exist)...
2005-08-24 18:05:27 StandardWrapperValve[Faces Servlet]:
Servlet.service() for servlet Faces Servlet threw exception
javax.faces.FacesException: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:83)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:109)
snip
Caused by: javax.faces.el.EvaluationException:
java.lang.IllegalStateException: No WebApplicationContext found: no
ContextLoaderListener registered?
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:206)
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:154)
at
org.apache.shale.faces.ShaleViewHandler.setupViewController(ShaleViewHandler.java:224)
at
org.apache.shale.faces.ShaleViewHandler.createView(ShaleViewHandler.java:122)
at
org.apache.shale.clay.faces.ClayViewHandler.createView(ClayViewHandler.java:111)
at
com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:135)
at
org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:184)
at
... snip
Caused by: java.lang.IllegalStateException: No WebApplicationContext
found: no ContextLoaderListener registered?
at
org.springframework.web.jsf.FacesContextUtils.getRequiredWebApplicationContext(FacesContextUtils.java:78)
at
org.springframework.web.jsf.DelegatingVariableResolver.getWebApplicationContext(DelegatingVariableResolver.java:134)
at
org.springframework.web.jsf.DelegatingVariableResolver.resolveVariable(DelegatingVariableResolver.java:112)
at
org.apache.shale.spring.WebApplicationContextVariableResolver.resolveVariable(WebApplicationContextVariableResolver.java:86)
at
org.apache.shale.faces.ShaleVariableResolver.resolveVariable(ShaleVariableResolver.java:99)
at com.sun.faces.el.impl.NamedValue.evaluate(NamedValue.java:125)
at
com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:243)
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:173)
... 43 more
-- Rick
Let's write that doc!
I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=http://wiki.apache.org/myfaces/MyFacesComponents>let's start documenting those components/a>. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message> instead of h:message>. -Ken sean x-tad-smallerMet vriendelijke groeten, Jan Dockx /x-tad-smallerx-tad-smaller PeopleWare NV - Head Office/x-tad-smallerx-tad-smaller Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 /x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller PeopleWare NV - Branch Office Geel/x-tad-smallerx-tad-smaller Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25/x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller http://www.peopleware.be/ /x-tad-smallerx-tad-smallerhttp://www.mobileware.be//x-tad-smaller smime.p7s Description: S/MIME cryptographic signature
Re: I know annoying when someone posts a stacktrace, but any help ?
Rick Reumann wrote: I feel stupid posting this, but his stack trace doesn't seem to help me pinpoint why my navigation to a follow up page after a backingbean method is invoked is not working. (I've checked the spelling this time, and the employeeForm.jsp is in the root dir)... navigation-rule Don't you need a from-view-id here? navigation-case from-outcomesuccess/from-outcome to-view-id/employeeForm.jsp/to-view-id /navigation-case /navigation-rule
RE: Setting error page
Title: Message To Set the error page, put the following entry in your web.xml file: error-page error-code500/error-code location/errorPage.jsf/location /error-page I believe you can set a page for each type of error but this seems to redirect on all exceptions. In order to redirect to a page when the session ends, you will have to write a session filter. I found this article very useful: http://www.jguru.com/forums/view.jsp?EID=1248692 Paul From: Clément Maignien [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 8:42 AM To: MyFaces Discussion Subject: Setting error page Hi, I would like to know how to set a JSFerror page that will be displayed instead of the default Tomcat one. Is it possible to redirect the navigation to a specific page when the user session times out ? Thx. Clément
RE : RE : RE : inputSuggest : some others improvement to do
OK I'll add all my observations as commentaries on the JIRA issue I already opened previously. Regards, Clément -Message d'origine- De : Sean Schofield [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 15:33 À : MyFaces Discussion Objet : Re: RE : RE : inputSuggest : some others improvement to do inputSuggest is still very rough as var as the JSF part goes. So its entirely possible. I will try and turn my attention to it once we get the release done. Someone should add a JIRA issue for now. sean On 8/25/05, Matt Blum [EMAIL PROTECTED] wrote: No, that wouldn't seem to me to be the expected behavior. Sean coded that piece, so I can't be 100% sure, but I'd think the expected behavior should be that, if the user doesn't enter anything (either by picking from the list of suggestions or typing in something not on the list), a null value would be submitted to the model, just as it would be for a normal text box left blank. So, to my mind, that would also be a bug. Sean, any comments? -Matt On 8/25/05, Clément Maignien [EMAIL PROTECTED] wrote: What about the #3 problem ? Is it really the expected behaviour of this component ? Thanks Clément -Message d'origine- De : Clément Maignien Envoyé : mercredi 24 août 2005 11:34 À : MyFaces Discussion Objet : RE : inputSuggest : some others improvement to do Hummm, sorry, the #2 issue is a mistake : I have another page with an inputSuggest with many items into and the white space isn't there. So I'm asking why it is displayed on my other page and disappier when I don't add the inputSuggest in the page ... wierd ... Bye, Clément. -Message d'origine- De : Clément Maignien Envoyé : mercredi 24 août 2005 10:37 À : MyFaces Discussion Objet : s:inputSuggest : some others improvement to do I've noticed some more improvements to make on this sandbox component. I don't know if they really comes from the component itself but I here they are : 1- I have a small JSF page with an s:inputSuggest component and an t:inputDate component under it. When clicking inside the inputSuggest a dropdown box open and displays firsts suggests. The problem is that under IE (not Firefox) the dropdown-box is displayed behind the inputDate, hiding some suggests. 2- It also seems that under Firefox (not IE), the page vertical lenght is increased depending on the number of items in the inputSuggest. A white space is displayed under the last element of the page. In my case I try to avoid the use of the page scroller in my webapp pages, and now there is a scroller displayed because of this big white space. Are those problems come from the browsers or the component implementation ? 3- When you click inside the inputSuggest and then click outside without typing anything or choosing an item, I get a value of -1 in the model. In fact, a new suggest is added to the component with an empty string as label and -1 as value. Is this the expected behaviour of the inputSuggest component ? Thx, Clément.
RE : Let's write that doc!
Title: Message +1 -Message d'origine-De: ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Envoyé: jeudi 25 août 2005 16:16À: MyFaces DiscussionObjet: Let's write that doc!I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=""let's start documenting those components/a. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday.I just added a little grain. More to come, I promise.On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just aboutto write something similar because I didn't know about it. Is itlisted somewhere on the MyFaces website? I don't see it here:http://myfaces.apache.org/tomahawk/overview.htmlUnfortunately that page is woefully out of date. Updating it is on myshortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it onlyspecific to the MyFaces extensions? In other words, couldn't I use itwith the RI as long as I included the myfaces-extensions-1.0.9.jar andreferenced the taglib?Right you can use tomahawk with the RI and if you want thatfunctionality use t:message instead of h:message. -KenseanMet vriendelijke groeten,Jan DockxPeopleWare NV - Head OfficeCdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office GeelKleinhoefstraat 5B-2440 GeelTel: +32 14 57.00.90Fax: +32 14 58.13.25http://www.peopleware.be/http://www.mobileware.be/
Re: RE : Let's write that doc!
+1 ;) If you want to get involved even more, it would be great if you would add this documentation to the /forrest/content section of our sourcetree for viewing it on the homepage. (just send us patches, we will commit them) If not, just put it on the WIKI, and gradually we will move it over to the homepage. regards, Martin On 8/25/05, Clément Maignien [EMAIL PROTECTED] wrote: +1 -Message d'origine- De : ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 16:16 À : MyFaces Discussion Objet : Let's write that doc! I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=http://wiki.apache.org/myfaces/MyFacesComponents;let's start documenting those components/a. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message instead of h:message. -Ken sean Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
Re: I know annoying when someone posts a stacktrace, but any help ?
On 8/25/05, David Haynes [EMAIL PROTECTED] wrote: Rick Reumann wrote: I feel stupid posting this, but his stack trace doesn't seem to help me pinpoint why my navigation to a follow up page after a backingbean method is invoked is not working. (I've checked the spelling this time, and the employeeForm.jsp is in the root dir)... navigation-ruleDon't you need a from-view-id here? I've tried it with that and without it. Same problem. (I thought you don't have to use from-view-id - at least the book I'm using it shows it both ways? Concept of global forwards) -- Rick
RE: I know annoying when someone posts a stacktrace, but any help ?
Title: Message
Did
you wrap your JSF code in f:view.../f:view?
-
Brendan
-Original Message-From: Rick Reumann
[mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005
9:01 AMTo: MyFaces DiscussionSubject: I know annoying
when someone posts a stacktrace, but any help ?I feel
stupid posting this, but his stack trace doesn't seem to help me pinpoint why
my navigation to a follow up page after a backingbean method is invoked is not
working. (I've checked the spelling this time, and the employeeForm.jsp is in
the root dir)...navigation-rule
navigation-case
from-outcomesuccess/from-outcome
to-view-id/employeeForm.jsp/to-view-id
/navigation-case
/navigation-rule Method that "is'" being called:public
String retrieveEmployeeAction()
{ log.debug("in
retrieveEmployeeAction()");
//get Employee from backend this.name =
"Rover"; this.age = new
Integer(25); return
"success"; }After the above method fires, I get
the nice 500 errorI have no idea why. (Couple notes... the backing bean method
first called is returning "success" and "employeeForm.jsp" is spelled
correctly and does exist)...2005-08-24 18:05:27
StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces
Servlet threw exception javax.faces.FacesException:
java.lang.IllegalStateException: No WebApplicationContext found: no
ContextLoaderListener registered? at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:83)
at
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
at
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
at
javax.faces.webapp.FacesServlet.service(FacesServlet.java:109)
snip Caused by:
javax.faces.el.EvaluationException: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:206)
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:154)
at
org.apache.shale.faces.ShaleViewHandler.setupViewController(ShaleViewHandler.java:224)
at
org.apache.shale.faces.ShaleViewHandler.createView(ShaleViewHandler.java:122)
at
org.apache.shale.clay.faces.ClayViewHandler.createView(ClayViewHandler.java:111)
at
com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:135)
at
org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:184)
at
... snip Caused by: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
org.springframework.web.jsf.FacesContextUtils.getRequiredWebApplicationContext(FacesContextUtils.java:78)
at
org.springframework.web.jsf.DelegatingVariableResolver.getWebApplicationContext(DelegatingVariableResolver.java:134)
at
org.springframework.web.jsf.DelegatingVariableResolver.resolveVariable(DelegatingVariableResolver.java:112)
at
org.apache.shale.spring.WebApplicationContextVariableResolver.resolveVariable(WebApplicationContextVariableResolver.java:86)
at
org.apache.shale.faces.ShaleVariableResolver.resolveVariable(ShaleVariableResolver.java:99)
at
com.sun.faces.el.impl.NamedValue.evaluate(NamedValue.java:125)
at
com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:243)
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:173)
... 43 more -- Rick
Antwort: Re: Re: Re: Redirect Tree2 _restoredState
No, I mean you can create your own method for expanding the tree in your backing bean and use some source code of the mentioned methods. But as I said thats not the way it should be ... maybe we should move the expand methods back to the TreeModel and leave the ones in UITreeData as delegates. If the functions are in the TreeModel you could then easily call them form your backing bean. [EMAIL PROTECTED] schrieb am 25.08.2005 15:57:33: Do you mean that my tree backing bean should implement the PhaseListener interface and be registered as a phase listener, so before render I could call the expandAll() method from the UITreeData? 2005/8/25, Sean Schofield [EMAIL PROTECTED]: What about adding a phase listener to expand the nodes just before rendering? Or as I have suggested before, Shale's prerender method? sean On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well its more a ugly hack than a solution, but as long as there are no methods for that in the TreeModel you could mimic the behaviour with customized code form the expandAll() and expandEverything() methods of UITreeData in your backing bean getter method that supplies the TreeModel.
Re: I know annoying when someone posts a stacktrace, but any help ?
Currently I'm just trying to see if I can get to a blank page without errors so I just have...
%@ taglib uri=http://java.sun.com/jsf/core prefix=f %
%@ taglib uri=http://java.sun.com/jsf/html prefix=h %
%@ taglib uri=http://java.sun.com/jsp/jstl/core prefix=c %
f:view
h:form
/h:form
/f:view
But I've tried other things.. just blank, just one word, just
f:view /f:view and tried with my actual form that I
wanted between the h:form tags.
I'm wondering if the problem is because I'm using all the shale jars
from the struts-shale-usecases example but I'm not setting up a bunch
of the other configs I see under web-xml that are in that example (ie
chain-config.xml, dialog-config.xml, etc). I wasn't sure what the
minimal jars I needed to use Shale and the ViewController were so I
just included them all (I tried removing the Spring ones and the
application wouldn't start up).On 8/25/05, CONNER, BRENDAN (SBCSI) [EMAIL PROTECTED] wrote:
Did
you wrap your JSF code in f:view.../f:view?
-
Brendan
-Original Message-From: Rick Reumann
[mailto:[EMAIL PROTECTED]] Sent: Thursday, August 25, 2005
9:01 AMTo: MyFaces DiscussionSubject: I know annoying
when someone posts a stacktrace, but any help ?I feel
stupid posting this, but his stack trace doesn't seem to help me pinpoint why
my navigation to a follow up page after a backingbean method is invoked is not
working. (I've checked the spelling this time, and the employeeForm.jsp is in
the root dir)...navigation-rule
navigation-case
from-outcomesuccess/from-outcome
to-view-id/employeeForm.jsp/to-view-id
/navigation-case
/navigation-rule Method that is' being called:public
String retrieveEmployeeAction()
{ log.debug(in
retrieveEmployeeAction());
//get Employee from backend this.name =
Rover; this.age = new
Integer(25); return
success; }After the above method fires, I get
the nice 500 errorI have no idea why. (Couple notes... the backing bean method
first called is returning success and employeeForm.jsp is spelled
correctly and does exist)...2005-08-24 18:05:27
StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces
Servlet threw exception javax.faces.FacesException:
java.lang.IllegalStateException: No WebApplicationContext found: no
ContextLoaderListener registered? at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:83)
at
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
at
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
at
javax.faces.webapp.FacesServlet.service(FacesServlet.java:109)
snip Caused by:
javax.faces.el.EvaluationException: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:206)
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:154)
at
org.apache.shale.faces.ShaleViewHandler.setupViewController(ShaleViewHandler.java:224)
at
org.apache.shale.faces.ShaleViewHandler.createView(ShaleViewHandler.java:122)
at
org.apache.shale.clay.faces.ClayViewHandler.createView(ClayViewHandler.java:111)
at
com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:135)
at
org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:184)
at
... snip Caused by: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
org.springframework.web.jsf.FacesContextUtils.getRequiredWebApplicationContext(FacesContextUtils.java:78)
at
org.springframework.web.jsf.DelegatingVariableResolver.getWebApplicationContext(DelegatingVariableResolver.java:134)
at
org.springframework.web.jsf.DelegatingVariableResolver.resolveVariable(DelegatingVariableResolver.java:112)
at
org.apache.shale.spring.WebApplicationContextVariableResolver.resolveVariable(WebApplicationContextVariableResolver.java:86)
at
org.apache.shale.faces.ShaleVariableResolver.resolveVariable(ShaleVariableResolver.java:99)
at
com.sun.faces.el.impl.NamedValue.evaluate(NamedValue.java:125)
at
com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:243)
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:173)
... 43 more -- Rick
-- Rick
Re: Assign target window for the first Jsf response.sendRedirect()
Greetings: I want to assign a target name for the Jsf entry page so its child window can point back to the same browser window. Here is what I have tried, but it does not seems to work. The entry index page conditionally forwards the request to different section and has: jsp:forward page=/public/section1/index.jsp jsp:param name=target value=portal / /jsp:forward Then, the /public/section1/index.jsp has: % response.sendRedirect(http://localhost:8080/public/section1/welcome.jsf;); % Hope some one may help. Thanks. BaTien
Re: Bypassing validation while still preserving values
Enrique Medina wrote: Hi Richard, I've been reading your post, but I think I'm missing something... If you set immediate=false, then only two phases will be executed: 1) Restore view 2) Apply request values so, as you correctly say, the model will not be updated, as the Update Model phase is not invoked. But AFAIK one thing is the component and another is the model. I mean, the component must be always updated independently of the value for the immediate attribute, so I don't understand why you loose your component values between requests (maybe it's just a matter of scope, and not really the immediate attribute). You are correct. In this situation, when the user clicks the command link they are forwarded to a different page so they can do a quick add on the drop-down and then send them back to the main page with the information from before they clicked the link repopulated in the form. That's why I need the model updated is because then on the form that gets redirected to I can easily have x:saveState elements for each of the model values I want to save while the user goes to a different page. Then when they go back to the main page the saved values get put back in the model and the page looks just like when they left it except that now there's a new item in the drop-down. Rich Just my 2 cents ;-) 2005/8/24, Richard Wallace [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: James Reynolds wrote: Ooo! I know this one! I lean heavily on the Core JSF book by Geary Horstmann, there is some good info on this in the page life cycle in Chapter 7. Specifically, the Immediate Components information on page 292. As you mentioned, the immediate attribute must be set to true for your components. The portion I tripped up on was adding context.renderResponse (); at the end of my ValueChangeEvent code for the valueChangeListener. Then, the model maintained the previous state of my page without firing validation. The problem with that is that then the model doesn't get updated when the command link is clicked so on the page they get directed to can't preserve the model info cause it was never updated. The situation I have in mind is something like: The user loads the page. They enter some contact info. They click on one of the command links. The contact info shouldn't be validated but the model values should be udpated. If you look at the lifecycle the validation occurs before updating the model values. And immediate event handling gets handled before validation. So, if I set the immediate attribute to true it will forward to the quick add page before validating the data or updating the model. So t:saveState will be preserving old information, not the latest info the user entered. JR -Original Message- From: Richard Wallace [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 24, 2005 10:14 AM To: MyFaces Discussion Subject: Bypassing validation while still preserving values Hey everyone, I've got a form that has a couple of optional command links on it. They are basically quick add buttons so a user can quickly add things to drop downs if they aren't there. When these quick add buttons are clicked the user is sent to an add page, the user enters the new info and is then redirected back to the original page where the new entry is selected and all the other data is preserved from before they clicked the quick add button. The backing beans involved are request scoped and the values filled in before clicking the quick add button are preserved through the process using the t:saveState element. I'm trying to get the validation correct. I want all the form elements to be required when the user clicks the submit button, but when they hit the quick add link the validation should be bypassed. I thought of doing this with the immediate attribute set to true on the quick add command links but if I do that then any data the user entered on that page load (contact info type stuff) is lost. So I kind of need to bypass the validation but still update the model values if one of the command links are clicked, but have full validation done when the command button is pressed. I was looking at the new OptionalValidation Framework but I'm not sure exactly how to apply it in this case. I mean, what I really want is to have the validation type be none when command links are used and hard otherwise. Any ideas? Thanks, Rich
Re: I know annoying when someone posts a stacktrace, but any help ?
Make sure that you have the ShaleApplicationFilter in your web deployment
descriptor (web.xml). This guy registers the
ShalePhaseListener that fires some of the livecycle events on the view
controller.
!-- Shale Application Controller Filter --
filter
filter-nameshale/filter-name
filter-class
org.apache.shale.faces.ShaleApplicationFilter
/filter-class
/filter
!-- Shale Application Controller Filter Mapping --
filter-mapping
filter-nameshale/filter-name
url-pattern/*/url-pattern
/filter-mapping
You might not need the shale-clay.jar archive. It is optional and you won't
need this stuff if you are not using it (in your web.xml).
!-- Clay Configuration Resources --
context-param
param-nameclay-config-files/param-name
param-value/WEB-INF/clay-config.xml/param-value
/context-param
!-- Clay template suffix override, default is .clay --
context-param
param-nameclay-template-suffix/param-name
param-value.html/param-value
/context-param
!-- Clay Configuration Listener --
listener
listener-classorg.apache.shale.clay.config.ClayConfigureListener/listener-class
/listener
servlet-mapping
servlet-namefaces/servlet-name
url-pattern*.html/url-pattern
/servlet-mapping
Gary
---BeginMessage---
Currently I'm just trying to see if I can get to a blank page without errors so I just have...
%@ taglib uri=http://java.sun.com/jsf/core prefix=f %
%@ taglib uri=http://java.sun.com/jsf/html prefix=h %
%@ taglib uri=http://java.sun.com/jsp/jstl/core prefix=c %
f:view
h:form
/h:form
/f:view
But I've tried other things.. just blank, just one word, just
f:view /f:view and tried with my actual form that I
wanted between the h:form tags.
I'm wondering if the problem is because I'm using all the shale jars
from the struts-shale-usecases example but I'm not setting up a bunch
of the other configs I see under web-xml that are in that example (ie
chain-config.xml, dialog-config.xml, etc). I wasn't sure what the
minimal jars I needed to use Shale and the ViewController were so I
just included them all (I tried removing the Spring ones and the
application wouldn't start up).On 8/25/05, CONNER, BRENDAN (SBCSI) [EMAIL PROTECTED] wrote:
Did
you wrap your JSF code in f:view.../f:view?
-
Brendan
-Original Message-From: Rick Reumann
[mailto:[EMAIL PROTECTED]] Sent: Thursday, August 25, 2005
9:01 AMTo: MyFaces DiscussionSubject: I know annoying
when someone posts a stacktrace, but any help ?I feel
stupid posting this, but his stack trace doesn't seem to help me pinpoint why
my navigation to a follow up page after a backingbean method is invoked is not
working. (I've checked the spelling this time, and the employeeForm.jsp is in
the root dir)...navigation-rule
navigation-case
from-outcomesuccess/from-outcome
to-view-id/employeeForm.jsp/to-view-id
/navigation-case
/navigation-rule Method that is' being called:public
String retrieveEmployeeAction()
{ log.debug(in
retrieveEmployeeAction());
//get Employee from backend this.name =
Rover; this.age = new
Integer(25); return
success; }After the above method fires, I get
the nice 500 errorI have no idea why. (Couple notes... the backing bean method
first called is returning success and employeeForm.jsp is spelled
correctly and does exist)...2005-08-24 18:05:27
StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces
Servlet threw exception javax.faces.FacesException:
java.lang.IllegalStateException: No WebApplicationContext found: no
ContextLoaderListener registered? at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:83)
at
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
at
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
at
javax.faces.webapp.FacesServlet.service(FacesServlet.java:109)
snip Caused by:
javax.faces.el.EvaluationException: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:206)
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:154)
at
org.apache.shale.faces.ShaleViewHandler.setupViewController(ShaleViewHandler.java:224)
at
org.apache.shale.faces.ShaleViewHandler.createView(ShaleViewHandler.java:122)
at
org.apache.shale.clay.faces.ClayViewHandler.createView(ClayViewHandler.java:111)
at
com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:135)
at
org.apache.shale.dialog.faces.DialogNavigationHandler.handleNavigation(DialogNavigationHandler.java:184)
at
... snip Caused by: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
RE: Let's write that doc!
Title: Message Very Good suggestion. I already intend to put example and doc for the JSCookMenu. If everyone who gains experience with some specific component could put example and how to use the component in the wiki, this will reduce mails and questions when we start working with a new component. Everyone should go in that direction if we want that Myfaces components are used more and more in projects. Henri-Philippe Delbrouck -Original Message-From: ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Sent: jeudi 25 août 2005 16:16To: MyFaces DiscussionSubject: Let's write that doc! I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=""let's start documenting those components/a. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message instead of h:message. -Ken sean Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/
Re: I know annoying when someone posts a stacktrace, but any help ?
I do have the shale fliter in place and it is working because the
prerender is being called in my backingBean that extends
AbstractViewController. I did have the clay.jar in my lib and no config
set up for it, but I removed that jar and I'm still getting the same
error:(
The current jars I have in my web app lib are:
commons-beanutils.jar
commons-chain.jar
commons-collections.jar
commons-digester.jar
commons-el.jar
commons-logging.jar
commons-validator.jar
jsf-impl.jar
jstl.jar
log4j-1.2.7.jar
myfaces.jar
shale-core.jar
shale-spring.jar
spring-beans.jar
spring-context.jar
spring-core.jar
spring-web.jar
standard.jar
struts.jar
On 8/25/05, Gary VanMatre [EMAIL PROTECTED] wrote:
Make sure that you have the ShaleApplicationFilter in your web deployment descriptor (web.xml). This guy registers theShalePhaseListener that fires some of the livecycle events on the view controller. !-- Shale Application Controller Filter --
filter filter-nameshale/filter-name filter-class org.apache.shale.faces.ShaleApplicationFilter /filter-class /filter !-- Shale Application Controller Filter Mapping --
filter-mapping filter-nameshale/filter-name url-pattern/*/url-pattern /filter-mappingYou
might not need the shale-clay.jar archive. It is optional and you
won't need this stuff if you are not using it (in your web.xml). !-- Clay Configuration Resources -- context-param param-nameclay-config-files/param-name param-value/WEB-INF/clay-
config.xml/param-value /context-param !-- Clay template suffix override, default is .clay -- context-param param-nameclay-template-suffix/param-name
param-value.html/param-value /context-param !-- Clay Configuration Listener -- listener listener-classorg.apache.shale.clay.config.ClayConfigureListener
/listener-class /listener servlet-mapping servlet-namefaces/servlet-name url-pattern*.html/url-pattern /servlet-mapping
Gary-- Forwarded message --From:Rick Reumann [EMAIL PROTECTED]To:MyFaces Discussion
users@myfaces.apache.orgDate:Thu, 25 Aug 2005 15:22:57 +Subject:Re: I know annoying when someone posts a stacktrace, but any help ?Currently I'm just trying to see if I can get to a blank page without errors so I just have...
%@ taglib uri=http://java.sun.com/jsf/core prefix=f %
%@ taglib uri=http://java.sun.com/jsf/html prefix=h %
%@ taglib uri=http://java.sun.com/jsp/jstl/core prefix=c %
f:view
h:form
/h:form
/f:view
But I've tried other things.. just blank, just one word, just
f:view /f:view and tried with my actual form that I
wanted between the h:form tags.
I'm wondering if the problem is because I'm using all the shale jars
from the struts-shale-usecases example but I'm not setting up a bunch
of the other configs I see under web-xml that are in that example (ie
chain-config.xml, dialog-config.xml, etc). I wasn't sure what the
minimal jars I needed to use Shale and the ViewController were so I
just included them all (I tried removing the Spring ones and the
application wouldn't start up).On 8/25/05, CONNER, BRENDAN (SBCSI)
[EMAIL PROTECTED] wrote:
Did
you wrap your JSF code in f:view.../f:view?
-
Brendan
-Original Message-From: Rick Reumann
[mailto:[EMAIL PROTECTED]] Sent: Thursday, August 25, 2005
9:01 AMTo: MyFaces DiscussionSubject: I know annoying
when someone posts a stacktrace, but any help ?I feel
stupid posting this, but his stack trace doesn't seem to help me pinpoint why
my navigation to a follow up page after a backingbean method is invoked is not
working. (I've checked the spelling this time, and the employeeForm.jsp is in
the root dir)...navigation-rule
navigation-case
from-outcomesuccess/from-outcome
to-view-id/employeeForm.jsp/to-view-id
/navigation-case
/navigation-rule Method that is' being called:public
String retrieveEmployeeAction()
{ log.debug(in
retrieveEmployeeAction());
//get Employee from backend this.name =
Rover; this.age = new
Integer(25); return
success; }After the above method fires, I get
the nice 500 errorI have no idea why. (Couple notes... the backing bean method
first called is returning success and employeeForm.jsp is spelled
correctly and does exist)...2005-08-24 18:05:27
StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces
Servlet threw exception javax.faces.FacesException:
java.lang.IllegalStateException: No WebApplicationContext found: no
ContextLoaderListener registered? at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:83)
at
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
at
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
at
javax.faces.webapp.FacesServlet.service(FacesServlet.java:109)
snip Caused by:
javax.faces.el.EvaluationException: java.lang.IllegalStateException: No
WebApplicationContext found: no ContextLoaderListener registered?
at
Re: I know annoying when someone posts a stacktrace, but any help ?
On 8/25/05, Rick Reumann [EMAIL PROTECTED] wrote:
I do have the shale fliter in place and it is working because the prerender
is being called in my backingBean that extends AbstractViewController. I did
have the clay.jar in my lib and no config set up for it, but I removed that
jar and I'm still getting the same error:(
See my response on the Struts user list.
ContextControllerLIstener is a Spring Framework thing, used to
initialize the Spring BeanFactory (in a webapp, that's a
WebApplicationContext). If you're using the Spring integration you
need to register this listener in web.xml (like the use cases app
does). If you're not using the Spring integration, you shouldn't need
to -- that's a Shale bug if it blows up in that case.
Craig
The current jars I have in my web app lib are:
commons-beanutils.jar
commons-chain.jar
commons-collections.jar
commons-digester.jar
commons-el.jar
commons-logging.jar
commons-validator.jar
jsf-impl.jar
jstl.jar
log4j-1.2.7.jar
myfaces.jar
shale-core.jar
shale-spring.jar
spring-beans.jar
spring-context.jar
spring-core.jar
spring-web.jar
standard.jar
struts.jar
On 8/25/05, Gary VanMatre [EMAIL PROTECTED] wrote:
Make sure that you have the ShaleApplicationFilter in your web deployment
descriptor (web.xml). This guy registers the
ShalePhaseListener that fires some of the livecycle events on the view
controller.
!-- Shale Application Controller Filter --
filter
filter-nameshale/filter-name
filter-class
org.apache.shale.faces.ShaleApplicationFilter
/filter-class
/filter
!-- Shale Application Controller Filter Mapping --
filter-mapping
filter-nameshale/filter-name
url-pattern/*/url-pattern
/filter-mapping
You might not need the shale-clay.jar archive. It is optional and you
won't need this stuff if you are not using it (in your web.xml).
!-- Clay Configuration Resources --
context-param
param-nameclay-config-files/param-name
param-value/WEB-INF/clay- config.xml/param-value
/context-param
!-- Clay template suffix override, default is .clay --
context-param
param-nameclay-template-suffix/param-name
param-value.html/param-value
/context-param
!-- Clay Configuration Listener --
listener
listener-classorg.apache.shale.clay.config.ClayConfigureListener
/listener-class
/listener
servlet-mapping
servlet-namefaces/servlet-name
url-pattern*.html/url-pattern
/servlet-mapping
Gary
-- Forwarded message --
From: Rick Reumann [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Date: Thu, 25 Aug 2005 15:22:57 +
Subject: Re: I know annoying when someone posts a stacktrace, but any help
?
Currently I'm just trying to see if I can get to a blank page without
errors so I just have...
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
%@ taglib uri=http://java.sun.com/jsf/html; prefix=h %
%@ taglib uri=http://java.sun.com/jsp/jstl/core;
prefix=c %
f:view
h:form
/h:form
/f:view
But I've tried other things.. just blank, just one word, just f:view
/f:view and tried with my actual form that I wanted between the h:form
tags.
I'm wondering if the problem is because I'm using all the shale jars from
the struts-shale-usecases example but I'm not setting up a bunch of the
other configs I see under web-xml that are in that example (ie
chain-config.xml, dialog-config.xml, etc). I wasn't sure what the minimal
jars I needed to use Shale and the ViewController were so I just included
them all (I tried removing the Spring ones and the application wouldn't
start up).
On 8/25/05, CONNER, BRENDAN (SBCSI) [EMAIL PROTECTED] wrote:
Did you wrap your JSF code in f:view.../f:view?
- Brendan
-Original Message-
From: Rick Reumann [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 25, 2005 9:01 AM
To: MyFaces Discussion
Subject: I know annoying when someone posts a stacktrace, but any help ?
I feel stupid posting this, but his stack trace doesn't seem to help me
pinpoint why my navigation to a follow up page after a backingbean method is
invoked is not working. (I've checked the spelling this time, and the
employeeForm.jsp is in the root dir)...
navigation-rule
navigation-case
from-outcomesuccess/from-outcome
to-view-id/employeeForm.jsp/to-view-id
/navigation-case
/navigation-rule
Method that is' being called:
public String retrieveEmployeeAction() {
log.debug(in retrieveEmployeeAction());
//get Employee from backend
this.name = Rover;
this.age = new Integer(25);
return success;
}
After the above method fires, I get the nice 500 errorI have no
Re: I know annoying when someone posts a stacktrace, but any help ?
On 8/25/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/25/05, Rick Reumann [EMAIL PROTECTED] wrote: I do have the shale fliter in place and it is working because the prerender is being called in my backingBean that extends AbstractViewController. I did have the clay.jar in my lib and no config set up for it, but I removed that jar and I'm still getting the same error:( See my response on the Struts user list. ContextControllerLIstener is a Spring Framework thing, used to initialize the Spring BeanFactory (in a webapp, that's a WebApplicationContext). If you're using the Spring integration you need to register this listener in web.xml (like the use cases app does). If you're not using the Spring integration, you shouldn't need to -- that's a Shale bug if it blows up in that case. Craig One more note -- if you're not using the Spring integration, you'll want to remove shale-spring.jar and all the other Spring related jars. Craig
SaveState Question
Am I correct in believing that the x:saveState tag will only save state for the life of a single view? In other words as long as I'm posting back to the same viewId that state will be saved but as soon as I navigate to another view the state is gone? Or does this tag allow you to save state across requests across views? Thanks, Galen
Re: Bypassing validation while still preserving values
Sorry, I've been on vacation the last week. The default for the Optional Validation Framework is hard, so it's just a matter of setting validation to none for your command links, and wrapping all of your validators/converters. Note that if validation is set to none, your model isn't going to be updated. You'll need to pull out any values with getSubmittedValue(). Note that you can't have it both ways -- if you're not validating data, then you can't update the model since the data may not be valid. You really want to be preserving your submitted values, not your model values. -Mike On 8/24/05, Richard Wallace [EMAIL PROTECTED] wrote: Hey everyone, I've got a form that has a couple of optional command links on it. They are basically quick add buttons so a user can quickly add things to drop downs if they aren't there. When these quick add buttons are clicked the user is sent to an add page, the user enters the new info and is then redirected back to the original page where the new entry is selected and all the other data is preserved from before they clicked the quick add button. The backing beans involved are request scoped and the values filled in before clicking the quick add button are preserved through the process using the t:saveState element. I'm trying to get the validation correct. I want all the form elements to be required when the user clicks the submit button, but when they hit the quick add link the validation should be bypassed. I thought of doing this with the immediate attribute set to true on the quick add command links but if I do that then any data the user entered on that page load (contact info type stuff) is lost. So I kind of need to bypass the validation but still update the model values if one of the command links are clicked, but have full validation done when the command button is pressed. I was looking at the new OptionalValidation Framework but I'm not sure exactly how to apply it in this case. I mean, what I really want is to have the validation type be none when command links are used and hard otherwise. Any ideas? Thanks, Rich
Re: How to call a method in the backing bean from a JSF page
I agree with Rick. Shale is what you want if you want to do something before rendering. In fact, there is a prerender method in the ViewControllr interface for just such an occassion. sean On 8/25/05, Rick Reumann [EMAIL PROTECTED] wrote: On 8/24/05, Saul Qunming Yuan [EMAIL PROTECTED] wrote: Thanks for your response. I guess I didn't make me clear here. My question is how to call a method in the backing bean from a JSF page without rendering out anything to the screen. I would suggest using Shale with JSF. Use the Shale jars and then have your backing bean implement a ViewController (I just extend AbstractViewController), and then you'll have several nice methods you can override. One is called prerender(). So if you map this backingbean to the correct path, for example fooBar, when fooBar.jsp is called the prerender method is invoked. That's the ultra simplified explanation and since I'm new to this, others (Craig) will probably elaborate more. It's really useful though for exactly what you want. -- Rick
Re: I know annoying when someone posts a stacktrace, but any help ?
Thanks Craig. That was the problem.On 8/25/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/25/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/25/05, Rick Reumann [EMAIL PROTECTED] wrote: I do have the shale fliter in place and it is working because the prerender is being called in my backingBean that extends AbstractViewController. I did have the clay.jar in my lib and no config set up for it, but I removed that jar and I'm still getting the same error:( See my response on the Struts user list. ContextControllerLIstener is a Spring Framework thing, used to initialize the Spring BeanFactory (in a webapp, that's a WebApplicationContext).If you're using the Spring integration you need to register this listener in web.xml (like the use cases app does).If you're not using the Spring integration, you shouldn't need to -- that's a Shale bug if it blows up in that case. CraigOne more note -- if you're not using the Spring integration, you'llwant to remove shale-spring.jar and all the other Spring related jars. Craig-- Rick
Re: SaveState Question
Will that work even over a redirect?On 8/25/05, Mike Kienenberger [EMAIL PROTECTED] wrote: As long as you navigate to a page that contains a matching x:saveStatetag, the data will be moved from your posted form data to the currentcomponent tree and be rendered back out as html again.On 8/25/05, Galen Dunkleberger [EMAIL PROTECTED] wrote: Am I correct in believing that the x:saveState tag will only save state for the life of a single view? In other words as long as I'm posting back to the same viewId that state will be saved but as soon as I navigate to another view the state is gone? Or does this tag allow you to save state across requests across views? Thanks, Galen
Re: Bypassing validation while still preserving values
Mike Kienenberger wrote: Sorry, I've been on vacation the last week. The default for the Optional Validation Framework is hard, so it's just a matter of setting validation to none for your command links, and wrapping all of your validators/converters. Note that if validation is set to none, your model isn't going to be updated. You'll need to pull out any values with getSubmittedValue(). Note that you can't have it both ways -- if you're not validating data, then you can't update the model since the data may not be valid. You really want to be preserving your submitted values, not your model values. Ok, that's reasonable. How can I preserve the submitted values instead of trying to get the model values updated so I can preserve them? Thanks, Rich -Mike On 8/24/05, Richard Wallace [EMAIL PROTECTED] wrote: Hey everyone, I've got a form that has a couple of optional command links on it. They are basically quick add buttons so a user can quickly add things to drop downs if they aren't there. When these quick add buttons are clicked the user is sent to an add page, the user enters the new info and is then redirected back to the original page where the new entry is selected and all the other data is preserved from before they clicked the quick add button. The backing beans involved are request scoped and the values filled in before clicking the quick add button are preserved through the process using the t:saveState element. I'm trying to get the validation correct. I want all the form elements to be required when the user clicks the submit button, but when they hit the quick add link the validation should be bypassed. I thought of doing this with the immediate attribute set to true on the quick add command links but if I do that then any data the user entered on that page load (contact info type stuff) is lost. So I kind of need to bypass the validation but still update the model values if one of the command links are clicked, but have full validation done when the command button is pressed. I was looking at the new OptionalValidation Framework but I'm not sure exactly how to apply it in this case. I mean, what I really want is to have the validation type be none when command links are used and hard otherwise. Any ideas? Thanks, Rich
Re: Bypassing validation while still preserving values
There's probably better ways of doing it outside of my novice experience, but I'd either hardcode in the logic to retrieve and store each value (if it's not too much work to manage it), or I'd manually call saveState on the full component tree and maybe pass that in as the value of a t:saveState component. Actually, this second approach seems the most reasonable to me, although I'm not entirely sure how you'd reconstruct the component tree when you were done. There's also a ComponentWalker in the OptValFW that you could subclass to manually walk through each component in the tree and use to save/restore each UIInput's submitted values . On 8/25/05, Richard Wallace [EMAIL PROTECTED] wrote: Mike Kienenberger wrote: Sorry, I've been on vacation the last week. The default for the Optional Validation Framework is hard, so it's just a matter of setting validation to none for your command links, and wrapping all of your validators/converters. Note that if validation is set to none, your model isn't going to be updated. You'll need to pull out any values with getSubmittedValue(). Note that you can't have it both ways -- if you're not validating data, then you can't update the model since the data may not be valid. You really want to be preserving your submitted values, not your model values. Ok, that's reasonable. How can I preserve the submitted values instead of trying to get the model values updated so I can preserve them? Thanks, Rich -Mike On 8/24/05, Richard Wallace [EMAIL PROTECTED] wrote: Hey everyone, I've got a form that has a couple of optional command links on it. They are basically quick add buttons so a user can quickly add things to drop downs if they aren't there. When these quick add buttons are clicked the user is sent to an add page, the user enters the new info and is then redirected back to the original page where the new entry is selected and all the other data is preserved from before they clicked the quick add button. The backing beans involved are request scoped and the values filled in before clicking the quick add button are preserved through the process using the t:saveState element. I'm trying to get the validation correct. I want all the form elements to be required when the user clicks the submit button, but when they hit the quick add link the validation should be bypassed. I thought of doing this with the immediate attribute set to true on the quick add command links but if I do that then any data the user entered on that page load (contact info type stuff) is lost. So I kind of need to bypass the validation but still update the model values if one of the command links are clicked, but have full validation done when the command button is pressed. I was looking at the new OptionalValidation Framework but I'm not sure exactly how to apply it in this case. I mean, what I really want is to have the validation type be none when command links are used and hard otherwise. Any ideas? Thanks, Rich
Re: Redirect Tree2 _restoredState
Thanks Mathias. So, when will that move of methods be done? On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: No, I mean you can create your own method for expanding the tree in your backing bean and use some source code of the mentioned methods. But as I said thats not the way it should be ... maybe we should move the expand methods back to the TreeModel and leave the ones in UITreeData as delegates. If the functions are in the TreeModel you could then easily call them form your backing bean. [EMAIL PROTECTED] schrieb am 25.08.2005 15:57:33: Do you mean that my tree backing bean should implement the PhaseListener interface and be registered as a phase listener, so before render I could call the expandAll() method from the UITreeData? 2005/8/25, Sean Schofield [EMAIL PROTECTED]: What about adding a phase listener to expand the nodes just before rendering? Or as I have suggested before, Shale's prerender method? sean On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well its more a ugly hack than a solution, but as long as there are no methods for that in the TreeModel you could mimic the behaviour with customized code form the expandAll() and expandEverything() methods of UITreeData in your backing bean getter method that supplies the TreeModel.
url of the current page.
Hi When a page is loaded with a navigation rule, the url of that page will refer to the previous page's url, if the redirect is not set in the navigation rule. Is there any other way to set the url of the current page correctly without using the redirect in the navigation rule ? TIA -Srikanth Madarapu
Re: Spanish accents in Javascript
Maybe the ConvertEncoding class in this article from OnJava.com would be useful:
http://www.onjava.com/pub/a/onjava/excerpt/javaexIAN3_chap8/index.html
If not, it might at least give you an idea how to fix your issue.
-Matt
On 8/25/05, Enrique Medina [EMAIL PROTECTED] wrote:
Hi Matt,
Yes, the same thing occurs...2005/8/25, Matt Blum
[EMAIL PROTECTED]:
What does it do now? The same thing as before?
-MattOn 8/25/05, Enrique Medina
[EMAIL PROTECTED] wrote:
I have tried to define my properties file (resource bundle) using Unicode encodings:
combiVariables_ValidacionOK = La f\u00F3rmula es correcta
combiVariables_ValidacionNotOK = La f\u00F3rmula no es correcta
But it still doesn't work :-(2005/8/25, Enrique Medina [EMAIL PROTECTED]
:
Thanks. Let me try it ;-)2005/8/25, Matt Blum [EMAIL PROTECTED]:
I understand that. I'm suggesting that, instead of La fórmula es correcta in your properties file, you put La f\u00f3rmula es correcta.
-MattOn 8/24/05, Enrique Medina [EMAIL PROTECTED]
wrote:
Hi Matt,
But the problem is that encoding is generated by JSF when using EL like this:
#{messages.literal1}2005/8/24, Matt Blum [EMAIL PROTECTED]:
You need to use the Unicode encoding for the character, like so:
La f\u00f3rmula es correcta
There's a handy online tool to find the codes for most special characters here:
http://www.saila.com/usage/tips/examples/special_characters.html
-MattOn 8/24/05, Enrique Medina
[EMAIL PROTECTED]
wrote:Hi,
I know this is not a question directly related with MyFaces, but does anybody knows how to solve this problem?
I define my literal strings in a properties file, and then I have
created a custom messages tag that renders the message as an alert of
_javascript_. So when a JSF message is generated, it is rendered as an
alert. My problem is with accents. For example, in the alert window the
text appears like:
La f#243;rmula es correcta
while it should be:
La fórmula es correcta
Is it a matter of escaping the text in _javascript_? Because I have tried the escape() function but with no success...
Re: url of the current page.
May I ask why the URL is needed? Obviously the controller uses this - but when an application developer needs it, it may indicate the logic is location specific, and therefore not portable. Original message Date: Thu, 25 Aug 2005 14:20:29 -0400 From: Srikanth Madarapu [EMAIL PROTECTED] Subject: url of the current page. To: Apache My Faces (E-mail) users@myfaces.apache.org Hi When a page is loaded with a navigation rule, the url of that page will refer to the previous page's url, if the redirect is not set in the navigation rule. Is there any other way to set the url of the current page correctly without using the redirect in the navigation rule ? TIA -Srikanth Madarapu Dennis Byrne
RE: url of the current page.
I have a page with an applet. That page is loaded with a navigation rule which cannot have redirect set to true. The applet on the resulting page may find that the client does not have JRE installed. On IE, in such case, the information bar appears with a message saying that this page needs some activeX control. When you click on that information bar the user will be given a choice of installing the control. When the user clicks on the install activex control, the browser is refreshing the page. Because the url of that page is actually pointing to the previous page the refresh is causing to back the previous page. If I can set the url of the current page with the correct url this wont happen. I think I have found a solution, not tested yet. I will post the results once I am done. But please give your input on how to solve this problem. Thanks Srikanth -Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 2:49 PM To: MyFaces Discussion Subject: Re: url of the current page. May I ask why the URL is needed? Obviously the controller uses this - but when an application developer needs it, it may indicate the logic is location specific, and therefore not portable. Original message Date: Thu, 25 Aug 2005 14:20:29 -0400 From: Srikanth Madarapu [EMAIL PROTECTED] Subject: url of the current page. To: Apache My Faces (E-mail) users@myfaces.apache.org Hi When a page is loaded with a navigation rule, the url of that page will refer to the previous page's url, if the redirect is not set in the navigation rule. Is there any other way to set the url of the current page correctly without using the redirect in the navigation rule ? TIA -Srikanth Madarapu Dennis Byrne
RE : Let's write that doc!
Well, -1 on that, actually. I am a great believer in wiki's, and I suggest that you won't copy the doc to the homepage, but link from the homepage to the wiki. One of the stifling things about the MyFaces documentation is that it is in Too Many Places. Nobody knows where to look exactly, people are not eager to work on doc's that are not the reals doc's, and create patches and submit them and stuff is far to time consuming. For writing doc's in the wiki, you don't need to checkout the source tree. This is enduser documentation, not developer documentation, so the overhead is stifling the work. I suggest we decide that the documentation will be the wiki. Let's move whatever there is in /forest/content to the wiki (users can do that), and kill that part it Subversion. The examples should stay. At a (much) later date, somebody could decide to create a pdf or a book based on the wiki, but that's another story, and not our current concern. On 25 Aug 2005, at 16:29, Martin Marinschek wrote: +1 ;) If you want to get involved even more, it would be great if you would add this documentation to the /forrest/content section of our sourcetree for viewing it on the homepage. (just send us patches, we will commit them) If not, just put it on the WIKI, and gradually we will move it over to the homepage. regards, Martin On 8/25/05, Clément Maignien [EMAIL PROTECTED]> wrote: +1 -Message d'origine- De : ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 16:16 À : MyFaces Discussion Objet : Let's write that doc! I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=http://wiki.apache.org/myfaces/MyFacesComponents>let's start documenting those components/a>. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message> instead of h:message>. -Ken sean Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German x-tad-smallerMet vriendelijke groeten, Jan Dockx /x-tad-smallerx-tad-smaller PeopleWare NV - Head Office/x-tad-smallerx-tad-smaller Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 /x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller PeopleWare NV - Branch Office Geel/x-tad-smallerx-tad-smaller Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25/x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller http://www.peopleware.be/ /x-tad-smallerx-tad-smallerhttp://www.mobileware.be//x-tad-smaller smime.p7s Description: S/MIME cryptographic signature
Re: Redirect Tree2 _restoredState
Not until after the release. IMO this is a minor feature and we don't want to risk breaking other aspects of tree2 just before the release. sean On 8/25/05, Enrique Medina [EMAIL PROTECTED] wrote: Thanks Mathias. So, when will that move of methods be done? On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: No, I mean you can create your own method for expanding the tree in your backing bean and use some source code of the mentioned methods. But as I said thats not the way it should be ... maybe we should move the expand methods back to the TreeModel and leave the ones in UITreeData as delegates. If the functions are in the TreeModel you could then easily call them form your backing bean. [EMAIL PROTECTED] schrieb am 25.08.2005 15:57:33: Do you mean that my tree backing bean should implement the PhaseListener interface and be registered as a phase listener, so before render I could call the expandAll() method from the UITreeData? 2005/8/25, Sean Schofield [EMAIL PROTECTED]: What about adding a phase listener to expand the nodes just before rendering? Or as I have suggested before, Shale's prerender method? sean On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well its more a ugly hack than a solution, but as long as there are no methods for that in the TreeModel you could mimic the behaviour with customized code form the expandAll() and expandEverything() methods of UITreeData in your backing bean getter method that supplies the TreeModel.
Re: RE : Let's write that doc!
I disagree with moving stuff from the website to the wiki. I think the component doc should go on the website and be part of the official MyFaces svn. This will also ensure uniform standards and quality of the doc. If users want to put extra component doc in the wiki (or are not comfortable with Forrest or subversion) then as Martin said, this will be a small help b/c eventually we can move it. IMO wiki is also a good candidate for server configuration, IDE configuration, etc. Additional examples are also fine for wiki. But documentation on the components should be on the website. That's what is expected. Check out the Ant project. You will see all of the tasks documented right there (no wiki.) sean On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED] wrote: Well, -1 on that, actually. I am a great believer in wiki's, and I suggest that you won't copy the doc to the homepage, but link from the homepage to the wiki. One of the stifling things about the MyFaces documentation is that it is in Too Many Places. Nobody knows where to look exactly, people are not eager to work on doc's that are not the reals doc's, and create patches and submit them and stuff is far to time consuming. For writing doc's in the wiki, you don't need to checkout the source tree. This is enduser documentation, not developer documentation, so the overhead is stifling the work. I suggest we decide that the documentation will be the wiki. Let's move whatever there is in /forest/content to the wiki (users can do that), and kill that part it Subversion. The examples should stay. At a (much) later date, somebody could decide to create a pdf or a book based on the wiki, but that's another story, and not our current concern. On 25 Aug 2005, at 16:29, Martin Marinschek wrote: +1 ;) If you want to get involved even more, it would be great if you would add this documentation to the /forrest/content section of our sourcetree for viewing it on the homepage. (just send us patches, we will commit them) If not, just put it on the WIKI, and gradually we will move it over to the homepage. regards, Martin On 8/25/05, Clément Maignien [EMAIL PROTECTED] wrote: +1 -Message d'origine- De : ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 16:16 À : MyFaces Discussion Objet : Let's write that doc! I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=http://wiki.apache.org/myfaces/MyFacesComponents;let's start documenting those components/a. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message instead of h:message. -Ken sean Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/
Re: RE : Let's write that doc!
I totally agree with Sean. Wikis are great for additional info! I like the idea though to link from the homepage component page to the wiki page, to find that link faster. regards, Martin On 8/25/05, Sean Schofield [EMAIL PROTECTED] wrote: I disagree with moving stuff from the website to the wiki. I think the component doc should go on the website and be part of the official MyFaces svn. This will also ensure uniform standards and quality of the doc. If users want to put extra component doc in the wiki (or are not comfortable with Forrest or subversion) then as Martin said, this will be a small help b/c eventually we can move it. IMO wiki is also a good candidate for server configuration, IDE configuration, etc. Additional examples are also fine for wiki. But documentation on the components should be on the website. That's what is expected. Check out the Ant project. You will see all of the tasks documented right there (no wiki.) sean On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED] wrote: Well, -1 on that, actually. I am a great believer in wiki's, and I suggest that you won't copy the doc to the homepage, but link from the homepage to the wiki. One of the stifling things about the MyFaces documentation is that it is in Too Many Places. Nobody knows where to look exactly, people are not eager to work on doc's that are not the reals doc's, and create patches and submit them and stuff is far to time consuming. For writing doc's in the wiki, you don't need to checkout the source tree. This is enduser documentation, not developer documentation, so the overhead is stifling the work. I suggest we decide that the documentation will be the wiki. Let's move whatever there is in /forest/content to the wiki (users can do that), and kill that part it Subversion. The examples should stay. At a (much) later date, somebody could decide to create a pdf or a book based on the wiki, but that's another story, and not our current concern. On 25 Aug 2005, at 16:29, Martin Marinschek wrote: +1 ;) If you want to get involved even more, it would be great if you would add this documentation to the /forrest/content section of our sourcetree for viewing it on the homepage. (just send us patches, we will commit them) If not, just put it on the WIKI, and gradually we will move it over to the homepage. regards, Martin On 8/25/05, Clément Maignien [EMAIL PROTECTED] wrote: +1 -Message d'origine- De : ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 16:16 À : MyFaces Discussion Objet : Let's write that doc! I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=http://wiki.apache.org/myfaces/MyFacesComponents;let's start documenting those components/a. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message instead of h:message. -Ken sean Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
Re: RE : Let's write that doc!
You obviously have a lot of time at your disposal ;-). But hey, it's you project. I was writing some doc's on the wiki right now, but I am not going to go through the hassle of creating patches and stuff. You obviously want tight control, and you're welcome to that, of course. Sadly, that means no doc's by Monday, created by a giant, well-willing, communal user effort. ;-). Bummer. On 25 Aug 2005, at 21:08, Sean Schofield wrote: I disagree with moving stuff from the website to the wiki. I think the component doc should go on the website and be part of the official MyFaces svn. This will also ensure uniform standards and quality of the doc. If users want to put extra component doc in the wiki (or are not comfortable with Forrest or subversion) then as Martin said, this will be a small help b/c eventually we can move it. IMO wiki is also a good candidate for server configuration, IDE configuration, etc. Additional examples are also fine for wiki. But documentation on the components should be on the website. That's what is expected. Check out the Ant project. You will see all of the tasks documented right there (no wiki.) sean On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED]> wrote: Well, -1 on that, actually. I am a great believer in wiki's, and I suggest that you won't copy the doc to the homepage, but link from the homepage to the wiki. One of the stifling things about the MyFaces documentation is that it is in Too Many Places. Nobody knows where to look exactly, people are not eager to work on doc's that are not the reals doc's, and create patches and submit them and stuff is far to time consuming. For writing doc's in the wiki, you don't need to checkout the source tree. This is enduser documentation, not developer documentation, so the overhead is stifling the work. I suggest we decide that the documentation will be the wiki. Let's move whatever there is in /forest/content to the wiki (users can do that), and kill that part it Subversion. The examples should stay. At a (much) later date, somebody could decide to create a pdf or a book based on the wiki, but that's another story, and not our current concern. On 25 Aug 2005, at 16:29, Martin Marinschek wrote: +1 ;) If you want to get involved even more, it would be great if you would add this documentation to the /forrest/content section of our sourcetree for viewing it on the homepage. (just send us patches, we will commit them) If not, just put it on the WIKI, and gradually we will move it over to the homepage. regards, Martin On 8/25/05, Clément Maignien [EMAIL PROTECTED]> wrote: +1 -Message d'origine- De : ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 16:16 À : MyFaces Discussion Objet : Let's write that doc! I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=http://wiki.apache.org/myfaces/MyFacesComponents>let's start documenting those components/a>. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message> instead of h:message>. -Ken sean Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ x-tad-smallerMet vriendelijke groeten, Jan Dockx /x-tad-smallerx-tad-smaller PeopleWare NV - Head Office/x-tad-smallerx-tad-smaller Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 /x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller PeopleWare NV - Branch Office Geel/x-tad-smallerx-tad-smaller Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14
Re: RE : Let's write that doc!
No one is saying that you shouldn't write the docs on the wiki. They're just saying that the official version of the documentation is in svn, and that documentation in the wiki eventually needs to be ported over to the website, and that submitting a patch to do so make the process go faster. In my opinion, this is the correct choice. The website/xml docs are something that can be distributed and used without an internet connection, while the wiki requires an active internet connection. -Mike On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED] wrote: You obviously have a lot of time at your disposal ;-). But hey, it's you project. I was writing some doc's on the wiki right now, but I am not going to go through the hassle of creating patches and stuff. You obviously want tight control, and you're welcome to that, of course. Sadly, that means no doc's by Monday, created by a giant, well-willing, communal user effort. ;-). Bummer. On 25 Aug 2005, at 21:08, Sean Schofield wrote: I disagree with moving stuff from the website to the wiki. I think the component doc should go on the website and be part of the official MyFaces svn. This will also ensure uniform standards and quality of the doc. If users want to put extra component doc in the wiki (or are not comfortable with Forrest or subversion) then as Martin said, this will be a small help b/c eventually we can move it. IMO wiki is also a good candidate for server configuration, IDE configuration, etc. Additional examples are also fine for wiki. But documentation on the components should be on the website. That's what is expected. Check out the Ant project. You will see all of the tasks documented right there (no wiki.) sean On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED] wrote: Well, -1 on that, actually. I am a great believer in wiki's, and I suggest that you won't copy the doc to the homepage, but link from the homepage to the wiki. One of the stifling things about the MyFaces documentation is that it is in Too Many Places. Nobody knows where to look exactly, people are not eager to work on doc's that are not the reals doc's, and create patches and submit them and stuff is far to time consuming. For writing doc's in the wiki, you don't need to checkout the source tree. This is enduser documentation, not developer documentation, so the overhead is stifling the work. I suggest we decide that the documentation will be the wiki. Let's move whatever there is in /forest/content to the wiki (users can do that), and kill that part it Subversion. The examples should stay. At a (much) later date, somebody could decide to create a pdf or a book based on the wiki, but that's another story, and not our current concern. On 25 Aug 2005, at 16:29, Martin Marinschek wrote: +1 ;) If you want to get involved even more, it would be great if you would add this documentation to the /forrest/content section of our sourcetree for viewing it on the homepage. (just send us patches, we will commit them) If not, just put it on the WIKI, and gradually we will move it over to the homepage. regards, Martin On 8/25/05, Clément Maignien [EMAIL PROTECTED] wrote: +1 -Message d'origine- De : ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 16:16 À : MyFaces Discussion Objet : Let's write that doc! I suggest that we make this a user effort. Everybody, make an account in the wiki, and a href=http://wiki.apache.org/myfaces/MyFacesComponents;let's start documenting those components/a. If everybody writes a little piece (what is it for, how to use it), we'll have full documentation by Monday. I just added a little grain. More to come, I promise. On 25 Aug 2005, at 15:30, Sean Schofield wrote: Thanks so much for pointing out that messages tag. I was just about to write something similar because I didn't know about it. Is it listed somewhere on the MyFaces website? I don't see it here: http://myfaces.apache.org/tomahawk/overview.html Unfortunately that page is woefully out of date. Updating it is on my shortlist of things to do. Regarding your comment on it being specific to MyFaces: Isn't it only specific to the MyFaces extensions? In other words, couldn't I use it with the RI as long as I included the myfaces-extensions-1.0.9.jar and referenced the taglib? Right you can use tomahawk with the RI and if you want that functionality use t:message instead of h:message. -Ken sean Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ --
Any implementations of DataTable let you use a Map?
Are there any components that let me build a DataTable from a Map? (currently it's sort of a pain having to covert my Map to a List to be used by the DataTable). -- Rick
Re: RE : Let's write that doc!
I'm not saying *I* am not writing doc's on the wiki. I am saying that with these rules, there won't be a giant, inspired, communal effort to create the docs. I *am* saying that I will not be submitting patches for documentation, and that I suspect nobody will, because of the large effort this requires, in contrast to editing a wiki. And with this setup, that effort (during a development project at your day time job, with an undoubtedly impossible deadline) doesn't weigh against the eeny weeny gain in your noösphere ;-). Like all OSS, it's about scratching your own itch. People are simply not inclined to work on make-believe material, and right now the wiki is playing house, not the 'real' stuff. Imagine the people at WikiPedia saying yeah, yeah, but what you type here is not interesting, not 'real', you should see the 'real' stuff we do. And with what I am seeing on progress you make on the code, the pain it takes to get to a next stable version, and the effort that goes in there (see the masses of communication on the mailing list and in the JIRA), I believe the project people (kudo's) won't have the time to copy doc's to svn. Let's be honest: this hasn't been a serious consideration in the past. Yes, this is a note of critique: this project is seriously under-documented (not only in the user doc's, but also in the source code, BTW). So, by combining these opinions, I come to the conclusion that there will be no, not even mediocre, evolving, user documentation in the foreseeable future. Like I said: bummer. Frankly, this discussion (I really didn't intend on starting, but it's a slow night here ;-)) reminds me a bit of the discussion 2 months ago about using maven or not. It is clear that the project leaders are not comfortable, in this case, with the basic idea of wiki. We have a different opinion on that (I have enormously positive experiences with wiki's), and that's ok. Still kudo's and muchas gracias for the MyFaces effort. On 25 Aug 2005, at 22:47, Mike Kienenberger wrote: No one is saying that you shouldn't write the docs on the wiki. They're just saying that the official version of the documentation is in svn, and that documentation in the wiki eventually needs to be ported over to the website, and that submitting a patch to do so make the process go faster. In my opinion, this is the correct choice. The website/xml docs are something that can be distributed and used without an internet connection, while the wiki requires an active internet connection. -Mike On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED]> wrote: You obviously have a lot of time at your disposal ;-). But hey, it's you project. I was writing some doc's on the wiki right now, but I am not going to go through the hassle of creating patches and stuff. You obviously want tight control, and you're welcome to that, of course. Sadly, that means no doc's by Monday, created by a giant, well-willing, communal user effort. ;-). Bummer. On 25 Aug 2005, at 21:08, Sean Schofield wrote: I disagree with moving stuff from the website to the wiki. I think the component doc should go on the website and be part of the official MyFaces svn. This will also ensure uniform standards and quality of the doc. If users want to put extra component doc in the wiki (or are not comfortable with Forrest or subversion) then as Martin said, this will be a small help b/c eventually we can move it. IMO wiki is also a good candidate for server configuration, IDE configuration, etc. Additional examples are also fine for wiki. But documentation on the components should be on the website. That's what is expected. Check out the Ant project. You will see all of the tasks documented right there (no wiki.) sean On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED]> wrote: Well, -1 on that, actually. I am a great believer in wiki's, and I suggest that you won't copy the doc to the homepage, but link from the homepage to the wiki. One of the stifling things about the MyFaces documentation is that it is in Too Many Places. Nobody knows where to look exactly, people are not eager to work on doc's that are not the reals doc's, and create patches and submit them and stuff is far to time consuming. For writing doc's in the wiki, you don't need to checkout the source tree. This is enduser documentation, not developer documentation, so the overhead is stifling the work. I suggest we decide that the documentation will be the wiki. Let's move whatever there is in /forest/content to the wiki (users can do that), and kill that part it Subversion. The examples should stay. At a (much) later date, somebody could decide to create a pdf or a book based on the wiki, but that's another story, and not our current concern. On 25 Aug 2005, at 16:29, Martin Marinschek wrote: +1 ;) If you want to get involved even more, it would be great if you would add this documentation to the /forrest/content section of our sourcetree for viewing it on the homepage. (just send us
Re: RE : Let's write that doc!
No one is saying that you shouldn't write the docs on the wiki. They're just saying that the official version of the documentation is in svn, and that documentation in the wiki eventually needs to be ported over to the website, and that submitting a patch to do so make the process go faster. Exactly. -Mike sean
Re: RE : Let's write that doc!
It's not too hard to write forrest documentation. It takes a little bit of effort and if you or any other user does not want to put forth that effort then fine. As for your lack of interest in creating svn patches ... well that is how things are done at the ASF. The project is not a giant free-for-all like a wiki is. We rely on our users to help us. There are many ways to help. The most important is this mailing list. Users helping other users. If you have something you want to share with other users then the wiki is fine. Nobody is afraid of wikis and if you look at what I said in my earlier post, I gave several examples of where wiki's are appropriate. In fact, I am the one who added a link to the wiki from our website and I made several updates to the wiki (for project management stuff) just yesterday. The tomahawk documentation is a key part of the MyFaces project that is every bit as important as the source code. So therefore we have chosen to put the same restrictions on this documentation as we do the source code. Yes that slows things down but you are focusing on the down-side. It also keeps things under control and useable. Again I refer you to other ASF projects (commons, ant, struts, etc.) Some have wikis but the key documentation on how to use the product is part of svn and under control of the PMC and committers. Sorry, that's just how ASF works. We're happy to accept consider any of your suggestions/contributions. If you would like to limit your contributions to mailing list participation and/or wiki documentation we welcome your help. I agree that there is a lack of documentation. We are working on it. We all have day jobs and things on this project are moving incredibly fast. Please bear with us or better yet, help us in the way we most need help (xdocs and svn patches.) sean I'm not saying *I* am not writing doc's on the wiki. I am saying that with these rules, there won't be a giant, inspired, communal effort to create the docs. I *am* saying that I will not be submitting patches for documentation, and that I suspect nobody will, because of the large effort this requires, in contrast to editing a wiki. And with this setup, that effort (during a development project at your day time job, with an undoubtedly impossible deadline) doesn't weigh against the eeny weeny gain in your noösphere ;-). Like all OSS, it's about scratching your own itch. People are simply not inclined to work on make-believe material, and right now the wiki is playing house, not the 'real' stuff. Imagine the people at WikiPedia saying yeah, yeah, but what you type here is not interesting, not 'real', you should see the 'real' stuff we do. And with what I am seeing on progress you make on the code, the pain it takes to get to a next stable version, and the effort that goes in there (see the masses of communication on the mailing list and in the JIRA), I believe the project people (kudo's) won't have the time to copy doc's to svn. Let's be honest: this hasn't been a serious consideration in the past. Yes, this is a note of critique: this project is seriously under-documented (not only in the user doc's, but also in the source code, BTW). So, by combining these opinions, I come to the conclusion that there will be no, not even mediocre, evolving, user documentation in the foreseeable future. Like I said: bummer. Frankly, this discussion (I really didn't intend on starting, but it's a slow night here ;-)) reminds me a bit of the discussion 2 months ago about using maven or not. It is clear that the project leaders are not comfortable, in this case, with the basic idea of wiki. We have a different opinion on that (I have enormously positive experiences with wiki's), and that's ok. Still kudo's and muchas gracias for the MyFaces effort. On 25 Aug 2005, at 22:47, Mike Kienenberger wrote: No one is saying that you shouldn't write the docs on the wiki. They're just saying that the official version of the documentation is in svn, and that documentation in the wiki eventually needs to be ported over to the website, and that submitting a patch to do so make the process go faster. In my opinion, this is the correct choice. The website/xml docs are something that can be distributed and used without an internet connection, while the wiki requires an active internet connection. -Mike On 8/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED] wrote: You obviously have a lot of time at your disposal ;-). But hey, it's you project. I was writing some doc's on the wiki right now, but I am not going to go through the hassle of creating patches and stuff. You obviously want tight control, and you're welcome to that, of course. Sadly, that means no doc's by Monday, created by a giant, well-willing, communal user effort. ;-). Bummer. On 25 Aug 2005, at 21:08, Sean Schofield wrote: I disagree with moving stuff from the website to the
x:convertBoolean
JSF has f:convertDateTime and f:convertNumber, but nothing I've
seen to convert Booleans to custom values. Has something like
x:convertBoolean already been written by anyone? I have just
written one and would be willing to contribute it to MyFaces if there
is interest.
It is used like this:
h:outputText value=#{backingBean.isABooleanValue}
x:convertBoolean trueValue=Yes falseValue=No/
/h:outputText
-Ken
Re: x:convertBoolean
Looks convenient Ken. Please post your code. I would like to see it, even if this does not make it to the issue tracker. Dennis Byrne
RE: url of the current page.
Instead of using the navigation rule I am calling the externalContext.redirect(url) and returning null from the backing bean method. Dennis Byrne: Did you get any ideas ? Srikanth -Original Message- From: Srikanth Madarapu Sent: Thursday, August 25, 2005 2:57 PM To: MyFaces Discussion Subject: RE: url of the current page. I have a page with an applet. That page is loaded with a navigation rule which cannot have redirect set to true. The applet on the resulting page may find that the client does not have JRE installed. On IE, in such case, the information bar appears with a message saying that this page needs some activeX control. When you click on that information bar the user will be given a choice of installing the control. When the user clicks on the install activex control, the browser is refreshing the page. Because the url of that page is actually pointing to the previous page the refresh is causing to back the previous page. If I can set the url of the current page with the correct url this wont happen. I think I have found a solution, not tested yet. I will post the results once I am done. But please give your input on how to solve this problem. Thanks Srikanth -Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 2:49 PM To: MyFaces Discussion Subject: Re: url of the current page. May I ask why the URL is needed? Obviously the controller uses this - but when an application developer needs it, it may indicate the logic is location specific, and therefore not portable. Original message Date: Thu, 25 Aug 2005 14:20:29 -0400 From: Srikanth Madarapu [EMAIL PROTECTED] Subject: url of the current page. To: Apache My Faces (E-mail) users@myfaces.apache.org Hi When a page is loaded with a navigation rule, the url of that page will refer to the previous page's url, if the redirect is not set in the navigation rule. Is there any other way to set the url of the current page correctly without using the redirect in the navigation rule ? TIA -Srikanth Madarapu Dennis Byrne
Re: x:convertBoolean
Suggestion: Add an issue to JIRA (select sandbox as the component type.) This gives committers a chance to shout down any ideas they find completely objectionable so you don't waste your time (this is not one of those ideas btw.) Then provide a SVN patch and we'll add it to sandbox. Be prepared to provide documentation and a simple example (or add to an existing simple example) when appropriate. The docs and examples are now required for new tomahawk goodies. sean On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Looks convenient Ken. Please post your code. I would like to see it, even if this does not make it to the issue tracker. Dennis Byrne
Re: url of the current page.
You can also configure a navigation rule to use redirect. sean On 8/25/05, Srikanth Madarapu [EMAIL PROTECTED] wrote: Instead of using the navigation rule I am calling the externalContext.redirect(url) and returning null from the backing bean method. Dennis Byrne: Did you get any ideas ? Srikanth -Original Message- From: Srikanth Madarapu Sent: Thursday, August 25, 2005 2:57 PM To: MyFaces Discussion Subject: RE: url of the current page. I have a page with an applet. That page is loaded with a navigation rule which cannot have redirect set to true. The applet on the resulting page may find that the client does not have JRE installed. On IE, in such case, the information bar appears with a message saying that this page needs some activeX control. When you click on that information bar the user will be given a choice of installing the control. When the user clicks on the install activex control, the browser is refreshing the page. Because the url of that page is actually pointing to the previous page the refresh is causing to back the previous page. If I can set the url of the current page with the correct url this wont happen. I think I have found a solution, not tested yet. I will post the results once I am done. But please give your input on how to solve this problem. Thanks Srikanth -Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 2:49 PM To: MyFaces Discussion Subject: Re: url of the current page. May I ask why the URL is needed? Obviously the controller uses this - but when an application developer needs it, it may indicate the logic is location specific, and therefore not portable. Original message Date: Thu, 25 Aug 2005 14:20:29 -0400 From: Srikanth Madarapu [EMAIL PROTECTED] Subject: url of the current page. To: Apache My Faces (E-mail) users@myfaces.apache.org Hi When a page is loaded with a navigation rule, the url of that page will refer to the previous page's url, if the redirect is not set in the navigation rule. Is there any other way to set the url of the current page correctly without using the redirect in the navigation rule ? TIA -Srikanth Madarapu Dennis Byrne
Re: RE : Let's write that doc!
Trust me, I love the work you're doing. And I don't want to make enemies. Sadly, the response you sent confirms my analysis: you are very, very busy after hours making great code for MyFaces, and you have no time to spent on the documentation 'right now'. That next version needs shipping. You're being bugged by users on the mailing list that really need it, and you want to oblige. Furthermore, from looking at the history of the project, it is clear that the committers don't really have a natural drive towards user documentation. Now, that is not a complaint, that is not a reproach, it's however a fact. You're not alone in those dire straits, BTW ;-). But the fact remains that user documentation is not a priority for you, since the committers know the code from the inside, and don't have this itch: you don't need user documentation yourself. All this together makes that we will not have even mediocre user documentation for a while. That's a problem for your users. What I am suggesting is that you prioritize, and put the svn / forrest documentation on hold for now. Stabilize the code, and get that next version out! What you like to do, what you want to do, and what you are good at. In the mean while, lower the bar for users to scratch their itch, and motivate them to solve their own problem, and leave you to focus at the code. Yes, for users it is too hard to write forrest documentation. I work with a bunch of them. Seriously. Promote the wiki to official documentation at interim, and plan to move it to the svn / forrest documentation format at a later time, and respond to all emails with if you solved your issue, and you understand the component a bit better now, please report your findings in the wiki; it's 10 minutes work. At a later time, you will find an almost finished documentation set, you can work into the format you require. But I strongly believe that for that to succeed, 1) the bar needs to be extremely low for users 2) it needs to be 'official' (be it at interim) 3) new users need to be pointed to the 'growing documentation', directly, it can't be second tier (be it at interim) 4) and they need to be reminded constantly that they can easily contribute (mailing list) Sorry, couldn't resist on making my point. I hope I convinced the committers, but I'll leave it at this. I'm going to bed now ;-). On 26 Aug 2005, at 0:17, Sean Schofield wrote: It's not too hard to write forrest documentation. It takes a little bit of effort and if you or any other user does not want to put forth that effort then fine. As for your lack of interest in creating svn patches ... well that is how things are done at the ASF. The project is not a giant free-for-all like a wiki is. We rely on our users to help us. There are many ways to help. The most important is this mailing list. Users helping other users. If you have something you want to share with other users then the wiki is fine. Nobody is afraid of wikis and if you look at what I said in my earlier post, I gave several examples of where wiki's are appropriate. In fact, I am the one who added a link to the wiki from our website and I made several updates to the wiki (for project management stuff) just yesterday. The tomahawk documentation is a key part of the MyFaces project that is every bit as important as the source code. So therefore we have chosen to put the same restrictions on this documentation as we do the source code. Yes that slows things down but you are focusing on the down-side. It also keeps things under control and useable. Again I refer you to other ASF projects (commons, ant, struts, etc.) Some have wikis but the key documentation on how to use the product is part of svn and under control of the PMC and committers. Sorry, that's just how ASF works. We're happy to accept consider any of your suggestions/contributions. If you would like to limit your contributions to mailing list participation and/or wiki documentation we welcome your help. I agree that there is a lack of documentation. We are working on it. We all have day jobs and things on this project are moving incredibly fast. Please bear with us or better yet, help us in the way we most need help (xdocs and svn patches.) sean I'm not saying *I* am not writing doc's on the wiki. I am saying that with these rules, there won't be a giant, inspired, communal effort to create the docs. I *am* saying that I will not be submitting patches for documentation, and that I suspect nobody will, because of the large effort this requires, in contrast to editing a wiki. And with this setup, that effort (during a development project at your day time job, with an undoubtedly impossible deadline) doesn't weigh against the eeny weeny gain in your noösphere ;-). Like all OSS, it's about scratching your own itch. People are simply not inclined to work on make-believe material, and right now the wiki is playing house, not the 'real' stuff. Imagine the people at WikiPedia saying
Re: [jira] Commented: (MYFACES-447) tree2 TreeNode interface has too many methods
Now we are on the list, and we can discuss this ;-). The first suggested patch doesn't influence anybody, actually, since the methods that are removed from the interface are not used by any tree2 code. And TreeNodeBase keeps behaving as it did before (actually, for it should better be changed too, but it should stay in now at least for backward compatibility reasons). The second suggested patch takes cleaning up the interface further. But since the differences between isLeaf(), getChildren().isEmpty() and getChildCount() == 0 on the one hand, and getChildren().size() and getChildCount() on the other hand, are rather obscure (and, as far as I can see, not applied consistently in the existing tree2 code either), I bet that there are not that many users out there that depend on the differences. If so, please let me know here: it might increase my understanding of the differences. And if your current implementation of a TreeNode is consistent (getChildCount() == getChildren().size() and isLeaf() ==> getChildren().isEmpty() ==> getChildCount() == 0), this change will not affect your code either, since that is how the code is changed in tree2 implementation. On 26 Aug 2005, at 1:10, sean schofield (JIRA) wrote: [ http://issues.apache.org/jira/browse/MYFACES-447?page=comments#action_12320067 ] sean schofield commented on MYFACES-447: No you did not miss a discussion. Don't worry this patch will not be applied in the short term for a few reasons. The first reason is that it is too close to release time to change an interface. The second reason is that we will need to do extensive review and consultation with users before a major change such as this. I'm definitely interested in improving tree2 so I will take a close look at this patch when I get a chance. We can discuss the changes now even if we don't make them for a while. @Jan JIRA is a good place to discuss matters like this (especially when patches are provided to help illustrate the requestor's point.) In the future can you also email the user list if you have a *major* change of this nature? Let them know the JIRA link. That way nobody gets left out of a crucial discussion. Bug fixes or minor feature additions (that's don't impact existing features, interfaces) can go directly to JIRA though. This is kind of a special case b/c its a major change. @Dennis You may want to add yourself as a watcher to issues when you do spot them on the dev list. Now that you know you're interested, why take the chance on missing out on an important discussion? tree2 TreeNode interface has too many methods - Key: MYFACES-447 URL: http://issues.apache.org/jira/browse/MYFACES-447 Project: MyFaces Type: Improvement Components: Tomahawk Versions: Nightly Build Reporter: Jan Dockx Attachments: tree2_TreeNode_extensive_patch.txt, tree2_TreeNode_extensive_patch_examples.txt, tree2_TreeNode_patch.txt The TreeNode interface is the hook for the backing bean developer, the user, into the tree2 framework. As such, the interface should pose minimal requirements for the user. It should only require from the user to implement those methods that are strictly needed for the framework to work, and leave as much freedom for the user as possible. The patch included removes unnecessary methods. Apart from a minor change in TreeNodeBase, the change doesn't affect the existing tree2 code, nor the example, at all. The patch also contains some documentation for the interface, and some suggestions for further changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira x-tad-smallerMet vriendelijke groeten, Jan Dockx /x-tad-smallerx-tad-smaller PeopleWare NV - Head Office/x-tad-smallerx-tad-smaller Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 /x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller PeopleWare NV - Branch Office Geel/x-tad-smallerx-tad-smaller Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25/x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller http://www.peopleware.be/ /x-tad-smallerx-tad-smallerhttp://www.mobileware.be//x-tad-smaller smime.p7s Description: S/MIME cryptographic signature
RE: url of the current page.
Why can't the navigation rule ... have redirect set to true? Dennis Byrne
Re: x:convertBoolean
Ok, great, I will get familiar with the sandbox, change my code to follow the packages for tomahawk, and submit patches to JIRA. Looking forward to participating... On 8/25/05, Sean Schofield [EMAIL PROTECTED] wrote: Suggestion: Add an issue to JIRA (select sandbox as the component type.) This gives committers a chance to shout down any ideas they find completely objectionable so you don't waste your time (this is not one of those ideas btw.) Then provide a SVN patch and we'll add it to sandbox. Be prepared to provide documentation and a simple example (or add to an existing simple example) when appropriate. The docs and examples are now required for new tomahawk goodies. sean On 8/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Looks convenient Ken. Please post your code. I would like to see it, even if this does not make it to the issue tracker. Dennis Byrne
RE: url of the current page.
If I set the redirect to true, the attributes in the request are gone which are set by the previous page of my applet page. With externalContext.redirect(url) I am sending the attributes as parameters. I hope I made it clear now. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]Sent: Thursday, August 25, 2005 7:37 PMTo: MyFaces DiscussionSubject: RE: url of the current page.Why can't the "navigation rule ... have redirect set to true"? Dennis Byrne
Re: [jira] Commented: (MYFACES-447) tree2 TreeNode interface has too many methods
The first suggested patch doesn't influence anybody Your words, in JIRA: The TreeNode interface is the hook for the backing bean developer, the user, into the tree2 framework. If the TreeNode interface is the hook for the backing bean developer, and the first patch changes the TreeNode interface ... how can the first patch not affect anybody?
Re: x:convertBoolean
I think you'll want to put it in a package for the sandbox, not tomahawk. I'd check to see if this is true, but http://svn.apache.org/repos/asf/myfaces/ gives me a gateway timeout. Dennis Byrne
