[TRINIDAD] Eclipse/Ganymede has visual page editing support for Trinidad
All, I searched back on the forums and there seems to be no mention of this, but yesterday I came across an optional plug-in that brings visual editing, component palette and property editing for Trinidad components to the standard Web Page Editor in Eclipse 3.4 Ganymede release for JavaEE developers. I had to go to Software Updates, Available Software, Web Tools (WTP) Update Side to find the plugin, but once downloaded and my project configured it seemed to work reasonably well. Perhaps we should add this information/feature to the Trinidad home page, given there are few other component libraries that have this. Related link: http://www.eclipse.org/webtools/ The JSF Tools Project has added features to improve web application development productivity. The release provides visual editing support for Apache MyFaces Trinidad components and enables support for future JSF 2.0 (JSR-314) enhancements such as Facelets. Regards, D.
Re: [Trinidad] Is it possible to PPR the tr:document?
Andrew, Any chance you could share a how-to on this - or at least some tips. It's something we've seen in past projects also. Thanks, Danny On Sun, Feb 24, 2008 at 11:13 PM, Andrew Robinson [EMAIL PROTECTED] wrote: Ignore this thread Sorry, as long as the UIView root is not re-used the partial target code is not needed On Sun, Feb 24, 2008 at 9:02 PM, Andrew Robinson [EMAIL PROTECTED] wrote: I am attempting to create a 100% AJAX interfaces to my application, that not only includes page updates but navigation as well. If 2 of my pages share the same facelets template, I am fine. If the user is navigating between two unrelated templates I want to PPR the entire page. In order to do this, I use the RequestContext addPartialTarget(UIComponent) method with the UIXDocument. The problem is that the PPR framework of Trinidad is not escaping any CDATA blocks in the response. As a result the CDATA block terminates early. The beginning of the response content: ?xml version=1.0 ? ?Tr-XHR-Response-Type ? content action=/test-app/test.jsf fragment![CDATA[html xmlns=http://www.w3.org/1999/xhtml; dir=ltr xml:lang=en head meta name=generator content=Apache Trinidad ... ]] appear inside this CDATA block (nested blocks from the document's scripts). I presume this is a bug, or am I missing something? trinidad 1.2.7-SNAPSHOT -Andrew -- Chordiant Software Inc. www.chordiant.com
Loading View(.xhtml) from Classpath
Does anyone know if it is possible to load .xhtml files from a jar using Facelets? If not, what would be required to do this, including ensuring that facelets templating still works OK? I know this belongs on the Facelets list - but the facelets site is running sooo slow for me today. D.
Re: Antwort: AW: Antwort: [Trinidad] Panel Popup not working correctly in tr:table?
This is already possible in the latest release - but you need to configure lightweight dialogs by setting the web.xml param. org.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS=true On Dec 6, 2007 9:36 AM, Döring Markus [EMAIL PROTECTED] wrote: Thanks a lot, that helps. I've read that currently there is no way to use a div to show the popup inside the current page as tr:panelPopup does. Are there any plans to implement this soon™? Markus Döring *Von:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *Gesendet:* Donnerstag, 6. Dezember 2007 15:14 *An:* MyFaces Discussion *Betreff:* Antwort: AW: Antwort: [Trinidad] Panel Popup not working correctly in tr:table? http://myfaces.apache.org/trinidad/devguide/dialogs.html Best, Wolfgang. *Döring Markus [EMAIL PROTECTED]* 06.12.2007 15:10 Bitte antworten an MyFaces Discussion users@myfaces.apache.org An MyFaces Discussion users@myfaces.apache.org Kopie Thema AW: Antwort: [Trinidad] Panel Popup not working correctly in tr:table? Hi, thanks, missed that. Can't find any documentation to the Trinidad Dialogue, can someone give me a hint where to find something about it? Greetings Markus *Von:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] * Gesendet:* Donnerstag, 6. Dezember 2007 12:16* An:* MyFaces Discussion* Betreff:* Antwort: [Trinidad] Panel Popup not working correctly in tr:table? Hi, The doc says The panelPopup is used to place ancillary information on a page, made visible via a clickable link (e.g icon or link). Practice also has shown to me that the use of panelPopup is rather restricted to pure display. Have you tried a Trinidad dialogue? I think this is the way to go in your case. Best, Wolfgang. -- Chordiant Software Inc. www.chordiant.com
Re: [Announce] Release of Apache MyFaces Trinidad 1.0.3
If you used daily builds of 1.0.3 prior to the release, then you have to clear your browser cache. For others who are moving from earlier releases 1.0.1/1.0.2, then they won't have a problem as the .js filename changes with each release. On 10/1/07, Stephen Friedrich [EMAIL PROTECTED] wrote: I just spent an unproductive hour because after upgrading, my app did no longer work, but was throwing javascript errors everywhere. Lesson learned: Clear your browser cache after update. Is there anything we can do about this? Setting some header meta info to make javascript files caching expire every day or so? -- Chordiant Software Inc. www.chordiant.com
[TRINIDAD] Building a dynamic tr:panelTabbed
Posting on behalf of a collegue: I need an example of how to build a PanelTabbed component with a dynamic number of ShowDetailItem(s) using the API's. Any examples you may have on how to do this in a managed bean would be greatly appreciated. His attempts to do this using iteration style tags seemed not to work, but if others have managed it, let me know how. Any help is appreciated, Thanks, Danny -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] panelPopup: how to avoid full page refreshing
Renzo, Do you have a small test-case you can post, you certainly should be able to use PPR inside a model panelPopup. Although it may be a better option to use lightweight dialogs for what you're suggesting. Danny On 9/25/07, Renzo Tomaselli [EMAIL PROTECTED] wrote: Hi, I'm using tr:panelPopup in modal mode only. It works well, but since it can host alternative panels (e.g. components in the Facelets sense), the entire page is refreshed whenever a panel is replaced by another one. Not a nice effect. Panel navigation occurs from user actions (next/previous) inside the panel itself. AFAIK PPR is there just to avoid this effect, e.g. I should be able somehow to force panel contents refresh only. But I don't know how to do it. Suggestions are welcome. -- Renzo -- Chordiant Software Inc. www.chordiant.com
Re: Is Trinidad-PPR using iframe or XMLHttpRequest ?
XMLHttpRequest since 1.0.2, iframe prior to that. On 9/25/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi! Just a short question: Does the Trinidad-PPR-Feature use iframe or XMLHttpRequest? Thanks, Hij -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] autosubmit of row selection
Paul, This was fixed a while ago, although not certain which build you are using. https://issues.apache.org/jira/browse/TRINIDAD-376 https://issues.apache.org/jira/browse/TRINIDAD-364 Regards, Danny On 9/20/07, Paul Mander [EMAIL PROTECTED] wrote: I require to perform an action when the user selects a row on a tr:table with rowSelection=single but there does not appear to be support for this. The select facet was removed in favour of this attribute when ported from ADF but it means that you have less control. This must be a common requirement. Does anyone have a good workaround? -- View this message in context: http://www.nabble.com/-Trinidad--autosubmit-of-row-selection-tf4487863.html#a12798203 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] panelPopup in 1.0.3 SNAPSHOT
I noticed the style attributes were not being output as they should a few
days ago. I've put a fix together, just wanted to test a few other bits.
Certainly triggerStyle was totally unecessary. I'll make the necessary
tweaks as per Adam's suggestions.
The original reason for 3 divs was to keep seperate the skin styles that a
developer could tweak from those required by the component. Hence, the
outer div controlled the show/hide and couldn't easily be modified though
bad style entries.
On 9/11/07, Adam Winer [EMAIL PROTECTED] wrote:
Good question
In general, they go on the root element. In this case,
that's the span. However, the primary purpose of this
component is definitely the popup itself, , so you could
very reasonably argue that it ought to go there.
Looking at the content, I have more questions:
- Why do we need three divs - one with an ID and
the visibility:hidden, as well as the container and
content style classes? IMO, we should only need two,
and the middle one would be unnecessary.
- There's no styleclass on the outer span.
I think what I'd recommend is deleting the middle DIV,
renaming af|panelPopup::content to just af|panelPopup,
rendering styleclass on that content DIV, and finally
adding an af|panelPopup::trigger class onto the outer
span.
Oh, and also doc the styles in the skin-selectors page. :)
-- Adam
On 9/11/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Before filing a bug, I was wondering what the intended result of this
was:
tr:panelPopup text=test styleClass=testclass
test
/tr:panelPopup
from what I can see of 1.0.3-SNAPSHOT the testclass style class is
ignored. Is it supposed to render on the trigger, the popup content,
the popup outer element or the element that contains the content for
the entire control?
Here is the HTML from the above example:
span id_popuptrigger=_id45
a href=# class=OraLink
onclick=TrPanelPopup.showPopup('_id45_popupContainer', '_id45',
event, 'click','null',false,0,0,0,0); return false; name=_id45
id=_id45test/a
div style=position: absolute; top: 0px; left: 0px; visibility:
hidden; id=_id45_popupContainer
div class=af_panelPopup_container
div class=af_panelPopup_content
test/div
/div
/div
/span
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] IE rendering issues.
Darren That's a known reported (sorry I don't have the issue number to hand) issue that we hope to fix very soon. Check the archives for possible workarounds. Danny On 9/11/07, Darren McEntee [EMAIL PROTECTED] wrote: Hi, I have some issues with rendering input fields in IE when they have validators or required attribute is set. The page contains several fields and partial page rendered is used. On a redisplay of the page, with drop downs etc. correctly updated, there is a 'padded' space under the validated fields (dates and a required drop down). This 'padded' space is where I would expect validation messages to appear. There are no validation errors so I would not expect this space to appear. Is this down to IE handling/mishandling the default Trinidad css? Or is there some other configuration required? Works fine in Firefox. Thanks, Darren. P Please consider the environment before printing this email _ 1. The information contained in this E-mail, including any files transmitted with it, is confidential and may be legally privileged. This E-mail is intended only for the personal attention of the stated addressee(s). Any access to this E-mail, including any files transmitted with it, by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this E-mail or any files transmitted with it. Such unauthorised use may be unlawful. If you have received this E-mail in error, please inform the sender immediately and delete it and all copies from your system. You may not forward this E-mail without the permission of the sender. 2. The views expressed in this E-mail are those of the author, and do not necessarily represent the views of AMT-SYBEX. Internet communications are not secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the contents of this message nor for any damage caused by viruses. AMT-SYBEX Limited is a UK company, registration number GB03036807 at address The Spirella Building, Bridge Road, Letchworth, SG6 4ET. AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ. For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com _ -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] modal panel popup demo non closing
Renzo, This seems to be fixed in the latest trunk. Would you be able to upgrade and verify also? Thanks, Danny On 9/10/07, Renzo Tomaselli [EMAIL PROTECTED] wrote: Hi, I was trying the panelPopup demo from http://www.irian.at/trinidad-demo/faces/components/panelPopup.jspx, as linked from the Trinidad website. There is an evident issue about closing the modal panel, according to the sequence: - click on Simple Popup link. - click on Modal Centered Test. Now the displayed modal paned does not react upon clicking its X close icon. This effect occurs only if the Simple Popup is visible while activating the Modal Test. Otherwise the latter behaves as expected. Same result while activating other non-modal popups. -- Renzo -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] Question regarding client-side validation and tr:form defaultCommand
Vadim, This is definately an oversight. We'll need to add some calls to the c/s validation into this method. Looking at the javascript I don't think this even happens for the older ALERT based validation, let alone the newer INLINE version. Can you raise an JIRA bug and we'll get this fixed asap. Thanks, Danny On 9/6/07, Vadim Dmitriev [EMAIL PROTECTED] wrote: Hi! It looks like client-side validation is intentionally skipped if form is submitted via tr:form defaultCommand. Can anyone explain why such a decision was taken by devs or just why it's useful for client-side to be skipped in this case? Thanks in advance. P.S. At least tr:form behaves like that in 1.0.2 and 3-4 days old 1.0.3revision. -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] Warning: Illegal HTML... should be reported?
If you can supply the source page snippet and the rendered output we should be able to figure out if there's a problem to report. Thx, Danny On 9/6/07, Vadim Dmitriev [EMAIL PROTECTED] wrote: Hi. I was making up yet another page when noticed that when i open it in the browser about 10-15 warning got printed to console: 07.09.2007 0:18:07 org.apache.myfaces.trinidadinternal.io.DebugHtmlResponseWriter _errorWithComment WARNING: Illegal HTML: cannot put a tr element in a td element. I checked HTML and there are really some strange tdtrtd blocks. My question is should those warnings be reported? Or I just have to set logger threshold a little higher in production? :) Thanks. -- Chordiant Software Inc. www.chordiant.com
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: [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
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] 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] 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: [Trinidad] Client-side validation of conditionally disabled inputText
Which version of Trinidad?
On 8/30/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi!
I have some problem with client-side validation (CSV) of conditionally
disabled field marked as required.
Let's say that there is some inputText:
tr:inputText disabled=#{bean.disabled} required=true /
Intially, bean.disabled is true, so inputText is disabled and if we try to
submit relative form no value required errors will issue.
However, if:
1. some event change bean.disabled to false and trigger ppr with that
input, and after that
2. some other event change bean.disabled back to true and ppr that
inputText yet again
then inputText will still be marked as required field on client, though it
is disabled.
It leads CSV to issue error in FF on disabled field and to cannot focus
disabled element error in IE. Sadly, it renders whole form totaly unusable
:(
Am I missing some special configuration?
Thanks.
--
Chordiant Software Inc.
www.chordiant.com
Re: [TRINIDAD] Proposal - fieldset/legend component
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 attachment: panelFieldsetLayout.GIF
[TRINIDAD] Proposal - fieldset/legend component
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
Re: trinidad outputFormat and f:param support
Paul,
I'm confused as to what that would give you over using something like:
tr:outputFormatted value=Hello #{propsFile.world}
Can you provide a more complex example.
Danny
On 8/29/07, Paul Mander [EMAIL PROTECTED] wrote:
I'm having trouble getting variable substitution to work with any of the
trinidad tags. Using standard faces I can do the following to substitute
parts of a message
h:outputFormat value=Hello {0}.
f:param value=World /
/h:outputFormat
However, I cannot get any of the trinidad output tags to work with the
f:param tag. The reason why I want to use a trinidad tag is so that I can
skin the text correctly.
--
View this message in context:
http://www.nabble.com/trinidad-outputFormat-and-f%3Aparam-support-tf4347417.html#a12385896
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Chordiant Software Inc.
www.chordiant.com
[TRINIDAD] - IMPORTANT - Custom Skin Developers
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
Re: [Trinidad] Looking for client-side partial page validation
I think your issue is mixing components outside of the subform. Instead, just use multiple subforms. Try something like this, which works fine for me. : tr:document tr:messages/ tr:form tr:subform tr:inputText required=true label=Sub 1:/ tr:commandButton text=Submit 1/ /tr:subform tr:subform tr:inputText required=true label=Sub 2:/ tr:commandButton text=Submit 2/ /tr:subform tr:subform default=true tr:inputText required=true label=Sub Default:/ tr:commandButton text=Submit Default/ /tr:subform tr:commandButton text=Submit Outside/ /tr:form /tr:document On 8/28/07, Vadim Dmitriev [EMAIL PROTECTED] wrote: Hi! As far as I know ADF had some limitation regarding client-side validation with subforms. Suppose we have following block in a page: tr:form tr:inputText required=true / tr:subform tr:inputText / tr:commandButton / /tr:subform /tr:form In that case if we will try to submit that page via commandButton with outer input field empty - validation error will occur on client, while with client-side validation disabled this request will be absolutely valid (i.e. no server-side validation exceptions will be thrown). Yesterday i faced that problem with trinidad. Maybe there is some quick workaround? I really don't want to take immediate/binding/submitted value way. Not to mention that that method leads to skipping subform validation :) I took a quick look into trinidad's client-side validation implementation and found interesting block of code in the _multiValidation() function related to skipping all subform's fields validators if user submitted outer form. Maybe it will be easier for me (if at all possible) to modify that filtering process to skip outer form validators if subform is submitted? Thank you in advance! P.S. I understand that AJAX-enabled server-side validation is actually fast and consumes very little of traffic, but my boss stands for if we can do it on client-side - we'll do it on client. So I have choice of either fixing said problem in trinidad itself or writing all client-side validation from scratch. -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] iframe popup skinning
Found it. It's because the client-side style map isn't initialized by
inputDate, but it is by using a dialog, so once you open a dialog, then
inputDate works. The fix needs some thought as inputDate launches the popup
via _ldp() and not via the dialog framework and hence doesn't have a place
where we can easily insert the style map. Thoughts anyone!
On 8/22/07, Simon Lessard [EMAIL PROTECTED] wrote:
Ok, finally, after numerous stupid mistakes, I can say that the problem
occurs only with inputDate component and not with standard dialogs nor
inputListOfValues. Furthermore, for some even more obscure reasons, if I
ever popup a working dialog (through inputListOfValues or any dialog:xyz
outcome) then inputDate starts to work...
Regards,
~ Simon
On 8/22/07, Simon Lessard [EMAIL PROTECTED] wrote:
Nope, I'm just being stupid as usual and was getting those warning
because I made a typo in the navigation case...
On 8/22/07, Simon Lessard [EMAIL PROTECTED] wrote:
Interesting... inputDate give me the non compressed style classes, and
normal dialog framework give me the following:
ATTENTION: No RenderingContext available
2007-08-22 10:29:51
org.apache.myfaces.trinidad.context.RenderingContext attach
ATTENTION: Trying to attach RenderingContext to a thread that already
had one.
2007-08-22 10:29:51
org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKitencodeFinally
ATTENTION: No RenderingContext available
I'll try from a new application rather than a degraded one, just to
see.
On 8/22/07, Simon Lessard [EMAIL PROTECTED] wrote:
Ah, then they're needed in this case since the key contains | and
::. I'm going to degrade to a simpler page and less installed components
(phase listeners and such) to see if the problem still occurs.
On 8/22/07, Adam Winer [EMAIL PROTECTED] wrote:
On 8/22/07, Simon Lessard [EMAIL PROTECTED] wrote:
I probably found one of the culprits, but it's not the only one
as it
doesn't fix the issue... Since keys in JavaScript structures
does not need
quotes, I changed
FWIW: quotes don't hurt, and they're necessary if your keys
are not valid JS identifiers. If you know your key is a valid
JS identifier, then it's a waste of space, and is worth getting
deleted.
-- Adam
out.writeText(TrPage.getInstance().addStyleClassMap( {',
null);
out.writeText(SkinSelectors.AF_PANEL_POPUP_CONTAINER_STYLE_CLASS
+ ':', null);
out.writeText(arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_CONTAINER_STYLE_CLASS),
null);
out.writeText(',' +
SkinSelectors.AF_PANEL_POPUP_CONTENT_STYLE_CLASS + ':',
null);
out.writeText(arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_CONTENT_STYLE_CLASS),
null);
out.writeText(',' +
SkinSelectors.AF_PANEL_POPUP_TITLE_STYLE_CLASS + ':',
null);
out.writeText(arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_TITLE_STYLE_CLASS),
null);
out.writeText(',' +
SkinSelectors.AF_PANEL_POPUP_TITLEBAR_STYLE_CLASS + ':',
null);
out.writeText(arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_TITLEBAR_STYLE_CLASS),
null);
out.writeText('} ); , null);
to
out.writeText(TrPage.getInstance().addStyleClassMap( {, null);
out.writeText(SkinSelectors.AF_PANEL_POPUP_CONTAINER_STYLE_CLASS
+ :', null);
out.writeText (arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_CONTAINER_STYLE_CLASS),
null);
out.writeText(', +
SkinSelectors.AF_PANEL_POPUP_CONTENT_STYLE_CLASS + :',
null);
out.writeText(arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_CONTENT_STYLE_CLASS),
null);
out.writeText(', +
SkinSelectors.AF_PANEL_POPUP_TITLE_STYLE_CLASS + :',
null);
out.writeText(arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_TITLE_STYLE_CLASS),
null);
out.writeText(', +
SkinSelectors.AF_PANEL_POPUP_TITLEBAR_STYLE_CLASS + :',
null);
out.writeText(arc.getStyleClass(
SkinSelectors.AF_PANEL_POPUP_TITLEBAR_STYLE_CLASS
), null);
out.writeText('} ); , null);
But, as I said, this is probably not everything that need to be
done as I
still have the issue.
Regards,
~ Simon
On 8/22/07, Simon Lessard [EMAIL PROTECTED] wrote:
Personally, I use JDeveloper 11 to run JSF 1.2.
Also, I got two more issues with the iframe popup as well. One
with
inputDate where the popup get bigger and bigger when I change
the month or
year (I'll have to test navigation in the popup to see if it's
generalized).
The other is that the popup's DIV does not get cleared from the
DOM after
being closed so if you keep selecting a date then
Re: [Trinidad] Skinnning dev guide now available!
Looks great Jeanne, much needed. Next step if for us to get the skin selectors reference page back up-to-date and linked into the docs. On 8/22/07, Matt Cooper [EMAIL PROTECTED] wrote: Hi Jeanne, This looks great! Do you think we need to call out that *-tr-inhibit* will only perform server-side inhibiting; it will not inhibit styles that resolve in the browser bases on things like selector specificity. Thank you, Matt On 8/22/07, Jeanne Waldman [EMAIL PROTECTED] wrote: Hi there, I finally took some time to put together a skinning dev guide. This is the first draft. I'll give myself a break from looking at it and then proofread it, unless anyone else wants to. :) Feel free to give suggestions on new sections or sections that are confusing. You can create a JIRA issue if you want. The link is: http://myfaces.apache.org/trinidad/devguide/skinning.html I just noticed that I didn't link to it from the devguide's index page. I'll look into doing that right now. - Jeanne -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] Programmatically get a style from the skin
The Trinidad renderers usually just call: renderStyleClass(context, arc, styleClass); If you want to do this from a non-Trinidad component, then you could call RenderingContext arc = RenderingContext.getCurrentInstance(); String style = arc.getStyleClass(styleClass); where styleClass would be af|panelBox::body or similar. On 8/21/07, Andrew Robinson [EMAIL PROTECTED] wrote: Is there a way to get a value from the skin programmatically? For example, I have to add a color to an attribute of a JSF component. I would like to use a value from the current skin. Specifically the background color from: af|panelBox::medium af|panelBox::body Is there any way to accomplish this? -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] customizing converter messages
Use tr:convertNumber maxFractionDigits=2 minFractionDigits=2 type=number messageDetailConvertNumber=My custom message / as an example, but there are 3 other messageDetail... attributes for different conversion types supported by tr:convertNumber. On 8/21/07, Darren McEntee [EMAIL PROTECTED] wrote: Hi guys, Can anyone tell me how to custom the messages a javax.faces converter outputs under a field after validation fails. We have a messages.properties file that contains key-value pairs like: javax.faces.converter.BigIntegerConverter.BIGINTEGER= testing 111 javax.faces.converter.BigIntegerConverter.CONVERSION_detail value must be a number 222 and the component is tr:inputText …. f:converter converterId=javax.faces.BigInteger/ /tr:inputText This currently does not work, is there something I'm over reading here? Any info appreciated. Thanks, Darren. P Please consider the environment before printing this email _ 1. The information contained in this E-mail, including any files transmitted with it, is confidential and may be legally privileged. This E-mail is intended only for the personal attention of the stated addressee(s). Any access to this E-mail, including any files transmitted with it, by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this E-mail or any files transmitted with it. Such unauthorised use may be unlawful. If you have received this E-mail in error, please inform the sender immediately and delete it and all copies from your system. You may not forward this E-mail without the permission of the sender. 2. The views expressed in this E-mail are those of the author, and do not necessarily represent the views of AMT-SYBEX. Internet communications are not secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the contents of this message nor for any damage caused by viruses. AMT-SYBEX Limited is a UK company, registration number GB03036807 at address The Spirella Building, Bridge Road, Letchworth, SG6 4ET. AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ. For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com _ -- Chordiant Software Inc. www.chordiant.com
Re: Action not working in jspx page
Try removing the html and body tags from your code, they are auto generated through the use of tr:document. Danny On 8/13/07, Bandaru [EMAIL PROTECTED] wrote: Hi, I'm configuring Trinidad in Jdeveloper 10g, evering is getting fine but the actions in the page are not working example: inputDate not displaying calender content in pop up.and other actions are also not working. what may the problem.. My code in jspx .. * ?xml version='1.0' encoding='windows-1252'? jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0 xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:tr=http://myfaces.apache.org/trinidad; jsp:output omit-xml-declaration=true doctype-root-element=HTML doctype-system=http://www.w3.org/TR/html4/loose.dtd; doctype-public=-//W3C//DTD HTML 4.01 Transitional//EN/ jsp:directive.page contentType=text/html;charset=windows-1252/ f:view html body tr:document title=Trinidad Index tr:form id=form1 tr:inputDate label=Date/ /tr:form /tr:document /body /html /f:view !--oracle-jdev-comment:auto-binding-backing-bean-name:backing_trinaidad-- /jsp:root lib used : - Activation-1.1.jar Commons-beanutils-1.7.0.jar Commons-codec-1.3.jar Commons-collections-3.1.jar Commons-digester-1.6.jar Commons-el-1.0.jar Commons-lang-2.1.jar Commons-logging-1.0.4.jar Jsf-impl.jar Jstl-1.1.2.jar Mail-1.4.jar Myfaces-api-1.1.5.jar Myfaces-impl-1.1.5.jar Oracle-portlet-tags.jar Trinidad-api-1.0.1.jar Trinidad-impl-1.0.1.jar - Configured web.xml,faces-config,correctly what else to do to resolve this problem Please suggest me.. Thank in Advance, Bandaru -- View this message in context: http://www.nabble.com/Action-not-working-in-jspx-page-tf4259576.html#a12121863 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] executing js during PPR
So no script will ever get executed in the context of the AJAX request. Unlike the pprIFrame (which caused the browser to actually parse and render the whole page inside the hidden iframe, thus executing script also), an AJAX request is simply a receive of some text content through a pipe with no parsing or rendering of the content. The Trinidad PPR code receives the content through the pipe and parses the chunks and replaces the various elements in the page with these chunks. At this point the browser does re-render those elements, but then I believe we're then at the mercy of the browser implementation as to if it executes any script content or not. On 8/9/07, Renzo Tomaselli [EMAIL PROTECTED] wrote: Thanks Danny, meanwhile I wonder why we shouldn't expect for a js chunk included in a PPR target not to be executed at some point during the PPR cycle. Perhaps this is a matter of semantics, but I would expect the same rendering behavior as for full page rendering. I mean js should execute during PPR if part of a target. Why an included script shouldn't get executed at all in IE ? Is this part of Ajax specs (if any) to update dom but not to run js ? -- Renzo Danny Robinson wrote: Renzo, I suggest you don't count on this behaviour, as the 1.0.2 release due any time soon switches to using AJAX rather than the _pprIFrame. This means your script won't get executed at all in IE, and once in Firefox. There's talk of some hooks into the AJAX routines to provide hooks when updates occur to certain elements of the page, however there's a generic hook for pre-and-post AJAX calls already in 1.0.2. AJAX powered PPR details are available here: http://myfaces.apache.org/trinidad/devguide/ppr.html Perhaps someone else can shed some light on a reliable mechanism to have script snippets executed on PPR completion. Danny. On 8/9/07, *Renzo Tomaselli* [EMAIL PROTECTED] wrote: Hi, I noticed a strong asymmetry while executing a js block included into a PPR target: on IE this runs once, in the context of _pprIFrame. On FF it runs twice, once in the context of _pprIFrame and then in the context of the original page, after PPR modifications have been applied to the dom. While on FF this behavior offers a full suite of tuning opportunities to play with PPR contents, on IE the game is severely constrained. Is that a bug to hunt for, a side-effect or a wanted feature ? Thanks, -- Renzo -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] executing js during PPR
Sample:
FacesContext facesContext = FacesContext.getCurrentInstance();
ExtendedRenderKitService service = (ExtendedRenderKitService)
Service.getRenderKitService(facesContext,
ExtendedRenderKitService.class);
service.addScript(facesContext, alert('Script added by
ExtendedRenderKitService'));
On 8/9/07, Renzo Tomaselli [EMAIL PROTECTED] wrote:
Great ! Your statement makes less important to hook into PPR completion
by some dedicated js api, since this will be possible in any case by
including some js snippet in a target region.
-- Renzo
Adam Winer wrote:
In fact, in 1.0.2, scripts that are rendered as part of a
component or via ExtendedRenderKitService *will* get
executed, and exactly once, in the proper context
(the parent document). Anything added via
ExtendedRenderKitService will get rendered after
all of the other PPR contents.
We'll also dynamically load any JS libraries that are
rendered out - script src=/ will turn into
a subsequent AJAX request for that script library,
and its execution, unless the library is already loaded
on the browser.
-- Adam
On 8/9/07, Danny Robinson [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Renzo,
I suggest you don't count on this behaviour, as the 1.0.2 release due any
time soon switches to using AJAX rather than the _pprIFrame. This means
your script won't get executed at all in IE, and once in Firefox. There's
talk of some hooks into the AJAX routines to provide hooks when updates
occur to certain elements of the page, however there's a generic hook for
pre-and-post AJAX calls already in 1.0.2.
AJAX powered PPR details are available here:
http://myfaces.apache.org/trinidad/devguide/ppr.html
Perhaps someone else can shed some light on a reliable mechanism to have
script snippets executed on PPR completion.
Danny.
On 8/9/07, Renzo Tomaselli [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi, I noticed a strong asymmetry while executing a js block included
into a PPR target: on IE this runs once, in the context of _pprIFrame.
On FF it runs twice, once in the context of _pprIFrame and then in the
context of the original page, after PPR modifications have been applied
to the dom.
While on FF this behavior offers a full suite of tuning opportunities to
play with PPR contents, on IE the game is severely constrained.
Is that a bug to hunt for, a side-effect or a wanted feature ?
Thanks,
-- Renzo
--
Chordiant Software Inc.
www.chordiant.com
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] popupPanel -- onmouseover, onmouseout, timed close support
I've already implemented the hover functionality, but I'm waiting on
1.0.2release before committing it into
1.0.3. I hadn't thought of your second point, but that would be really
great feature. I'll give this some thought and see what we can come up
with.
On the skinning front for the 'X', you need to use :
af|panelPopup::close-icon {
content: url(/images/close.gif);
text-align: right;
}
I'll get the skinning guide updated along with the other enhancements.
Danny
ps - It's possible the component name will change to just 'popup' in 1.0.3,
along with extra attributes to support the things you've asked for.
On 8/9/07, Andrew Robinson [EMAIL PROTECTED] wrote:
I am wondering if there is an easy way, or if it is planned to have
popupPanel open and hide by different methods.
Additional method 1:
onmouseover of the trigger opens the popup
onmouseout of the trigger and the popup closes the popup
This would be like the tomahawk popup functionality, but have Trinidad
funcitonality
Additional method 2:
Show the popup on a partial rendering and have it close after x
milliseconds.
This would make the functionality similar to a message bubble shown
from the tray in windows to alert the user of a message.
Also, I didn't see in the documentation when using the modal setting,
how the developer can customize the X link to use an image instead or
style the X link.
Thanks,
Andrew
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] PPR from table cells failure
Sandeep, That's one way, but a bit overly complex. Here's the easy way: tr:table idaTable ... tr:column tr:commandLink id=suggester partialSubmit=true... ... /tr:table tr:selectOneListbox id=suggestion partialTriggers=aTable:suggester Regards, Danny On 8/8/07, sandeep gururaj [EMAIL PROTECTED] wrote: I encountered this problem too. Here's how I worked around this issue. a) Create a binding for your ListBox suggestion in the bean (Say, suggestionBinding). b) In the action or actionListener or the like (returnListener in case you are using a Dialog) of the suggester, do the following at the end. RequestContext.getCurrentInstance().addPartialTarget(suggestionBinding); RequestContext.getCurrentInstance().partialUpdateNotify(suggestionBindin g); FacesContext.getCurrentInstance().renderResponse(); Hope this helps! ~Sandeep -Original Message- From: Renzo Tomaselli [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 1:00 PM To: MyFaces Discussion Subject: [Trinidad] PPR from table cells failure Hi, I wonder how I can trigger PPR from inside a table cell, since it appears not working - I guess because of some id mismatch. I have something like: tr:table ... tr:column tr:commandLink id=suggester partialSubmit=true... ... /tr:table tr:selectOneListbox id=suggestion partialTriggers=suggester then I get a warning from Trinidad as soon as I click on any table link: Could not find partial trigger suggester from CoreSelectOneListbox[UIXEditableFacesBeanImpl, id=suggestion] However, if I place the trigger component also outside the table, then PPR works properly and there is no warning., even while clicking on any link inside the table. I guess this issue has something to do with real trigger name, which is container:rowIndex:suggester, but I thought Trinidad should take care of matching these ids against a partialTrigger attribute. If not, how can I workaround it ? -- Renzo -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] PPR from table cells failure
Sandeep,
It works in exactly the same way for tables with x rows. I know you would
think it surely can't but it does. Here's a snippet from one of my examples
for removing rows from a table.
Danny
tr:table id=incExpTable value=#{incExpBean.list}
rows=10 binding=#{incExpBean.tableComponent}
summary=Element information var=item
partialTriggers=addRowButton
incExpTable:removeRowButtonincLink expLink
tr:column headerText=Amount
tr:inputText id=tableAmountField simple=true
label=amount
value=#{item.amount} required=true autoSubmit=true
tr:convertNumber maxFractionDigits=2
minFractionDigits=2 type=number /
tr:validateLongRange minimum=0 /
/tr:inputText
tr:message for=tableAmountField /
/tr:column
tr:column headerText=Remove
tr:commandButton id=removeRowButton
actionListener=#{incExpBean.removeRow}
icon=/components/images/file.gif partialSubmit=true
/tr:commandButton
/tr:column
/tr:table
public void removeRow(ActionEvent event)
{
CoreTable table = getTableComponent();
int idx = table.getRowIndex();
if (idx = 0)
getList().remove(idx);
}
On 8/8/07, sandeep gururaj [EMAIL PROTECTED] wrote:
Hello Danny,
Thanks very much.
I did use this at places where the number of rows of the table is fixed
and known. In this case, the id for all the commandLinks can be different.
Do we have a similar way for the case when the number of rows is not
fixed? Let me explain the scenario further.
In the same example as before, if there are more than one suggesters
(number not known), I need to have command links for all. How do I determine
the id for all of them?
Thanks.
~Sandeep
From: Danny Robinson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 08, 2007 6:14 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] PPR from table cells failure
Sandeep,
That's one way, but a bit overly complex. Here's the easy way:
tr:table idaTable ...
tr:column
tr:commandLink id=suggester partialSubmit=true...
...
/tr:table
tr:selectOneListbox id=suggestion partialTriggers=aTable:suggester
Regards,
Danny
On 8/8/07, sandeep gururaj [EMAIL PROTECTED] wrote:
I encountered this problem too. Here's how I worked around this issue.
a) Create a binding for your ListBox suggestion in the bean (Say,
suggestionBinding).
b) In the action or actionListener or the like (returnListener in case
you are using a Dialog) of the suggester, do the following at the end.
RequestContext.getCurrentInstance().addPartialTarget(suggestionBinding);
RequestContext.getCurrentInstance().partialUpdateNotify(suggestionBindin
g);
FacesContext.getCurrentInstance().renderResponse();
Hope this helps!
~Sandeep
-Original Message-
From: Renzo Tomaselli [mailto:[EMAIL PROTECTED] ]
Sent: Wednesday, August 08, 2007 1:00 PM
To: MyFaces Discussion
Subject: [Trinidad] PPR from table cells failure
Hi, I wonder how I can trigger PPR from inside a table cell, since it
appears not working - I guess because of some id mismatch.
I have something like:
tr:table ...
tr:column
tr:commandLink id=suggester partialSubmit=true...
...
/tr:table
tr:selectOneListbox id=suggestion partialTriggers=suggester
then I get a warning from Trinidad as soon as I click on any table link:
Could not find partial trigger suggester from
CoreSelectOneListbox[UIXEditableFacesBeanImpl, id=suggestion]
However, if I place the trigger component also outside the table, then
PPR works properly and there is no warning., even while clicking on any
link inside the table.
I guess this issue has something to do with real trigger name, which is
container:rowIndex:suggester, but I thought Trinidad should take
care of matching these ids against a partialTrigger attribute. If not,
how can I workaround it ?
-- Renzo
--
Chordiant Software Inc.
www.chordiant.com
--
Chordiant Software Inc.
www.chordiant.com
Re: Integrate Trinidad and Tiles
Honestly? Use facelets instead, it's much more Faces friendly and has a few little extras also, like turning page snippets into components. On 8/8/07, pdt_p [EMAIL PROTECTED] wrote: Hi I just wonder how to integrate Trinidad with Tiles? I try to search in this forum and in the net but I can't found a good explaination about this. I did try to integrate it but I got exception : java.lang.IllegalStateException: No RenderingContext org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin( CoreRenderer.java:181) org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer.encodeBegin (HtmlFormRenderer.java:56) javax.faces.component.UIComponentBase.encodeBegin( UIComponentBase.java:515) javax.faces.webapp.UIComponentTag.encodeBegin(UIComponentTag.java :467) javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java :320) org.apache.jsp.common.navigation_jsp._jspx_meth_h_form_0( org.apache.jsp.common.navigation_jsp:92) org.apache.jsp.common.navigation_jsp._jspService( org.apache.jsp.common.navigation_jsp:70) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java :325) org.apache.jasper.servlet.JspServlet.serviceJspFile( JspServlet.java:302) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:246) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java :966) org.apache.jasper.runtime.PageContextImpl.include( PageContextImpl.java:581) org.apache.struts.tiles.TilesUtilImpl.doInclude(TilesUtilImpl.java :99) org.apache.struts.tiles.TilesUtil.doInclude(TilesUtil.java:135) org.apache.struts.taglib.tiles.InsertTag.doInclude(InsertTag.java :760) org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag( InsertTag.java:892) org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java :462) org.apache.jsp.template.template_jsp._jspx_meth_tiles_insert_0( org.apache.jsp.template.template_jsp:172) org.apache.jsp.template.template_jsp._jspx_meth_f_subview_0( org.apache.jsp.template.template_jsp:150) org.apache.jsp.template.template_jsp._jspx_meth_f_view_0( org.apache.jsp.template.template_jsp:103) org.apache.jsp.template.template_jsp._jspService( org.apache.jsp.template.template_jsp:67) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java :325) org.apache.jasper.servlet.JspServlet.serviceJspFile( JspServlet.java:302) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:246) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch( ServletExternalContextImpl.java:419) org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch( ExternalContextDecorator.java:43) org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch (FacesContextFactoryImpl.java:260) org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl.dispatch (JspTilesViewHandlerImpl.java:236) org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl.renderView (JspTilesViewHandlerImpl.java:222) org.apache.myfaces.lifecycle.RenderResponseExecutor.execute( RenderResponseExecutor.java:41) org.apache.myfaces.lifecycle.LifecycleImpl.render( LifecycleImpl.java:132) javax.faces.webapp.FacesServlet.service(FacesServlet.java:140) org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter( ExtensionsFilter.java:147) org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter (TrinidadFilterImpl.java:208) org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl (TrinidadFilterImpl.java:165) org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter( TrinidadFilterImpl.java:138) org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter( TrinidadFilter.java:92) org.ajaxanywhere.AAFilter.doFilter(AAFilter.java:46) faces config.xml: application default-render-kit-id org.apache.myfaces.trinidad.core /default-render-kit-id view-handler org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl /view-handler /application web.xml: context-param param-nametiles-definitions/param-name param-value/WEB-INF/tiles.xml/param-value /context-param context-param param-namejavax.faces.CONFIG_FILES/param-name param-value /WEB-INF/faces-config.xml /param-value /context-param Any Idea?
Re: Trinidad Migration to 1.0.1
Could one of the guys who found this problem create a JIRA issue so we don't loose track. On 8/6/07, Danny Robinson [EMAIL PROTECTED] wrote: Good question. Did a quick test and it's the style, but it's not that easy looking at the code!!! The MessageRenderer isn't the simplest piece of code. Really hard to understand just what gets rendered when. Before you discovered it's the style, I did a quick refactor that seemed to fix the IE problem. As the inline validation is now the default it seems to make sense to have it output div's for each message section (help, message, inline-message). Prior to this, it was pushing out span-br-span or span-br-span-br-span depending on the scenario. We should try and keep things consistent for successful skinning - as it stands now, changes to OraInlineInfoText would unintentionally appear in OraInlineErrorText. I've attached a patch file - see what you think. There's definate further improvements that could be made. D. On 8/6/07, Adam Winer [EMAIL PROTECTED] wrote: Is it the span, or the OraInlineInfoText style that's to blame? -- Adam On 8/6/07, Danny Robinson [EMAIL PROTECTED] wrote: I can see it also. Not tracked this down in the renderer, but just saved the output html and played with it. Would seem to be related to the outer SPAN inside the DIV that renders under each input field. DIV class=af_panelFormLayout_message-cell style=DISPLAY: none!--Start: org.apache.myfaces.trinidad.Input[_idJsp3]--SPAN class=OraInlineInfoTextSPAN class=OraInlineErrorText id=_idJsp1:_idJsp3::msg style=DISPLAY: none/SPAN/SPAN/DIV With the SPAN removed it seems to behave. On 8/6/07, Butash, Bob [EMAIL PROTECTED] wrote: Adam, I'm testing with IE 6. Here is the simple.jsp page that I created: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; %@ page contentType=text/html;charset=windows-1252% %@ taglib uri=http://java.sun.com/jsf/html prefix=h% %@ taglib uri=http://java.sun.com/jsf/core prefix=f% %@ taglib uri= http://myfaces.apache.org/trinidad; prefix=tr% f:view tr:document h:form tr:panelFormLayout tr:inputText label=Label 1 required=true/ tr:inputText label=Label 2 required=true/ tr:commandButton action=/jsp/simple.jspx/ /tr:panelFormLayout /h:form /tr:document /f:view I enter a value in the first field and then click on the buttonI get whitespace below the first field and I properly get the error message under the second field. If the Trinidad client-validation is set to DISABLED the weird spacing goes away, but then this takes away the client side validation. Obviously if it is set to ALERT, the JavaScript alert box is shown. We were hoping to get a consistent look and feel with the messages that need to come from the server and the ones that could be checked on the client. I have attached some screen shots, not sure if they will make it to the distribution list. Thanks, Bob -Original Message- From: Adam Winer [mailto: [EMAIL PROTECTED] Sent: Monday, August 06, 2007 2:03 PM To: MyFaces Discussion Subject: Re: Trinidad Migration to 1.0.1 I've just tested with the current Trinidad 1.0.2 code and IE 7, and don't see a problem. Are you seeing problems with IE 6 or IE 7? If IE 7, could you post the simplest page you can think of that shows a problem? -- Adam On 8/6/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote: I have this issue as well. I have not found a solution to it yet. Nate Perkins 480-441-3667 [EMAIL PROTECTED] This email message is for the sole use of the intended recipient(s) and may contain GDC4S confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. From: Butash, Bob [mailto: [EMAIL PROTECTED] ] Sent: Monday, August 06, 2007 10:42 AM To: users@myfaces.apache.org Subject: Trinidad Migration to 1.0.1 Hello - I'm migrating from a Snapshot build of Trinidad to version 1.0.1and I'm noticing differences between Firefox and Internet Explorer when I'm using the required attribute on a form field. The issue that I'm having is that when I submit the page with Internet Explore I see a flash of the screen with the input fields expanded as if there was room for the error messages
Re: [Trinidad] selectOneChoice - changing other component properties
tr:inputXyz partialTriggers=checker disabled=#{
aBean.someBooleanThatWasUpdatedByYourChoice}.../
On 8/7/07, Darren McEntee [EMAIL PROTECTED] wrote:
Thanks Matthias,
Just wondering how the other components properties are accessed/changed in
the bean, presumable by their ID?
Is there documentation/examples on this?
Thanks,
Darren.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Matthias Wessendorf
Sent: 07 August 2007 15:31
To: MyFaces Discussion
Subject: Re: [Trinidad] selectOneChoice - changing other component
properties
** This Message Originated From The Internet Please Be Aware Of
Suspicious Attachments And Content **
Hi Darren,
use PPR, like
tr:selectOneChoice autoSubmit=true id=checker
valueChangeListener=#{
aBean.methodToDoSomeWorkLikeDisableOrEnableAnotherComp}
...
/tr:selectOneChoice
tr:inputXyz partialTriggers=checker .../
Here are demos of similar stuff:
http://www.irian.at/trinidad-demo/faces/demos/pprDemos.jspx
HTH,
Matthias
On 8/7/07, Darren McEntee [EMAIL PROTECTED] wrote:
Hi, I am using a trinidad tr:selectOneChoice component on one of my
pages,
and I also have other input components below this on the same page. The
selectOneChoice contains two values.
What I want to do is when I select either one of the selectOneChoice
drop
down values, it would then enable/disable the other components on the
page.
Is this possible, as I'm not sure how to go about it.
Thanks,
Darren.
P Please consider the environment before printing this email
_
1. The information contained in this E-mail, including any files
transmitted
with it, is confidential and may be legally privileged. This E-mail is
intended only for the personal attention of the stated addressee(s). Any
access to this E-mail, including any files transmitted with it, by any
other
person is unauthorised. If you are not an addressee, you must not
disclose,
copy, circulate or in any other way use or rely on the information
contained
in this E-mail or any files transmitted with it. Such unauthorised use
may
be unlawful. If you have received this E-mail in error, please inform
the
sender immediately and delete it and all copies from your system. You
may
not forward this E-mail without the permission of the sender.
2. The views expressed in this E-mail are those of the author, and do
not
necessarily represent the views of AMT-SYBEX. Internet communications
are
not secure and AMT-SYBEX cannot, therefore, accept legal responsibility
for
the contents of this message nor for any damage caused by viruses.
AMT-SYBEX Limited is a UK company, registration number GB03036807 at
address The Spirella Building, Bridge Road, Letchworth, SG6 4ET.
AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at
address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
For more information on the AMT-SYBEX Group visit
http://www.amt-sybex.com
_
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
P Please consider the environment before printing this email
--
Chordiant Software Inc.
www.chordiant.com
Re: Trinidad Migration to 1.0.1
I used FireBug to look at inhibiting that style. If I inhibit the style
then the text becomes spaced out on FireFox (but not IE), but if you use the
DOCTYPE from the Bob's example then it fixes itself. So I guess it was put
there originally to correct a FireFox quirk for our default doctype.
On 8/7/07, Adam Winer [EMAIL PROTECTED] wrote:
The downside of switching to DIVs is that anyone who wanted
messages on the right:
MyLabel [ input field ]
MyLabel2 [.input field ] ERROR!
wouldn't be able to do it, right? Dunno that I care that much.
FWIW, I'm almost certain that the big problem is:
style selector=.OraInlineInfoText
includeStyle name=AFVerySmallFont/
includeStyle name=AFDarkForeground/
includeStyle selector=.p_OraDisplayBlock/
/style
... specifically the .p_OraDisplayBlock entry, which is
just really an alias for display:block. HUH?!? What's
that doing there? And, for that matter, what's the
point of this style at all? I think we should kill this style,
and attach styles directly to each message section.
I suspect that a skinner can simply override the style
of OraInlineInfoText to remove the display property
with something like:
.OraInlineInfoText {
-tr-inhibit: display;
}
-- Adam
On 8/6/07, Danny Robinson [EMAIL PROTECTED] wrote:
Good question. Did a quick test and it's the style, but it's not that
easy
looking at the code!!! The MessageRenderer isn't the simplest piece of
code. Really hard to understand just what gets rendered when. Before
you
discovered it's the style, I did a quick refactor that seemed to fix the
IE
problem.
As the inline validation is now the default it seems to make sense to
have
it output div's for each message section (help, message,
inline-message).
Prior to this, it was pushing out span-br-span or span-br-span-br-span
depending on the scenario. We should try and keep things consistent for
successful skinning - as it stands now, changes to OraInlineInfoText
would
unintentionally appear in OraInlineErrorText.
I've attached a patch file - see what you think. There's definate
further
improvements that could be made.
D.
On 8/6/07, Adam Winer [EMAIL PROTECTED] wrote:
Is it the span, or the OraInlineInfoText style that's to blame?
-- Adam
On 8/6/07, Danny Robinson [EMAIL PROTECTED] wrote:
I can see it also. Not tracked this down in the renderer, but just
saved
the output html and played with it.
Would seem to be related to the outer SPAN inside the DIV that
renders
under
each input field.
DIV class=af_panelFormLayout_message-cell
style=DISPLAY:
none!--Start:
org.apache.myfaces.trinidad.Input[_idJsp3]--SPAN
class=OraInlineInfoTextSPAN class=OraInlineErrorText
id=_idJsp1:_idJsp3::msg
style=DISPLAY: none/SPAN/SPAN/DIV
With the SPAN removed it seems to behave.
On 8/6/07, Butash, Bob [EMAIL PROTECTED] wrote:
Adam,
I'm testing with IE 6. Here is the simple.jsp page that I
created:
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
http://www.w3.org/TR/html4/loose.dtd;
%@ page
contentType=text/html;charset=windows-1252%
%@ taglib uri=http://java.sun.com/jsf/html prefix=h%
%@ taglib uri= http://java.sun.com/jsf/core prefix=f%
%@ taglib uri=
http://myfaces.apache.org/trinidad;
prefix=tr%
f:view
tr:document
h:form
tr:panelFormLayout
tr:inputText label=Label 1 required=true/
tr:inputText label=Label 2 required=true/
tr:commandButton action=/jsp/simple.jspx/
/tr:panelFormLayout
/h:form
/tr:document
/f:view
I enter a value in the first field and then click on the
buttonI
get
whitespace below the first field and I properly get the error
message
under the second field. If the Trinidad client-validation is
set to
DISABLED the weird spacing goes away, but then this takes away the
client side validation. Obviously if it is set to ALERT, the
JavaScript
alert box is shown. We were hoping to get a consistent look and
feel
with the messages that need to come from the server and the ones
that
could be checked on the client.
I have attached some screen shots, not sure if they will make it
to
the
distribution list.
Thanks,
Bob
-Original Message-
From: Adam Winer [mailto: [EMAIL PROTECTED]
Sent: Monday, August 06, 2007 2:03 PM
To: MyFaces Discussion
Subject: Re: Trinidad Migration to 1.0.1
I've just tested with the current Trinidad 1.0.2 code and IE 7,
and
don't see a problem. Are you seeing problems with IE 6 or IE
7? If
IE
7, could you post the simplest page you can think of that shows
Re: Trinidad Migration to 1.0.1
I can see it also. Not tracked this down in the renderer, but just saved the output html and played with it. Would seem to be related to the outer SPAN inside the DIV that renders under each input field. DIV class=af_panelFormLayout_message-cell style=DISPLAY: none!--Start: org.apache.myfaces.trinidad.Input[_idJsp3]--SPAN class=OraInlineInfoTextSPAN class=OraInlineErrorText id=_idJsp1:_idJsp3::msg style=DISPLAY: none/SPAN/SPAN/DIV With the SPAN removed it seems to behave. On 8/6/07, Butash, Bob [EMAIL PROTECTED] wrote: Adam, I'm testing with IE 6. Here is the simple.jsp page that I created: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; %@ page contentType=text/html;charset=windows-1252% %@ taglib uri=http://java.sun.com/jsf/html; prefix=h% %@ taglib uri=http://java.sun.com/jsf/core; prefix=f% %@ taglib uri=http://myfaces.apache.org/trinidad; prefix=tr% f:view tr:document h:form tr:panelFormLayout tr:inputText label=Label 1 required=true/ tr:inputText label=Label 2 required=true/ tr:commandButton action=/jsp/simple.jspx/ /tr:panelFormLayout /h:form /tr:document /f:view I enter a value in the first field and then click on the buttonI get whitespace below the first field and I properly get the error message under the second field. If the Trinidad client-validation is set to DISABLED the weird spacing goes away, but then this takes away the client side validation. Obviously if it is set to ALERT, the JavaScript alert box is shown. We were hoping to get a consistent look and feel with the messages that need to come from the server and the ones that could be checked on the client. I have attached some screen shots, not sure if they will make it to the distribution list. Thanks, Bob -Original Message- From: Adam Winer [mailto:[EMAIL PROTECTED] Sent: Monday, August 06, 2007 2:03 PM To: MyFaces Discussion Subject: Re: Trinidad Migration to 1.0.1 I've just tested with the current Trinidad 1.0.2 code and IE 7, and don't see a problem. Are you seeing problems with IE 6 or IE 7? If IE 7, could you post the simplest page you can think of that shows a problem? -- Adam On 8/6/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote: I have this issue as well. I have not found a solution to it yet. Nate Perkins 480-441-3667 [EMAIL PROTECTED] This email message is for the sole use of the intended recipient(s) and may contain GDC4S confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. From: Butash, Bob [mailto:[EMAIL PROTECTED] Sent: Monday, August 06, 2007 10:42 AM To: users@myfaces.apache.org Subject: Trinidad Migration to 1.0.1 Hello - I'm migrating from a Snapshot build of Trinidad to version 1.0.1 and I'm noticing differences between Firefox and Internet Explorer when I'm using the required attribute on a form field. The issue that I'm having is that when I submit the page with Internet Explore I see a flash of the screen with the input fields expanded as if there was room for the error messages to be displayed between the fields. If I submit the form with a missing required field, I get the error message properly but once again all of the other fields have been spaced for error messages. These pages look fine with Firefox. Has anyone else seen this behavior? I'm assuming that it has something to do with the new AJAX validation instead of the javascript validation, but I did not think that it would cause all of the screen flashes and spacing issues. Thanks, Bob -- Chordiant Software Inc. www.chordiant.com
Re: Trinidad Migration to 1.0.1
Good question. Did a quick test and it's the style, but it's not that easy looking at the code!!! The MessageRenderer isn't the simplest piece of code. Really hard to understand just what gets rendered when. Before you discovered it's the style, I did a quick refactor that seemed to fix the IE problem. As the inline validation is now the default it seems to make sense to have it output div's for each message section (help, message, inline-message). Prior to this, it was pushing out span-br-span or span-br-span-br-span depending on the scenario. We should try and keep things consistent for successful skinning - as it stands now, changes to OraInlineInfoText would unintentionally appear in OraInlineErrorText. I've attached a patch file - see what you think. There's definate further improvements that could be made. D. On 8/6/07, Adam Winer [EMAIL PROTECTED] wrote: Is it the span, or the OraInlineInfoText style that's to blame? -- Adam On 8/6/07, Danny Robinson [EMAIL PROTECTED] wrote: I can see it also. Not tracked this down in the renderer, but just saved the output html and played with it. Would seem to be related to the outer SPAN inside the DIV that renders under each input field. DIV class=af_panelFormLayout_message-cell style=DISPLAY: none!--Start: org.apache.myfaces.trinidad.Input[_idJsp3]--SPAN class=OraInlineInfoTextSPAN class=OraInlineErrorText id=_idJsp1:_idJsp3::msg style=DISPLAY: none/SPAN/SPAN/DIV With the SPAN removed it seems to behave. On 8/6/07, Butash, Bob [EMAIL PROTECTED] wrote: Adam, I'm testing with IE 6. Here is the simple.jsp page that I created: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; %@ page contentType=text/html;charset=windows-1252% %@ taglib uri=http://java.sun.com/jsf/html prefix=h% %@ taglib uri=http://java.sun.com/jsf/core; prefix=f% %@ taglib uri= http://myfaces.apache.org/trinidad; prefix=tr% f:view tr:document h:form tr:panelFormLayout tr:inputText label=Label 1 required=true/ tr:inputText label=Label 2 required=true/ tr:commandButton action=/jsp/simple.jspx/ /tr:panelFormLayout /h:form /tr:document /f:view I enter a value in the first field and then click on the buttonI get whitespace below the first field and I properly get the error message under the second field. If the Trinidad client-validation is set to DISABLED the weird spacing goes away, but then this takes away the client side validation. Obviously if it is set to ALERT, the JavaScript alert box is shown. We were hoping to get a consistent look and feel with the messages that need to come from the server and the ones that could be checked on the client. I have attached some screen shots, not sure if they will make it to the distribution list. Thanks, Bob -Original Message- From: Adam Winer [mailto:[EMAIL PROTECTED] Sent: Monday, August 06, 2007 2:03 PM To: MyFaces Discussion Subject: Re: Trinidad Migration to 1.0.1 I've just tested with the current Trinidad 1.0.2 code and IE 7, and don't see a problem. Are you seeing problems with IE 6 or IE 7? If IE 7, could you post the simplest page you can think of that shows a problem? -- Adam On 8/6/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote: I have this issue as well. I have not found a solution to it yet. Nate Perkins 480-441-3667 [EMAIL PROTECTED] This email message is for the sole use of the intended recipient(s) and may contain GDC4S confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. From: Butash, Bob [mailto:[EMAIL PROTECTED] ] Sent: Monday, August 06, 2007 10:42 AM To: users@myfaces.apache.org Subject: Trinidad Migration to 1.0.1 Hello - I'm migrating from a Snapshot build of Trinidad to version 1.0.1 and I'm noticing differences between Firefox and Internet Explorer when I'm using the required attribute on a form field. The issue that I'm having is that when I submit the page with Internet Explore I see a flash of the screen with the input fields expanded as if there was room for the error messages to be displayed between the fields. If I submit the form with a missing required field, I get the error message properly but once again all of the other fields have been spaced for error messages. These pages look fine with Firefox. Has anyone else seen this behavior? I'm assuming
Re: Client validation configuration
Which version of Trinidad are you using, as client-validation=INLINE was only available in 1.0.1 onwards. On 7/27/07, Balaji Phani Krishna Annangi [EMAIL PROTECTED] wrote: Hi Everyone, I am trying to configure the client side validation [inline/disabled/alert] of UI components. But no matter how I configured, The client validations are always shown as alerts. I removed the configuration-still the validations are Shown as alerts – I'm trying to validate tr:inputText component in Trinidad components demo using tr:validateRegExp id=id pattern=[0-9]* messageDetailNoMatch=Error message / Also I am getting the following console warning when I use client-validationinline/client-validation WARNING: Element client-validation is not understood Any help? Thanks, K.Annangi -- Chordiant Software Inc. www.chordiant.com
[Trinidad] Dialogs - Launch Close Hooks
Guys, We have a requirement in an application where we need to detect when a modal lightweight dialog is launched and when it is closed. We basically need to execute some javascript before and after the dialog to cause other areas of our application. I could see adding some javascript to the actual dialog page so that would execute when loaded, but I can't see how I could detect the close of the dialog and execute some script then. Unless there's some funky way to add javascript dynamically to the page through a return listener. Failing this, I'm thinking of adding hooks into TrPopupDialog that would allow you to register launch close event listeners. Thanks, Danny -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] Dialogs - Launch Close Hooks
Our Trinidad applications run inside an iframe of a Web Desktop - hence we can't use old style dialogs which disable the whole window (and hence desktop). However, there are other iframes that that need to be disabled/enabled when the dialog is shown. Danny On 7/27/07, Adam Winer [EMAIL PROTECTED] wrote: Out of curiosity, what is it you're trying to do when launching and closing? (If it's a UI effect, it might be generically useful.) -- Adam On 7/27/07, Danny Robinson [EMAIL PROTECTED] wrote: Guys, We have a requirement in an application where we need to detect when a modal lightweight dialog is launched and when it is closed. We basically need to execute some javascript before and after the dialog to cause other areas of our application. I could see adding some javascript to the actual dialog page so that would execute when loaded, but I can't see how I could detect the close of the dialog and execute some script then. Unless there's some funky way to add javascript dynamically to the page through a return listener. Failing this, I'm thinking of adding hooks into TrPopupDialog that would allow you to register launch close event listeners. Thanks, Danny -- Chordiant Software Inc. www.chordiant.com -- Chordiant Software Inc. www.chordiant.com
Re: tab index in trinidad component
Vergil, Unfortunately we don't have this attribute currently, so there's no easy way to control tab ordering. However, this issue keeps coming back around every few months, so I've created a new issue to add this attribute. https://issues.apache.org/jira/browse/TRINIDAD-100 Danny On 7/12/07, vergil santos [EMAIL PROTECTED] wrote: how will i be able to implement tab index order in trinidad? thanks. -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] tr:inputText / Submit PPR On Enter
Until then, you could call your own function in onkeyup that checked for
Enter key being hit, and caused a hidden commandButton (one per inputText
that needed this feature) to be pressed which would perform the PPR. You'd
likely not be able to easily use defaultCommand with this solution though.
On 7/12/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
currently the PPR function is *rendered* out to onchange, to cause the
PPR, when you tab out.
We could add this for onkeyup event, when no defaultCommand is set on
form and check inside if ENTER was the pressed key. Sounds like an
enhancement request ?
-Matthuas
On 7/12/07, William Hoover [EMAIL PROTECTED] wrote:
Thanks for the reply!
I have considered using defaultCommand on the form, but I have a form
that has multiple tr:inputText / each having it's own call to a backing
bean method. They are all in the same form because they share other common
fields within it.
Any other suggestions?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Matthias Wessendorf
Sent: Thursday, July 12, 2007 8:54 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] tr:inputText / Submit PPR On Enter
Have you tried tr:form defaultCommand=... ...
http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_form.html
Setz the button/link to be a ppr command.
On 7/12/07, William Hoover [EMAIL PROTECTED] wrote:
Is there a way invoke a PPR call for a tr:inputText / when the enter
key is pressed?
For Example (I know submitOnEnter is not a valid attribute- just
illustration):
tr:inputText id=submitsOnEnter submitOnEnter=#{
myBean.processOnEnterCall} /
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] tr:inputText required=true silently blocks submission
I've now migrated the MessageBoxRenderer, but I have a few questions
remaining:
The old implementation defers the rendering of the header, and used a
_RESOURCE_KEY_MAP to map messages skin selectors to panelHeader skin
selectors as below:
_RESOURCE_KEY_MAP.put(af_panelHeader.INFORMATION,
af_messages.INFORMATION);
The updated implementation uses private class HeaderRenderer extends
PanelHeaderRenderer to delegate the header rendering to panelHeader.
However, there doesn't seem a standard mechansim to influence styles in the
way it was previously used. The only simple way seems to be to modify
private String PanelHeaderRenderer._getMessageIconName() to allow the
superclass to override the method and substitute its icons.
I'm also hesitant to migrate the existing skin selectors for
af|messages::top-start-icon etc., which allow the component to have rounded
corners etc. It would seem better to have a generic Renderer that we could
delegate to for this similar to the roundedDiv component. Until we have
this, it would mean the af|messages::top-start-icon etc. styles would be
removed.
Danny
On 7/10/07, Adam Winer [EMAIL PROTECTED] wrote:
On 7/10/07, Danny Robinson [EMAIL PROTECTED] wrote:
I'm currently moving the tr:messages code from the old 'laf' package
into
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.MessageBoxRenderer
(extends XhtmlRenderer) unless someone tells me otherwise.
Sounds great!
Once working, we can factor this into the inline validation so messages
are
also posted there. If simple=true and tr:messages doesn't exist, I
propose we then pop an alert.
+1
-- Adam
Danny
Any thoughts on how we'd like the MessageBoxRenderer to handle other
On 7/10/07, Adam Winer [EMAIL PROTECTED] wrote:
Now http://issues.apache.org/jira/browse/TRINIDAD-94
Thanks, Adam
On 7/9/07, noah [EMAIL PROTECTED] wrote:
On 7/6/07, Adam Winer [EMAIL PROTECTED] wrote:
If you remove simple=true from the inputText, what happens?
Or, if you set an id on the tr:inputText and add a tr:message
component, what happens?
Removing it and clicking the link prints a nice message next to the
form field. Also, adding
tr:message for=foo /
and setting the input's id to foo gives the same effect. So I think
you're right, it silently chokes if there isn't anywhere to show the
message.
simple=true means
there's no implict message component in the content.
My suspicion is that the client-side validation is trying
to show the error message inline, failing to find anywhere
to write the message, and just swallowing it. We
could either:
1. show these messages as JS alerts
2. show these messages in some other block of content,
picked perhaps arbitrarily (in tr:messages by default,
otherwise at the head of the page?)
3. blow off client-side validation altogether for those elements
-- Adam
On 7/6/07, noah [EMAIL PROTECTED] wrote:
I'm getting weird client side behavior with the tr:inputs. It
seems
to be connected to validation. The example below just has one
required
field, but I get the same behavior on larger forms when other
validation rules are not satisfied.
tr:document xmlns= http://www.w3.org/1999/xhtml;
xmlns:ui= http://java.sun.com/jsf/facelets;
xmlns:f= http://java.sun.com/jsf/core;
xmlns:h= http://java.sun.com/jsf/html;
xmlns:tr= http://myfaces.apache.org/trinidad;
tr:form
tr:messages /
h:outputText value=Foo=#{pageFlowScope.foo } /
tr:inputText required=true simple=true
value=#{pageFlowScope.bar} /
tr:commandLink text=foo
f:setPropertyActionListener
target=#{pageFlowScope.foo}
value=bar /
/tr:commandLink
/tr:form
/tr:document
Anyhow, if the input field is blank clicking the link does
nothing.
No
messages, nothing. If I switch to an h:inputText, the form
submits
and I get a message. Do I need to do something special to get
messages from the client side validation that appears to be
going
on?
--
Chordiant Software Inc.
www.chordiant.com
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] tr:inputText required=true silently blocks submission
I'm currently moving the tr:messages code from the old 'laf' package into
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.MessageBoxRenderer(extends
XhtmlRenderer) unless someone tells me otherwise.
Once working, we can factor this into the inline validation so messages are
also posted there. If simple=true and tr:messages doesn't exist, I
propose we then pop an alert.
Danny
Any thoughts on how we'd like the MessageBoxRenderer to handle other
On 7/10/07, Adam Winer [EMAIL PROTECTED] wrote:
Now http://issues.apache.org/jira/browse/TRINIDAD-94
Thanks, Adam
On 7/9/07, noah [EMAIL PROTECTED] wrote:
On 7/6/07, Adam Winer [EMAIL PROTECTED] wrote:
If you remove simple=true from the inputText, what happens?
Or, if you set an id on the tr:inputText and add a tr:message
component, what happens?
Removing it and clicking the link prints a nice message next to the
form field. Also, adding
tr:message for=foo /
and setting the input's id to foo gives the same effect. So I think
you're right, it silently chokes if there isn't anywhere to show the
message.
simple=true means
there's no implict message component in the content.
My suspicion is that the client-side validation is trying
to show the error message inline, failing to find anywhere
to write the message, and just swallowing it. We
could either:
1. show these messages as JS alerts
2. show these messages in some other block of content,
picked perhaps arbitrarily (in tr:messages by default,
otherwise at the head of the page?)
3. blow off client-side validation altogether for those elements
-- Adam
On 7/6/07, noah [EMAIL PROTECTED] wrote:
I'm getting weird client side behavior with the tr:inputs. It seems
to be connected to validation. The example below just has one
required
field, but I get the same behavior on larger forms when other
validation rules are not satisfied.
tr:document xmlns=http://www.w3.org/1999/xhtml;
xmlns:ui=http://java.sun.com/jsf/facelets;
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:tr=http://myfaces.apache.org/trinidad;
tr:form
tr:messages /
h:outputText value=Foo=#{pageFlowScope.foo} /
tr:inputText required=true simple=true
value=#{pageFlowScope.bar} /
tr:commandLink text=foo
f:setPropertyActionListener target=#{pageFlowScope.foo}
value=bar /
/tr:commandLink
/tr:form
/tr:document
Anyhow, if the input field is blank clicking the link does nothing.
No
messages, nothing. If I switch to an h:inputText, the form submits
and I get a message. Do I need to do something special to get
messages from the client side validation that appears to be going
on?
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] Skinning from a war file
Did you try an absolute path to your css file (e.g. /resources or /WEB-INF/./resources). Danny On 6/27/07, Francisco Passos [EMAIL PROTECTED] wrote: I'm using a skin perfectly when the application is expanded. However when I generate a war file the skin isn't used for rendering... here's my trinidad-skins.xml: ?xml version=1.0 encoding=ISO-8859-1? skins xmlns=http://myfaces.apache.org/trinidad/skin; skin id stp.desktop /id family stp /family render-kit-id org.apache.myfaces.trinidad.desktop /render-kit-id style-sheet-name resources/css/skin-stp.css /style-sheet-name extendssimple.desktop/extends /skin /skins When expanded, the skin-stp.css file is located in WEB-INF/../resources/css/skin-stp. Inside the war file, I've tried both in the same place and moving the resources dir into WEB-INF. None seems to work. Surely I'm missing something... -- Chordiant Software Inc. www.chordiant.com
Re: Partial Page Rendering issue with Trinidad
Mladen, Are you able to see PPR working correctly in the trinidad-demo? There's an example under the features section. Danny On 6/22/07, Mladen Nisevic [EMAIL PROTECTED] wrote: Thanks for such a quick reply. I am using trinidad-impl-1.0.0-incubating as I thought that was the latest stable build. Matthias Wessendorf wrote: sure. perhaps you're using a version, that has a bug. what are you using? The current trunk has real Ajax instead of IFrame (only used on uploads) ,M On 6/22/07, Mladen Nisevic [EMAIL PROTECTED] wrote: Hello, I'm having a an issue with the partial page rendering using Trinidad. The whole page is reloaded every time although I have set autoSubmit and am using partial trigger as explained in the example on partial page rendering in Trnidad in MyFaces wiki. Also, partialSubmit for Command Buttons does page reload. We also tried using panelPartialRoot with the same results i.e. full page reloading. Now, my understanding of partial page rendering (or AJAX) is that it allows for asynchronous updating of components. I.e. a portion of a page can be updated without reloading the whole page. Is it possible to have Partial Page Rendering in Trinidad without full page reload? And if yes are there any working examples? Thanks Mladen Alaric Systems Ltd. Registered in England No. 3314005 Registered Office: 108 Linton House, 164-180 Union Street, London SE1 0LH This e-mail has been scanned for all known viruses by Star. The service is powered by MessageLabs. Alaric Systems Ltd. Registered in England No. 3314005 Registered Office: 108 Linton House, 164-180 Union Street, London SE1 0LH This e-mail has been scanned for all known viruses by Star. The service is powered by MessageLabs. -- Chordiant Software Inc. www.chordiant.com
Re: Partial Page Rendering issue with Trinidad
Just updated Matthias' old build steps http://wiki.apache.org/myfaces/Building_Trinidad_With_Maven On 6/22/07, Safurudin Mahic [EMAIL PROTECTED] wrote: The trunk is located at https://svn.apache.org/repos/asf/myfaces/trinidad/trunk If you are using windows, you could use the excellent TortoiseSVN app (tortoisesvn.tigris.org) to do the checkout. On linux you just do svn co https://svn.apache.org/repos/asf/myfaces/trinidad/trunk Also, you have the excellent Trinidad documentation at http://myfaces.apache.org/trinidad/source-repository.html - Safi Mladen Nisevic skrev: Thanks a lot to everyone who replied. Yes, I can see now that it was reloading the frame and not the whole page. I would like to use the 'real' AJAX that Matthias mentioned. How can I get the current trunk? noah wrote: Using the same version, I've noticed that it looks like a full page refresh is happening, but it actually isn't, probably due to the iframe. In other words, your browser will act like something changed, but the actual visible page is being updated piecemeal. You can test this by having an output with partialTriggers and one without. The one without will not change on partial submits. On 6/22/07, Mladen Nisevic [EMAIL PROTECTED] wrote: Thanks for such a quick reply. I am using trinidad-impl-1.0.0-incubating as I thought that was the latest stable build. Matthias Wessendorf wrote: sure. perhaps you're using a version, that has a bug. what are you using? The current trunk has real Ajax instead of IFrame (only used on uploads) ,M On 6/22/07, Mladen Nisevic [EMAIL PROTECTED] wrote: Hello, I'm having a an issue with the partial page rendering using Trinidad. The whole page is reloaded every time although I have set autoSubmit and am using partial trigger as explained in the example on partial page rendering in Trnidad in MyFaces wiki. Also, partialSubmit for Command Buttons does page reload. We also tried using panelPartialRoot with the same results i.e. full page reloading. Now, my understanding of partial page rendering (or AJAX) is that it allows for asynchronous updating of components. I.e. a portion of a page can be updated without reloading the whole page. Is it possible to have Partial Page Rendering in Trinidad without full page reload? And if yes are there any working examples? Thanks Mladen Alaric Systems Ltd. Registered in England No. 3314005 Registered Office: 108 Linton House, 164-180 Union Street, London SE1 0LH This e-mail has been scanned for all known viruses by Star. The service is powered by MessageLabs. Alaric Systems Ltd. Registered in England No. 3314005 Registered Office: 108 Linton House, 164-180 Union Street, London SE1 0LH This e-mail has been scanned for all known viruses by Star. The service is powered by MessageLabs. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk Alaric Systems Ltd. Registered in England No. 3314005 Registered Office: 108 Linton House, 164-180 Union Street, London SE1 0LH This e-mail has been scanned for all known viruses by Star. The service is powered by MessageLabs. -- Chordiant Software Inc. www.chordiant.com
Re: [Trinidad] m1-incubating - 1.0.1 SNAPSHOT changes
_validateAlert is not defined
Clear your browser cache.
On 5/24/07, Luka Surija [EMAIL PROTECTED] wrote:
I've just tryed to switch from trinidad-xxx-incubator-m1-SNAPSHOT.jar to
trinidad-xxx-1.0.1-SNAPSHOT.jar but my web app doesn't working any more
(clicking on links nothing happends). I use also facelets 1.1.11, but
till now everything worked fine.
Now, all I've changed was replacing
trinidad-api-incubator-m1-SNAPSHOT.jar and
trinidad-impl-incubator-m1-SNAPSHOT.jar with
trinidad-api-1.0.1-SNAPSHOT.jar and trinidad-impl-1.0.1-SNAPSHOT.jar in
WEB-INF/lib folder.
Starting my glassfish AS and looking into server.log I've noticed
following error:
Error configuring application listener of class
org.apache.myfaces.trinidadinternal.webapp.TrinidadListenerImpl
java.lang.ClassNotFoundException:
org.apache.myfaces.trinidadinternal.webapp.TrinidadListenerImpl
at
org.apache.catalina.loader.WebappClassLoader.loadClass(
WebappClassLoader.java:1507)
at
org.apache.catalina.core.StandardContext.listenerStart(
StandardContext.java:4421)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:5140)
at com.sun.enterprise.web.WebModule.start(WebModule.java:302)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java
:1224)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:924)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java
:1224)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:520)
at org.apache.catalina.startup.Embedded.start(Embedded.java:916)
at com.sun.enterprise.web.WebContainer.start(WebContainer.java:853)
at
com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java
:742)
at
com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(
PEWebContainerLifecycle.java:71)
at
com.sun.enterprise.server.ApplicationServer.onStartup(
ApplicationServer.java:332)
at
com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(
OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
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:585)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
... hmm, odd.
OK, to workaround, I've copied all necessary jars into glassfish/lib
folder and restart glassfish.
Now, there is no more errors in server.log but still I can't do anything
(just displaying site content without clicking) .
Using firebug I've noticed following error in console every time I try
to click on some tr:commandLink or tr:commandButton:
_validateAlert is not defined
_j_id1Validator(form#j_id1 index.xhtml, j_id1:j_id14) index.xhtml
(line 221)
_validateForm(form#j_id1 index.xhtml, j_id1:j_id14) Common11-m7.js
(line 3579)
submitForm(form#j_id1 index.xhtml, 1, Object event=show
source=j_id1:j_id14 partial=true) Common11-m7.js (line 3830)
_submitPartialChange(form#j_id1 index.xhtml, 1, Object event=show
source=j_id1:j_id14 partial=true) Common11-m7.js (line 5187)
_submitHideShow(j_id1, 1, show, j_id1:j_id14, j_id1:j_id14__xc_,
undefined) index.xhtml (line 130)
onclick(click clientX=28, clientY=9) index.xhtml (line 1)
Looking into the generated html, I've found this:
input type=hidden name=value
scriptvar
_resetj_id1Names=[event,source,partial,state,value];/script
scriptvar _j_id1_Validations=['new
TrNumberConverter(null,\'number\',null,null)'];var
_j_id1_Validators=[j_id1:searchTable:edBrPonude,0,,0,[]];function
_j_id1Validator(f,s){return _validateAlert(f,s,_j_id1_Validators,0,Form
validation failures:);}var _j_id1_Labels={};var _j_id1_Formats=['{0} -
{1}'];var j_id1_SF={};/script
/spanscript_submitFormCheck();/script/form
/body
but there is no function called _validateAlert in Common11-m7.js.
Can someone tell me what I have to do, to switch to a new version of
trinidad?
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] _validateAlert is not defined
Michael,
I quickly ran your sample in both JSP and Facelets against the very latest
trunk and it works fine. I'm not able to test the 1.2 branch right now, but
might be good to know which one you've built against.
D.
On 5/24/07, Michael Trompertz [EMAIL PROTECTED] wrote:
Here is my example. Without the required-attribute in the tr:input-tag
ist works.
?
xml version=1.0 encoding=ISO-8859-1 ?
jsp:root xmlns:jsp= http://java.sun.com/JSP/Page;
xmlns:tr= http://myfaces.apache.org/trinidad;
xmlns:f= http://java.sun.com/jsf/core;
xmlns:ui= http://java.sun.com/jsf/facelets;
xmlns:c= http://java.sun.com/jstl/core; version=2.0
c:set var= webRoot
value=#{facesContext.externalContext.requestContextPath } /
ui:composition id=comp
tr:document title=PMScada-Demo initialFocusId=form1:user
tr:form id=form1
tr:inputText label=Filename id=filename required=true
value=${logging.filename} /tr:inputText
tr:commandButton action=logging text=Logging /
/tr:form
/tr:document
/ui:composition /
jsp:root
--
*Von:* Danny Robinson [mailto:[EMAIL PROTECTED]
*Gesendet:* Mittwoch, 23. Mai 2007 23:23
*An:* MyFaces Discussion
*Betreff:* Re: [Trinidad] _validateAlert is not defined
Are you able to reproduce this in the 'demo' or put together a small
snippet that can be replicated?
On 5/23/07, Michael Trompertz [EMAIL PROTECTED] wrote:
Thanks - it was indeed a caching problem.
But now my submit fails without any error message. I stepped through the
javascript code, but I did not have any idea. At least the DoSubmit variable
is set to false. All my required fields has values. It seems that it has
something to with the required=true attribute.
Michael
--
*Von:* Danny Robinson [mailto:[EMAIL PROTECTED]
*Gesendet: * Mittwoch, 23. Mai 2007 14:50
*An:* MyFaces Discussion
*Betreff:* Re: [Trinidad] _validateAlert is not defined
Michael,
This method was modified a few days ago, so it sounds like your browser
cache needs to re-read the javascript. Did you clear it?
Danny
On 5/23/07, Michael Trompertz [EMAIL PROTECTED] wrote:
Hello
After switching from trinidad-1.0.1-incubating-SNAPSHOT to
trinidad-1.0.1-SNAPSHOT I got the message _validateAlert is not
defined after pressing the
tr:commandButton action=#{loginData.login} text=Anmelden /
With switching back to the incubator jars everything is ok. I am using
trinidad with facelets.
Any ideas?
Michael
--
Chordiant Software Inc.
www.chordiant.com
--
Chordiant Software Inc.
www.chordiant.com
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] _validateAlert is not defined
Michael,
This method was modified a few days ago, so it sounds like your browser
cache needs to re-read the javascript. Did you clear it?
Danny
On 5/23/07, Michael Trompertz [EMAIL PROTECTED] wrote:
Hello
After switching from trinidad-1.0.1-incubating-SNAPSHOT to
trinidad-1.0.1-SNAPSHOT I got the message _validateAlert is not defined
after pressing the
tr:commandButton action=#{loginData.login} text=Anmelden /
With switching back to the incubator jars everything is ok. I am using
trinidad with facelets.
Any ideas?
Michael
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] How to add a custom JavaScript resource script
Will,
I'm not totally sure on that one, but I believe the functions parameter is
related to Trinidad ensuring any depend libraries/functions are also
included for you. From memory, I'm not certain this is really working as
all the core js libraries that are part of the framework are listed out in
CoreCommonScriptsResourceLoader anyway.
So to include a library and then call functions from it, you'd just follow
the outputScriptlet call from my last email with something like:
// output the popup javascript library
scriptLib.outputScriptlet(context, arc);
writer.startElement(script, component);
renderScriptTypeAttribute(context, arc);
renderScriptDeferAttribute(context, arc);
writer.writeText(callMyFunction();, null);
writer.endElement(script);
Thanks,
Danny
On 5/23/07, William Hoover [EMAIL PROTECTED] wrote:
Danny,
Thanks for your help! I noticed that the new LibraryScriptlet(String
libraryName, String[] functions) passes the script directly into the
libraryName. Would I just replace YourScript with the actual js functions
(i.e. function(){...}) or would I use an identifier for the library name
and pass in the function names as a String array?
Thanks,
Will
-Original Message-
*From:* Danny Robinson [mailto:[EMAIL PROTECTED]
*Sent:* Wednesday, May 23, 2007 10:12 AM
*To:* MyFaces Discussion
*Subject:* Re: [Trinidad] How to add a custom JavaScript resource script
The simplest route I found was the following:
Copy your YourScript.js to META-INF/adf/jsLibs in your custom component
jar.
Then in your renderer add the following code. This will cause your script
to be added only once the first time your component is used in a page.
@Override
protected void findTypeConstants(Type type)
{
super.findTypeConstants(type);
scriptLib = new LibraryScriptlet(YourScript, null);
}
@Override
protected void encodeAll(FacesContext context, RenderingContext arc,
UIComponent component, FacesBean bean) throws IOException
{
// output the popup javascript library
scriptLib.outputScriptlet(context, arc);
...do your encoding here
}
private Scriptlet scriptLib;
Regards,
Danny
On 5/23/07, William Hoover [EMAIL PROTECTED] wrote:
I was wondering if anyone knows how to add a* js* resource in Trinidad?
I have a custom component that needs to render a script. I noticed that
there is a*
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.XhtmlUtils *class
that has the* writeLibImport(FacesContext context, RenderingContext arc,
Object libURL)* and* addLib(FacesContext context, RenderingContext arc,
Object libKey)* methods. Is this the correct approach? Is there a better
way to add the script without referring to a implicit URL? Can the *
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.AliasedScriptlet
* class be used to accomplish this?
--
Chordiant Software Inc.
www.chordiant.com
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] _validateAlert is not defined
Are you able to reproduce this in the 'demo' or put together a small snippet
that can be replicated?
On 5/23/07, Michael Trompertz [EMAIL PROTECTED] wrote:
Thanks - it was indeed a caching problem.
But now my submit fails without any error message. I stepped through the
javascript code, but I did not have any idea. At least the DoSubmit variable
is set to false. All my required fields has values. It seems that it has
something to with the required=true attribute.
Michael
--
*Von:* Danny Robinson [mailto:[EMAIL PROTECTED]
*Gesendet:* Mittwoch, 23. Mai 2007 14:50
*An:* MyFaces Discussion
*Betreff:* Re: [Trinidad] _validateAlert is not defined
Michael,
This method was modified a few days ago, so it sounds like your browser
cache needs to re-read the javascript. Did you clear it?
Danny
On 5/23/07, Michael Trompertz [EMAIL PROTECTED] wrote:
Hello
After switching from trinidad-1.0.1-incubating-SNAPSHOT to
trinidad-1.0.1-SNAPSHOT I got the message _validateAlert is not
defined after pressing the
tr:commandButton action=#{loginData.login} text=Anmelden /
With switching back to the incubator jars everything is ok. I am using
trinidad with facelets.
Any ideas?
Michael
--
Chordiant Software Inc.
www.chordiant.com
--
Chordiant Software Inc.
www.chordiant.com
