I simply solved it by doing
f:view xmlns:f=http://java.sun.com/jsf/core;
contentType=*/*
f:verbatim thecss .../f:verbatim
/f:view
It didn't htmlescape my special characters, and now my CSSS is valid
again + I have the power of EL expressions inside CSS
I can now simply use EL expressions
If only a getter is called, the ELResolver will return null - if you
try to call a setter (or a method-binding), you'll fall flat on the
nose with an exception.
regards,
Martin
On 6/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Is your bean returning null?
Try this to ensure that the
Hi Abhi,
2. My second question is also related to tr:table. Whatever how I set
the CSS, sortable column header will insists
using a border style like this:
border-style: inset;
border-width: 2px;
I think you are talking about
https://issues.apache.org/jira/browse/TRINIDAD-70
which has
BTW, you should be able to add a
c:set var=cp value=#{facesContext.externalContext.requestContextPath}/
to your page so you can just write:
body {
background:
url(#{cp}/images/background.jpg);
}
-- Adam
On 6/30/07, Safurudin Mahic [EMAIL PROTECTED] wrote:
I simply solved it by doing
On 6/30/07, Zarick Lau [EMAIL PROTECTED] wrote:
Hi Abhi,
4. Finally, I find some .xss files in Trinidad sources, is it the
definitely way to completely define a skin?
As I know, defining the CSS files is only customizing or extending
the simple skin.
AFAIK, XSS is an internal
No, there isn't any supported feature for this.
-- Adam
On 6/30/07, Zarick Lau [EMAIL PROTECTED] wrote:
Hi list,
When showRequired are set to true for all kinds of label components.
The * icon are displayed left to the label.
Is it possible to make the icon display right to the label?
I'm encountering a strange behavior, when trying to update detail records in
tomahawk detailStamp dataTable.
The bean method attached to the valueChangeListener gets called even so,
there is no one detail value is changed. When I display
event.getOldvalue()/.getNewValue(), it shows the new value
Hi Michael!
the problem seems to be the first partial submit. After that a new
Conversation is created. On subsequent partial submits it works like
expected.
Thanks for your webapp!
I managed to find the problem and I think I fixed it.
The problem was: I tried to work with the
Weird. Are cookies supported in the browser that fails? Is JavaScript?
Have you been able to reproduce it?
On 6/29/07, Titi Wangsa [EMAIL PROTECTED] wrote:
yes. that's what i initially thought
but the form fields are empty
if there was an error in validation/conversion
then the values would be
Andrew,
I ran the test successfully, the jsp contained...
t:div forceId=true id=searchClosed1 styleClass=#{'tmsHidden'}
123
/t:div
The resultant browser view source correctly yeilded...
div id=searchClosed1 class=tmsHidden
123
/div
This shows that the faces back end is properly parsing the
Sorry, just had a kid, barely any time to just read my email :-)
On 6/30/07, Marty Bergerud [EMAIL PROTECTED] wrote:
Andrew,
I ran the test successfully, the jsp contained...
t:div forceId=true id=searchClosed1 styleClass=#{'tmsHidden'}
123
/t:div
The resultant browser view source correctly
Congratulations!!!
On 6/30/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Sorry, just had a kid, barely any time to just read my email :-)
On 6/30/07, Marty Bergerud [EMAIL PROTECTED] wrote:
Andrew,
I ran the test successfully, the jsp contained...
t:div forceId=true id=searchClosed1
got it solved..
apparently its not myfaces..
rather its the tcnative (tomcat native code to make tomcat go faster)
that's causing it
sometimes, it can't parse the post parameters properly..
the logs are full of this
so when it can't parse ViewState parameter, i doesn't know the viewstate
but it
13 matches
Mail list logo
