Matthieu,
The Tomahawk taglib on the wiki is the one most of us are using. As
we need new components, we add new entries for them in the wiki page.
If there's an entry missing, it's probably because no one has needed
that particular component under facelets yet.
Note also that there is a
I can't remember if my web designers have had to use this, but at
least under Velocity, there's an escape XML function you can call if
you have the escapeTool installed.
http://velocity.apache.org/tools/devel/generic/EscapeTool.html
On 5/29/07, Andrew Robinson [EMAIL PROTECTED] wrote:
It can
[EMAIL PROTECTED] wrote:
They were both filled :/
Nevertheless I opted for having a fixed set of columns and rendering them
conditionally. I haven't tested it thoroughly yet, but at least the tables
are being displayed.
On 5/29/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Well, if the table
First of all, either use the myfaces jars or the sun jars. You
cannot use both.
I'm guessing you probably have the wrong listener (or multiple
listeners) defined in your web.xml file.
So choose one JSF implementation and make sure your web.xml file is
correct. If you're still having
Best practice is to use one h:form and then put form A and B into
separate sandbox:subForm elements.
However, if you're not willing to use subforms, there should be no
technical reason why you couldn't use multiple h:form elements.
On 5/30/07, Caroline Jen [EMAIL PROTECTED] wrote:
I am
not know how to handle the situation.
--- Mike Kienenberger [EMAIL PROTECTED] wrote:
Best practice is to use one h:form and then put
form A and B into
separate sandbox:subForm elements.
However, if you're not willing to use subforms,
there should be no
technical reason why you couldn't use multiple
I would check the code for inputDate's renderer. I haven't used it,
but I know that inputCalendar internally sets its own
dateTimeConverter.
On 5/30/07, Steven Gollery [EMAIL PROTECTED] wrote:
I'm having problems getting t:inputDate to use a custom converter class. In
the page, I have this:
I'd call it a bug.
Steven, at minimum, it's probably worth opening a JIRA issue on this.
Ideally you'd submit a patch to allow a converter to be specified.
On 5/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Just looked at the code, the tomahawk input date renderer does not use
the converter
Is it expected behaviour for an EL arithmetic expression to always return a
Long?
Yes. Or a Double if the value cannot be represented as a Long.
On 5/31/07, gazlm [EMAIL PROTECTED] wrote:
I have a problem with type conversions when using updateActionListener to set
an int property in a
Supposedly 1.1 and 1.2 are backward-compatible.It should work
fine, but there will probably be unforseen issues :-)
On 5/15/07, Robert Lin [EMAIL PROTECTED] wrote:
Hi,
I'm planning to upgrade to JSF 1.2, but I still have myFaces 1.0 and would
like to wait until myFaces 1.2 is
Your understanding of value binding syntax is incorrect.
Try this:
t:dataTable value=#{myBean.boolean ? oneBean.dataModel :
anotherBean.dataModel}
I can't think of any reason why this won't work.
On 5/31/07, Rønnevik, Eivind [EMAIL PROTECTED] wrote:
Hi!
I was just curious, is there
- any help appreciated.
Cheers,
Mike Kienenberger wrote:
Is it expected behaviour for an EL arithmetic expression to always return
a
Long?
Yes. Or a Double if the value cannot be represented as a Long.
On 5/31/07, gazlm [EMAIL PROTECTED] wrote:
I have a problem with type conversions
See here for ideas:
https://issues.apache.org/jira/browse/TOMAHAWK-548
No one's been motivated enough yet to submit patches.
On 5/31/07, Michael Böckling [EMAIL PROTECTED] wrote:
Hi!
I have a problem with t:dataScroller, it does not reset itself when the
underlying data model changes. When I
isn't a actionSource.
Is there a way to do this properly? This seems to be one of the easiest
things, yet I can't do it.
And thanks for your help so far, Mike! That was great!
Michael
-Ursprüngliche Nachricht-
Von: Mike Kienenberger [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag
I think the behavior of the component changes depending on whether
you're using server-side or client-side tabbing.
If you're using client-side tabbing, then I believe all tabs are
generated and all values are validated. If you're using server-side
tabbing, then I think only the current tab is
The Tomahawk selectItems tag t:selectItems will give you far more
control over how the items are constructed.
http://myfaces.apache.org/tomahawk/selectItems.html
On 5/28/07, Pich [EMAIL PROTECTED] wrote:
Hi!
I have a f:selectOneMenu and a couple of f:selectItem tags. I use the
itemLabel and
We used the component family because we need to conditionally choose
what kind of event is needed to determine the submit condition.
That's not possible from the base interfaces. input fields require
keypress, select menus require change, and so on.
Worse case, the end-user can override it.
Your idea of using t:radio was the first thought I had as well. Maybe
if you specify the for as a fully-qualified client-id it will work.
If you don't want to hardcode this, one possibility is to bind the
selectOneRadio to a backing bean and fetch the clientid for that
component as the value
I've had one (maybe two) similar problems in the past.
In one, the page gets randomly truncated by the Oracle Application
Server, but runs fine elsewhere.
In another, I've seen exceptions generated in the middle of the
client-side state saving, corrupting the value -- that looks kind of
like
What about doing something like this? This is how I clear out all
state when the end-user clicks the Reset button on a search page.
navigation-rule
description/description
from-view-id/pages/Search.xhtml/from-view-id
navigation-case
from-outcomeclear/from-outcome
Seems pretty straight forward -- what's the value binding of the _id14
component bound to? Apparently not a NavigationMenuItem or collection
of NavigationMenuItems.
On 6/1/07, Anupama Dande [EMAIL PROTECTED] wrote:
Hi,
I am getting the following error
SEVERE: Error Rendering
/managed-bean
I tried changing the scope from session to none .. but the error just
keeps coming.
I am using Facelets, Trinidad, Tomahawk for the Presentation.
If you need more information please let me know.
Thanks,
Anu
On 6/1/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Seems
, it is not breaking at getMenu() method .. for some
reason. Do you think it is some caching problem?
Thanks,
Anu
On 6/1/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
What is the method signature of myPackage.TestMenu.getMenu()?
What is the contents of getMenu()?
I don't see that the scope
: h:outputText value=#{ umenu.menu}/
I tried to debug, it is not breaking at getMenu() method .. for some
reason. Do you think it is some caching problem?
Thanks,
Anu
On 6/1/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
What is the method signature of myPackage.TestMenu.getMenu
to fix it with help from u guys. This is my first topic on this
forum. It is great to get the replies so prompt.
Thanks to all of you,
Anu
On 6/1/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
This looks to me like the same issue as with Problem with Binding in
tr:table -- your managed
el-api.jar and el-ri.jar are available from the Apache Tomcat 6.x project.
I don't know the details of how to fetch them. Asking on that mailing
list is probably your best bet.
Wendy posted this in the past for maven users:
dependency
groupIdorg.apache.tomcat/groupId
You've already summarized the general answer to your question: use
component bindings and manually validate and update the values.
There may be other options (sandbox:subForm, perhaps), but it will
require that you post specifically what you're trying to do.
On 6/4/07, Sertic Mirko, Bedag
Labels are a component like anything else.
However, I suspect you'd need to iterate through the entire component
tree, looking for any h:label component that contains a reference to
the current component.
Another way to go is to use the t:message/messages component with
replaceIdWithLabel=true
why the HtmlSelectOneRadio cause the
RequestAttribute to be remove / prevents it from being set.
Does anybody have any clue about how to get the working properly?
Any suggestions are greatly appreciated.
With kind regards,
Marco Beelen
-Original Message-
From: Mike Kienenberger
-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
Sent: dinsdag 5 juni 2007 18:55
To: MyFaces Discussion
Subject: Re: How to have the label of SelectOneRadio as a commandLink
You're using the same variable name for two different things:
t:selectItems
var=seeker
t:dataList
I don't think you can safely mix different Tomahawk and Tomahawk
Sandbox versions.
These two jar files are tightly-coupled. Be sure you are using jars
built from the same source.
This is probably also the reason for the other problems you posted.
On 6/4/07, is_maximum [EMAIL PROTECTED] wrote:
Here's the wiki page showing how to create a PDF download action.
http://wiki.apache.org/myfaces/Sending_Files
On 6/2/07, Erlend Hamnaberg [EMAIL PROTECTED] wrote:
Hello.
I need to create a component that can render a PDF file from a given
model object.
The pdf needs to be written to the
Don't know about Seam, RichFaces, or A4J, but I know that integrated
support for facelets is already part of Tobago and Trinidad, and is
planned for the next version of Tomahawk (for which I recently saw
someone create a new branch) by leveraging the infrastructure that
Trinidad provides.
On
How does this compare to validateRegExpr in Tomahawk, particularly if
it becomes a validator instead of a component?
http://myfaces.apache.org/tomahawk/validateRegExpr.html
On 6/6/07, William Hoover [EMAIL PROTECTED] wrote:
Point well taken! The component should extend UIXInput instead and
Your jpg shows that you're still using the jsf-api and jsf-ri jar
files and not using the myfaces-api and myfaces-impl jar files.
However, your web.xml file is using the MyFaces listener.
You need to pick one or the other, and then use the same version in
your web.xml file.
On 6/5/07,
This is because you're using an xml file format for your page.
You have to represent a literal P using xml escaping -- lt;Pgt;
When you change your value binding to an EL expression rather than a
string literal, you won't have this issue.
Also, wouldn't it be better to use BR/ instead of P?
On
As Jan-Kees says, you can directly access them from the session map.
If that doesn't appeal to you (or you want to do something more
complicated), you can use this technique. Just remember to dispose
of the FacesContext when you're done with it.
I think there's a valueChangeNotifier (or something like that) in
Tomahawk that does this as well -- it's a value-change-listener that
executes after updateModel.
On 6/6/07, anoe [EMAIL PROTECTED] wrote:
got the solution thanks to kaapa in irc. The problem is the phase when the
been changed by another
view or is changed before the apply request values phase. (S) Make
sure the rendered and/or disabled properties of components do not
change after rendering and before the apply request values.
-Andrew
On 6/5/07, Shane Petroff [EMAIL PROTECTED] wrote:
Mike Kienenberger
request values phase. (S) Make
sure the rendered and/or disabled properties of components do not
change after rendering and before the apply request values.
-Andrew
On 6/5/07, Shane Petroff [EMAIL PROTECTED] wrote:
Mike Kienenberger wrote:
I've also had it happen if the page changes
, cache-induced
changes, etc.
On 6/8/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Assuming that the error points to a component with id myTextArea,
you should have generated html (use view source before you hit the
submit button) that has something along these lines:
textarea name=myForm:myTextArea
that will trap and log the values.
Lots of different options, but the key is to verify that there is no
value being submitted for your component, which is what the error
message is claming.
On 6/8/07, Shane Petroff [EMAIL PROTECTED] wrote:
Mike Kienenberger wrote:
If there's no such element, then you
contained in
the request parameter map. While that's good for me to know, I'm
guessing you guys already knew that :) What could cause the mismatch?
Thanks in advance.
On 6/8/07, Shane Petroff [EMAIL PROTECTED] wrote:
Mike Kienenberger wrote:
Another way would be to set a breakpoint somewhere
be able to get further help on this is to
a) create a simplified example showing the problem, or
b) post your page code, the generated html, and the form-value pairs
submitted afterward.
On 6/8/07, Shane Petroff [EMAIL PROTECTED] wrote:
Mike Kienenberger wrote:
So the question is why does _id30 get
the _id* values that we
saw before), then this would explain why the submitted form values can
no longer be matched up to the newly-created component paths in C.
On 6/11/07, Shane Petroff [EMAIL PROTECTED] wrote:
Mike Kienenberger wrote:
I'm confused.
That's good, at least I have some company
1.1.6 is 1.1.5 + a security patch. It should be 100% compatible (In
an ideal world, it would have been released as 1.1.5.1, but we don't
have processes in place to do that yet).
On 6/13/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Sorry for the simple question, but the compatibility matrix is
It's not set up correctly.
The first filter mapping must point to the same thing as your faces servlet.
The second filter mapping must point to a specific url:
/faces/myFacesExtensionResource/*
You can find the detailed directions for setting it up here.
for your time!
Mike Kienenberger wrote:
It's not set up correctly.
The first filter mapping must point to the same thing as your faces
servlet.
The second filter mapping must point to a specific url:
/faces/myFacesExtensionResource/*
You can find the detailed directions for setting it up here
No, having your jsp files inside WEB-INF should not matter.
On 6/15/07, weull [EMAIL PROTECTED] wrote:
The url I'm returning from my Spring controller is:
/WEB-INF/jsp/welcome.faces
Does it have something to do with the JSP being behind inside the WEB-INF?
Mike Kienenberger wrote
one that might help -- I don't remember what this one does
context-param
descriptionFor JSF 1.1/description
param-nameorg.apache.myfaces.validate/param-name
param-valuetrue/param-value
/context-param
On 6/15/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
No, having your jsp
a charm!
Thank you so much for your time Mike!
Mike Kienenberger wrote:
One other thing you can try is to disable the extension filter check.
Perhaps the errors that occur after that will provide more insight.
context-param
param-nameorg.apache.myfaces.CHECK_EXTENSIONS_FILTER/param
me back the ExtensionFilter not correctly configured exception. I've
done a compare of the jars in my classpath with the ones in the
tomahawk-examples.war and they're exactly the same. I'm stumped. Any other
ideas?
Mike Kienenberger wrote:
Great! I thought it might be a classpath issue
manually constructing a url and see if you can fetch a
resource that way.
On 6/15/07, weull [EMAIL PROTECTED] wrote:
The references look correct, the extension filter resources are not being
served.
Mike Kienenberger wrote:
Are you saying that none of the generated html has references
the following url into my browser:
http://localhost:8080/webcore.base/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11819395/calendar.HtmlCalendarRenderer/DB/close.gif
and I was able to see the image.
Mike Kienenberger wrote:
This is the entry that would
Extend org.apache.myfaces.component.html.ext.HtmlDataTable instead,
and you should be set.
On 6/18/07, Ken Clark [EMAIL PROTECTED] wrote:
I think our problem is that we have build our own datatable extension that I
thought was based on the Tomahawk datatable but is actually based on the
This is for a different converter, but here's what the taglib.xml and
faces-config.xml file entries would look like:
==taglib.xml=
tag
tag-nameconvertNumberToBigDecimal/tag-name
converter
Actually, as far as I know, all of the MyFaces committers are +1 for
making a tomahawk.taglib.xml file for MyFaces part of the
distribution. The problem is that we don't have an automated process
in place to keep the file up to date yet. Hence Bruno's comment that
we'll address it in Tomahawk
It would look like this:
div class=addItemTable
ul class=addItem
li
h:commandLink action=#{globalOptionsMgr.addOption}
value=LABEL /
/li
/ul
/div
[ie, what you had without any verbatim tags]
I think your only other option would be to xml-escape all of
I'm not entirely certain, but setting this parameter to 1 might solve
the problem for you if you use server-side state-saving. However, I
use client-side state-saving so I can't say for sure.
context-param
param-nameorg.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION/param-name
A lot of times this is caused because the developer made the backing
list for the t:dataTable request-scoped, or made the rendered
attribute value for the commandList request-scoped.
On 8/9/07, Christopher Cudennec [EMAIL PROTECTED] wrote:
Hi everybody,
I can't get the commandLink to work
If you're using JSF 1.1 and JSP, then you'd need to use f:verbatim,
probably with a CDATA.
If you're using either facelets or JSF 1.2, then you can just drop it in as is.
On 8/9/07, daniel ccss [EMAIL PROTECTED] wrote:
Anybody??
On 8/9/07, daniel ccss [EMAIL PROTECTED] wrote:
I use a an
For what it's worth:
From Mike Kienenberger [EMAIL PROTECTED]
Subject Experiences with t:dataTable row clicking, selecting, and
highlighting
DateWed, 14 Mar 2007 18:24:45 GMT
http://mail-archives.apache.org/mod_mbox/myfaces-users/200703.mbox/[EMAIL
PROTECTED]
On 8/15/07, Jochen
a
dataTable, then organize them in newspaper way using a new table. But there
is not a way to specify styleclasses for the new table.
newspaperColumn1, newspaperColumn2,
Mike Kienenberger [EMAIL PROTECTED] wrote:
Have you tried the regular columnClasses attribute?
On 8/14/07, Dave
understanding of how it works. I also got a workaround for my
problem.
Thanks,
Christopher
Mike Kienenberger schrieb:
A lot of times this is caused because the developer made the backing
list for the t:dataTable request-scoped, or made the rendered
attribute value
The complexity of using t:saveState will probably depend on your application.
I've got an application with more than 100 pages, but most of the uses
of those pages are self-contained.The t:saveState needs are either
self-contained in a specific page or only span a small number of
pages.
On
If your old version was considerably old (maybe 1.1.3 or older? I
don't remember the exact changeover date), then you were probably
using implicitly created dummy form components around certain sets of
components, like menus.
That implicit form creation no longer happens, and you probably need
to
Thomas,
Gracefully-degrading javascript support sounds like an excellent
addition to MyFaces. The topic has come up before in the last couple
of weeks.
However, I'm not entirely certain if DETECT_JAVASCRIPT is still being
honored in MyFaces these days. You'll probably need to implement it
Submit a patch that allows multiple email addresses if allowMultiple=true.
On 8/21/07, rosanil [EMAIL PROTECTED] wrote:
Hi,
I have to do Email validation on TO, CC and BCC fields of mail sending
module. I saw this t:validateEmail tag. I tried to use it but it validates
only one email
sorry but I dont understand. Would appreciate if you can be more
elaborate.
Thanks a lot for replying!
Mike Kienenberger wrote:
Submit a patch that allows multiple email addresses if allowMultiple=true.
On 8/21/07, rosanil [EMAIL PROTECTED] wrote:
Hi,
I have to do Email validation
Use the sandbox subForm component. Each subform can perform custom
partial validation.
On 8/22/07, Nikhil Gahlot [EMAIL PROTECTED] wrote:
I have used myfaces-1.1.2 and sandbox-1.1.2 in my application. I have
created a form which has many command links/buttons for different actions
(add
[EMAIL PROTECTED] wrote:
thanks for the reply. I tried with this but it seems the tag is not defined
under sandbox version 1.1.2.
Mike Kienenberger wrote:
Use the sandbox subForm component. Each subform can perform custom
partial validation.
On 8/22/07, Nikhil Gahlot [EMAIL
To me it sounds like you need to change how your data model is
provided to your table.
I think the most reasonable approach is to set the backing model of
the table to only include your current scroll set, then you can use a
standard sorting model for your table. So each change of the
scroll
On 8/23/07, simon [EMAIL PROTECTED] wrote:
I can't initially think of an easy way to narrow the problem down
either...
What about simply deleting parts of the view until the size of the
saved state changes dramatically? That should tell you which
component(s) are contributing the most to the
Yes, I think you're on the right track. You don't need to create a
custom OutputText component; you just need to create a custom
OutputText renderer.
If you're using facelets, you can probably do this by using a generic
attribute, so you really only need to create a new renderer.
If you're
One other idea: Consider outputting the highlighted string in a
span, and having a highlightedStyleClass (and/or highlightedStyle)
attribute that you'd add to the span. That should allow a great deal
of flexibility to what can be done with this component.
On 8/29/07, Mike Kienenberger [EMAIL
(UIComponent component) { return lamb; }
Once you have the custom renderer working, then it's just a matter of
doing the busywork and debugging to provide the matching value to the
renderer by replacing lamb with component.getMatchingValue()
On 8/29/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Yes, I
It's certainly stable enough at this point.
However, I've never gotten around to localizing the messages or operator names.
There should probably be some unit tests as well.
It's probably not enough to hold it back from being promoted, though.
Perhaps you can start a vote on promotion on [EMAIL
My understanding is that t:buffer immediately creates the bean target
of into during the render phase.
Are you asking to have the buffered value available on the next
request? It doesn't seem like there'd be much point in capturing the
value into the bean for this request.
If it's the next
] wrote:
Hi,
can we move this one and some others to the long discussed myfaces-jsf-commons
(or how it should be named) subproject?
If there is nothing tomahawk related in this validator i like to use
it without tomahawk.jar in the classpath.
Regards,
Volker
2007/8/30, Mike
Actually, I think it's still in the tomahawk-sandbox.jar right now,
since someone asked earlier today about promoting it to tomahawk
proper.
It has some minor dependencies on the shared utility classes, but if
tomahawk+sandbox is too much to add to your project, it shouldn't take
much to pull it
html disabled attribute means don't send the input field value back to
the server when the form is submitted. If you want to be able to
change the field value, don't set the field disabled. (or at least
use javascript to un-disable it before you submit the form)
On 8/30/07, Gargi Iyer [EMAIL
JSF 1.1 doesn't support opening multiple windows in the same session
to the same JSF application unless you're using client-side state
saving.
Are you using JSF 1.1?
Are you using client-side state saving?/
On 8/31/07, Evgeniy Karimov [EMAIL PROTECTED] wrote:
As it seems, the problem is
I'm pretty sure that MyFaces 1.1 (JSF 1.1) is required by the spec to
support both Java 1.3 and Servlet 2.3. Open a JIRA issue if you find
a specific issue where this is not true.
MyFaces 1.2 (JSF 1.2) requires Java 1.5 and servlet 2.4.
On 8/31/07, Mehlstaeubl, Sabine [EMAIL PROTECTED] wrote:
This is complete guesswork, but what about extending navigationHandler
and installing a custom navigation handler? You could then make the
default behavior of your navigation handler to get outcomes from
somewhere else, perhaps by setting
navigationHandler.setFallBackOutcomeCallback(Method
Do you have a LanguageManager public Locale getLocale() method?
You need to have a public String getLocale() method.
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSFPage3.html
On 8/31/07, Eric Lewandowski [EMAIL PROTECTED] wrote:
Hi
I want to change the locale for all my faces pages.
Seems like a strange thing to do, but I guess you'd do it just like t:saveState.
You'd point your h:hiddenText (is that the right name?) value to
#{bean.objectState} and you'd have getObjectState serialize the object
into a string, and setObjectState unserialize the object.
On 8/31/07, Costa
with client-side state
saving, though.
On 8/31/07, Costa Basil [EMAIL PROTECTED] wrote:
Thank you. I need to pass some objects from a page to a dialog opened from
that page and I do not want to use session objects.
Mike Kienenberger [EMAIL PROTECTED] wrote:
Seems like a strange thing to do, but I
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
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
Generally, you do this with the rendered attribute of the component.
If you want to group a bunch of components, use a panelGroup rendered.
On 9/5/07, daniel ccss [EMAIL PROTECTED] wrote:
Hi all,
I have one question, how can I do an IF in a JSP wit myFaces/Tomahawk? In
struts I used
1) Are you accessing the xhtml file directly rather than through the
facelets servlet?
2) Is s:fieldset defined in your sandbox.taglib.xml file?
3) Are there errors parsing your facelets configuration files?
There's probably other possibilities as well, but these are a few that
immediately come
/
componentToRenderWhenFalse/
componentToRenderWhenFalse/
/panelGroup
On 9/5/07, daniel ccss [EMAIL PROTECTED] wrote:
Can you give some example code, another way?
On 9/5/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Generally, you do this with the rendered attribute of the component
Sounds like you need to clear the backing list in the code before
populating it with new items.
On 9/7/07, Wolfgang [EMAIL PROTECTED] wrote:
Hi,
I have a website with different sites. One site contains a t:datatable
which get its content
via a list. If I click on this side again the table
The apache best practices on this topic are that if the projects are
similar enough to be under the same master project, then the same
mailing lists should be used to encourage community between the
sub-projects.
On 9/10/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Have there been any thoughts
It would be done by creating your own anchor component, just as David said.
However, as far as I know, anchor is meaningless outside of html.
So the renderer for non-html should be trivial -- render nothing.
On 9/10/07, Chris Pratt [EMAIL PROTECTED] wrote:
Chris Pratt a écrit :
I'm trying
If you're looking for an argument, try somewhere else :-) If you want
help accomplishing something specific, ask.
I think there are 24 standard tags defined. That means there's
somewhere around (infinity-24) tags that are not defined.That's
why JSF supports creating your own components.
Maybe f:convertNumber pattern=###.##/ instead? I'm not an expert
on format patterns, but doesn't 0 mean at least one digit?
On 9/11/07, Michael Heinen [EMAIL PROTECTED] wrote:
I have a conversion problem with doubles and null values.
JSP snippet:
h:inputText
value=#{!empty
Back when I was working on this, I came up with a custom component
that could trigger either a javascript or JSF action for each function
key (actually, any key):
Here's some of the code from the renderer:
writer.write(\n);
writer.startElement(script, component);
In Facelets, you can use the jstl:length() function -- you don't have
to create your own function.
xmlns:jstl=http://java.sun.com/jsp/jstl/functions;
rendered=#{jstl:length(list) gt 0 and
page.limit eq jstl:length(list)}
Note that you can also use #{empty list}
You can change where the repository is located using
MAVEN_HOME_LOCAL=E:\maven for example.
Also, if you check out the full trunk (core, shared, tomahawk) at a
specific revision, I would think you could build everything without
having to worry about MyFaces versions and repository snapshots.
1 - 100 of 2009 matches
Mail list logo
