As I mentioned in the dev thread, only supporting messages for PPR
requests with conversion and validation errors is not adequate for
production usage.
On 9/3/07, Adam Winer [EMAIL PROTECTED] wrote:
This all seems like enormous overkill *just* to get messages
sent down. We have Javascript that
Hi all,
I'm trying to get a jsCookMenu work with AJAX.
I've tried to use a4j:commandLink and a4j:support.
But nothing works ...
The JS-script calls window.open(link) on the mouseup-event.
I think this may be the problem ...
Is there a way to get jsCookMenu work with AJAX ?
Greetings
Matze
Hi Adrian Mitev
Thanx for giving the response for my post.
but i am not getting the javascript code in nabble site. due to the security
reason.
i am getting the javascript message like this . (The Javascript code that
came with this message has been removed. Learn more about Nabble's security
Hi,
seems this is not only the datePicker, I just got a
EmptyStackException in a page without datePicker.
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:79)
at java.util.Stack.pop(Stack.java:61)
at
Andrew,
I was about to use A4J in that combination without any experience with. Your
support
on that has been priceless. Thank you so much again.
- Original Message
From: Andrew Robinson [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Monday, September 3, 2007
Hi everyone,
either this is a bug or I'm not using it correctly, so:
How is the attribute shortDesc in tr:column supposed to work?
I have something like
tr:column headerText=Title shortDesc=My column tooltip
...
/tr:column
and I never see this column tooltip, neither on the header nor on
Hi,
There is also another issue with Trinidad and integration if you use Seam:
As of now, you cannot use it with tr:table unless you
do the 'plumbing' into Seam yourself and even so it does not seem clear
how to make the paging work..
See also
Wolfgang,
Thanks for share this information and link. I was catch also for this comment
in that link:
Its things like this that have conviced me that its time to throw away
a huge amount of in-house crufty stuff and move ahead with Seam/JSF for
all of our new development.
I did not understand if
Hi,
Definitely the latter one (only some of the in-house..). Actually, I
found the comment rather manager-like and not really very informative.. ;)
I am looking forward to the Seam people and their Trinidad integration
work. Otherwise we will have lots of different plumbing implementations
I happen to have the Trinidad 1.2.1 demo running in Tomcat 6.0.13. I
had not looked at the Progress Steps demo before. When I did, I got the
following:
org.apache.jasper.JasperException: /demos/progressSteps.jspx(106,30) According to the TLD or the tag file, attribute text is mandatory for
The "text" attribute is indeed missing for the panelHeader tag on line
106 of the progressSteps.jspx file. Fixing this might fix the entire
problem.
-= Gregg =-
Gregg Leichtman wrote:
I happen to have the Trinidad 1.2.1 demo running in Tomcat 6.0.13. I
had not looked at the Progress
Hi Helmut,
there was a Problem in the ButtonRenderer introduced with the changes
for tabindex.
Please try next nightly or build you own from svn head.
Regards,
Volker
2007/9/4, Volker Weber [EMAIL PROTECTED]:
Hi,
seems this is not only the datePicker, I just got a
EmptyStackException
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
Hi,
I tried to solve the problem and to disable a checkbox with the following
code:
TreeNodeChecked treeNode;
...
UIComponent nodeTypeFacet = getHtmlTree().getFacet(treeNode.getType());
HtmlSelectBooleanCheckbox checkBox = (HtmlSelectBooleanCheckbox)
nodeTypeFacet.getChildren().get(0);
Hi Volker,
thanks, the datepicker works now in general.
But I have very strange effects with the datepicker in a special use case.
I have a sheet with a link in one column which opens a popup. And this popup
has a date field and a datepicker.
The first time I click on the picker image on the
Hi Helmut,
the problem with the popups in wrong order is a known issue:
https://issues.apache.org/jira/browse/TOBAGO-133 / -134
The other (nothing happen after first click) must be a other Problem.
Can you see if a request is made after the first click and what the response is?
You can set the
Hi Volker,
yes, a request is made. This is the only debug output (with
org.apache.myfaces.tobago.ajax.api.AjaxResponseRenderer enabled):
AjaxUtils ajaxComponentIds =
mainPage:tabsView:meineAufgabenView:meineAufgabenSheet:0:ablaufdatumPopup:ablaufdatum_pickerpopup
ComponentUtil idRemainder =
Hello Wolfgang,
That's give a good path where I should go through.
Thanks a lot! Cheers.
- Original Message
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Tuesday, September 4, 2007 12:25:51 PM
Subject: Antwort: Re: Antwort: Re: Why so
Hi the good team,
I'm experiencing a problem while I'm moving to facelets. This is absolutely
normal until the point where I don't know where the problem occurs ;-p.
In fact, I have an existing set of jsp that I attempted to transform to
facelets templates. I had a lot of jsp includes until a
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
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
-0.5; outputText performance is really critical to overall performance,
and even adding a boolean attribute slows it down a bit.
-- Adam
On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote:
Should we look at providing this variable replacement functionality into
outputText. Although I'm
It is missing, but the bug is that the TLD claims it's required. That
got fixed in 1.0.2/1.2.2.
-- Adam
On 9/4/07, Gregg Leichtman [EMAIL PROTECTED] wrote:
The text attribute is indeed missing for the panelHeader tag on line 106
of the progressSteps.jspx file. Fixing this might fix the
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
Gregg,
FYI, I don't think Trinidad is adding the content:. Perhaps
Tiles 2.0 is (I've not looked at the newer version).
-- Adam
On 9/3/07, Gregg Leichtman [EMAIL PROTECTED] wrote:
I have found a bug in the generated JavaScript for the Select*Shuttle
components. A patch follows:
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]
What about tr:outputFormat? This would be a direct extension of the
core h:outputFormat with the skinning, partialTriggers and other
functionality that Trinidad provides added to it?
On 9/4/07, Adam Winer [EMAIL PROTECTED] wrote:
-0.5; outputText performance is really critical to overall
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
Finally i reconsidered the compatibility issue, spent some more time on it
and got working toghether(like a miracle) the following : WebLogic 8.1
SP4, myfaces 1.5 and tomahawk 1.1.6 !!
Martin Marinschek wrote:
Interesting - it looks as if the tomahawk-tld couldn't be resolved.
You
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
I'm again at a sorta -0.5 on this; in JSF 1.2, I'd rather provide
EL functions to do formatting, since that gives you format
functionality in all components instead of just one. (ADF Faces
does just this in JDev 11). That still leaves JSF 1.1 users with
just h:outputFormat, which isn't great.
On 9/4/07, Danny Robinson [EMAIL PROTECTED] wrote:
Yeah, I initially went with the enhanced panelFormLayout approach and
decided against it.
The name is also frustrating, so how about tr:panelCaptionGroup ...?
I think I like that name.
-- Adam
I'll give it 24hrs for other people to chime
It is for my own usage of a component that I wanted on my project. It
could be useful to other people, but it is very specific to a few
libraries and therefore not a good candidate for any of them due to
dependencies.
My custom view handler on my project is to implement a new component: UIInclude
Hello,
can send the page, please.
Regards
Bernd
Zied Hamdi wrote:
Hi the good team,
I'm experiencing a problem while I'm moving to facelets. This is absolutely
normal until the point where I don't know where the problem occurs ;-p.
In fact, I have an existing set of jsp that I attempted to
Hello,
I have bound an HtmlSelectOneMenu to my backing bean using binding=...
on the tag. I can get the chosen value easily enough with:
HtmlSelectOneMenu m;
...
String chosenValue = m.getValue();
Is there any way to get the label of the chosen item instead of the
value from the
Hello,
Just moved from Weblogic 8.1 SP4, SUN RI 1.1 tomahawk 1.1.1. to WebLogic 81.
SP4, myfaces 1.5 and tomahawk 1.1.6.
Gained some functionality but also lost some functionality :(
I am using a tabbed pane , and in each pane I have an independent jsf, as
it follows :
The problem with using EL is it has a major drawback of not supporting arrays.
For example:
a = my {0} text
b = my {0} text {1} is longer
c = my {0} text {1} needs a lot of {2} parameters
With the way EL functions are written I have to create three (or more
actually) functions to handle this
I am using the tomahawk validateEqual tag to check if two (non mandatory)
fields on a form are equal to each other but hitting some problems related
to the order of the field validations.
In the example below the validation and error message attached to the second
field works fine. However
I looked at the HTML generated code and I noticed that each button had the
same HTML code... there were no unique ID's. I believe this is the reason
why my method got called hundreds of times... Maybe there could be some
issue in generating the ids. However, I moved to myfaces 1.5 and tomahawk
Not a solution but a question,
why have the validate equal on both components, it should only be
necessary to put it on one of the components (like the 2nd one). The
user shouldn't need two messages telling them they screwed up, one
should be necessary :-)
-Andrew
On 9/4/07, Suhel Rizvi [EMAIL
I agree with you but unfortunately the customer for whom I'm developing the
software doesn't, but additionally the problem in itself is something we
should be able to solve relatively simply I would have thought as it may be
a valid scenario in other software projects.
From: Andrew
I took a look into the code to make sure I knew what was going on and
here is what I found:
It looks like the problem you are having is due to the design of the
ValidateEqual class. It is performing its logic in the validation
phase using the EditableValueHolder.getValue() function. This presents
radu_milos a écrit :
Hello,
Just moved from Weblogic 8.1 SP4, SUN RI 1.1 tomahawk 1.1.1. to WebLogic 81.
SP4, myfaces 1.5 and tomahawk 1.1.6.
Gained some functionality but also lost some functionality :(
I am using a tabbed pane , and in each pane I have an independent jsf, as
it follows :
It is really nice to have the functionality of the Trinidad plugin
that generates the tag documentation, but I was wondering if it would
be possible to have it generate a frames-based documentation like the
TLD documentation:
http://myfaces.apache.org/tomahawk/tlddoc/index.html
Currently the
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
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
Thanks for the explanation of the code which shows why it doesnt work.
However if I do take up your suggestion and put the validation on the second
field only then there is one use case where it is a particular problem; As
you may have noticed both my fields are not required fields -
Hi Bernd,
I'm sorry, I changed all the pages containing !DOCTYPE html PUBLIC -//... and
removed it, now it works. So I don't know which was the page, this mail was
just a parentheses to recall we can enhance the error messages (probably
somewhere in prepareRender() to catch and rethrow with a
Yes that does pose a problem, once again hitting the large JSF flaw of
using required as a flag instead of as a validator. I don't see an
adequate solution to that problem without using a custom component and
overriding the validate function or using and action or actionListener
to ensure that
I'm pretty sure that I wrote the compareToValidator so that it will
work on either component, unlike the equalsValidator. However, I
doubt many people have used it as a validator for the first component
listed (I know that I don't use it this way), so there might be a
minor bug to fix.
On
That'd be a very useful option for the tagdoc plugin - it'd certainly
make it much easier to navigate between components.
-- Adam
On 9/4/07, Andrew Robinson [EMAIL PROTECTED] wrote:
It is really nice to have the functionality of the Trinidad plugin
that generates the tag documentation, but I
You may find it useful. Today I faced similar problem with
validating-two-separate-mandatory-fields.
I ended up using h:hiddenText value=1 required=true
validator=#{validating.function} / somewhere after these two input
components. So validating function is invoked in processValidations
phase even
I like that name too. Should the text for it be text like on other
components or caption?
Regarding this example mentioned earlier:
tr:panelFormLayout
tr:panelCaptionGroup caption=Personal Details
tr:inputText.../
/tr:panelCaptionGroup
/tr:panelFormLayout
this could potentially be
Yes, and having required=false value=null is why validateCompareTo
doesn't work. validateCompareTo doesn't do validation if the foreign
component has no value set. That's a reasonable solution for every
case but equals.
// Don't perform validation if the foreign value is null
While looking at the tr:messages component and its renderer, I
couldn't find the ability for some functionality. In the
MessageBoxRenderer._renderGlobalMessages function, it doesn't appear
there is any why to style each message text based on severity. The
icon is severity based, by not the text.
On 9/4/07, Matt Cooper [EMAIL PROTECTED] wrote:
I like that name too. Should the text for it be text like on other
components or caption?
We already have an example of convenience-attribute+facet
on column; there it's header and headerText. So
perhaps the facet should be caption and the
I also noticed that the icon is rendered in the messages header
instead of next to each message. As a result, the user will not know
which messages are errors and which are informational, etc.
Could this be enhanced, changed so that per list item, the icon and
then the text are rendered, and the
Hi,
my application has a panel accordion component and I need to navigate to
different pages on disclosure of each of the showDetailItem's that it holds.
For example:
tr:panelAccordion discloseNone=true
tr:showDetailItem text=PA1 disclosureListener=#{
Ok, I think I figured out my problem. I'll summarize here in the hopes that
this helps someone. I initially got the solution half right, by implementing
a Converter to convert between the String representation of an Employee and
an Employee object. However, I was still failing during the
You must iterate on component children, look at each uiselectitem and
uiselectitems, and queary each of them until you get a SelectItem which
value match the current one. you can then get label of this SelectItem.
Note that this iteration will call the various EL associated with your
select
Remove from-action. There is no action here (you passed
null to the NavigationHandler!), just an outcome.
-- Adam
On 9/4/07, Rakesh Patnaik [EMAIL PROTECTED] wrote:
Hi,
my application has a panel accordion component and I need to navigate to
different pages on disclosure of each of the
After reading the tag doc for panelLabelAndMessage I would have
thought that in the following example the tr:message would not
be needed.
However if I omit the tr:message then on validation failure it
fails silently without ever showing a message.
(Trinidad 1.2.1)
tr:panelLabelAndMessage
Fixed in 1.0.3-SNAPSHOT
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
After reading the tag doc for panelLabelAndMessage I would have
thought that in the following example the tr:message would not
be needed.
However if I omit the tr:message then on validation failure it
fails
Thanks for the info, Andrew!
Adam, will 1.2.2 contain this fix, too?
Or will you strictly only transfer fixes from 1.0._2_?
Depending on how many changes there were in between 1.0.2 and 1.0.3
maybe it would make sense to skip 1.0.2 and directly go to 1.2.3?
Well, 1.2.3 really makes for a nicer
While we're at it - a few more questions regarding panelLabelAndMessage:
If there are multiple child components will messages for all of them be shown?
If so, in a single place/message component or individually where the messages
would be if the components were not simple?
Does it work if child
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
While we're at it - a few more questions regarding panelLabelAndMessage:
If there are multiple child components will messages for all of them be shown?
No, it requires a for attribute. That is the component that the
label and the message are
Good evening.
I'm wondering if there is a way to use tr:tables with large datasets that
allows us to fetch the specific data page from the database upon navigation
to that page, instead of having the whole list in memory.
It works fine for small tables, but for tables with a couple million of
Andrew Robinson wrote:
No, it requires a for attribute. That is the component that the
label and the message are for. Also in 1.0.3 the code will
automatically use the first EditableValueHolder it finds if the for is
not given, but it still only supports one component. To get multiple
Having thought about this following your FYI (thank you for the hint), I
realized that Tiles must indeed be adding a tiles name prefix to the
name and ID attributes. The shuttle component is in a tile whose
definition name is, not surprisingly, content.
Given this, however, I still would classify
Why don't you submit a wish jira for the functionality, sounds like
something that makes sense to develop.
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
Andrew Robinson wrote:
No, it requires a for attribute. That is the component that the
label and the message are for. Also in 1.0.3
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
Thanks for the info, Andrew!
Adam, will 1.2.2 contain this fix, too?
Or will you strictly only transfer fixes from 1.0._2_?
1.2.2 is exactly 1.0.2 + 1.2 changes.
Depending on how many changes there were in between 1.0.2 and 1.0.3
On 9/4/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
Andrew Robinson wrote:
No, it requires a for attribute. That is the component that the
label and the message are for. Also in 1.0.3 the code will
automatically use the first EditableValueHolder it finds if the for is
not given, but it
Oh, absolutely, it's a bug, and we'll apply the fix you've provided.
I'm just pointing out that it's a really long-standing one, and that:
'This worked fine in ADF Faces before
porting to Trinidad where the listName was just shuttle1:leading.
Note, however, that Trinidad now adds an additional
The model for the Trinidad table is not java.util.List. It's
org.apache.myfaces.trinidad.model.CollectionModel; and
Trinidad also supports javax.faces.model.DataModel.
Both of these fully support large datasets.
The Tomahawk page you refer to is 100% applicable to
Trinidad as well, as it talks
The old parameter was trinidadinternal, and therefore was
never officially supported. If we were changing from one
supported name to another, I'd agree that we should keep the
old name around, but supporting backwards compatibility
for anything trinidadinternal is a precedent I don't think we
On 8/28/07, Stephen Friedrich [EMAIL PROTECTED] wrote:
Should I file a jira issue?
Please do.
BTW: Is there a time line for 1.2.2 containing recent fixes from head?
No, not really. That'll be 1.2.3, not 1.2.2.
-- Adam
Adam Winer wrote:
Stephen,
You're correct. The bug is in
Agreed. The port to Trinidad did _not_ cause this problem. My initial
diagnosis was incorrect and your point on Tiles demonstrating the
problem is the correct diagnosis.
Are you in a position to say if this fix will make it into 1.2.2?
-= Gregg =-
Adam Winer wrote:
Oh, absolutely, it's a
77 matches
Mail list logo
