Re: [Trinidad] ppr: partialTriggers doesn't work if there are validation messages?
As I mentioned in the dev thread, only supporting messages for PPR requests with conversion and validation errors is not adequate for production usage. On 9/3/07, Adam Winer [EMAIL PROTECTED] wrote: This all seems like enormous overkill *just* to get messages sent down. We have Javascript that can insert messages on the client. All we need to do is lean slightly on that code to reuse it for inserting server-side messages, and this'll work fine without any architectural changes at all. -- Adam On 8/29/07, Andrew Robinson [EMAIL PROTECTED] wrote: After thinking it on some more and researching how Trinidad is handling the PPR triggers more, I thought that maybe the best solution is just a new component. I am already using such a component in my own project for a site I own. I just posted the code to JIRA so that you all can see it, comment on it and decide if you would like to have it as a core component of Trinidad. The issue: https://issues.apache.org/jira/browse/TRINIDAD-663 -Andrew
[tomahawk] jscookmenu and ajax
Hi all, I'm trying to get a jsCookMenu work with AJAX. I've tried to use a4j:commandLink and a4j:support. But nothing works ... The JS-script calls window.open(link) on the mouseup-event. I think this may be the problem ... Is there a way to get jsCookMenu work with AJAX ? Greetings Matze ___ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00 BEGIN:VCARD VERSION:2.1 N:Imhof;Matthias;;; FN:Matthias Imhof EMAIL;INTERNET:[EMAIL PROTECTED] END:VCARD
Re: Hi All ,Is it possibility Pipe(|) or Divider in DataScroller Pagination.....
Hi Adrian Mitev
Thanx for giving the response for my post.
but i am not getting the javascript code in nabble site. due to the security
reason.
i am getting the javascript message like this . (The Javascript code that
came with this message has been removed. Learn more about Nabble's security
policy. )
Extend the renderer class of the data scroller or use JavaScript to insert
the pipes :).
can u send me that code to my mail id please
[EMAIL PROTECTED]
sorry for asking like this
Thanks Regards
Suresh
inalasuresh wrote:
Hi Folks,
I am new to Jsf / Myfaces.
is there possibility to get the Pipe or Divider in DataScroller?
i am using datascroller in that scroller i want to use pipe(|)
symbol. in jsf/myfaces how to implement that.
If any body know the solution for this plz send rep as soon as
possible
Now onto my question..I would like to have a divider (|), but I don't
know how to implement it.
I know it is possible to do a border only on one side, but then one always
ends up after the Next button. Is there any way to do this? Thanks!
i am using this attribute in the datascroller
paginatorColumnClass=pipe
.pipe{
background-image:url(../images/divider.gif);
background-repeat:repeat-y;
}
But it not a correct approach and it willn't working properly
e.g.: Like such type of pipe symbol(|) i want to use in between those
number.
1 | 2 | 3 | 4| 5 |
So plz Kindly response my request.
--
View this message in context:
http://www.nabble.com/Hi-All-%2CIs-it-possibility-Pipe%28%7C%29-or-Divider-in-DataScroller-Pagination.-tf4372197.html#a12472571
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Tobago] EmptyStackException in datepicker
Hi, seems this is not only the datePicker, I just got a EmptyStackException in a page without datePicker. java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at java.util.Stack.pop(Stack.java:61) at org.apache.myfaces.tobago.webapp.TobagoResponseWriterImpl.endElement(TobagoResponseWriterImpl.java:232) at org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent(TabGroupRenderer.java:80) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView(TabGroupRenderer.java:342) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.encodeAjax(TabGroupRenderer.java:368) I'm going to look at this. Regards, Volker 2007/9/3, Helmut Swaczinna [EMAIL PROTECTED]: Hi, in the current snapshot the datepicker is broken. You get an EmptyStackException when you click on the picker image. You can see this in the demo. Regards Helmut
Re: Why so many components?
Andrew, I was about to use A4J in that combination without any experience with. Your support on that has been priceless. Thank you so much again. - Original Message From: Andrew Robinson [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Monday, September 3, 2007 11:54:16 PM Subject: Re: Why so many components? FYI, I don't recommend that you use A4J in that combination unless you need RichFaces. Just use the PPR functionality in Trinidad. You will most likely have rendering problems with Trinidad+A4J See http://myfaces.apache.org/trinidad/devguide/ppr.html for information on Trinidad's AJAX -Andrew On 9/3/07, distillingweb [EMAIL PROTECTED] wrote: Hello, I know this use to be a obvious choice, but because I am a newcomer in the MyFaces world, what answer I would give to my manager if he ask me why am I using so many components? Now, following advices, I am planning to use MyFaces + Trinidad + Tomahawk + Facelets + Ajax4JSF and maybe Seam. I know each of them provide different resources, but is there a couple or three of them that could give me like 90% of all my requirements need? Thank you in advance. Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/
[Trinidad] tr:column, attribute shortDesc not working?
Hi everyone,
either this is a bug or I'm not using it correctly, so:
How is the attribute shortDesc in tr:column supposed to work?
I have something like
tr:column headerText=Title shortDesc=My column tooltip
...
/tr:column
and I never see this column tooltip, neither on the header nor on the column
elements
(nothing rendered in the HTML as far as I can see, neither).
In case, that this might be of relevance here: I'm working in a Facelets
environment.
Note that if I put some element with its own tooltip/shortDesc like
tr:outputText value=#{person.title} shortDesc=The title for
#{person.title}
/tr:outputText
into the column then, of course, I see the element's tooltip...
I likewise get a tooltip when using facet header in tr:column, no problem
there:
f:facet name=header
tr:outputText value=Title shortDesc=The title for the given person
/
/f:facet
Any ideas about tr:columns shortDesc?
Thanks a lot,
Carsten
--
View this message in context:
http://www.nabble.com/-Trinidad--tr%3Acolumn%2C-attribute-shortDesc-not-working--tf4376587.html#a12474869
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Antwort: Re: Why so many components?
Hi, There is also another issue with Trinidad and integration if you use Seam: As of now, you cannot use it with tr:table unless you do the 'plumbing' into Seam yourself and even so it does not seem clear how to make the paging work.. See also http://pmuir.bleepbleep.org.uk/2007/04/backing-trinidads-datatable-with-seam.html Best, Wolfgang. distillingweb [EMAIL PROTECTED] 04.09.2007 11:08 Bitte antworten an MyFaces Discussion users@myfaces.apache.org An MyFaces Discussion users@myfaces.apache.org Kopie Thema Re: Why so many components? Andrew, I was about to use A4J in that combination without any experience with. Your support on that has been priceless. Thank you so much again. - Original Message From: Andrew Robinson [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Monday, September 3, 2007 11:54:16 PM Subject: Re: Why so many components? FYI, I don't recommend that you use A4J in that combination unless you need RichFaces. Just use the PPR functionality in Trinidad. You will most likely have rendering problems with Trinidad+A4J See http://myfaces.apache.org/trinidad/devguide/ppr.html for information on Trinidad's AJAX -Andrew On 9/3/07, distillingweb [EMAIL PROTECTED] wrote: Hello, I know this use to be a obvious choice, but because I am a newcomer in the MyFaces world, what answer I would give to my manager if he ask me why am I using so many components? Now, following advices, I am planning to use MyFaces + Trinidad + Tomahawk + Facelets + Ajax4JSF and maybe Seam. I know each of them provide different resources, but is there a couple or three of them that could give me like 90% of all my requirements need? Thank you in advance. Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV.
Re: Antwort: Re: Why so many components?
Wolfgang, Thanks for share this information and link. I was catch also for this comment in that link: Its things like this that have conviced me that its time to throw away a huge amount of in-house crufty stuff and move ahead with Seam/JSF for all of our new development. I did not understand if the comment is meant to replace Trinidad by using Seam or only some of the in-house components implementations in this context. Could you give me a hint on that? Thank you very much. - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Tuesday, September 4, 2007 11:56:34 AM Subject: Antwort: Re: Why so many components? Hi, There is also another issue with Trinidad and integration if you use Seam: As of now, you cannot use it with tr:table unless you do the 'plumbing' into Seam yourself and even so it does not seem clear how to make the paging work.. See also http://pmuir.bleepbleep.org.uk/2007/04/backing-trinidads-datatable-with-seam.html Best, Wolfgang. distillingweb [EMAIL PROTECTED] 04.09.2007 11:08 Bitte antworten an MyFaces Discussion users@myfaces.apache.org An MyFaces Discussion users@myfaces.apache.org Kopie Thema Re: Why so many components? Andrew, I was about to use A4J in that combination without any experience with. Your support on that has been priceless. Thank you so much again. - Original Message From: Andrew Robinson [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Monday, September 3, 2007 11:54:16 PM Subject: Re: Why so many components? FYI, I don't recommend that you use A4J in that combination unless you need RichFaces. Just use the PPR functionality in Trinidad. You will most likely have rendering problems with Trinidad+A4J See http://myfaces.apache.org/trinidad/devguide/ppr.html for information on Trinidad's AJAX -Andrew On 9/3/07, distillingweb [EMAIL PROTECTED] wrote: Hello, I know this use to be a obvious choice, but because I am a newcomer in the MyFaces world, what answer I would give to my manager if he ask me why am I using so many components? Now, following advices, I am planning to use MyFaces + Trinidad + Tomahawk + Facelets + Ajax4JSF and maybe Seam. I know each of them provide different resources, but is there a couple or three of them that could give me like 90% of all my requirements need? Thank you in advance. Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC
Antwort: Re: Antwort: Re: Why so many components?
Hi, Definitely the latter one (only some of the in-house..). Actually, I found the comment rather manager-like and not really very informative.. ;) I am looking forward to the Seam people and their Trinidad integration work. Otherwise we will have lots of different plumbing implementations around.. Best, Wolfgang. distillingweb [EMAIL PROTECTED] 04.09.2007 12:08 Bitte antworten an MyFaces Discussion users@myfaces.apache.org An MyFaces Discussion users@myfaces.apache.org Kopie Thema Re: Antwort: Re: Why so many components? Wolfgang, Thanks for share this information and link. I was catch also for this comment in that link: Its things like this that have conviced me that its time to throw away a huge amount of in-house crufty stuff and move ahead with Seam/JSF for all of our new development. I did not understand if the comment is meant to replace Trinidad by using Seam or only some of the in-house components implementations in this context. Could you give me a hint on that? Thank you very much. - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Tuesday, September 4, 2007 11:56:34 AM Subject: Antwort: Re: Why so many components? Hi, There is also another issue with Trinidad and integration if you use Seam: As of now, you cannot use it with tr:table unless you do the 'plumbing' into Seam yourself and even so it does not seem clear how to make the paging work.. See also http://pmuir.bleepbleep.org.uk/2007/04/backing-trinidads-datatable-with-seam.html Best, Wolfgang. distillingweb [EMAIL PROTECTED] 04.09.2007 11:08 Bitte antworten an MyFaces Discussion users@myfaces.apache.org An MyFaces Discussion users@myfaces.apache.org Kopie Thema Re: Why so many components? Andrew, I was about to use A4J in that combination without any experience with. Your support on that has been priceless. Thank you so much again. - Original Message From: Andrew Robinson [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Monday, September 3, 2007 11:54:16 PM Subject: Re: Why so many components? FYI, I don't recommend that you use A4J in that combination unless you need RichFaces. Just use the PPR functionality in Trinidad. You will most likely have rendering problems with Trinidad+A4J See http://myfaces.apache.org/trinidad/devguide/ppr.html for information on Trinidad's AJAX -Andrew On 9/3/07, distillingweb [EMAIL PROTECTED] wrote: Hello, I know this use to be a obvious choice, but because I am a newcomer in the MyFaces world, what answer I would give to my manager if he ask me why am I using so many components? Now, following advices, I am planning to use MyFaces + Trinidad + Tomahawk + Facelets + Ajax4JSF and maybe Seam. I know each of them provide different resources, but is there a couple or three of them that could give me like 90% of all my requirements need? Thank you in advance. Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. Got a little couch potato? Check out fun summer activities for kids.
Re: [Trinidad] Trinidad 1.2.1 demo on Tomcat 6.0.13
I happen to have the Trinidad 1.2.1 demo running in Tomcat 6.0.13. I had not looked at the Progress Steps demo before. When I did, I got the following: org.apache.jasper.JasperException: /demos/progressSteps.jspx(106,30) According to the TLD or the tag file, attribute text is mandatory for tag panelHeader org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:802) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838) ... I did things a little differently than described below. I opened the war and inserted the same JSF version files as described below along with JSTL 1.1.2 into the WEB-INF/libs folder, jarred up the contents into a new war and dropped this into the Tomcat webapps folder. The result is as stated above. Maybe the difference in error output will be helpful. -= Gregg =- Adam Winer wrote: This doesn't make much sense to me. That line is a tr:forEach element. In 1.2.1, the tld for forEach has attribute description the ending index /description nameend/name deferred-value typejava.lang.Integer/type /deferred-value /attribute ... so "end" absolutely supports EL. Whether there's a Tomcat bug or a setup issue here, I don't know. -- Adam On 8/30/07, Thai Dang Vu [EMAIL PROTECTED] wrote: Hi everybody, I dropped the trinidad 1.2.1 demo war file in the webapps folder of Tomcat 6, run tomcat so that it deployed that war file, stopped tomcat to dropped jsf-impl-1.2_04-p02.jar, jsf-api-1.2_04-p02.jar and jstl-1.2.jar in the trinidad-1.2.1-demo/WEB-INF/lib folder, started tomcat again and the Component Guide worked, but the Progress Step Demo didn't. This is the error: org.apache.jasper.JasperException: /demos/progressSteps.jspx(68,58) According to TLD or attribute directive in tag file, attribute end does not accept any expressions org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHand ler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java :407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java :148) org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes( Validator.java:1119) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:819) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
Re: [Trinidad] Trinidad 1.2.1 demo on Tomcat 6.0.13
The "text" attribute is indeed missing for the panelHeader tag on line 106 of the progressSteps.jspx file. Fixing this might fix the entire problem. -= Gregg =- Gregg Leichtman wrote: I happen to have the Trinidad 1.2.1 demo running in Tomcat 6.0.13. I had not looked at the Progress Steps demo before. When I did, I got the following: org.apache.jasper.JasperException: /demos/progressSteps.jspx(106,30) According to the TLD or the tag file, attribute text is mandatory for tag panelHeader org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:802) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838) ... I did things a little differently than described below. I opened the war and inserted the same JSF version files as described below along with JSTL 1.1.2 into the WEB-INF/libs folder, jarred up the contents into a new war and dropped this into the Tomcat webapps folder. The result is as stated above. Maybe the difference in error output will be helpful. -= Gregg =- Adam Winer wrote: This doesn't make much sense to me. That line is a tr:forEach element. In 1.2.1, the tld for forEach has attribute description the ending index /description nameend/name deferred-value typejava.lang.Integer/type /deferred-value /attribute ... so "end" absolutely supports EL. Whether there's a Tomcat bug or a setup issue here, I don't know. -- Adam On 8/30/07, Thai Dang Vu [EMAIL PROTECTED] wrote: Hi everybody, I dropped the trinidad 1.2.1 demo war file in the webapps folder of Tomcat 6, run tomcat so that it deployed that war file, stopped tomcat to dropped jsf-impl-1.2_04-p02.jar, jsf-api-1.2_04-p02.jar and jstl-1.2.jar in the trinidad-1.2.1-demo/WEB-INF/lib folder, started tomcat again and the Component Guide worked, but the Progress Step Demo didn't. This is the error: org.apache.jasper.JasperException: /demos/progressSteps.jspx(68,58) According to TLD or attribute directive in tag file, attribute end does not accept any expressions org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHand ler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java :407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java :148) org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes( Validator.java:1119) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:819) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
Re: [Tobago] EmptyStackException in datepicker
Hi Helmut, there was a Problem in the ButtonRenderer introduced with the changes for tabindex. Please try next nightly or build you own from svn head. Regards, Volker 2007/9/4, Volker Weber [EMAIL PROTECTED]: Hi, seems this is not only the datePicker, I just got a EmptyStackException in a page without datePicker. java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at java.util.Stack.pop(Stack.java:61) at org.apache.myfaces.tobago.webapp.TobagoResponseWriterImpl.endElement(TobagoResponseWriterImpl.java:232) at org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent(TabGroupRenderer.java:80) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView(TabGroupRenderer.java:342) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.encodeAjax(TabGroupRenderer.java:368) I'm going to look at this. Regards, Volker 2007/9/3, Helmut Swaczinna [EMAIL PROTECTED]: Hi, in the current snapshot the datepicker is broken. You get an EmptyStackException when you click on the picker image. You can see this in the demo. Regards Helmut
Re: trinidad outputFormat and f:param support
Should we look at providing this variable replacement functionality into
outputText. Although I'm against just parsing the text by default, as this
would just add unnecessary parsing in 99% of the cases. Should we instead
look at an extra attribute that forces parsing of the string for variable
substitution.
Danny
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
BTW, for all of these examples, you should just use tr:outputText
instead of tr:outputFormatted.
outputFormatted really has nothing to do with outputFormat.
What tr:outputFormatted gives you is support for (a subset of)
HTML formatting without opening the security hole of
escape=false.
-- Adam
On 8/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Well you could do:
tr:outputFormatted value=#{myfunc:format2(str, arg1, arg2)} /
where you could write format1, format2, etc. EL functions to do the
work.
You could also do:
t:buffer into=#{formattedString}
h:outputFormat value=#{message.key}
f:param value=param1 /
/h:outputFormat
/t:buffer
tr:outputFormatted value=#{formattedString} /
On 8/30/07, Paul Mander [EMAIL PROTECTED] wrote:
Andrew Robinson-5 wrote:
Well, that is not localizable
I think the use case that he means is more like:
tr:outputFormatted value=#{messages.str}
f:param value=#{myarg} /
/tr:outputFormatted
messages.properties
str = Test {0} param
That's a better example.
--
View this message in context:
http://www.nabble.com/trinidad-outputFormat-and-f%3Aparam-support-tf4347417.html#a12401317
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Chordiant Software Inc.
www.chordiant.com
Re: disabling tree node checkbox for tree2
Hi,
I tried to solve the problem and to disable a checkbox with the following
code:
TreeNodeChecked treeNode;
...
UIComponent nodeTypeFacet = getHtmlTree().getFacet(treeNode.getType());
HtmlSelectBooleanCheckbox checkBox = (HtmlSelectBooleanCheckbox)
nodeTypeFacet.getChildren().get(0);
checkBox.setReadonly(true);
...
private HtmlTree getHtmlTree() {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent htmlTree =
context.getViewRoot().findComponent(myForm:idAvailable);
return (HtmlTree) htmlTree;
}
But what happens now is, that ALL nodes of type treeNode.getType() in the
tree get read only (disabled).
I expected, that only selected node (treeNode) would get read only
rendering.
Has anybody some idea what I do wrong here?
Regards,
Tomek
Tomek Chojnacki wrote:
Hi,
I am newbie to MyFaces and have a slight problem with the tree2 component.
In my JSP I have tree2 component with checkboxes (selectBooleanCheckbox).
It looks like this:
t:tree2 id=htmlTree ...
f:facet name=project
h:panelGroup
t:selectBooleanCheckbox id=man value=#{node.checked}/
t:graphicImage value=/images/project.gif
rendered=#{t.nodeExpanded} border=0/ ...
Now I want to disable dynamically a checkbox for a tree node.
I can do it in a static way - adding an attribute 'disabled=true' to
t:selectBooleanCheckbox/ in the JSP.
But I don't know how to do it on the server in the Java code.
I get tree component with this code:
private HtmlTree getHtmlTree() {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent htmlTree =
context.getViewRoot().findComponent(myForm:htmlTree);
return (HtmlTree) htmlTree;
}
With this I can get any node with getHtmlTree().getNode()
However TreeNode class has no property setDisabled or something like
this.
How do I get UIComponent for selectBooleanCheckbox and change it to
disabled, so that it renders then in the same way as disabled attribute
in JSP?
Thank you in advance.
Tomek
--
View this message in context:
http://www.nabble.com/disabling-tree-node-checkbox-for-tree2-tf4354647.html#a12477689
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Tobago] EmptyStackException in datepicker
Hi Volker,
thanks, the datepicker works now in general.
But I have very strange effects with the datepicker in a special use case.
I have a sheet with a link in one column which opens a popup. And this popup
has a date field and a datepicker.
The first time I click on the picker image on the popup after the page was
loaded for the first time nothing
happens. The datepicker doesn't open. When I close the popup and reopen it
and then click on the
picker image the datepicker opens but *behind* the popup, so it is not
accessable (see attachted scrennshot).
I have to close the popup first and then I can close the datepicker. When I
open the popup for the third time and
click on the picker image the datepicker opens normally and everything works
fine. To summarize: I must open
the popup three times after the page is initially loaded to make the
datepicker working.
Unfortunately I can't reproduce this behaviour in a small example.
Here is an extract from my jsp page:
tc:sheet id=meineAufgabenSheet
columns=30px;80px;80px;70px;65px;165px;60px;100px
showHeader=true
showRowRange=none
showPageRange=none
showDirectLinks=none
first=0
rows=1000
selectable=multi
value=#{mainController.meineAufgaben}
var=aufgabe
binding=#{mainController.sheetMeineAufgaben}
state=#{mainController.sheetStateMeineAufgaben}
f:facet name=popup
tc:popup id=ablaufdatumPopup width=300px height=150px
tc:box label=#{aufgabenBundle.box_label_ablaufdatum}
f:facet name=layout
tc:gridLayout rows=*;fixed;10px;fixed columns=*;*;*/
/f:facet
tc:cell spanX=3
tc:out escape=false
value=#{aufgabenBundle.out_value_ablaufdatum}/
/tc:cell
tc:label value=#{aufgabenBundle.label_value_ablaufdatum}/
tc:date id=ablaufdatum
required=true
value=#{mainController.ablaufdatum}/
tc:datePicker for=ablaufdatum/
tc:cell spanX=3/
tc:cell/
tc:button id=okButton
label=#{mainBundle.button_label_ok}
action=#{mainController.ablaufAction}
tc:attribute name=popupClose value=afterSubmit/
/tc:button
tc:button id=cancelButton
label=#{mainBundle.button_label_cancel}
tc:attribute name=popupClose value=immediate/
/tc:button
/tc:box
/tc:popup
/f:facet
...
tc:column id=ablaufColumn
label=#{aufgabenBundle.column_label_ablauf}
tip=#{aufgabenBundle.column_tip_ablauf}
sortable=true
tc:link id=ablaufLink
action=#{mainController.ablaufPopupAction}
tc:out id=ablauf
value=#{aufgabe.ablauf}/
tc:popupReference for=ablaufdatumPopup/
tc:attribute name=renderedPartially
value=:mainPage:tabsView:meineAufgabenView:meineAufgabenSheet:ablaufdatumPopup/
/tc:link
/tc:column
...
/tc:sheet
Regards,
Helmut
- Original Message -
From: Volker Weber [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Tuesday, September 04, 2007 1:39 PM
Subject: Re: [Tobago] EmptyStackException in datepicker
Hi Helmut,
there was a Problem in the ButtonRenderer introduced with the changes
for tabindex.
Please try next nightly or build you own from svn head.
Regards,
Volker
2007/9/4, Volker Weber [EMAIL PROTECTED]:
Hi,
seems this is not only the datePicker, I just got a
EmptyStackException in a page without datePicker.
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:79)
at java.util.Stack.pop(Stack.java:61)
at
org.apache.myfaces.tobago.webapp.TobagoResponseWriterImpl.endElement(TobagoResponseWriterImpl.java:232)
at
org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent(TabGroupRenderer.java:80)
at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView(TabGroupRenderer.java:342)
at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.encodeAjax(TabGroupRenderer.java:368)
I'm going to look at this.
Regards,
Volker
2007/9/3, Helmut Swaczinna [EMAIL PROTECTED]:
Hi,
in the current snapshot the datepicker is broken. You get an
EmptyStackException when you click on
the picker image. You can see this in the demo.
Regards
Helmut
attachment: Datepicker.jpg
Re: [Tobago] EmptyStackException in datepicker
Hi Helmut,
the problem with the popups in wrong order is a known issue:
https://issues.apache.org/jira/browse/TOBAGO-133 / -134
The other (nothing happen after first click) must be a other Problem.
Can you see if a request is made after the first click and what the response is?
You can set the debug level of
org.apache.myfaces.tobago.ajax.api.AjaxResponseRenderer
to trace to get the full response in the logs.
Regards,
Volker
2007/9/4, Helmut Swaczinna [EMAIL PROTECTED]:
Hi Volker,
thanks, the datepicker works now in general.
But I have very strange effects with the datepicker in a special use case.
I have a sheet with a link in one column which opens a popup. And this popup
has a date field and a datepicker.
The first time I click on the picker image on the popup after the page was
loaded for the first time nothing
happens. The datepicker doesn't open. When I close the popup and reopen it
and then click on the
picker image the datepicker opens but *behind* the popup, so it is not
accessable (see attachted scrennshot).
I have to close the popup first and then I can close the datepicker. When I
open the popup for the third time and
click on the picker image the datepicker opens normally and everything works
fine. To summarize: I must open
the popup three times after the page is initially loaded to make the
datepicker working.
Unfortunately I can't reproduce this behaviour in a small example.
Here is an extract from my jsp page:
tc:sheet id=meineAufgabenSheet
columns=30px;80px;80px;70px;65px;165px;60px;100px
showHeader=true
showRowRange=none
showPageRange=none
showDirectLinks=none
first=0
rows=1000
selectable=multi
value=#{mainController.meineAufgaben}
var=aufgabe
binding=#{mainController.sheetMeineAufgaben}
state=#{mainController.sheetStateMeineAufgaben}
f:facet name=popup
tc:popup id=ablaufdatumPopup width=300px height=150px
tc:box label=#{aufgabenBundle.box_label_ablaufdatum}
f:facet name=layout
tc:gridLayout rows=*;fixed;10px;fixed columns=*;*;*/
/f:facet
tc:cell spanX=3
tc:out escape=false
value=#{aufgabenBundle.out_value_ablaufdatum}/
/tc:cell
tc:label value=#{aufgabenBundle.label_value_ablaufdatum}/
tc:date id=ablaufdatum
required=true
value=#{mainController.ablaufdatum}/
tc:datePicker for=ablaufdatum/
tc:cell spanX=3/
tc:cell/
tc:button id=okButton
label=#{mainBundle.button_label_ok}
action=#{mainController.ablaufAction}
tc:attribute name=popupClose value=afterSubmit/
/tc:button
tc:button id=cancelButton
label=#{mainBundle.button_label_cancel}
tc:attribute name=popupClose value=immediate/
/tc:button
/tc:box
/tc:popup
/f:facet
...
tc:column id=ablaufColumn
label=#{aufgabenBundle.column_label_ablauf}
tip=#{aufgabenBundle.column_tip_ablauf}
sortable=true
tc:link id=ablaufLink
action=#{mainController.ablaufPopupAction}
tc:out id=ablauf
value=#{aufgabe.ablauf}/
tc:popupReference for=ablaufdatumPopup/
tc:attribute name=renderedPartially
value=:mainPage:tabsView:meineAufgabenView:meineAufgabenSheet:ablaufdatumPopup/
/tc:link
/tc:column
...
/tc:sheet
Regards,
Helmut
- Original Message -
From: Volker Weber [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Tuesday, September 04, 2007 1:39 PM
Subject: Re: [Tobago] EmptyStackException in datepicker
Hi Helmut,
there was a Problem in the ButtonRenderer introduced with the changes
for tabindex.
Please try next nightly or build you own from svn head.
Regards,
Volker
2007/9/4, Volker Weber [EMAIL PROTECTED]:
Hi,
seems this is not only the datePicker, I just got a
EmptyStackException in a page without datePicker.
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:79)
at java.util.Stack.pop(Stack.java:61)
at
org.apache.myfaces.tobago.webapp.TobagoResponseWriterImpl.endElement(TobagoResponseWriterImpl.java:232)
at
org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent(TabGroupRenderer.java:80)
at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView(TabGroupRenderer.java:342)
at
Re: [Tobago] EmptyStackException in datepicker
Hi Volker,
yes, a request is made. This is the only debug output (with
org.apache.myfaces.tobago.ajax.api.AjaxResponseRenderer enabled):
AjaxUtils ajaxComponentIds =
mainPage:tabsView:meineAufgabenView:meineAufgabenSheet:0:ablaufdatumPopup:ablaufdatum_pickerpopup
ComponentUtil idRemainder = :0:ablaufdatumPopup:_idJsp59
ComponentUtil set rowIndex = 0
Seems there's no response.
Regards
Helmut
- Original Message -
From: Volker Weber [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Tuesday, September 04, 2007 3:47 PM
Subject: Re: [Tobago] EmptyStackException in datepicker
Hi Helmut,
the problem with the popups in wrong order is a known issue:
https://issues.apache.org/jira/browse/TOBAGO-133 / -134
The other (nothing happen after first click) must be a other Problem.
Can you see if a request is made after the first click and what the
response is?
You can set the debug level of
org.apache.myfaces.tobago.ajax.api.AjaxResponseRenderer
to trace to get the full response in the logs.
Regards,
Volker
2007/9/4, Helmut Swaczinna [EMAIL PROTECTED]:
Hi Volker,
thanks, the datepicker works now in general.
But I have very strange effects with the datepicker in a special use
case.
I have a sheet with a link in one column which opens a popup. And this
popup
has a date field and a datepicker.
The first time I click on the picker image on the popup after the page
was
loaded for the first time nothing
happens. The datepicker doesn't open. When I close the popup and reopen
it
and then click on the
picker image the datepicker opens but *behind* the popup, so it is not
accessable (see attachted scrennshot).
I have to close the popup first and then I can close the datepicker. When
I
open the popup for the third time and
click on the picker image the datepicker opens normally and everything
works
fine. To summarize: I must open
the popup three times after the page is initially loaded to make the
datepicker working.
Unfortunately I can't reproduce this behaviour in a small example.
Here is an extract from my jsp page:
tc:sheet id=meineAufgabenSheet
columns=30px;80px;80px;70px;65px;165px;60px;100px
showHeader=true
showRowRange=none
showPageRange=none
showDirectLinks=none
first=0
rows=1000
selectable=multi
value=#{mainController.meineAufgaben}
var=aufgabe
binding=#{mainController.sheetMeineAufgaben}
state=#{mainController.sheetStateMeineAufgaben}
f:facet name=popup
tc:popup id=ablaufdatumPopup width=300px height=150px
tc:box label=#{aufgabenBundle.box_label_ablaufdatum}
f:facet name=layout
tc:gridLayout rows=*;fixed;10px;fixed
columns=*;*;*/
/f:facet
tc:cell spanX=3
tc:out escape=false
value=#{aufgabenBundle.out_value_ablaufdatum}/
/tc:cell
tc:label
value=#{aufgabenBundle.label_value_ablaufdatum}/
tc:date id=ablaufdatum
required=true
value=#{mainController.ablaufdatum}/
tc:datePicker for=ablaufdatum/
tc:cell spanX=3/
tc:cell/
tc:button id=okButton
label=#{mainBundle.button_label_ok}
action=#{mainController.ablaufAction}
tc:attribute name=popupClose value=afterSubmit/
/tc:button
tc:button id=cancelButton
label=#{mainBundle.button_label_cancel}
tc:attribute name=popupClose value=immediate/
/tc:button
/tc:box
/tc:popup
/f:facet
...
tc:column id=ablaufColumn
label=#{aufgabenBundle.column_label_ablauf}
tip=#{aufgabenBundle.column_tip_ablauf}
sortable=true
tc:link id=ablaufLink
action=#{mainController.ablaufPopupAction}
tc:out id=ablauf
value=#{aufgabe.ablauf}/
tc:popupReference for=ablaufdatumPopup/
tc:attribute name=renderedPartially
value=:mainPage:tabsView:meineAufgabenView:meineAufgabenSheet:ablaufdatumPopup/
/tc:link
/tc:column
...
/tc:sheet
Regards,
Helmut
- Original Message -
From: Volker Weber [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Tuesday, September 04, 2007 1:39 PM
Subject: Re: [Tobago] EmptyStackException in datepicker
Hi Helmut,
there was a Problem in the ButtonRenderer introduced with the changes
for tabindex.
Please try next nightly or build you own from svn head.
Regards,
Volker
2007/9/4, Volker Weber [EMAIL PROTECTED]:
Hi,
seems this is not only the datePicker, I just got a
EmptyStackException in a page without datePicker.
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:79)
at
Re: Antwort: Re: Antwort: Re: Why so many components?
Hello Wolfgang, That's give a good path where I should go through. Thanks a lot! Cheers. - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Tuesday, September 4, 2007 12:25:51 PM Subject: Antwort: Re: Antwort: Re: Why so many components? Hi, Definitely the latter one (only some of the in-house..). Actually, I found the comment rather manager-like and not really very informative.. ;) I am looking forward to the Seam people and their Trinidad integration work. Otherwise we will have lots of different plumbing implementations around.. Best, Wolfgang. distillingweb [EMAIL PROTECTED] 04.09.2007 12:08 Bitte antworten an MyFaces Discussion users@myfaces.apache.org An MyFaces Discussion users@myfaces.apache.org Kopie Thema Re: Antwort: Re: Why so many components? Wolfgang, Thanks for share this information and link. I was catch also for this comment in that link: Its things like this that have conviced me that its time to throw away a huge amount of in-house crufty stuff and move ahead with Seam/JSF for all of our new development. I did not understand if the comment is meant to replace Trinidad by using Seam or only some of the in-house components implementations in this context. Could you give me a hint on that? Thank you very much. - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Tuesday, September 4, 2007 11:56:34 AM Subject: Antwort: Re: Why so many components? Hi, There is also another issue with Trinidad and integration if you use Seam: As of now, you cannot use it with tr:table unless you do the 'plumbing' into Seam yourself and even so it does not seem clear how to make the paging work.. See also http://pmuir.bleepbleep.org.uk/2007/04/backing-trinidads-datatable-with-seam.html Best, Wolfgang. distillingweb [EMAIL PROTECTED] 04.09.2007 11:08 Bitte antworten an MyFaces Discussion users@myfaces.apache.org An MyFaces Discussion users@myfaces.apache.org Kopie Thema Re: Why so many components? Andrew, I was about to use A4J in that combination without any experience with. Your support on that has been priceless. Thank you so much again. - Original Message From: Andrew Robinson [EMAIL PROTECTED] To: MyFaces Discussion users@myfaces.apache.org Sent: Monday, September 3, 2007 11:54:16 PM Subject: Re: Why so many components? FYI, I don't recommend that you use A4J in that combination unless you need RichFaces. Just use the PPR functionality in Trinidad. You will most likely have rendering problems with Trinidad+A4J See http://myfaces.apache.org/trinidad/devguide/ppr.html for information on Trinidad's AJAX -Andrew On 9/3/07, distillingweb [EMAIL PROTECTED] wrote: Hello, I know this use to be a obvious choice, but because I am a newcomer in the MyFaces world, what answer I would give to my manager if he ask me why am I using so many components? Now, following advices, I am planning to use MyFaces + Trinidad + Tomahawk + Facelets + Ajax4JSF and maybe Seam. I know each of them provide different resources, but is there a couple or three of them that could give me like 90% of all my requirements need? Thank you in advance. Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. Got a little couch potato? Check out fun summer activities for kids. Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/
[tobago] error not verbose enough
Hi the good team, I'm experiencing a problem while I'm moving to facelets. This is absolutely normal until the point where I don't know where the problem occurs ;-p. In fact, I have an existing set of jsp that I attempted to transform to facelets templates. I had a lot of jsp includes until a deepness of 4. The probem is that when an exception occurs, there's no info on which page is beeing processed. Is there a way to activate a logger that writes which page is beeing included? (all I have is Invalid tag found: unexpected input while looking for attr name or '/' at line 3. Surroundings: '!DOCTYPE html PUBLIC -//W3C/') Thanks in advance if you have any idea... This is my exception to give you an idea :-) 16:31:57,593 ERROR [STDERR] 4 sept. 2007 16:31:57 com.sun.facelets.FaceletViewHandler *handleRenderException* GRAVE: Error Rendering View[/person/person.xhtml] *java.lang.IllegalArgumentException*: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(*Native Method*) at sun.reflect.NativeMethodAccessorImpl.invoke(* NativeMethodAccessorImpl.java:39*) at sun.reflect.DelegatingMethodAccessorImpl.invoke(* DelegatingMethodAccessorImpl.java:25*) at java.lang.reflect.Method.invoke(*Method.java:597*) at javax.faces.component.UIComponentBase$AttributesMap.put(* UIComponentBase.java:1590*) at javax.faces.component.UIComponentBase$AttributesMap.put(* UIComponentBase.java:1499*) at org.apache.myfaces.tobago.renderkit.html.StyleClasses.ensureStyleClasses(* StyleClasses.java:70*) at org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.createCssClass(* HtmlRendererUtil.java:119*) at org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.prepareRender(* HtmlRendererUtil.java:94*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.prepareRender (*DefaultLayoutRenderer.java:40*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:73*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.encodeChildrenOfComponent (*DefaultLayoutRenderer.java:47*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encodeChildren(* RenderUtil.java:56*) at org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent (*TabGroupRenderer.java:74*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView (*TabGroupRenderer.java:342*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.encodeEnd (*TabGroupRenderer.java:155*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:836*) at org.apache.myfaces.tobago.component.UITabGroup.encodeEnd(* UITabGroup.java:106*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:84*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent (*GridLayoutRenderer.java:366*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent(* UIGridLayout.java:276*) at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren(* UIPanelBase.java:43*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:77*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent (*GridLayoutRenderer.java:366*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent(* UIGridLayout.java:276*) at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren(* UIPanelBase.java:43*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:77*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:81*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.encodeChildrenOfComponent (*DefaultLayoutRenderer.java:47*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.PageRenderer.encodeEnd (*PageRenderer.java:128*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:836*) at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:896*) at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:892*) at com.sun.facelets.FaceletViewHandler.renderView(* FaceletViewHandler.java:578*) at
Re: [TRINIDAD] Proposal - fieldset/legend component
Just pinging for any other responses. On 8/30/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, True, panelBox does not include the Layout suffix (a fact I somehow forgotten / overlooked), so stripping the Layout suffix is fine with me. I like the attribute shortcut for the legend as well. ~ Simon On 8/30/07, Danny Robinson [EMAIL PROTECTED] wrote: I knocked together this component to see what it would look like and what skin selectors would be required. Here's some tag examples and an attached screenshot. FWIW while Simon's name suggestion was better, I'm not fan of the 'Layout' suffix, as it doesn't actually perform layout, and is therefore closer in functionality to panelBox. tr:panelFieldsetLayout captionText=Personal Details tr:panelFormLayout tr:inputText label=First Name / tr:inputText label=Middle Initial columns=1/ tr:inputText label=Family Name / tr:selectOneChoice label=Suffix / /tr:panelFormLayout /tr:panelFieldsetLayout OR tr:panelFieldsetLayout captionText=This shouldn't appear f:facet name=caption tr:icon name=error / /f:facet tr:inputDate label=Date of Birth / /tr:panelFieldsetLayout Thoughts anyone, D. On 8/29/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, I would prefer something along the lines of tr:panelFieldSetLayout with a legend facet. Regards, ~ Simon On 8/29/07, Danny Robinson [EMAIL PROTECTED] wrote: Would there be interest in a skinnable/ajaxified component that rendered output using html fieldset/legend. We'd like to include this in our applications and I'm keen to keep our users away from introducing other component libraries just for the odd extra component. I'm struggling to think of a nice sounding tag name, other than tr:panelBoxAndLegend but it could look something like: tr:panelBoxAndLegend title=The legend ... /tr:panelBoxAndLegend Thanks, Danny -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com
Re: [TRINIDAD] Proposal - fieldset/legend component
Yep, I agree that the Layout suffix shouldn't be there. I'm wondering if we want a name more abstracted from the HTML fieldset concept, though none really come to mind. Or, as a perhaps more radical suggestion, could this be something embedded inside panelFormLayout? Like if we supported caption on af:group? af:panelFormLayout af:group caption=Personal Details af:inputText.../ /af:group /af:panelFormLayout This has some major disadvantages, though. It's probably significantly harder to implement (more grunge in the already grungy PanelFormLayout code) and no way to use it outside of panelFormLayout. So I've probably just talked myself out of this suggestion. :) -- Adam On 8/30/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, True, panelBox does not include the Layout suffix (a fact I somehow forgotten / overlooked), so stripping the Layout suffix is fine with me. I like the attribute shortcut for the legend as well. ~ Simon On 8/30/07, Danny Robinson [EMAIL PROTECTED] wrote: I knocked together this component to see what it would look like and what skin selectors would be required. Here's some tag examples and an attached screenshot. FWIW while Simon's name suggestion was better, I'm not fan of the 'Layout' suffix, as it doesn't actually perform layout, and is therefore closer in functionality to panelBox. tr:panelFieldsetLayout captionText=Personal Details tr:panelFormLayout tr:inputText label=First Name / tr:inputText label=Middle Initial columns=1/ tr:inputText label=Family Name / tr:selectOneChoice label=Suffix / /tr:panelFormLayout /tr:panelFieldsetLayout OR tr:panelFieldsetLayout captionText=This shouldn't appear f:facet name=caption tr:icon name=error / /f:facet tr:inputDate label=Date of Birth / /tr:panelFieldsetLayout Thoughts anyone, D. On 8/29/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, I would prefer something along the lines of tr:panelFieldSetLayout with a legend facet. Regards, ~ Simon On 8/29/07, Danny Robinson [EMAIL PROTECTED] wrote: Would there be interest in a skinnable/ajaxified component that rendered output using html fieldset/legend. We'd like to include this in our applications and I'm keen to keep our users away from introducing other component libraries just for the odd extra component. I'm struggling to think of a nice sounding tag name, other than tr:panelBoxAndLegend but it could look something like: tr:panelBoxAndLegend title=The legend ... /tr:panelBoxAndLegend Thanks, Danny -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com
Re: trinidad outputFormat and f:param support
-0.5; outputText performance is really critical to overall performance,
and even adding a boolean attribute slows it down a bit.
-- Adam
On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote:
Should we look at providing this variable replacement functionality into
outputText. Although I'm against just parsing the text by default, as this
would just add unnecessary parsing in 99% of the cases. Should we instead
look at an extra attribute that forces parsing of the string for variable
substitution.
Danny
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
BTW, for all of these examples, you should just use tr:outputText
instead of tr:outputFormatted.
outputFormatted really has nothing to do with outputFormat.
What tr:outputFormatted gives you is support for (a subset of)
HTML formatting without opening the security hole of
escape=false.
-- Adam
On 8/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Well you could do:
tr:outputFormatted value=#{myfunc:format2(str, arg1, arg2)} /
where you could write format1, format2, etc. EL functions to do the
work.
You could also do:
t:buffer into=#{formattedString}
h:outputFormat value=#{message.key}
f:param value=param1 /
/h:outputFormat
/t:buffer
tr:outputFormatted value=#{formattedString} /
On 8/30/07, Paul Mander [EMAIL PROTECTED] wrote:
Andrew Robinson-5 wrote:
Well, that is not localizable
I think the use case that he means is more like:
tr:outputFormatted value=#{messages.str}
f:param value=#{myarg} /
/tr:outputFormatted
messages.properties
str = Test {0} param
That's a better example.
--
View this message in context:
http://www.nabble.com/trinidad-outputFormat-and-f%3Aparam-support-tf4347417.html#a12401317
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] Trinidad 1.2.1 demo on Tomcat 6.0.13
It is missing, but the bug is that the TLD claims it's required. That got fixed in 1.0.2/1.2.2. -- Adam On 9/4/07, Gregg Leichtman [EMAIL PROTECTED] wrote: The text attribute is indeed missing for the panelHeader tag on line 106 of the progressSteps.jspx file. Fixing this might fix the entire problem. -= Gregg =- Gregg Leichtman wrote: I happen to have the Trinidad 1.2.1 demo running in Tomcat 6.0.13. I had not looked at the Progress Steps demo before. When I did, I got the following: org.apache.jasper.JasperException: /demos/progressSteps.jspx(106,30) According to the TLD or the tag file, attribute text is mandatory for tag panelHeader org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:802) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838) ... I did things a little differently than described below. I opened the war and inserted the same JSF version files as described below along with JSTL 1.1.2 into the WEB-INF/libs folder, jarred up the contents into a new war and dropped this into the Tomcat webapps folder. The result is as stated above. Maybe the difference in error output will be helpful. -= Gregg =- Adam Winer wrote: This doesn't make much sense to me. That line is a tr:forEach element. In 1.2.1, the tld for forEach has attribute description the ending index /description nameend/name deferred-value typejava.lang.Integer/type /deferred-value /attribute ... so end absolutely supports EL. Whether there's a Tomcat bug or a setup issue here, I don't know. -- Adam On 8/30/07, Thai Dang Vu [EMAIL PROTECTED] wrote: Hi everybody, I dropped the trinidad 1.2.1 demo war file in the webapps folder of Tomcat 6, run tomcat so that it deployed that war file, stopped tomcat to dropped jsf-impl-1.2_04-p02.jar, jsf-api-1.2_04-p02.jar and jstl-1.2.jar in the trinidad-1.2.1-demo/WEB-INF/lib folder, started tomcat again and the Component Guide worked, but the Progress Step Demo didn't. This is the error: org.apache.jasper.JasperException: /demos/progressSteps.jspx(68,58) According to TLD or attribute directive in tag file, attribute end does not accept any expressions org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHand ler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java :407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java :148) org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes( Validator.java:1119) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:819) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.jav a:838) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
Re: [Trinidad] force reload and add message for partial update request and view has expired?
View expiry generally stinks in JSF 1.1; in 1.2, there's a ViewExpiredException, so the user should currently see an alert. That's not great - ideally, the main page would refresh or redirect automatically. I'm disinclined to tackle view expiry in JSF 1.1, as it's generally just badly broken there. -- Adam On 8/31/07, Andrew Robinson [EMAIL PROTECTED] wrote: Correct me if I am wrong, but it seems that if a view has expired, and someone initiates a partial update, the page is just updated as if it hadn't. This is quite confusing to the user as nothing happens when they click on a link. What I would like to have happen, is the user redirected to the requested view and be able to add a FacesMessage stating that the view had expired. Has anyone done this or is it built in somewhere and I have just missed it? Example: Go to the trinidad demo, go into the component demo. Walk away from it for a while. Click one of the links (like the component demo link). Nothing happens. A second click works (since now the user has a view in the back-end). Thanks, Andrew
Re: Trinidad 1.2.1: SelectOrderShuttle leading/trailingDescShown Fails For Me
Gregg,
FYI, I don't think Trinidad is adding the content:. Perhaps
Tiles 2.0 is (I've not looked at the newer version).
-- Adam
On 9/3/07, Gregg Leichtman [EMAIL PROTECTED] wrote:
I have found a bug in the generated JavaScript for the Select*Shuttle
components. A patch follows:
TrShuttleProxy._getDescArray = function(listName) {
// var descArray = window[listName.replace(':','_') + '_desc'];
var descArray = window[listName.replace(/:/g,'_') + '_desc']; // gsl fix
return descArray;
}
where listName is content:shuttle1:leading.
The problem is that the listName is not using a global replace; therefore
only the first ':' is being replaced. This worked fine in ADF Faces before
porting to Trinidad where the listName was just shuttle1:leading. Note,
however, that Trinidad now adds an additional content prefix to the
generated inline JavaScript variables:
content_shuttle1_leading_desc=new Array('The First Item
Desc',
'The Second Item Desc',
'The Third Item Desc','');
content_shuttle1_trailing_desc=new Array('');
This means that a global replace needs to be done to create the proper
variable name for matching in the JavaScript code. I will report this on
Jira for the Trinidad project.
I don't have access to the latest snapshots. The last one I see is from
July 11th at:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/trinidad/trinidad-impl/1.2.1-SNAPSHOT/
If this has been fixed already, then please clear my bug report which
should have the side benefit of letting people know that the bug has been
found and fixed already.
-= Gregg =-
Gregg Leichtman wrote:
I am trying to get the leadingDescShown and trailingDescShown attributes
to work for the Trinidad v1.2.1 SelectOrderShuttle. I have the shuttle
working for everything except for displaying the description of a
selected item in the textarea below the leading or trailing shuttle. I'm
running under Linux and Eclipse 3.3 Europa using J2EE5 with JSF 1.2 and
Tiles 2.0.4. I have a tile as follows:
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
%@ taglib uri=http://java.sun.com/jsf/html; prefix=h %
%@ taglib uri=http://tiles.apache.org/tags-tiles;
prefix=tiles %
%@ taglib uri=http://myfaces.apache.org/tomahawk;
prefix=t %
%@ taglib uri=http://myfaces.apache.org/trinidad;
prefix=tr%
tr:form
tr:panelGroupLayout layout=vertical
f:facet name=separator
tr:separator /
/f:facet
tr:messages/
tr:selectOrderShuttle id=shuttle1
label=Selected Values
leadingHeader=Available values:
leadingDescShown=true
trailingHeader=Selected values:
trailingDescShown=true
binding=#{editor.component}
valueChangeListener=#{list.valueChanged}
value=#{list.stringArray}
tr:selectItem shortDesc=The First Item Desc
longDesc=Long Desc 1 label=First value=foo/
tr:selectItem shortDesc=The Second Item Desc
longDesc=Long Desc 2 label=Second value=bar/
tr:selectItem shortDesc=The Third Item Desc
longDesc=Long Desc 3 label=Third value=baz/
/tr:selectOrderShuttle
tr:message for=shuttle1/
tr:commandButton text=Submit/
/tr:panelGroupLayout
/tr:form
The layout page uses f:view wrapping trh:html, trh:head and trh:body.
The trh:body element wraps one of several subviews which wrap several
tiles one of which is the above tile.
An excerpt from the generated page looks like this:
...
form id=content:j_id_jsp_709084578_0pc4
name=content:j_id_jsp_709084578_0pc4 style=margin:0px
method=POST onkeypress=return
_submitOnEnter(event,'content:j_id_jsp_709084578_0pc4');
action=/tutoring/tickerManagerPage.do!--Start:
org.apache.myfaces.trinidad.Panel[j_id_jsp_709084578_1pc4]--div!--Start:
org.apache.myfaces.trinidad.Messages[j_id_jsp_709084578_3pc4]--span
id=content:j_id_jsp_709084578_3pc4/spandiv!--Start:
org.apache.myfaces.trinidad.Object[j_id_jsp_709084578_2pc4]--
hr class=af_separator
/divscriptvar _shuttle_no_items='There are no items to move.';var
_shuttle_no_items_selected='Please select the items to move
first.';/script!--Start:
org.apache.myfaces.trinidad.SelectOrder[shuttle1]--table
cellpadding=0 cellspacing=0 border=0 width=10% summary=
id=content:shuttle1 class=af_selectManyShuttletr
td class=x9u valign=bottomAvailable values:/td
td/td
td class=x9u valign=bottomSelected values:/td
/trtr
td!--Start:
org.apache.myfaces.trinidad.SelectOrder[shuttle1]--table
class=af_selectOrderShuttle_box style=width:100%
cellpadding=0 cellspacing=0 border=0 summary=tbodytr
td class=af_selectOrderShuttle_box-top-start/td
td class=af_selectOrderShuttle_box-top/td
td class=af_selectOrderShuttle_box-top-end/td
/trtr
td class=af_selectOrderShuttle_box-start/td
td class=x59div class=x55table cellpadding=0 border=0
summary=tr
td nowrap valign=middle!--Start:
org.apache.myfaces.trinidad.SelectOrder[shuttle1]--span
class=x1i
select multiple id=content:shuttle1:leading
Re: [TRINIDAD] Proposal - fieldset/legend component
Yeah, I initially went with the enhanced panelFormLayout approach and decided against it. The name is also frustrating, so how about tr:panelCaptionGroup ...? I'll give it 24hrs for other people to chime in, then I'll go with the above. Thanks, Danny On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: Yep, I agree that the Layout suffix shouldn't be there. I'm wondering if we want a name more abstracted from the HTML fieldset concept, though none really come to mind. Or, as a perhaps more radical suggestion, could this be something embedded inside panelFormLayout? Like if we supported caption on af:group? af:panelFormLayout af:group caption=Personal Details af:inputText.../ /af:group /af:panelFormLayout This has some major disadvantages, though. It's probably significantly harder to implement (more grunge in the already grungy PanelFormLayout code) and no way to use it outside of panelFormLayout. So I've probably just talked myself out of this suggestion. :) -- Adam On 8/30/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, True, panelBox does not include the Layout suffix (a fact I somehow forgotten / overlooked), so stripping the Layout suffix is fine with me. I like the attribute shortcut for the legend as well. ~ Simon On 8/30/07, Danny Robinson [EMAIL PROTECTED] wrote: I knocked together this component to see what it would look like and what skin selectors would be required. Here's some tag examples and an attached screenshot. FWIW while Simon's name suggestion was better, I'm not fan of the 'Layout' suffix, as it doesn't actually perform layout, and is therefore closer in functionality to panelBox. tr:panelFieldsetLayout captionText=Personal Details tr:panelFormLayout tr:inputText label=First Name / tr:inputText label=Middle Initial columns=1/ tr:inputText label=Family Name / tr:selectOneChoice label=Suffix / /tr:panelFormLayout /tr:panelFieldsetLayout OR tr:panelFieldsetLayout captionText=This shouldn't appear f:facet name=caption tr:icon name=error / /f:facet tr:inputDate label=Date of Birth / /tr:panelFieldsetLayout Thoughts anyone, D. On 8/29/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, I would prefer something along the lines of tr:panelFieldSetLayout with a legend facet. Regards, ~ Simon On 8/29/07, Danny Robinson [EMAIL PROTECTED] wrote: Would there be interest in a skinnable/ajaxified component that rendered output using html fieldset/legend. We'd like to include this in our applications and I'm keen to keep our users away from introducing other component libraries just for the odd extra component. I'm struggling to think of a nice sounding tag name, other than tr:panelBoxAndLegend but it could look something like: tr:panelBoxAndLegend title=The legend ... /tr:panelBoxAndLegend Thanks, Danny -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com
Re: trinidad outputFormat and f:param support
What about tr:outputFormat? This would be a direct extension of the
core h:outputFormat with the skinning, partialTriggers and other
functionality that Trinidad provides added to it?
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
-0.5; outputText performance is really critical to overall performance,
and even adding a boolean attribute slows it down a bit.
-- Adam
On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote:
Should we look at providing this variable replacement functionality into
outputText. Although I'm against just parsing the text by default, as this
would just add unnecessary parsing in 99% of the cases. Should we instead
look at an extra attribute that forces parsing of the string for variable
substitution.
Danny
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
BTW, for all of these examples, you should just use tr:outputText
instead of tr:outputFormatted.
outputFormatted really has nothing to do with outputFormat.
What tr:outputFormatted gives you is support for (a subset of)
HTML formatting without opening the security hole of
escape=false.
-- Adam
On 8/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Well you could do:
tr:outputFormatted value=#{myfunc:format2(str, arg1, arg2)} /
where you could write format1, format2, etc. EL functions to do the
work.
You could also do:
t:buffer into=#{formattedString}
h:outputFormat value=#{message.key}
f:param value=param1 /
/h:outputFormat
/t:buffer
tr:outputFormatted value=#{formattedString} /
On 8/30/07, Paul Mander [EMAIL PROTECTED] wrote:
Andrew Robinson-5 wrote:
Well, that is not localizable
I think the use case that he means is more like:
tr:outputFormatted value=#{messages.str}
f:param value=#{myarg} /
/tr:outputFormatted
messages.properties
str = Test {0} param
That's a better example.
--
View this message in context:
http://www.nabble.com/trinidad-outputFormat-and-f%3Aparam-support-tf4347417.html#a12401317
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] force reload and add message for partial update request and view has expired?
Okay thanks, I already have my own custom view handler, so I should be able to handle the problem in it. I haven't switched to 1.2 yet as I don't yet feel that MyFaces 1.2 is stable enough for me yet and Trinidad 1.2.x is lagging behind 1.0.x and I am using functionality in 1.0.3. -Andrew On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: View expiry generally stinks in JSF 1.1; in 1.2, there's a ViewExpiredException, so the user should currently see an alert. That's not great - ideally, the main page would refresh or redirect automatically. I'm disinclined to tackle view expiry in JSF 1.1, as it's generally just badly broken there. -- Adam On 8/31/07, Andrew Robinson [EMAIL PROTECTED] wrote: Correct me if I am wrong, but it seems that if a view has expired, and someone initiates a partial update, the page is just updated as if it hadn't. This is quite confusing to the user as nothing happens when they click on a link. What I would like to have happen, is the user redirected to the requested view and be able to add a FacesMessage stating that the view had expired. Has anyone done this or is it built in somewhere and I have just missed it? Example: Go to the trinidad demo, go into the component demo. Walk away from it for a while. Click one of the links (like the component demo link). Nothing happens. A second click works (since now the user has a view in the back-end). Thanks, Andrew
Re: CommandLink in dataTabl
Finally i reconsidered the compatibility issue, spent some more time on it and got working toghether(like a miracle) the following : WebLogic 8.1 SP4, myfaces 1.5 and tomahawk 1.1.6 !! Martin Marinschek wrote: Interesting - it looks as if the tomahawk-tld couldn't be resolved. You might want to try to add the tld into your project directly, and see if this works. regards, Martin On 9/3/07, radu_milos [EMAIL PROTECTED] wrote: Being stuck with WebLogic 8.1 unfortunatelly means I am stuck with java 1.4 :( this is why I am using sun RI and tomahawk 1.1.1 However, retried again tomahawk 1.1.6 and got an incompatible tld error : /startPage.jsp(3): Could not parse deployment descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache.org/tomahawk' into a valid tag library probably occurred due to an error in /startPage.jsp line 3: %@ taglib uri=http://myfaces.apache.org/tomahawk; prefix=t % mybe some log from the weblogic server could bring some light : weblogic.servlet.jsp.JspException: (line 3): Could not parse deployment descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache .org/tomahawk' into a valid tag library at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:712) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5067) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4891) at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4737) at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2147) at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1933) at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1806) at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963) at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106) at weblogic.servlet.jsp.JspParser.parse(JspParser.java:234) at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125) at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258) at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:388) at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:238) at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:188) at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:535) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:373) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322) at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644) Radu Martin Marinschek wrote: what where the problems with these other versions? We should probably better fix these... regards, Martin On 9/3/07, radu_milos [EMAIL PROTECTED] wrote: First, thanks for the interest. Problem is that with WebLogic 8.1(this is my constrain) I am stuck to sun RI 1.1 and tomahawk 1.1.1 I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I couldn't get them working. Radu Martin Marinschek wrote: Hi Radu, you've run into a compatibility problem between Sun RI 1.1 and Tomahawk, both in earlier versions. An upgrade to the latest 1.1 version of both libraries should help! regards, Martin On 9/3/07, radu_milos [EMAIL PROTECTED] wrote: Hello, I am a newbie learning JSF while trying to meet deadlines on a JSF refactoring project. The docs
Re: [Trinidad] force reload and add message for partial update request and view has expired?
Andrew, Can you provide an example of what you've done in your custom VH? Thanks, Danny On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote: Okay thanks, I already have my own custom view handler, so I should be able to handle the problem in it. I haven't switched to 1.2 yet as I don't yet feel that MyFaces 1.2 is stable enough for me yet and Trinidad 1.2.x is lagging behind 1.0.x and I am using functionality in 1.0.3. -Andrew On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: View expiry generally stinks in JSF 1.1; in 1.2, there's a ViewExpiredException, so the user should currently see an alert. That's not great - ideally, the main page would refresh or redirect automatically. I'm disinclined to tackle view expiry in JSF 1.1, as it's generally just badly broken there. -- Adam On 8/31/07, Andrew Robinson [EMAIL PROTECTED] wrote: Correct me if I am wrong, but it seems that if a view has expired, and someone initiates a partial update, the page is just updated as if it hadn't. This is quite confusing to the user as nothing happens when they click on a link. What I would like to have happen, is the user redirected to the requested view and be able to add a FacesMessage stating that the view had expired. Has anyone done this or is it built in somewhere and I have just missed it? Example: Go to the trinidad demo, go into the component demo. Walk away from it for a while. Click one of the links (like the component demo link). Nothing happens. A second click works (since now the user has a view in the back-end). Thanks, Andrew -- Chordiant Software Inc. www.chordiant.com
Re: trinidad outputFormat and f:param support
I'm again at a sorta -0.5 on this; in JSF 1.2, I'd rather provide
EL functions to do formatting, since that gives you format
functionality in all components instead of just one. (ADF Faces
does just this in JDev 11). That still leaves JSF 1.1 users with
just h:outputFormat, which isn't great.
-- Adam
On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote:
What about tr:outputFormat? This would be a direct extension of the
core h:outputFormat with the skinning, partialTriggers and other
functionality that Trinidad provides added to it?
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
-0.5; outputText performance is really critical to overall performance,
and even adding a boolean attribute slows it down a bit.
-- Adam
On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote:
Should we look at providing this variable replacement functionality into
outputText. Although I'm against just parsing the text by default, as
this
would just add unnecessary parsing in 99% of the cases. Should we instead
look at an extra attribute that forces parsing of the string for variable
substitution.
Danny
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
BTW, for all of these examples, you should just use tr:outputText
instead of tr:outputFormatted.
outputFormatted really has nothing to do with outputFormat.
What tr:outputFormatted gives you is support for (a subset of)
HTML formatting without opening the security hole of
escape=false.
-- Adam
On 8/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Well you could do:
tr:outputFormatted value=#{myfunc:format2(str, arg1, arg2)} /
where you could write format1, format2, etc. EL functions to do the
work.
You could also do:
t:buffer into=#{formattedString}
h:outputFormat value=#{message.key}
f:param value=param1 /
/h:outputFormat
/t:buffer
tr:outputFormatted value=#{formattedString} /
On 8/30/07, Paul Mander [EMAIL PROTECTED] wrote:
Andrew Robinson-5 wrote:
Well, that is not localizable
I think the use case that he means is more like:
tr:outputFormatted value=#{messages.str}
f:param value=#{myarg} /
/tr:outputFormatted
messages.properties
str = Test {0} param
That's a better example.
--
View this message in context:
http://www.nabble.com/trinidad-outputFormat-and-f%3Aparam-support-tf4347417.html#a12401317
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Chordiant Software Inc.
www.chordiant.com
Re: [TRINIDAD] Proposal - fieldset/legend component
On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote: Yeah, I initially went with the enhanced panelFormLayout approach and decided against it. The name is also frustrating, so how about tr:panelCaptionGroup ...? I think I like that name. -- Adam I'll give it 24hrs for other people to chime in, then I'll go with the above. Thanks, Danny On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: Yep, I agree that the Layout suffix shouldn't be there. I'm wondering if we want a name more abstracted from the HTML fieldset concept, though none really come to mind. Or, as a perhaps more radical suggestion, could this be something embedded inside panelFormLayout? Like if we supported caption on af:group? af:panelFormLayout af:group caption=Personal Details af:inputText.../ /af:group /af:panelFormLayout This has some major disadvantages, though. It's probably significantly harder to implement (more grunge in the already grungy PanelFormLayout code) and no way to use it outside of panelFormLayout. So I've probably just talked myself out of this suggestion. :) -- Adam On 8/30/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, True, panelBox does not include the Layout suffix (a fact I somehow forgotten / overlooked), so stripping the Layout suffix is fine with me. I like the attribute shortcut for the legend as well. ~ Simon On 8/30/07, Danny Robinson [EMAIL PROTECTED] wrote: I knocked together this component to see what it would look like and what skin selectors would be required. Here's some tag examples and an attached screenshot. FWIW while Simon's name suggestion was better, I'm not fan of the 'Layout' suffix, as it doesn't actually perform layout, and is therefore closer in functionality to panelBox. tr:panelFieldsetLayout captionText=Personal Details tr:panelFormLayout tr:inputText label=First Name / tr:inputText label=Middle Initial columns=1/ tr:inputText label=Family Name / tr:selectOneChoice label=Suffix / /tr:panelFormLayout /tr:panelFieldsetLayout OR tr:panelFieldsetLayout captionText=This shouldn't appear f:facet name=caption tr:icon name=error / /f:facet tr:inputDate label=Date of Birth / /tr:panelFieldsetLayout Thoughts anyone, D. On 8/29/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, I would prefer something along the lines of tr:panelFieldSetLayout with a legend facet. Regards, ~ Simon On 8/29/07, Danny Robinson [EMAIL PROTECTED] wrote: Would there be interest in a skinnable/ajaxified component that rendered output using html fieldset/legend. We'd like to include this in our applications and I'm keen to keep our users away from introducing other component libraries just for the odd extra component. I'm struggling to think of a nice sounding tag name, other than tr:panelBoxAndLegend but it could look something like: tr:panelBoxAndLegend title=The legend ... /tr:panelBoxAndLegend Thanks, Danny -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] force reload and add message for partial update request and view has expired?
It is for my own usage of a component that I wanted on my project. It could be useful to other people, but it is very specific to a few libraries and therefore not a good candidate for any of them due to dependencies. My custom view handler on my project is to implement a new component: UIInclude It is a combination of functionality from Facelets, Seam and Trinidad. It is a component with a component tag handler that has a viewId property. This viewId is used in the tag handler to include a facelet on apply. It also uses the Seam Pages functionality to apply action and security based on included views (instead of just the view root). The view handler uses a custom UIViewRoot object to change the reported view ID in getViewId when currently inside of the UIInclude. So for example, if a.xhtml includes b.xhtml, components inside of b.xhtml that request the view ID will get /b.xhtml returned instead of /a.xhtml. The view handler also forces navigation of the include instead of the outer view. So in this example, b.xhtml will be navigated instead of a.xhtml (the root). It also supports relative view IDs. So in my example, the navigation could navigate to :/c.xhtml In this example, the root would be changed to c.xhtml instead of the include. By this same functionality, ::myOtherInclude/d.xhtml would allow one include to navigate the contents of another include. The component also uses partial rendering support from Trinidad. Since the code requires Facelets, Seam and Trinidad, I don't see a way of integrating into any of the libraries without a lot of work and would have to be put into jsf-comp or some other project where ASF-JBoss conflicts do not exist. As a result, I am keeping this to my own project at the moment. On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote: Andrew, Can you provide an example of what you've done in your custom VH? Thanks, Danny On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote: Okay thanks, I already have my own custom view handler, so I should be able to handle the problem in it. I haven't switched to 1.2 yet as I don't yet feel that MyFaces 1.2 is stable enough for me yet and Trinidad 1.2.x is lagging behind 1.0.x and I am using functionality in 1.0.3. -Andrew On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: View expiry generally stinks in JSF 1.1; in 1.2, there's a ViewExpiredException, so the user should currently see an alert. That's not great - ideally, the main page would refresh or redirect automatically. I'm disinclined to tackle view expiry in JSF 1.1, as it's generally just badly broken there. -- Adam On 8/31/07, Andrew Robinson [EMAIL PROTECTED] wrote: Correct me if I am wrong, but it seems that if a view has expired, and someone initiates a partial update, the page is just updated as if it hadn't. This is quite confusing to the user as nothing happens when they click on a link. What I would like to have happen, is the user redirected to the requested view and be able to add a FacesMessage stating that the view had expired. Has anyone done this or is it built in somewhere and I have just missed it? Example: Go to the trinidad demo, go into the component demo. Walk away from it for a while. Click one of the links (like the component demo link). Nothing happens. A second click works (since now the user has a view in the back-end). Thanks, Andrew -- Chordiant Software Inc. www.chordiant.com
Re: [tobago] error not verbose enough
Hello, can send the page, please. Regards Bernd Zied Hamdi wrote: Hi the good team, I'm experiencing a problem while I'm moving to facelets. This is absolutely normal until the point where I don't know where the problem occurs ;-p. In fact, I have an existing set of jsp that I attempted to transform to facelets templates. I had a lot of jsp includes until a deepness of 4. The probem is that when an exception occurs, there's no info on which page is beeing processed. Is there a way to activate a logger that writes which page is beeing included? (all I have is Invalid tag found: unexpected input while looking for attr name or '/' at line 3. Surroundings: '!DOCTYPE html PUBLIC -//W3C/') Thanks in advance if you have any idea... This is my exception to give you an idea :-) 16:31:57,593 ERROR [STDERR] 4 sept. 2007 16:31:57 com.sun.facelets.FaceletViewHandler *handleRenderException* GRAVE: Error Rendering View[/person/person.xhtml] *java.lang.IllegalArgumentException*: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(*Native Method*) at sun.reflect.NativeMethodAccessorImpl.invoke(* NativeMethodAccessorImpl.java:39*) at sun.reflect.DelegatingMethodAccessorImpl.invoke(* DelegatingMethodAccessorImpl.java:25*) at java.lang.reflect.Method.invoke(*Method.java:597*) at javax.faces.component.UIComponentBase$AttributesMap.put(* UIComponentBase.java:1590*) at javax.faces.component.UIComponentBase$AttributesMap.put(* UIComponentBase.java:1499*) at org.apache.myfaces.tobago.renderkit.html.StyleClasses.ensureStyleClasses(* StyleClasses.java:70*) at org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.createCssClass(* HtmlRendererUtil.java:119*) at org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.prepareRender(* HtmlRendererUtil.java:94*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.prepareRender (*DefaultLayoutRenderer.java:40*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:73*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.encodeChildrenOfComponent (*DefaultLayoutRenderer.java:47*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encodeChildren(* RenderUtil.java:56*) at org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent (*TabGroupRenderer.java:74*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView (*TabGroupRenderer.java:342*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.encodeEnd (*TabGroupRenderer.java:155*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:836*) at org.apache.myfaces.tobago.component.UITabGroup.encodeEnd(* UITabGroup.java:106*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:84*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent (*GridLayoutRenderer.java:366*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent(* UIGridLayout.java:276*) at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren(* UIPanelBase.java:43*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:77*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent (*GridLayoutRenderer.java:366*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent(* UIGridLayout.java:276*) at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren(* UIPanelBase.java:43*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:77*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:81*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.encodeChildrenOfComponent (*DefaultLayoutRenderer.java:47*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.PageRenderer.encodeEnd (*PageRenderer.java:128*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:836*) at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:896*) at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:892*) at com.sun.facelets.FaceletViewHandler.renderView(*
Chosen label from an HtmlSelectOneMenu?
Hello, I have bound an HtmlSelectOneMenu to my backing bean using binding=... on the tag. I can get the chosen value easily enough with: HtmlSelectOneMenu m; ... String chosenValue = m.getValue(); Is there any way to get the label of the chosen item instead of the value from the component? Or is it absolutely necessary to query the model that populated the HtmlSelectOneMenu in the first place? -Thank you! -- View this message in context: http://www.nabble.com/Chosen-label-from-an-HtmlSelectOneMenu--tf4378820.html#a12481694 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Tabbedpane forgets selected pane
Hello,
Just moved from Weblogic 8.1 SP4, SUN RI 1.1 tomahawk 1.1.1. to WebLogic 81.
SP4, myfaces 1.5 and tomahawk 1.1.6.
Gained some functionality but also lost some functionality :(
I am using a tabbed pane , and in each pane I have an independent jsf, as
it follows :
-HOME TABBED PANES---
t:panelTabbedPane
styleClass=tabbedPane
serverSideTabSwitch=false
activeTabStyleClass=activeTab
inactiveTabStyleClass=inactiveTab
disabledTabStyleClass=disabledTab
activeSubStyleClass=activeSub
inactiveSubStyleClass=inactiveSub
tabContentStyleClass=tabContent
bgcolor=#CC
t:panelTab id=tab1 label=General rendered=true
f:subview id=GeneralSubwiew
jsp:include page=adminGeneral.jsp/
/f:subview
/t:panelTab
and so on for the rest of the tabs.
-
Here's a short snap of the an included jsf :
---JSF PAGE INCLUDED IN A
PANE--
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
%@ taglib uri=http://java.sun.com/jsf/html; prefix=h %
%@ taglib uri=http://myfaces.apache.org/tomahawk; prefix=t %
t:htmlTag value=adminGeneral
body bgcolor=#ff
h:form id=devices
h:panelGrid styleClass=tableColapse columns=5
columnClasses=tdBorder
h:column h:outputText value=
/h:outputText/h:column
.
ending with
/h:form
/body
/t:htmlTag
--
Biggest issue is that my tabbing mechanism does not remember the pane
position. As soon as I click a
button or a link(action or action Listener) the method behind is executed
but I am redirected each time
to my first pane. Whatever action I do, at reload i get the first pane . :(
Searched the forum , and there was a sugestion on using facelets but I'm
afraid weblogic 8.1
is not ready for this. I have a wild guess I am missing a setting or
somthing...
Anyone got ideeas?
A hint could be a Javascript error that I have at the reload of each page:
Error: f has no properties
pointing towards this function
function clearFormHiddenParams_tab1_GeneralSubwiew_devices(currFormName)
{
var f = document.forms['tab1:GeneralSubwiew:devices'];
f.elements['tab1:GeneralSubwiew:devices:_link_hidden_'].value='';
f.elements['tab1:GeneralSubwiew:devices:_idcl'].value='';
f.target='';
}
To my this doesn't say to much
Regards,
Radu Milos
--
View this message in context:
http://www.nabble.com/Tabbedpane-forgets-selected-pane-tf4378844.html#a12481754
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: trinidad outputFormat and f:param support
The problem with using EL is it has a major drawback of not supporting arrays.
For example:
a = my {0} text
b = my {0} text {1} is longer
c = my {0} text {1} needs a lot of {2} parameters
With the way EL functions are written I have to create three (or more
actually) functions to handle this (format1, format2, format3). This
is because EL functions do not yet support variable arguments. Perhaps
Sun will make it so in the future, but until that happens outputFormat
is very useful.
One work around is something like:
tr:outputText ...style stuff...
h:outputFormat value= ...
f:param ... /
...
/h:outputFormat
/tr:outputText
it is more typing and 1 more component, but it would give you (Paul)
the ability to have Trinidad skinning on the outer component while
using the functionality of the outputFormat that there is apparently a
resistance to provide in Trinidad.
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
I'm again at a sorta -0.5 on this; in JSF 1.2, I'd rather provide
EL functions to do formatting, since that gives you format
functionality in all components instead of just one. (ADF Faces
does just this in JDev 11). That still leaves JSF 1.1 users with
just h:outputFormat, which isn't great.
-- Adam
On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote:
What about tr:outputFormat? This would be a direct extension of the
core h:outputFormat with the skinning, partialTriggers and other
functionality that Trinidad provides added to it?
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
-0.5; outputText performance is really critical to overall performance,
and even adding a boolean attribute slows it down a bit.
-- Adam
On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote:
Should we look at providing this variable replacement functionality into
outputText. Although I'm against just parsing the text by default, as
this
would just add unnecessary parsing in 99% of the cases. Should we
instead
look at an extra attribute that forces parsing of the string for
variable
substitution.
Danny
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
BTW, for all of these examples, you should just use tr:outputText
instead of tr:outputFormatted.
outputFormatted really has nothing to do with outputFormat.
What tr:outputFormatted gives you is support for (a subset of)
HTML formatting without opening the security hole of
escape=false.
-- Adam
On 8/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Well you could do:
tr:outputFormatted value=#{myfunc:format2(str, arg1, arg2)} /
where you could write format1, format2, etc. EL functions to do the
work.
You could also do:
t:buffer into=#{formattedString}
h:outputFormat value=#{message.key}
f:param value=param1 /
/h:outputFormat
/t:buffer
tr:outputFormatted value=#{formattedString} /
On 8/30/07, Paul Mander [EMAIL PROTECTED] wrote:
Andrew Robinson-5 wrote:
Well, that is not localizable
I think the use case that he means is more like:
tr:outputFormatted value=#{messages.str}
f:param value=#{myarg} /
/tr:outputFormatted
messages.properties
str = Test {0} param
That's a better example.
--
View this message in context:
http://www.nabble.com/trinidad-outputFormat-and-f%3Aparam-support-tf4347417.html#a12401317
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Chordiant Software Inc.
www.chordiant.com
[Tomahawk] validateEqual problem for second field
I am using the tomahawk validateEqual tag to check if two (non mandatory)
fields on a form are equal to each other but hitting some problems related
to the order of the field validations.
In the example below the validation and error message attached to the second
field works fine. However for the validation on the first field it seems I
have to submit the form the fields are in twice if the fields are equal -
the first time it always displays the error message saying they are unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
required=false
t:validateEqual for=equal /
/h:inputText
Does anyone know why this is happening or have a solution ?
[I have also tried the sandbox validateCompareTo tag as an alternative with
similar results.]
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
Re: CommandLink in dataTabl
I looked at the HTML generated code and I noticed that each button had the same HTML code... there were no unique ID's. I believe this is the reason why my method got called hundreds of times... Maybe there could be some issue in generating the ids. However, I moved to myfaces 1.5 and tomahawk 1.1.6 and stumbled over other bugs :) Thanks for the support! Martin Marinschek wrote: Interesting - it looks as if the tomahawk-tld couldn't be resolved. You might want to try to add the tld into your project directly, and see if this works. regards, Martin On 9/3/07, radu_milos [EMAIL PROTECTED] wrote: Being stuck with WebLogic 8.1 unfortunatelly means I am stuck with java 1.4 :( this is why I am using sun RI and tomahawk 1.1.1 However, retried again tomahawk 1.1.6 and got an incompatible tld error : /startPage.jsp(3): Could not parse deployment descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache.org/tomahawk' into a valid tag library probably occurred due to an error in /startPage.jsp line 3: %@ taglib uri=http://myfaces.apache.org/tomahawk; prefix=t % mybe some log from the weblogic server could bring some light : weblogic.servlet.jsp.JspException: (line 3): Could not parse deployment descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache .org/tomahawk' into a valid tag library at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:712) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5067) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4891) at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4737) at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2147) at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1933) at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1806) at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963) at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106) at weblogic.servlet.jsp.JspParser.parse(JspParser.java:234) at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125) at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258) at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:388) at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:238) at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:188) at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:535) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:373) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322) at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644) Radu Martin Marinschek wrote: what where the problems with these other versions? We should probably better fix these... regards, Martin On 9/3/07, radu_milos [EMAIL PROTECTED] wrote: First, thanks for the interest. Problem is that with WebLogic 8.1(this is my constrain) I am stuck to sun RI 1.1 and tomahawk 1.1.1 I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I couldn't get them working. Radu Martin Marinschek wrote: Hi Radu, you've run into a compatibility problem between Sun RI 1.1 and Tomahawk, both in earlier versions. An upgrade to the latest 1.1 version of both libraries should help! regards, Martin
Re: [Tomahawk] validateEqual problem for second field
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non mandatory)
fields on a form are equal to each other but hitting some problems related
to the order of the field validations.
In the example below the validation and error message attached to the second
field works fine. However for the validation on the first field it seems I
have to submit the form the fields are in twice if the fields are equal -
the first time it always displays the error message saying they are unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
required=false
t:validateEqual for=equal /
/h:inputText
Does anyone know why this is happening or have a solution ?
[I have also tried the sandbox validateCompareTo tag as an alternative with
similar results.]
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
Re: [Tomahawk] validateEqual problem for second field
I agree with you but unfortunately the customer for whom I'm developing the
software doesn't, but additionally the problem in itself is something we
should be able to solve relatively simply I would have thought as it may be
a valid scenario in other software projects.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 10:41:39 -0600
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non
mandatory)
fields on a form are equal to each other but hitting some problems
related
to the order of the field validations.
In the example below the validation and error message attached to the
second
field works fine. However for the validation on the first field it seems
I
have to submit the form the fields are in twice if the fields are equal
-
the first time it always displays the error message saying they are
unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
required=false
t:validateEqual for=equal /
/h:inputText
Does anyone know why this is happening or have a solution ?
[I have also tried the sandbox validateCompareTo tag as an alternative
with
similar results.]
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
Re: [Tomahawk] validateEqual problem for second field
I took a look into the code to make sure I knew what was going on and
here is what I found:
It looks like the problem you are having is due to the design of the
ValidateEqual class. It is performing its logic in the validation
phase using the EditableValueHolder.getValue() function. This presents
a problem on the first component. Reason as follows:
equal has an EqualValidator added to it during the view creation
equal2 has an EqualValidator added to it during the view creation
during the decode phase, equal and equal2 are decoded and the values
from the client are stored in the submittedValue property of each
component.
during the validation phase:
The equal component's processValidators method calls the validate
function. This function converts the submitted value. If there are no
problems, the validation of the component is called (validateValue
function). If the component is valid, the local value (setValue) is
called.
So, at the time that the equal is validating, equal2 has not set its
local value (it is currently null, only the submitted value is set)
and the submitted value is not converted.
So, equal cannot compare it's local value to equal2's local value
since equal2 is not yet validated.
This means that in order for the validate compare to and validate
equal components to work, they have to be on the second component as
the first component has to be already be validate, and be valid!
Otherwise, the local value is not set, which is what these validators
use to validate against.
So the short answer to your question is your use case is not
supported. The validators *have* to be only on the 2nd component.
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I agree with you but unfortunately the customer for whom I'm developing the
software doesn't, but additionally the problem in itself is something we
should be able to solve relatively simply I would have thought as it may be
a valid scenario in other software projects.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 10:41:39 -0600
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non
mandatory)
fields on a form are equal to each other but hitting some problems
related
to the order of the field validations.
In the example below the validation and error message attached to the
second
field works fine. However for the validation on the first field it seems
I
have to submit the form the fields are in twice if the fields are equal
-
the first time it always displays the error message saying they are
unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
required=false
t:validateEqual for=equal /
/h:inputText
Does anyone know why this is happening or have a solution ?
[I have also tried the sandbox validateCompareTo tag as an alternative
with
similar results.]
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
Re: Tabbedpane forgets selected pane
radu_milos a écrit : Hello, Just moved from Weblogic 8.1 SP4, SUN RI 1.1 tomahawk 1.1.1. to WebLogic 81. SP4, myfaces 1.5 and tomahawk 1.1.6. Gained some functionality but also lost some functionality :( I am using a tabbed pane , and in each pane I have an independent jsf, as it follows : snip body bgcolor=#ff h:form id=devices h:panelGrid styleClass=tableColapse columns=5 columnClasses=tdBorder 1st, tabbebpane is not meaned to be used outside of a form. So a form must be surrouding the tabbedpane. Second, the jsf you include inside the tabbedpane contain a body ... /body tag. The behaviour of broweser when he sees nested body tag is undetermined, but you sure are generating invalid html (which itself my broke browser's form handling mecanisms) Lastly, tabbedpane's included jsf contains a h:form. You are not suppose to use h:form inside a form based component (like tabbedpane is). If you want subforms inside your tabbed pane that only validates value for subform, use the sandbox's s:subform component.
[Trinidad] documentation plugin
It is really nice to have the functionality of the Trinidad plugin that generates the tag documentation, but I was wondering if it would be possible to have it generate a frames-based documentation like the TLD documentation: http://myfaces.apache.org/tomahawk/tlddoc/index.html Currently the trinidad site is very informative with the tag documentation, but it is hard to navigate between components. The frame-based approach would make it much easier to switch between documentation for different components
[Trinidad] tr:messages renderer?
Sorry to be obtuse, but I am having difficulty finding the code for the renderer for tr:messages. I can see the renderer-type, but cannot seem to find the renderer-class declared anywhere or a Java file that matches *Messages*.java. Some of the documentation wasn't 100% clear on the tr:messages tag (text vs. message property) and I also wanted to see what skin selectors were being used by this component. Thanks, Andrew
Re: [Trinidad] tr:messages renderer?
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.MessageBoxRenderer skin docs are up-to-date for this component http://myfaces.apache.org/trinidad/skin-selectors.html On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote: Sorry to be obtuse, but I am having difficulty finding the code for the renderer for tr:messages. I can see the renderer-type, but cannot seem to find the renderer-class declared anywhere or a Java file that matches *Messages*.java. Some of the documentation wasn't 100% clear on the tr:messages tag (text vs. message property) and I also wanted to see what skin selectors were being used by this component. Thanks, Andrew -- Chordiant Software Inc. www.chordiant.com
Re: [Tomahawk] validateEqual problem for second field
Thanks for the explanation of the code which shows why it doesnt work.
However if I do take up your suggestion and put the validation on the second
field only then there is one use case where it is a particular problem; As
you may have noticed both my fields are not required fields - therefore the
user can submit a value for the first field only and the validation on the
second field will not execute and the form will be submitted without the two
fields being equal.
If both fields were required fields then we would not have this problem but
the user requirements in this case are the fields are non mandatory but if
one of them is filled in then the other must match.
So if I cant use this validator I need to find an alternative way to solve
this problem.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 11:12:44 -0600
I took a look into the code to make sure I knew what was going on and
here is what I found:
It looks like the problem you are having is due to the design of the
ValidateEqual class. It is performing its logic in the validation
phase using the EditableValueHolder.getValue() function. This presents
a problem on the first component. Reason as follows:
equal has an EqualValidator added to it during the view creation
equal2 has an EqualValidator added to it during the view creation
during the decode phase, equal and equal2 are decoded and the values
from the client are stored in the submittedValue property of each
component.
during the validation phase:
The equal component's processValidators method calls the validate
function. This function converts the submitted value. If there are no
problems, the validation of the component is called (validateValue
function). If the component is valid, the local value (setValue) is
called.
So, at the time that the equal is validating, equal2 has not set its
local value (it is currently null, only the submitted value is set)
and the submitted value is not converted.
So, equal cannot compare it's local value to equal2's local value
since equal2 is not yet validated.
This means that in order for the validate compare to and validate
equal components to work, they have to be on the second component as
the first component has to be already be validate, and be valid!
Otherwise, the local value is not set, which is what these validators
use to validate against.
So the short answer to your question is your use case is not
supported. The validators *have* to be only on the 2nd component.
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I agree with you but unfortunately the customer for whom I'm developing
the
software doesn't, but additionally the problem in itself is something we
should be able to solve relatively simply I would have thought as it may
be
a valid scenario in other software projects.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 10:41:39 -0600
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non
mandatory)
fields on a form are equal to each other but hitting some problems
related
to the order of the field validations.
In the example below the validation and error message attached to
the
second
field works fine. However for the validation on the first field it
seems
I
have to submit the form the fields are in twice if the fields are
equal
-
the first time it always displays the error message saying they are
unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
required=false
t:validateEqual for=equal /
/h:inputText
Does anyone know why this is happening or have a solution ?
[I have also tried the sandbox validateCompareTo tag as an
alternative
with
similar results.]
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
Re: [tobago] error not verbose enough
Hi Bernd, I'm sorry, I changed all the pages containing !DOCTYPE html PUBLIC -//... and removed it, now it works. So I don't know which was the page, this mail was just a parentheses to recall we can enhance the error messages (probably somewhere in prepareRender() to catch and rethrow with a more verbose text about wich page or include failed). Regards and thanks for answering so fast, Zied 2007/9/4, Bernd Bohmann [EMAIL PROTECTED]: Hello, can send the page, please. Regards Bernd Zied Hamdi wrote: Hi the good team, I'm experiencing a problem while I'm moving to facelets. This is absolutely normal until the point where I don't know where the problem occurs ;-p. In fact, I have an existing set of jsp that I attempted to transform to facelets templates. I had a lot of jsp includes until a deepness of 4. The probem is that when an exception occurs, there's no info on which page is beeing processed. Is there a way to activate a logger that writes which page is beeing included? (all I have is Invalid tag found: unexpected input while looking for attr name or '/' at line 3. Surroundings: '!DOCTYPE html PUBLIC -//W3C/') Thanks in advance if you have any idea... This is my exception to give you an idea :-) 16:31:57,593 ERROR [STDERR] 4 sept. 2007 16:31:57 com.sun.facelets.FaceletViewHandler *handleRenderException* GRAVE: Error Rendering View[/person/person.xhtml] *java.lang.IllegalArgumentException*: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(*Native Method*) at sun.reflect.NativeMethodAccessorImpl.invoke(* NativeMethodAccessorImpl.java:39*) at sun.reflect.DelegatingMethodAccessorImpl.invoke(* DelegatingMethodAccessorImpl.java:25*) at java.lang.reflect.Method.invoke(*Method.java:597*) at javax.faces.component.UIComponentBase$AttributesMap.put(* UIComponentBase.java:1590*) at javax.faces.component.UIComponentBase$AttributesMap.put(* UIComponentBase.java:1499*) at org.apache.myfaces.tobago.renderkit.html.StyleClasses.ensureStyleClasses (* StyleClasses.java:70*) at org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.createCssClass (* HtmlRendererUtil.java:119*) at org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.prepareRender (* HtmlRendererUtil.java:94*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.prepareRender (*DefaultLayoutRenderer.java:40*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:73*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.encodeChildrenOfComponent (*DefaultLayoutRenderer.java:47*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encodeChildren(* RenderUtil.java:56*) at org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent (*TabGroupRenderer.java:74*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView (*TabGroupRenderer.java:342*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.encodeEnd (*TabGroupRenderer.java:155*) at javax.faces.component.UIComponentBase.encodeEnd(* UIComponentBase.java:836*) at org.apache.myfaces.tobago.component.UITabGroup.encodeEnd(* UITabGroup.java:106*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:84*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent (*GridLayoutRenderer.java:366*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent (* UIGridLayout.java:276*) at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren (* UIPanelBase.java:43*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:77*) at org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent (*GridLayoutRenderer.java:366*) at org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(* UILayout.java:71*) at org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent (* UIGridLayout.java:276*) at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren (* UIPanelBase.java:43*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(* RenderUtil.java:77*) at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(*
Re: [Tomahawk] validateEqual problem for second field
Yes that does pose a problem, once again hitting the large JSF flaw of
using required as a flag instead of as a validator. I don't see an
adequate solution to that problem without using a custom component and
overriding the validate function or using and action or actionListener
to ensure that when one is given, both are given.
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
Thanks for the explanation of the code which shows why it doesnt work.
However if I do take up your suggestion and put the validation on the second
field only then there is one use case where it is a particular problem; As
you may have noticed both my fields are not required fields - therefore the
user can submit a value for the first field only and the validation on the
second field will not execute and the form will be submitted without the two
fields being equal.
If both fields were required fields then we would not have this problem but
the user requirements in this case are the fields are non mandatory but if
one of them is filled in then the other must match.
So if I cant use this validator I need to find an alternative way to solve
this problem.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 11:12:44 -0600
I took a look into the code to make sure I knew what was going on and
here is what I found:
It looks like the problem you are having is due to the design of the
ValidateEqual class. It is performing its logic in the validation
phase using the EditableValueHolder.getValue() function. This presents
a problem on the first component. Reason as follows:
equal has an EqualValidator added to it during the view creation
equal2 has an EqualValidator added to it during the view creation
during the decode phase, equal and equal2 are decoded and the values
from the client are stored in the submittedValue property of each
component.
during the validation phase:
The equal component's processValidators method calls the validate
function. This function converts the submitted value. If there are no
problems, the validation of the component is called (validateValue
function). If the component is valid, the local value (setValue) is
called.
So, at the time that the equal is validating, equal2 has not set its
local value (it is currently null, only the submitted value is set)
and the submitted value is not converted.
So, equal cannot compare it's local value to equal2's local value
since equal2 is not yet validated.
This means that in order for the validate compare to and validate
equal components to work, they have to be on the second component as
the first component has to be already be validate, and be valid!
Otherwise, the local value is not set, which is what these validators
use to validate against.
So the short answer to your question is your use case is not
supported. The validators *have* to be only on the 2nd component.
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I agree with you but unfortunately the customer for whom I'm developing
the
software doesn't, but additionally the problem in itself is something we
should be able to solve relatively simply I would have thought as it may
be
a valid scenario in other software projects.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 10:41:39 -0600
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non
mandatory)
fields on a form are equal to each other but hitting some problems
related
to the order of the field validations.
In the example below the validation and error message attached to
the
second
field works fine. However for the validation on the first field it
seems
I
have to submit the form the fields are in twice if the fields are
equal
-
the first time it always displays the error message saying they are
unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
required=false
t:validateEqual for=equal /
Re: [Tomahawk] validateEqual problem for second field
I'm pretty sure that I wrote the compareToValidator so that it will
work on either component, unlike the equalsValidator. However, I
doubt many people have used it as a validator for the first component
listed (I know that I don't use it this way), so there might be a
minor bug to fix.
On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote:
I took a look into the code to make sure I knew what was going on and
here is what I found:
It looks like the problem you are having is due to the design of the
ValidateEqual class. It is performing its logic in the validation
phase using the EditableValueHolder.getValue() function. This presents
a problem on the first component. Reason as follows:
equal has an EqualValidator added to it during the view creation
equal2 has an EqualValidator added to it during the view creation
during the decode phase, equal and equal2 are decoded and the values
from the client are stored in the submittedValue property of each
component.
during the validation phase:
The equal component's processValidators method calls the validate
function. This function converts the submitted value. If there are no
problems, the validation of the component is called (validateValue
function). If the component is valid, the local value (setValue) is
called.
So, at the time that the equal is validating, equal2 has not set its
local value (it is currently null, only the submitted value is set)
and the submitted value is not converted.
So, equal cannot compare it's local value to equal2's local value
since equal2 is not yet validated.
This means that in order for the validate compare to and validate
equal components to work, they have to be on the second component as
the first component has to be already be validate, and be valid!
Otherwise, the local value is not set, which is what these validators
use to validate against.
So the short answer to your question is your use case is not
supported. The validators *have* to be only on the 2nd component.
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I agree with you but unfortunately the customer for whom I'm developing the
software doesn't, but additionally the problem in itself is something we
should be able to solve relatively simply I would have thought as it may be
a valid scenario in other software projects.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 10:41:39 -0600
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non
mandatory)
fields on a form are equal to each other but hitting some problems
related
to the order of the field validations.
In the example below the validation and error message attached to the
second
field works fine. However for the validation on the first field it seems
I
have to submit the form the fields are in twice if the fields are equal
-
the first time it always displays the error message saying they are
unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
required=false
t:validateEqual for=equal /
/h:inputText
Does anyone know why this is happening or have a solution ?
[I have also tried the sandbox validateCompareTo tag as an alternative
with
similar results.]
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
_
Get Pimped! FREE emoticon packs from Windows Live -
http://www.pimpmylive.co.uk
Re: [Trinidad] documentation plugin
That'd be a very useful option for the tagdoc plugin - it'd certainly make it much easier to navigate between components. -- Adam On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote: It is really nice to have the functionality of the Trinidad plugin that generates the tag documentation, but I was wondering if it would be possible to have it generate a frames-based documentation like the TLD documentation: http://myfaces.apache.org/tomahawk/tlddoc/index.html Currently the trinidad site is very informative with the tag documentation, but it is hard to navigate between components. The frame-based approach would make it much easier to switch between documentation for different components
[Tomahawk] validateEqual problem for second field
You may find it useful. Today I faced similar problem with
validating-two-separate-mandatory-fields.
I ended up using h:hiddenText value=1 required=true
validator=#{validating.function} / somewhere after these two input
components. So validating function is invoked in processValidations
phase even if input components don't have any value.
tr:hiddenText throws exception if it's value is empty, so i chose to use
h taglib instead. Was just going to look into it's code :)
Hope it helps.
Suhel Rizvi wrote:
Thanks for the explanation of the code which shows why it doesnt work.
However if I do take up your suggestion and put the validation on the
second field only then there is one use case where it is a particular
problem; As you may have noticed both my fields are not required
fields - therefore the user can submit a value for the first field
only and the validation on the second field will not execute and the
form will be submitted without the two fields being equal.
If both fields were required fields then we would not have this
problem but the user requirements in this case are the fields are non
mandatory but if one of them is filled in then the other must match.
So if I cant use this validator I need to find an alternative way to
solve this problem.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 11:12:44 -0600
I took a look into the code to make sure I knew what was going on and
here is what I found:
It looks like the problem you are having is due to the design of the
ValidateEqual class. It is performing its logic in the validation
phase using the EditableValueHolder.getValue() function. This presents
a problem on the first component. Reason as follows:
equal has an EqualValidator added to it during the view creation
equal2 has an EqualValidator added to it during the view creation
during the decode phase, equal and equal2 are decoded and the values
from the client are stored in the submittedValue property of each
component.
during the validation phase:
The equal component's processValidators method calls the validate
function. This function converts the submitted value. If there are no
problems, the validation of the component is called (validateValue
function). If the component is valid, the local value (setValue) is
called.
So, at the time that the equal is validating, equal2 has not set its
local value (it is currently null, only the submitted value is set)
and the submitted value is not converted.
So, equal cannot compare it's local value to equal2's local value
since equal2 is not yet validated.
This means that in order for the validate compare to and validate
equal components to work, they have to be on the second component as
the first component has to be already be validate, and be valid!
Otherwise, the local value is not set, which is what these validators
use to validate against.
So the short answer to your question is your use case is not
supported. The validators *have* to be only on the 2nd component.
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I agree with you but unfortunately the customer for whom I'm
developing the
software doesn't, but additionally the problem in itself is
something we
should be able to solve relatively simply I would have thought as
it may be
a valid scenario in other software projects.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 10:41:39 -0600
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non
mandatory)
fields on a form are equal to each other but hitting some problems
related
to the order of the field validations.
In the example below the validation and error message attached
to the
second
field works fine. However for the validation on the first field
it seems
I
have to submit the form the fields are in twice if the fields
are equal
-
the first time it always displays the error message saying they
are
unequal
but seems to realize they are equal on second submit.
h:inputText id=equal
value=#{validateForm.equal}
required=false
t:validateEqual for=equa2l /
/h:inputText
h:inputText id=equal2
value=#{validateForm.equal2}
Re: [TRINIDAD] Proposal - fieldset/legend component
I like that name too. Should the text for it be text like on other components or caption? Regarding this example mentioned earlier: tr:panelFormLayout tr:panelCaptionGroup caption=Personal Details tr:inputText.../ /tr:panelCaptionGroup /tr:panelFormLayout this could potentially be supported but without the lines drawn along the sides. I'm thinking that when placed directly inside of a panelFormLayout, it could have the simple separator lines (exactly like tr:group today) but with the caption appearing on top of the upper separator line, e.g.: label1field1 -- Caption - label2field2 label3field3 label4field4 and when outside of a panelFormLayout (as in your proposal) where you don't have to play well with the table structure of the form layout, the PanelCaptionGroupRenderer will use the normal fieldset elements. Regards, Matt On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote: Yeah, I initially went with the enhanced panelFormLayout approach and decided against it. The name is also frustrating, so how about tr:panelCaptionGroup ...? I think I like that name. -- Adam I'll give it 24hrs for other people to chime in, then I'll go with the above. Thanks, Danny On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: Yep, I agree that the Layout suffix shouldn't be there. I'm wondering if we want a name more abstracted from the HTML fieldset concept, though none really come to mind. Or, as a perhaps more radical suggestion, could this be something embedded inside panelFormLayout? Like if we supported caption on af:group? af:panelFormLayout af:group caption=Personal Details af:inputText.../ /af:group /af:panelFormLayout This has some major disadvantages, though. It's probably significantly harder to implement (more grunge in the already grungy PanelFormLayout code) and no way to use it outside of panelFormLayout. So I've probably just talked myself out of this suggestion. :) -- Adam On 8/30/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, True, panelBox does not include the Layout suffix (a fact I somehow forgotten / overlooked), so stripping the Layout suffix is fine with me. I like the attribute shortcut for the legend as well. ~ Simon On 8/30/07, Danny Robinson [EMAIL PROTECTED] wrote: I knocked together this component to see what it would look like and what skin selectors would be required. Here's some tag examples and an attached screenshot. FWIW while Simon's name suggestion was better, I'm not fan of the 'Layout' suffix, as it doesn't actually perform layout, and is therefore closer in functionality to panelBox. tr:panelFieldsetLayout captionText=Personal Details tr:panelFormLayout tr:inputText label=First Name / tr:inputText label=Middle Initial columns=1/ tr:inputText label=Family Name / tr:selectOneChoice label=Suffix / /tr:panelFormLayout /tr:panelFieldsetLayout OR tr:panelFieldsetLayout captionText=This shouldn't appear f:facet name=caption tr:icon name=error / /f:facet tr:inputDate label=Date of Birth / /tr:panelFieldsetLayout Thoughts anyone, D. On 8/29/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, I would prefer something along the lines of tr:panelFieldSetLayout with a legend facet. Regards, ~ Simon On 8/29/07, Danny Robinson [EMAIL PROTECTED] wrote: Would there be interest in a skinnable/ajaxified component that rendered output using html fieldset/legend. We'd like to include this in our applications and I'm keen to keep our users away from introducing other component libraries just for the odd extra component. I'm struggling to think of a nice sounding tag name, other than tr:panelBoxAndLegend but it could look something like: tr:panelBoxAndLegend title=The legend ... /tr:panelBoxAndLegend Thanks, Danny -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com
Re: [Tomahawk] validateEqual problem for second field
Yes, and having required=false value=null is why validateCompareTo
doesn't work. validateCompareTo doesn't do validation if the foreign
component has no value set. That's a reasonable solution for every
case but equals.
// Don't perform validation if the foreign value is null
if (null == foreignValue)
{
return;
}
You'd need to change the above code to instead do the right thing
based on the equals operation.
For equals, null on foreign component be a validation error (local
value must always be non-null).
I'd say the results are correct for not-equals and undefined for any
other comparator, so the current behavior would be correct for
everything but equals.
Seems like a reasonable patch to make, so open a JIRA issue and attach the fix.
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
Thanks for the explanation of the code which shows why it doesnt work.
However if I do take up your suggestion and put the validation on the second
field only then there is one use case where it is a particular problem; As
you may have noticed both my fields are not required fields - therefore the
user can submit a value for the first field only and the validation on the
second field will not execute and the form will be submitted without the two
fields being equal.
If both fields were required fields then we would not have this problem but
the user requirements in this case are the fields are non mandatory but if
one of them is filled in then the other must match.
So if I cant use this validator I need to find an alternative way to solve
this problem.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 11:12:44 -0600
I took a look into the code to make sure I knew what was going on and
here is what I found:
It looks like the problem you are having is due to the design of the
ValidateEqual class. It is performing its logic in the validation
phase using the EditableValueHolder.getValue() function. This presents
a problem on the first component. Reason as follows:
equal has an EqualValidator added to it during the view creation
equal2 has an EqualValidator added to it during the view creation
during the decode phase, equal and equal2 are decoded and the values
from the client are stored in the submittedValue property of each
component.
during the validation phase:
The equal component's processValidators method calls the validate
function. This function converts the submitted value. If there are no
problems, the validation of the component is called (validateValue
function). If the component is valid, the local value (setValue) is
called.
So, at the time that the equal is validating, equal2 has not set its
local value (it is currently null, only the submitted value is set)
and the submitted value is not converted.
So, equal cannot compare it's local value to equal2's local value
since equal2 is not yet validated.
This means that in order for the validate compare to and validate
equal components to work, they have to be on the second component as
the first component has to be already be validate, and be valid!
Otherwise, the local value is not set, which is what these validators
use to validate against.
So the short answer to your question is your use case is not
supported. The validators *have* to be only on the 2nd component.
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I agree with you but unfortunately the customer for whom I'm developing
the
software doesn't, but additionally the problem in itself is something we
should be able to solve relatively simply I would have thought as it may
be
a valid scenario in other software projects.
From: Andrew Robinson [EMAIL PROTECTED]
Reply-To: MyFaces Discussion users@myfaces.apache.org
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: [Tomahawk] validateEqual problem for second field
Date: Tue, 4 Sep 2007 10:41:39 -0600
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL PROTECTED] wrote:
I am using the tomahawk validateEqual tag to check if two (non
mandatory)
fields on a form are equal to each other but hitting some problems
related
to the order of the field validations.
In the example below the validation and error message attached to
the
second
field works fine. However for the validation on the first field it
seems
I
have to submit the form the fields are in twice if the fields are
equal
-
[Trinidad] tr:messages - no style selectors for each message?
While looking at the tr:messages component and its renderer, I couldn't find the ability for some functionality. In the MessageBoxRenderer._renderGlobalMessages function, it doesn't appear there is any why to style each message text based on severity. The icon is severity based, by not the text. For example, I'd like to have errors with red color, warnings in orange and info messages in black. Did I miss this ability, or is it not possible at the moment? Desired output simple example: ul li class=af|messages::error-texttest/li li class=af|messages::warning-texttest/li /ul
Re: [TRINIDAD] Proposal - fieldset/legend component
On 9/4/07, Matt Cooper [EMAIL PROTECTED] wrote: I like that name too. Should the text for it be text like on other components or caption? We already have an example of convenience-attribute+facet on column; there it's header and headerText. So perhaps the facet should be caption and the attribute captionText. -- Adam Regarding this example mentioned earlier: tr:panelFormLayout tr:panelCaptionGroup caption=Personal Details tr:inputText.../ /tr:panelCaptionGroup /tr:panelFormLayout this could potentially be supported but without the lines drawn along the sides. I'm thinking that when placed directly inside of a panelFormLayout, it could have the simple separator lines (exactly like tr:group today) but with the caption appearing on top of the upper separator line, e.g.: label1field1 -- Caption - label2field2 label3field3 label4field4 and when outside of a panelFormLayout (as in your proposal) where you don't have to play well with the table structure of the form layout, the PanelCaptionGroupRenderer will use the normal fieldset elements. Regards, Matt On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote: Yeah, I initially went with the enhanced panelFormLayout approach and decided against it. The name is also frustrating, so how about tr:panelCaptionGroup ...? I think I like that name. -- Adam I'll give it 24hrs for other people to chime in, then I'll go with the above. Thanks, Danny On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote: Yep, I agree that the Layout suffix shouldn't be there. I'm wondering if we want a name more abstracted from the HTML fieldset concept, though none really come to mind. Or, as a perhaps more radical suggestion, could this be something embedded inside panelFormLayout? Like if we supported caption on af:group? af:panelFormLayout af:group caption=Personal Details af:inputText.../ /af:group /af:panelFormLayout This has some major disadvantages, though. It's probably significantly harder to implement (more grunge in the already grungy PanelFormLayout code) and no way to use it outside of panelFormLayout. So I've probably just talked myself out of this suggestion. :) -- Adam On 8/30/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, True, panelBox does not include the Layout suffix (a fact I somehow forgotten / overlooked), so stripping the Layout suffix is fine with me. I like the attribute shortcut for the legend as well. ~ Simon On 8/30/07, Danny Robinson [EMAIL PROTECTED] wrote: I knocked together this component to see what it would look like and what skin selectors would be required. Here's some tag examples and an attached screenshot. FWIW while Simon's name suggestion was better, I'm not fan of the 'Layout' suffix, as it doesn't actually perform layout, and is therefore closer in functionality to panelBox. tr:panelFieldsetLayout captionText=Personal Details tr:panelFormLayout tr:inputText label=First Name / tr:inputText label=Middle Initial columns=1/ tr:inputText label=Family Name / tr:selectOneChoice label=Suffix / /tr:panelFormLayout /tr:panelFieldsetLayout OR tr:panelFieldsetLayout captionText=This shouldn't appear f:facet name=caption tr:icon name=error / /f:facet tr:inputDate label=Date of Birth / /tr:panelFieldsetLayout Thoughts anyone, D. On 8/29/07, Simon Lessard [EMAIL PROTECTED] wrote: Hello Danny, I would prefer something along the lines of tr:panelFieldSetLayout with a legend facet. Regards, ~ Simon On 8/29/07, Danny Robinson [EMAIL PROTECTED] wrote: Would there be interest in a skinnable/ajaxified component that rendered output using html fieldset/legend. We'd like to include this in our applications and I'm keen to keep our users away from introducing other component libraries just for the odd extra component. I'm struggling to think of a nice sounding tag name, other than tr:panelBoxAndLegend but it could look something like: tr:panelBoxAndLegend title=The legend ... /tr:panelBoxAndLegend Thanks, Danny
Re: [Trinidad] tr:messages - no style selectors for each message?
I also noticed that the icon is rendered in the messages header instead of next to each message. As a result, the user will not know which messages are errors and which are informational, etc. Could this be enhanced, changed so that per list item, the icon and then the text are rendered, and the header has the most severe icon? To make it backward compatible, I would presume that the icon was not added to each message or that the icon per-list item would have a different style selector (like af|messages::message::error-icon)? On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote: While looking at the tr:messages component and its renderer, I couldn't find the ability for some functionality. In the MessageBoxRenderer._renderGlobalMessages function, it doesn't appear there is any why to style each message text based on severity. The icon is severity based, by not the text. For example, I'd like to have errors with red color, warnings in orange and info messages in black. Did I miss this ability, or is it not possible at the moment? Desired output simple example: ul li class=af|messages::error-texttest/li li class=af|messages::warning-texttest/li /ul
How to navigate on DisclosureEvent using a tr:showDetailItem
Hi,
my application has a panel accordion component and I need to navigate to
different pages on disclosure of each of the showDetailItem's that it holds.
For example:
tr:panelAccordion discloseNone=true
tr:showDetailItem text=PA1 disclosureListener=#{
backingBean.navigateToAppPage}
tr:outputText value=detail1/
/tr:showDetailItem
tr:showDetailItem text=PA2 disclosureListener=#{
backingBean.navigateToMgmtPage}
tr:outputText value=detail2/
/tr:showDetailItem
/tr:panelAccordion
I tried using NavigationHandler code in the backing bean methods as follows:
public void navigate(DisclosureEvent de){
try{
NavigationHandler navigator = FacesContext.getCurrentInstance
().getApplication().getNavigationHandler();
navigator.handleNavigation( FacesContext.getCurrentInstance(),
null, xyz );
FacesContext.getCurrentInstance().renderResponse();
}
catch(Exception e){.}
xyz is a navigation outcome definition:
navigation-rule
navigation-case
from-outcomexyz/from-outcome
from-actionxyz/from-action
to-view-id/TestNavigation.jsp/to-view-id
redirect/
/navigation-case
/navigation-rule
but this doesnot work.
Any suggestions as to how to achieve this navigation?
Re: JSF Newbie needs help with selectOneMenu and valueChangeListener
Ok, I think I figured out my problem. I'll summarize here in the hopes that this helps someone. I initially got the solution half right, by implementing a Converter to convert between the String representation of an Employee and an Employee object. However, I was still failing during the validation phase even though I had implemented a null validator that always returned. The problem is that the UISelectOne class has a validateValue method that attempts to validate that the selected item is in fact contained within the UISelectItems list. It does this by essentially calling java.lang.Object.equals() on the selected object to compare it against items in the list. Even though all the data fields within the Employee object instances were the same, they had different object references, and therefore were deemed to be different. This ultimately led to a failure during validation. In order to solve this, I had to implement an equals method of my own in the Employee class that overrides the default java.lang.Object.equals method. This equals method compared the data fields within two Employee objects and declared them equal if all fields were equal. To summarize, if you want to populate a UISelectOne control with a list of objects that are not simple Strings, you need to do two things; implement a Converter to go back and forth between String and Object, and override java.lang.Object.equals with your own equals implementation that compares the Object's data fields. Hope this helps someone out there. Good luck finding this documented somewhere. -- View this message in context: http://www.nabble.com/JSF-Newbie-needs-help-with-selectOneMenu-and-valueChangeListener-tf4341404.html#a12484864 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Chosen label from an HtmlSelectOneMenu?
You must iterate on component children, look at each uiselectitem and uiselectitems, and queary each of them until you get a SelectItem which value match the current one. you can then get label of this SelectItem. Note that this iteration will call the various EL associated with your select menu child components. This is because JSF never cache EL results. Rob99 a écrit : Hello, I have bound an HtmlSelectOneMenu to my backing bean using binding=... on the tag. I can get the chosen value easily enough with: HtmlSelectOneMenu m; ... String chosenValue = m.getValue(); Is there any way to get the label of the chosen item instead of the value from the component? Or is it absolutely necessary to query the model that populated the HtmlSelectOneMenu in the first place? -Thank you!
Re: How to navigate on DisclosureEvent using a tr:showDetailItem
Remove from-action. There is no action here (you passed
null to the NavigationHandler!), just an outcome.
-- Adam
On 9/4/07, Rakesh Patnaik [EMAIL PROTECTED] wrote:
Hi,
my application has a panel accordion component and I need to navigate to
different pages on disclosure of each of the showDetailItem's that it holds.
For example:
tr:panelAccordion discloseNone=true
tr:showDetailItem text=PA1
disclosureListener=#{backingBean.navigateToAppPage}
tr:outputText value=detail1/
/tr:showDetailItem
tr:showDetailItem text=PA2
disclosureListener=#{backingBean.navigateToMgmtPage}
tr:outputText value=detail2/
/tr:showDetailItem
/tr:panelAccordion
I tried using NavigationHandler code in the backing bean methods as follows:
public void navigate(DisclosureEvent de){
try{
NavigationHandler navigator =
FacesContext.getCurrentInstance().getApplication().getNavigationHandler();
navigator.handleNavigation ( FacesContext.getCurrentInstance(),
null, xyz );
FacesContext.getCurrentInstance().renderResponse();
}
catch(Exception e){.}
xyz is a navigation outcome definition:
navigation-rule
navigation-case
from-outcomexyz/from-outcome
from-actionxyz/from-action
to-view-id/TestNavigation.jsp/to-view-id
redirect/
/navigation-case
/navigation-rule
but this doesnot work.
Any suggestions as to how to achieve this navigation?
[Trinidad] panelLabelAndMessage still needs extra message tag?!
After reading the tag doc for panelLabelAndMessage I would have
thought that in the following example the tr:message would not
be needed.
However if I omit the tr:message then on validation failure it
fails silently without ever showing a message.
(Trinidad 1.2.1)
tr:panelLabelAndMessage styleClass=inputLabel_10 label=#{Output.BRANCH}
showRequired=true
tr:selectOneChoice id=employeeBranchId value=#{_employeeList.employeeBranchId}
required=true unselectedLabel= simple=true
f:selectItems value=#{_employeeList.employeeBranchItems}/
/tr:selectOneChoice
tr:message for=employeeBranchId/
/tr:panelLabelAndMessage
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
Fixed in 1.0.3-SNAPSHOT
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
After reading the tag doc for panelLabelAndMessage I would have
thought that in the following example the tr:message would not
be needed.
However if I omit the tr:message then on validation failure it
fails silently without ever showing a message.
(Trinidad 1.2.1)
tr:panelLabelAndMessage styleClass=inputLabel_10 label=#{Output.BRANCH}
showRequired=true
tr:selectOneChoice id=employeeBranchId
value=#{_employeeList.employeeBranchId} required=true unselectedLabel=
simple=true
f:selectItems value=#{_employeeList.employeeBranchItems}/
/tr:selectOneChoice
tr:message for=employeeBranchId/
/tr:panelLabelAndMessage
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
Thanks for the info, Andrew!
Adam, will 1.2.2 contain this fix, too?
Or will you strictly only transfer fixes from 1.0._2_?
Depending on how many changes there were in between 1.0.2 and 1.0.3
maybe it would make sense to skip 1.0.2 and directly go to 1.2.3?
Well, 1.2.3 really makes for a nicer version number anyhow ;-
Also releases and corresponding downloads seem to be a little mixed
up currently:
http://myfaces.apache.org/ has latest news about 1.0._1_ and 1.2.1
If you follow the download link from that main page you'll find
core, tomahawk, tobago, but no trinidad.
If you first select trinidad project then go to downloads you'll
find only 1.0.2 even though the release notes available on the
trinidad project page talk about 1.0.3.
The trinidad download page has a link to nightly builds, but I haven't
found any when following that link.
Andrew Robinson wrote:
Fixed in 1.0.3-SNAPSHOT
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
After reading the tag doc for panelLabelAndMessage I would have
thought that in the following example the tr:message would not
be needed.
However if I omit the tr:message then on validation failure it
fails silently without ever showing a message.
(Trinidad 1.2.1)
tr:panelLabelAndMessage styleClass=inputLabel_10 label=#{Output.BRANCH}
showRequired=true
tr:selectOneChoice id=employeeBranchId value=#{_employeeList.employeeBranchId}
required=true unselectedLabel= simple=true
f:selectItems value=#{_employeeList.employeeBranchItems}/
/tr:selectOneChoice
tr:message for=employeeBranchId/
/tr:panelLabelAndMessage
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
While we're at it - a few more questions regarding panelLabelAndMessage: If there are multiple child components will messages for all of them be shown? If so, in a single place/message component or individually where the messages would be if the components were not simple? Does it work if child components are nested in a panelHorizontalLayout? Andrew Robinson wrote: Fixed in 1.0.3-SNAPSHOT
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote: While we're at it - a few more questions regarding panelLabelAndMessage: If there are multiple child components will messages for all of them be shown? No, it requires a for attribute. That is the component that the label and the message are for. Also in 1.0.3 the code will automatically use the first EditableValueHolder it finds if the for is not given, but it still only supports one component. To get multiple components, you have to have multiple panelLabelAndMessage components. Does it work if child components are nested in a panelHorizontalLayout? Yes.
[Trinidad] Working with large tables
Good evening. I'm wondering if there is a way to use tr:tables with large datasets that allows us to fetch the specific data page from the database upon navigation to that page, instead of having the whole list in memory. It works fine for small tables, but for tables with a couple million of records it could hit the server memory really hard. I know Tomahawk addresses this issue for their tables here http://wiki.apache.org/myfaces/WorkingWithLargeTables . I imagine I could just extend a java.util.List and override the getSize() - that coupled with the rangechangelisteners could do the trick. The question is: is it already done? -- Francisco Passos
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
Andrew Robinson wrote: No, it requires a for attribute. That is the component that the label and the message are for. Also in 1.0.3 the code will automatically use the first EditableValueHolder it finds if the for is not given, but it still only supports one component. To get multiple components, you have to have multiple panelLabelAndMessage components. Hm, that kind of defeats the purpose of panelLabelAndMessage: I nested firstName and lastName fields in a single panelLabelAndMessage to have them shown in a single row of a form managed by panelFormLayout. Of course I'd like to show messages for both of them. How can I do that? Can I switch the automatic message part OFF and then add two tr:message tag (one for each input field)? Then again that would require some additional layout to get the messages to appear under the correct field. It really would be easiest to be able to have a semi-simple where the component does not manage its label, but manages its own message. simple=message-only ? BTW: The same structure repeats in my app with other pairs with other pairs (zip/city, start/end date, street/no, ...).
Re: Trinidad 1.2.1: SelectOrderShuttle leading/trailingDescShown Fails For Me
Having thought about this following your FYI (thank you for the hint), I
realized that Tiles must indeed be adding a tiles name prefix to the
name and ID attributes. The shuttle component is in a tile whose
definition name is, not surprisingly, content.
Given this, however, I still would classify this behavior in Trinidad as
a bug based on the following reasoning. The component code that is
generating the JavaScript variables:
content_shuttle1_leading_desc
content_shuttle1_trailing_desc
appears to use a global replace of underscore for colon (I didn't check
the Java code for this, but it seems reasonable based upon the generated
ID); however, the code in the generated JavaScript function
TrShuttleProxy._getDescArray that searches for an element match via ID
uses a single or first replace of underscore for colon. This
inconsistency in the handling of the modification of element IDs will
always cause a problem for any code, Tiles or otherwise that adds
something with a colon to the ID.
Therefore, I would re-categorize this as an integration bug instead of a
general Trinidad bug, but I would suggest that it is still a bug in
Trinidad that should be fixed. If nothing else, I will need to,
hopefully temporarily, create a duplicate TrShuttleProxy._getDescArray
function with the suggested patch in order to get this functionality to
work with Tiles or alternatively modify the Java generation code,
something I would rather not do, since the latter interferes with easy
upgrades.
Do you agree that this is a bug and that it should be fixed?
-= Gregg =-
Adam Winer wrote:
Gregg,
FYI, I don't think Trinidad is adding the content:. Perhaps
Tiles 2.0 is (I've not looked at the newer version).
-- Adam
On 9/3/07, Gregg Leichtman [EMAIL PROTECTED] wrote:
I have found a bug in the generated JavaScript for the Select*Shuttle
components. A patch follows:
TrShuttleProxy._getDescArray = function(listName) {
// var descArray = window[listName.replace(':','_') + '_desc'];
var descArray = window[listName.replace(/:/g,'_') + '_desc']; // gsl fix
return descArray;
}
where listName is content:shuttle1:leading.
The problem is that the listName is not using a global replace; therefore
only the first ':' is being replaced. This worked fine in ADF Faces before
porting to Trinidad where the listName was just shuttle1:leading. Note,
however, that Trinidad now adds an additional content prefix to the
generated inline JavaScript variables:
content_shuttle1_leading_desc=new Array('The First Item
Desc',
'The Second Item Desc',
'The Third Item Desc','');
content_shuttle1_trailing_desc=new Array('');
This means that a global replace needs to be done to create the proper
variable name for matching in the JavaScript code. I will report this on
Jira for the Trinidad project.
I don't have access to the latest snapshots. The last one I see is from
July 11th at:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/trinidad/trinidad-impl/1.2.1-SNAPSHOT/
If this has been fixed already, then please clear my bug report which
should have the side benefit of letting people know that the bug has been
found and fixed already.
-= Gregg =-
signature.asc
Description: OpenPGP digital signature
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
Why don't you submit a wish jira for the functionality, sounds like something that makes sense to develop. On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote: Andrew Robinson wrote: No, it requires a for attribute. That is the component that the label and the message are for. Also in 1.0.3 the code will automatically use the first EditableValueHolder it finds if the for is not given, but it still only supports one component. To get multiple components, you have to have multiple panelLabelAndMessage components. Hm, that kind of defeats the purpose of panelLabelAndMessage: I nested firstName and lastName fields in a single panelLabelAndMessage to have them shown in a single row of a form managed by panelFormLayout. Of course I'd like to show messages for both of them. How can I do that? Can I switch the automatic message part OFF and then add two tr:message tag (one for each input field)? Then again that would require some additional layout to get the messages to appear under the correct field. It really would be easiest to be able to have a semi-simple where the component does not manage its label, but manages its own message. simple=message-only ? BTW: The same structure repeats in my app with other pairs with other pairs (zip/city, start/end date, street/no, ...).
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
Thanks for the info, Andrew!
Adam, will 1.2.2 contain this fix, too?
Or will you strictly only transfer fixes from 1.0._2_?
1.2.2 is exactly 1.0.2 + 1.2 changes.
Depending on how many changes there were in between 1.0.2 and 1.0.3
maybe it would make sense to skip 1.0.2 and directly go to 1.2.3?
Well, 1.2.3 really makes for a nicer version number anyhow ;-
Also releases and corresponding downloads seem to be a little mixed
up currently:
http://myfaces.apache.org/ has latest news about 1.0._1_ and 1.2.1
If you follow the download link from that main page you'll find
core, tomahawk, tobago, but no trinidad.
If you first select trinidad project then go to downloads you'll
find only 1.0.2 even though the release notes available on the
trinidad project page talk about 1.0.3.
The trinidad download page has a link to nightly builds, but I haven't
found any when following that link.
Matthias, can you look at these?
-- Adam
Andrew Robinson wrote:
Fixed in 1.0.3-SNAPSHOT
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
After reading the tag doc for panelLabelAndMessage I would have
thought that in the following example the tr:message would not
be needed.
However if I omit the tr:message then on validation failure it
fails silently without ever showing a message.
(Trinidad 1.2.1)
tr:panelLabelAndMessage styleClass=inputLabel_10 label=#{
Output.BRANCH} showRequired=true
tr:selectOneChoice id=employeeBranchId
value=#{_employeeList.employeeBranchId} required=true unselectedLabel=
simple=true
f:selectItems
value=#{_employeeList.employeeBranchItems}/
/tr:selectOneChoice
tr:message for=employeeBranchId/
/tr:panelLabelAndMessage
Re: [Trinidad] panelLabelAndMessage still needs extra message tag?!
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote: Andrew Robinson wrote: No, it requires a for attribute. That is the component that the label and the message are for. Also in 1.0.3 the code will automatically use the first EditableValueHolder it finds if the for is not given, but it still only supports one component. To get multiple components, you have to have multiple panelLabelAndMessage components. Hm, that kind of defeats the purpose of panelLabelAndMessage: I nested firstName and lastName fields in a single panelLabelAndMessage to have them shown in a single row of a form managed by panelFormLayout. Of course I'd like to show messages for both of them. How can I do that? The simplest way I can think of is to use panelLabelAndMessage containing a panelHorizontalLayout with two non-simple fields, where you haven't set the label on either (but do set the shortDesc attribute for accessibility). -- Adam Can I switch the automatic message part OFF and then add two tr:message tag (one for each input field)? Then again that would require some additional layout to get the messages to appear under the correct field. It really would be easiest to be able to have a semi-simple where the component does not manage its label, but manages its own message. simple=message-only ? BTW: The same structure repeats in my app with other pairs with other pairs (zip/city, start/end date, street/no, ...).
Re: Trinidad 1.2.1: SelectOrderShuttle leading/trailingDescShown Fails For Me
Oh, absolutely, it's a bug, and we'll apply the fix you've provided.
I'm just pointing out that it's a really long-standing one, and that:
'This worked fine in ADF Faces before
porting to Trinidad where the listName was just shuttle1:leading.
Note, however, that Trinidad now adds an additional content prefix'
... isn't quite right, since the bug existed in ADF Faces too,
and Trinidad doesn't add the content prefix itself.
-- Adam
On 9/4/07, Gregg Leichtman [EMAIL PROTECTED] wrote:
Having thought about this following your FYI (thank you for the hint), I
realized that Tiles must indeed be adding a tiles name prefix to the
name and ID attributes. The shuttle component is in a tile whose
definition name is, not surprisingly, content.
Given this, however, I still would classify this behavior in Trinidad as
a bug based on the following reasoning. The component code that is
generating the JavaScript variables:
content_shuttle1_leading_desc
content_shuttle1_trailing_desc
appears to use a global replace of underscore for colon (I didn't check
the Java code for this, but it seems reasonable based upon the generated
ID); however, the code in the generated JavaScript function
TrShuttleProxy._getDescArray that searches for an element match via ID
uses a single or first replace of underscore for colon. This
inconsistency in the handling of the modification of element IDs will
always cause a problem for any code, Tiles or otherwise that adds
something with a colon to the ID.
Therefore, I would re-categorize this as an integration bug instead of a
general Trinidad bug, but I would suggest that it is still a bug in
Trinidad that should be fixed. If nothing else, I will need to,
hopefully temporarily, create a duplicate TrShuttleProxy._getDescArray
function with the suggested patch in order to get this functionality to
work with Tiles or alternatively modify the Java generation code,
something I would rather not do, since the latter interferes with easy
upgrades.
Do you agree that this is a bug and that it should be fixed?
-= Gregg
=-
Adam Winer wrote:
Gregg,
FYI, I don't think Trinidad is adding the content:. Perhaps
Tiles 2.0 is (I've not looked at the newer version).
-- Adam
On 9/3/07, Gregg Leichtman [EMAIL PROTECTED] wrote:
I have found a bug in the generated JavaScript for the Select*Shuttle
components. A patch follows:
TrShuttleProxy._getDescArray = function(listName) {
// var descArray = window[listName.replace(':','_') + '_desc'];
var descArray = window[listName.replace(/:/g,'_') + '_desc']; // gsl
fix
return descArray;
}
where listName is content:shuttle1:leading.
The problem is that the listName is not using a global replace;
therefore
only the first ':' is being replaced. This worked fine in ADF Faces
before
porting to Trinidad where the listName was just shuttle1:leading.
Note,
however, that Trinidad now adds an additional content prefix to the
generated inline JavaScript variables:
content_shuttle1_leading_desc=new Array('The First Item
Desc',
'The Second Item Desc',
'The Third Item Desc','');
content_shuttle1_trailing_desc=new Array('');
This means that a global replace needs to be done to create the proper
variable name for matching in the JavaScript code. I will report this
on
Jira for the Trinidad project.
I don't have access to the latest snapshots. The last one I see is
from
July 11th at:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/trinidad/trinidad-impl/1.2.1-SNAPSHOT/
If this has been fixed already, then please clear my bug report which
should have the side benefit of letting people know that the bug has
been
found and fixed already.
-= Gregg =-
Re: [Trinidad] Working with large tables
The model for the Trinidad table is not java.util.List. It's org.apache.myfaces.trinidad.model.CollectionModel; and Trinidad also supports javax.faces.model.DataModel. Both of these fully support large datasets. The Tomahawk page you refer to is 100% applicable to Trinidad as well, as it talks about the JSF DataModel API, not anything Tomahawk-specific. If you want to support efficient Trinidad sorting on large datasets, you'd need to implement the full CollectionModel API, not just DataModel. -- Adam On 9/4/07, Francisco Passos [EMAIL PROTECTED] wrote: Good evening. I'm wondering if there is a way to use tr:tables with large datasets that allows us to fetch the specific data page from the database upon navigation to that page, instead of having the whole list in memory. It works fine for small tables, but for tables with a couple million of records it could hit the server memory really hard. I know Tomahawk addresses this issue for their tables here http://wiki.apache.org/myfaces/WorkingWithLargeTables . I imagine I could just extend a java.util.List and override the getSize() - that coupled with the rangechangelisteners could do the trick. The question is: is it already done? -- Francisco Passos
Re: [TRINIDAD] - IMPORTANT - Custom Skin Developers
The old parameter was trinidadinternal, and therefore was never officially supported. If we were changing from one supported name to another, I'd agree that we should keep the old name around, but supporting backwards compatibility for anything trinidadinternal is a precedent I don't think we should set... -- Adam On 8/31/07, Martin Marinschek [EMAIL PROTECTED] wrote: Hi Danny, eventually we could additionally support also the old name for the configuration parameter, and only phase this out in a major release? regards, Martin On 8/28/07, Danny Robinson [EMAIL PROTECTED] wrote: In the hope of pre-empting some emails, be aware that the trunk has switched to now use the following config setting for disabling skin compression. org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION became org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION The docs and release notes in trunk also mention this. Thanks, Danny -- Chordiant Software Inc. www.chordiant.com -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [Trinidad] Bug in XMLMenuModel / ItemNode ?
On 8/28/07, Stephen Friedrich [EMAIL PROTECTED] wrote: Should I file a jira issue? Please do. BTW: Is there a time line for 1.2.2 containing recent fixes from head? No, not really. That'll be 1.2.3, not 1.2.2. -- Adam Adam Winer wrote: Stephen, You're correct. The bug is in ItemNode.doAction(), which calls a MenuUtils.getBoundValue() function, which in turn tries to process this as a ValueBinding/ValueExpression. It's not - it's a MethodBinding/MethodExpression. -- Adam
Re: Trinidad 1.2.1: SelectOrderShuttle leading/trailingDescShown Fails For Me
Agreed. The port to Trinidad did _not_ cause this problem. My initial
diagnosis was incorrect and your point on Tiles demonstrating the
problem is the correct diagnosis.
Are you in a position to say if this fix will make it into 1.2.2?
-= Gregg =-
Adam Winer wrote:
Oh, absolutely, it's a bug, and we'll apply the fix you've
provided.
I'm just pointing out that it's a really long-standing one, and that:
'This worked fine in ADF Faces before
porting to Trinidad where the listName was just "shuttle1:leading".
Note, however, that Trinidad now adds an additional "content" prefix'
... isn't quite right, since the bug existed in ADF Faces too,
and Trinidad doesn't add the "content" prefix itself.
-- Adam
On 9/4/07, Gregg
Leichtman [EMAIL PROTECTED]
wrote:
Having
thought about this following your FYI (thank you for the hint), I
realized that Tiles must indeed be adding a tiles name prefix to the
name and ID attributes. The shuttle component is in a tile whose
definition name is, not surprisingly, "content".
Given this, however, I still would classify this behavior in Trinidad as
a bug based on the following reasoning. The component code that is
generating the _javascript_ variables:
content_shuttle1_leading_desc
content_shuttle1_trailing_desc
appears to use a global replace of underscore for colon (I didn't check
the Java code for this, but it seems reasonable based upon the generated
ID); however, the code in the generated _javascript_ function
TrShuttleProxy._getDescArray that searches for an element match via ID
uses a single or first replace of underscore for colon. This
inconsistency in the handling of the modification of element IDs will
always cause a problem for any code, Tiles or otherwise that adds
something with a colon to the ID.
Therefore, I would re-categorize this as an integration bug instead of a
general Trinidad bug, but I would suggest that it is still a bug in
Trinidad that should be fixed. If nothing else, I will need to,
hopefully temporarily, create a duplicate TrShuttleProxy._getDescArray
function with the suggested patch in order to get this functionality to
work with Tiles or alternatively modify the Java generation code,
something I would rather not do, since the latter interferes with easy
upgrades.
Do you agree that this is a bug and that it should be fixed?
-=
Gregg =-
Adam Winer wrote:
Gregg,
FYI, I don't think Trinidad is adding the "content:". Perhaps
Tiles 2.0 is (I've not looked at the newer version).
-- Adam
On 9/3/07, Gregg Leichtman [EMAIL PROTECTED]
wrote:
I have found a bug in the generated _javascript_ for the
Select*Shuttle
components. A patch follows:
TrShuttleProxy._getDescArray = function(listName) {
//var descArray = window[listName.replace(':','_') +
'_desc'];
var descArray = window[listName.replace
(/:/g,'_') + '_desc']; // gsl fix
return descArray;
}
where listName is content:shuttle1:leading.
The problem is that the listName is not using a global
replace; therefore
only the first ':' is being replaced. This worked fine in ADF
Faces before
porting to Trinidad where the listName was just
"shuttle1:leading". Note,
however, that Trinidad now adds an additional "content" prefix
to the
generated inline _javascript_ variables:
content_shuttle1_leading_desc=new Array('The First Item
Desc',
'The Second Item Desc',
'The Third Item Desc','');
content_shuttle1_trailing_desc=new Array('');
This means that a global replace needs to be done to create
the proper
variable name for matching in the _javascript_ code. I will
report this on
Jira for the Trinidad project.
I don't have access to the latest snapshots. The last one I
see is from
July 11th at:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/trinidad/trinidad-impl/1.2.1-SNAPSHOT/
If this has been fixed already, then please clear my bug
report which
should have the side benefit of letting people know that the
bug has been
found and fixed already.
-= Gregg =-
signature.asc
Description: OpenPGP digital signature
