Re: FlowScope beans are being added to the FlowScope.
may be weld (see http://weld.cdi-spec.org) Am 04.07.2014 um 06:52 schrieb Paul Spencer pau...@apache.org: MyFaces 2.2.3 2.2.4 jetty-maven-plugin:8.1.15.v20140411 FlowScope beans are being added to the FlowScope. I suspect this is related to the message below. org.apache.myfaces.util.ExternalSpecifications isCDIAvailable INFO: MyFaces CDI support disabled What dependencies are need to enable CDI? Paul Spencer signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [a bit off topic] Trying to use xhtml instead of html, problem with IE?
Yes! the browser takes the content type, which is sent by the server
as part of the http-header. but have a look at this ugly anouncement http://blogs.msdn.com/ie/archive/2005/09/15/467901.aspx
.
burghard.
Am 23.01.2009 um 23:44 schrieb Bjørn T Johansen:
Not sure if I understand your question... I thought the server sent
the content type and not the browser?
BTJ
On Fri, 23 Jan 2009 15:19:37 -0700
Andrew Robinson andrew.rw.robin...@gmail.com wrote:
what is your content type header that the browser is sending?
On Fri, Jan 23, 2009 at 2:42 PM, Bjørn T Johansen b...@havleik.no
wrote:
Ok, but I tried changing the content type to text/html with no
change in the outcome...
What else do I need to do to make IE work?
BTJ
On Fri, 23 Jan 2009 12:57:27 -0700
Andrew Robinson andrew.rw.robin...@gmail.com wrote:
Most browsers need content type of text/html, even for XHTML
documents. It is a bug in the browser.
-Andrew
On Fri, Jan 23, 2009 at 11:57 AM, Bjørn T Johansen
b...@havleik.no wrote:
When I use the following in my xhtml page..:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en
xmlns:ui=http://java.sun.com/jsf/facelets;
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
head
meta http-equiv=Content-Type content=application/xhtml+xml/
meta http-equiv=Pragma content=no-cache/
meta http-equiv=Expires content=-1/
link href=#{facesContext.externalContext.requestContextPath}/
secure/css/stylesheet2.css rel=stylesheet
type=text/css/ /head
it works great in Firefox. But trying to open the same page in
IE, IE just asks f I want to save the file or
find a program online to open it
How can I code the page so IE will display the page correctly?
Regards,
BTJ
Re: [Trinidad] charset
to verify if you are rendering xml, have a look at source code in the
browser or the http response data.
to set html rendering use code like the following:
?xml version=1.0 encoding=UTF-8 ?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.1
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:tr=http://myfaces.apache.org/trinidad;
jsp:directive.page contentType=text/html; charset=UTF-8/
f:view
...
/f:view
/jsp:root
Am 31.12.2008 um 14:28 schrieb desik:
I don't have any settings regarding html / xhtml rendering. So I
guess it's
default rendering. Voted for both bugs.
Burghard Britzke wrote:
are you trying to render xml? you probably run into
https://issues.apache.org/jira/browse/TRINIDAD-1139
and https://issues.apache.org/jira/browse/TRINIDAD-818 . the
javascript generated for xml rendered pages is not valid and does not
work. you should consider to vote for them or better fix it. I wonder
why so few users run into this issue. do they all render old
fashioned
html?
burghard.britzke
Am 30.12.2008 um 08:00 schrieb desik:
I have a simple trinidad page, with no jsp:directive.page charset
specified:
?xml version=1.0 encoding=UTF-8 ?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.1
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:tr=http://myfaces.apache.org/trinidad;
f:view
tr:document title=not working
tr:form
h:commandButton value=h: Click me
action=#{loginHandler.login}/
tr:commandButton text=tr: Click me
action=#{loginHandler.login}/
/tr:form
/tr:document
/f:view
/jsp:root
Both buttons don't work. When I click them request is not sent to
server.
Now, if I add:
jsp:directive.page contentType=text/html; charset=utf-8/
at the beginning of the page, both buttons work properly.
Environment: myfaces 1.2.5, trinidad 1.2.10, tomcat 6.0.18, windoze
vista,
firefox 3.
Do you thing this is a trinidad bug?
--
View this message in context:
http://www.nabble.com/-Trinidad--charset-tp21213794p21213794.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/-Trinidad--charset-problem-tp21213794p21231445.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] charset
...
may be f:view contentType=text/html will work, too. :-)
Am 31.12.2008 um 14:28 schrieb desik:
I don't have any settings regarding html / xhtml rendering. So I
guess it's
default rendering. Voted for both bugs.
Burghard Britzke wrote:
are you trying to render xml? you probably run into
https://issues.apache.org/jira/browse/TRINIDAD-1139
and https://issues.apache.org/jira/browse/TRINIDAD-818 . the
javascript generated for xml rendered pages is not valid and does not
work. you should consider to vote for them or better fix it. I wonder
why so few users run into this issue. do they all render old
fashioned
html?
burghard.britzke
Am 30.12.2008 um 08:00 schrieb desik:
I have a simple trinidad page, with no jsp:directive.page charset
specified:
?xml version=1.0 encoding=UTF-8 ?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.1
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:tr=http://myfaces.apache.org/trinidad;
f:view
tr:document title=not working
tr:form
h:commandButton value=h: Click me
action=#{loginHandler.login}/
tr:commandButton text=tr: Click me
action=#{loginHandler.login}/
/tr:form
/tr:document
/f:view
/jsp:root
Both buttons don't work. When I click them request is not sent to
server.
Now, if I add:
jsp:directive.page contentType=text/html; charset=utf-8/
at the beginning of the page, both buttons work properly.
Environment: myfaces 1.2.5, trinidad 1.2.10, tomcat 6.0.18, windoze
vista,
firefox 3.
Do you thing this is a trinidad bug?
--
View this message in context:
http://www.nabble.com/-Trinidad--charset-tp21213794p21213794.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/-Trinidad--charset-problem-tp21213794p21231445.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] PPR does not work for XHTML rendered pages (was: charset)
fine! but using html4 is just a workaround. trinidad does not work for xhtml rendered pages since more than one year! burghard. Am 01.01.2009 um 14:11 schrieb desik: You are right. Tried: jsp:directive.page contentType=text/html/ and it works. Verified page source. Without contentType attribute page is rendered as xhtml, with contentType - as html. Thank you! -- View this message in context: http://www.nabble.com/-Trinidad--charset-problem-tp21213794p21241118.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] PPR does not work for XHTML rendered pages (was: charset)
but even if it will be possible to change the doctype to XHTML with tr:document, trinidad is not usable for rendering XHTML, because of invalid javascript code in it for XHTML. For exactness: PPR will not work properly. burghard. Am 01.01.2009 um 17:14 schrieb Andrew Robinson: If you use tr:document I believe Trinidad always uses the HTML doctype. This is something that I have wanted to change. For example, the demos render: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; This is one of those issues that other community members where hesitant to change. Perhaps this is part of the problem? On Thu, Jan 1, 2009 at 7:30 AM, Burghard Britzke b...@charmides.in-berlin.de wrote: fine! but using html4 is just a workaround. trinidad does not work for xhtml rendered pages since more than one year! burghard. Am 01.01.2009 um 14:11 schrieb desik: You are right. Tried: jsp:directive.page contentType=text/html/ and it works. Verified page source. Without contentType attribute page is rendered as xhtml, with contentType - as html. Thank you! -- View this message in context: http://www.nabble.com/-Trinidad--charset-problem-tp21213794p21241118.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] charset
are you trying to render xml? you probably run into https://issues.apache.org/jira/browse/TRINIDAD-1139
and https://issues.apache.org/jira/browse/TRINIDAD-818 . the
javascript generated for xml rendered pages is not valid and does not
work. you should consider to vote for them or better fix it. I wonder
why so few users run into this issue. do they all render old fashioned
html?
burghard.britzke
Am 30.12.2008 um 08:00 schrieb desik:
I have a simple trinidad page, with no jsp:directive.page charset
specified:
?xml version=1.0 encoding=UTF-8 ?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.1
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:tr=http://myfaces.apache.org/trinidad;
f:view
tr:document title=not working
tr:form
h:commandButton value=h: Click me
action=#{loginHandler.login}/
tr:commandButton text=tr: Click me
action=#{loginHandler.login}/
/tr:form
/tr:document
/f:view
/jsp:root
Both buttons don't work. When I click them request is not sent to
server.
Now, if I add:
jsp:directive.page contentType=text/html; charset=utf-8/
at the beginning of the page, both buttons work properly.
Environment: myfaces 1.2.5, trinidad 1.2.10, tomcat 6.0.18, windoze
vista,
firefox 3.
Do you thing this is a trinidad bug?
--
View this message in context:
http://www.nabble.com/-Trinidad--charset-tp21213794p21213794.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Trinidad Large Tree
may be it is the javascript code used by the tree component which screw up ie? burghard. Am 25.10.2008 um 15:30 schrieb Matthias Wessendorf: Are you saying the issue is the JavaScript in IE ? -Matthias On Fri, Oct 24, 2008 at 6:27 PM, Wu, Billy [EMAIL PROTECTED] wrote: Hi everyone, I have a large tree (500 nodes under a node), and it is taking a very long time to load (like 46 seconds) in Internet Explorer. In Firefox and Chrome, it only takes a few seconds. Unfortunately my company has to support IE. Does anyone know a good solution to this? (Maybe like a TreePanel widget that will go get data as needed?) Thanks, Billy -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad] Skinning Error: CSS not available
I use
tr:document
f:facet name=metaContainer
h:panelGroup
style type=text/css
@import
#{facesContext.externalContext.requestContextPath}/path to my.css
/style
...
/h:panelGroup
/f:facet
and it worked for me. the link-element should also work as the script-
and the style-element does. you can group more elements to a
h:panelGroup which is rendered a a sequence of elements in the head-
element of the html response.
hth
burghard.
Am 18.08.2008 um 19:15 schrieb Marco Vieira:
Thanks for the quick replies,
I've tried manually linking the CSS file within trh:head tags. But
it didn't work it just added another CSS reference.
Anyone have more ideias? I've been on this for 3 days...I'm sort of
a beginner :)
Thanks in advance,
Marco
On Mon, Aug 18, 2008 at 3:38 PM, Simon Lessard [EMAIL PROTECTED]
wrote:
Hi,
No, tr:document should add the skin reference correctly, I don't
know why it isn't working for you yet however.
Regards,
~ Simon
On Mon, Aug 18, 2008 at 10:33 AM, René van Wijk [EMAIL PROTECTED]
wrote:
I am not sure but to my knowledge you have to use
trh:html
trh:head title=Departments
meta http-equiv=Content-Type content=text/html;
charset=windows-1252/
/trh:head
trh:body
/trh:body
trh:html
if you want the trinidad metadata, such as skins, to be loaded. The
tag tr:document only adds the default html, head and body tags.
Hope this helps.
-Original Message-
From: Marco Vieira [mailto:[EMAIL PROTECTED]
Sent: Mon 8/18/2008 16:17 PM
To: users@myfaces.apache.org
Cc:
Subject: [Trinidad] Skinning Error: CSS not available
Hello,
I'm trying to working with skinning for the tr:table tag.
However, the styles I specify are not showing up. Using Firebug I
noticed that when I expand the link tag in the head section I
get an Apache Error message em html format, here's the message:
html
head
titleApache Tomcat/6.0.16 - Error report/title
style!--H1 {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-
family:Tahoma,Arial,sans-serif;color:white;background-
color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;font-size:14px;} BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-
color:white;} B {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;} P {font-
family:Tahoma,Arial,sans-serif;background:white;color:black;font-
size:12px;}A {color : black;}A.name {color : black;}HR {color :
#525D76;}--/style
/head
body
h1HTTP Status 404 - /RxMasterNV/adf/styles/cache/tableskin-
desktop-b2dkl6-en-ltr-gecko.css/h1
HR size=1 noshade=noshadepbtype/b
Status report/ppbmessage/b u/RxMasterNV/adf/styles/
cache/tableskin-desktop-b2dkl6-en-ltr-gecko.css/u/
ppbdescription/b uThe requested resource (/RxMasterNV/adf/
styles/cache/tableskin-desktop-b2dkl6-en-ltr-gecko.css) is not
available./u/pHR size=1 noshade=noshade
h3Apache Tomcat/6.0.16/h3
/body
/html
It seems that the CSS cannot be found. Does anyone have any
ideias on how to approach the problem? This is my set up:
* Netbeans 6.1
* Tomcat 6.16
* Trinidad 1.2.8
* MyFaces Core 1.2.3
trinidad-config.xml
?xml version=1.0 encoding=UTF-8?
trinidad-config xmlns=http://myfaces.apache.org/trinidad/config
!-- Enable debug output --
debug-outputtrue/debug-output
!-- Pick accessibility options based on a per-user
managed bean --
!--accessibility-modedefault/accessibility-mode--
skin-familytableskin/skin-family
/trinidad-config
trinidad-skins.xml
?xml version=1.0 encoding=ISO-8859-1?
skins xmlns=http://myfaces.apache.org/trinidad/skin;
skin
idtableskin.desktop/id
familytableskin/family
render-kit-idorg.apache.myfaces.trinidad.desktop/
render-kit-id
style-sheet-nameskins/tableskin/tableskin.css/
style-sheet-name
/skin
/skins
web.xml
I have
org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION set to true.
skins/tableskin/tableskin.css
.AFDarkForeground:alias {
color:#00CC00;
}
.AFDefaultFontFamily:alias {
font-family: Tahoma, Verdana, Helvetica, sans-serif;
}
/*Specifies the background color for data cells. This is
included in the af|column::cell* and af|table::control-bar*
selectors.*/
.AFTableCellDataBackgroundColor:alias {
padding-left: 1px;
padding-right: 1px;
margin: 0;
background-color: blue;
}
/*
Re: [Trinidad] Skinning Error: CSS not available
but it it not the trinidad skinning css file which I included. the
skinning css file should exist at the location you specified in the
trinidad-skins.xml configuration file. the skin-elements you specify
there should be referenced by a skin-family-element in the trinidad-
config.xml
so you have to decide if you want to import styles without the
skinning mechanism or if you want to take advantage of the trinidad
skinning mechanism. for the latter take the above steps.
burghard.
Am 18.08.2008 um 19:31 schrieb Burghard Britzke:
I use
tr:document
f:facet name=metaContainer
h:panelGroup
style type=text/css
@import
#{facesContext.externalContext.requestContextPath}/path to my.css
/style
...
/h:panelGroup
/f:facet
and it worked for me. the link-element should also work as the
script-and the style-element does. you can group more elements to a
h:panelGroup which is rendered a a sequence of elements in the head-
element of the html response.
hth
burghard.
Am 18.08.2008 um 19:15 schrieb Marco Vieira:
Thanks for the quick replies,
I've tried manually linking the CSS file within trh:head tags. But
it didn't work it just added another CSS reference.
Anyone have more ideias? I've been on this for 3 days...I'm sort of
a beginner :)
Thanks in advance,
Marco
On Mon, Aug 18, 2008 at 3:38 PM, Simon Lessard [EMAIL PROTECTED]
wrote:
Hi,
No, tr:document should add the skin reference correctly, I don't
know why it isn't working for you yet however.
Regards,
~ Simon
On Mon, Aug 18, 2008 at 10:33 AM, René van Wijk [EMAIL PROTECTED]
wrote:
I am not sure but to my knowledge you have to use
trh:html
trh:head title=Departments
meta http-equiv=Content-Type content=text/html;
charset=windows-1252/
/trh:head
trh:body
/trh:body
trh:html
if you want the trinidad metadata, such as skins, to be loaded. The
tag tr:document only adds the default html, head and body tags.
Hope this helps.
-Original Message-
From: Marco Vieira [mailto:[EMAIL PROTECTED]
Sent: Mon 8/18/2008 16:17 PM
To: users@myfaces.apache.org
Cc:
Subject: [Trinidad] Skinning Error: CSS not available
Hello,
I'm trying to working with skinning for the tr:table tag.
However, the styles I specify are not showing up. Using Firebug I
noticed that when I expand the link tag in the head section I
get an Apache Error message em html format, here's the message:
html
head
titleApache Tomcat/6.0.16 - Error report/title
style!--H1 {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;font-size:22px;} H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-
color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;font-size:14px;} BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-
color:white;} B {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;} P {font-
family:Tahoma,Arial,sans-serif;background:white;color:black;font-
size:12px;}A {color : black;}A.name {color : black;}HR {color :
#525D76;}--/style
/head
body
h1HTTP Status 404 - /RxMasterNV/adf/styles/cache/tableskin-
desktop-b2dkl6-en-ltr-gecko.css/h1
HR size=1 noshade=noshadepbtype/b
Status report/ppbmessage/b u/RxMasterNV/adf/styles/
cache/tableskin-desktop-b2dkl6-en-ltr-gecko.css/u/
ppbdescription/b uThe requested resource (/RxMasterNV/adf/
styles/cache/tableskin-desktop-b2dkl6-en-ltr-gecko.css) is not
available./u/pHR size=1 noshade=noshade
h3Apache Tomcat/6.0.16/h3
/body
/html
It seems that the CSS cannot be found. Does anyone have any
ideias on how to approach the problem? This is my set up:
* Netbeans 6.1
* Tomcat 6.16
* Trinidad 1.2.8
* MyFaces Core 1.2.3
trinidad-config.xml
?xml version=1.0 encoding=UTF-8?
trinidad-config xmlns=http://myfaces.apache.org/trinidad/config
!-- Enable debug output --
debug-outputtrue/debug-output
!-- Pick accessibility options based on a per-user
managed bean --
!--accessibility-modedefault/accessibility-mode--
skin-familytableskin/skin-family
/trinidad-config
trinidad-skins.xml
?xml version=1.0 encoding=ISO-8859-1?
skins xmlns=http://myfaces.apache.org/trinidad/skin;
skin
idtableskin.desktop/id
familytableskin/family
render-kit-idorg.apache.myfaces.trinidad.desktop/
render-kit-id
style-sheet-nameskins/tableskin/tableskin.css/
style-sheet-name
/skin
/skins
web.xml
I have
org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION set to true
Re: [Trinidad] Skinning Error: CSS not available
Am 19.08.2008 um 00:58 schrieb Marco Vieira:
Hi,
Well I would like to use the Trinidad Skinning mechanism. I verified
that the CSS file is deployed to the WAR. In the trinidad-skins.xml
file I even tried to make the path more specific using this url: //
RxMasterNV/skins/tableskin/tableskin.css
But still no luck. Burghard, I tried your solution, but I kept
getting an error saying that I cannot use #{...} in the templating
text body, or something like that.
I feel that the issue is simple, but I just can't put my finger on
it. Any other suggestions?
Thanks,
Marco
On Mon, Aug 18, 2008 at 6:51 PM, Burghard Britzke [EMAIL PROTECTED]
wrote:
but it it not the trinidad skinning css file which I included. the
skinning css file should exist at the location you specified in the
trinidad-skins.xml configuration file. the skin-elements you specify
there should be referenced by a skin-family-element in the trinidad-
config.xml
so you have to decide if you want to import styles without the
skinning mechanism or if you want to take advantage of the trinidad
skinning mechanism. for the latter take the above steps.
burghard.
Am 18.08.2008 um 19:31 schrieb Burghard Britzke:
I use
tr:document
f:facet name=metaContainer
h:panelGroup
style type=text/css
@import
#{facesContext.externalContext.requestContextPath}/path to my.css
/style
...
/h:panelGroup
/f:facet
and it worked for me. the link-element should also work as the
script-and the style-element does. you can group more elements to a
h:panelGroup which is rendered a a sequence of elements in the head-
element of the html response.
hth
burghard.
Am 18.08.2008 um 19:15 schrieb Marco Vieira:
Thanks for the quick replies,
I've tried manually linking the CSS file within trh:head tags. But
it didn't work it just added another CSS reference.
Anyone have more ideias? I've been on this for 3 days...I'm sort
of a beginner :)
Thanks in advance,
Marco
On Mon, Aug 18, 2008 at 3:38 PM, Simon Lessard [EMAIL PROTECTED]
wrote:
Hi,
No, tr:document should add the skin reference correctly, I don't
know why it isn't working for you yet however.
Regards,
~ Simon
On Mon, Aug 18, 2008 at 10:33 AM, René van Wijk [EMAIL PROTECTED]
wrote:
I am not sure but to my knowledge you have to use
trh:html
trh:head title=Departments
meta http-equiv=Content-Type content=text/html;
charset=windows-1252/
/trh:head
trh:body
/trh:body
trh:html
if you want the trinidad metadata, such as skins, to be loaded.
The tag tr:document only adds the default html, head and body
tags. Hope this helps.
-Original Message-
From: Marco Vieira [mailto:[EMAIL PROTECTED]
Sent: Mon 8/18/2008 16:17 PM
To: users@myfaces.apache.org
Cc:
Subject: [Trinidad] Skinning Error: CSS not available
Hello,
I'm trying to working with skinning for the tr:table tag.
However, the styles I specify are not showing up. Using Firebug I
noticed that when I expand the link tag in the head section I
get an Apache Error message em html format, here's the message:
html
head
titleApache Tomcat/6.0.16 - Error report/title
style!--H1 {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;font-size:22px;} H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-
color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;font-size:14px;} BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-
color:white;} B {font-family:Tahoma,Arial,sans-
serif;color:white;background-color:#525D76;} P {font-
family:Tahoma,Arial,sans-serif;background:white;color:black;font-
size:12px;}A {color : black;}A.name {color : black;}HR {color :
#525D76;}--/style
/head
body
h1HTTP Status 404 - /RxMasterNV/adf/styles/cache/
tableskin-desktop-b2dkl6-en-ltr-gecko.css/h1
HR size=1 noshade=noshadepbtype/b
Status report/ppbmessage/b u/RxMasterNV/adf/
styles/cache/tableskin-desktop-b2dkl6-en-ltr-gecko.css/u/
ppbdescription/b uThe requested resource (/RxMasterNV/adf/
styles/cache/tableskin-desktop-b2dkl6-en-ltr-gecko.css) is not
available./u/pHR size=1 noshade=noshade
h3Apache Tomcat/6.0.16/h3
/body
/html
It seems that the CSS cannot be found. Does anyone have any
ideias on how to approach the problem? This is my set up:
* Netbeans 6.1
* Tomcat 6.16
* Trinidad 1.2.8
* MyFaces Core 1.2.3
trinidad-config.xml
?xml version=1.0 encoding=UTF-8?
trinidad-config xmlns=http://myfaces.apache.org/trinidad/config
!-- Enable debug output --
debug-outputtrue/debug-output
!-- Pick accessibility options based on a per
Re: trinidad xhtml compliance
use f:view contentType=text/xml to force xhtml content type, to be rendered. but be aware of the issues matthias mentioned. https://issues.apache.org/jira/browse/TRINIDAD-1152 https://issues.apache.org/jira/browse/TRINIDAD-1139 https://issues.apache.org/jira/browse/TRINIDAD-818 you probably want to vote for it to get it done. perhaps you want to fix it. sincerely, burghard. Am 06.08.2008 um 05:11 schrieb Ray Clough: Am I correct that Trinidad does not output, and cannot be forced to output valid xhtml? I am using Trinidad 1.2.8 with Facelets. Using the tr:document tag with mode=strict still only outputs HTML 4, with a strict mode html 4 dtd. The same is true trying trh:html. The doctype is not xhtml, and the meta and link tags are not closed. There are probably other deviations from xhtml, but these are the ones I've noticed first. Thanks, Ray Clough [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/trinidad-xhtml-compliance-tp18843548p18843548.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Partial Page Rendering using Trinidad does not work on Weblogic 10
unsupported class version means that you are trying to load java5
classes into a java 1.4 vm or a java6 class into a java5 vm.
Am 05.08.2008 um 15:33 schrieb René van Wijk:
Hi Matthias,
When I rebuild the trinidad project, I get an unsupported class
version error when I run it again. Could you please send me a
version of a Trinidad build with your patch in it.
Thank you in advance
-Original Message-
From: [EMAIL PROTECTED] on behalf of Matthias Wessendorf
Sent: Tue 8/5/2008 12:35 PM
To: MyFaces Discussion
Cc:
Subject: Re: Partial Page Rendering using Trinidad does not work on
Weblogic 10
On Tue, Aug 5, 2008 at 12:19 PM, René van Wijk
[EMAIL PROTECTED] wrote:
Hi Matthias,
First, thanks for your reaction. I tried Trinidad 1.0.9 on
WebLogic 10 but unfortunately no luck, still the same issue.
that indicates there is no fix on the svn :-)
The hack you proposed where I find the XmlHttpServletResponse,
that is in what
package is it located?
here is my temporary modified file:
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* License); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
package org.apache.myfaces.trinidadinternal.config.xmlHttp;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletOutputStream;
import javax.servlet.ServletResponse;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpServletResponseWrapper;
import org.apache.myfaces.trinidad.logging.TrinidadLogger;
import
org
.apache.myfaces.trinidadinternal.renderkit.core.ppr.XmlResponseWriter;
@SuppressWarnings(deprecation)
final class XmlHttpServletResponse extends HttpServletResponseWrapper
{
XmlHttpServletResponse(ServletResponse response)
{
super((HttpServletResponse)response);
_contentType = text/xml;charset=utf-8;
// must set contentType here since
// setContentType is ignored when inside an included page (bug
5591124)
this.setContentType(_contentType);
}
@Override
public void sendRedirect(
final String url) throws IOException
{
XmlHttpConfigurator.__sendRedirect(getWriter(), url);
}
@Override
public ServletOutputStream getOutputStream()
throws IOException
{
ServletOutputStream base = super.getOutputStream();
return new XmlOutput(base).getOutputStream();
}
@Override
public PrintWriter getWriter() throws IOException
{
PrintWriter base = super.getWriter();
return new XmlOutput(base).getWriter();
}
@Override
public void setContentType(final String type)
{
// the reason we're using XmlHttpServletResponse is because
// we're producing a ppr xml response, so ignore any
// attempts to set the contentType, since the contentType
// must be text/xml:
_LOG.finer(ignoring setContentType:{0}, type);
super.setContentType(_contentType);
}
@Override
public void sendError(final int sc) throws IOException
{
sendError(sc, null);
}
@Override
public void sendError(final int sc, final String string) throws
IOException
{
PrintWriter writer = getWriter();
XmlResponseWriter rw = new XmlResponseWriter(writer, UTF-8);
rw.startDocument();
rw.startElement(error, null);
rw.writeAttribute(status, sc, null);
rw.writeText(string, null);
rw.endElement(error);
rw.endDocument();
rw.close();
}
[trinidad] Facelet Template with tr:document
I am developing a facelet template with a tr:document within. The html-title should vary for every use of that template. So I put the title-tag in a ui:insert within a f:facet name=metaContainer. That works well from my template-clients which use ui:define to overwrite the f:facet name=metaContainer. Unfortunally I want to insert other tags which should be rendered in the header and which should only be defined once in the template and should not be overwriten by each client (like a global script-tag). is there a way to do it? with the tr:document? or shold I use trh:html, trh:head and trh:body instead?
Re: Trinidad tr:treeTable expand/collapse commands
because of your filename ending (jspx) I think you are rendering xhtml. may be you are running into the issue [#TRINIDAD-1139] partial submit (for ppr) does not work for content type xhtml (_submitPartialChange() does not submitForm() for xhtml) - ASF JIRA . Vote for it and it will be fixed sooner. meanwhile you can debug the javascript code with firebug to verify that it is this issue. hth burghard. Am 27.07.2008 um 15:07 schrieb Alireza Salimi: My problem is expand/collapse commands of treeTable. I think they are supposed to automatically expand/collapse tree nodes, but by clicking them, nothing happens. I read the treeTable.jspx and its backing beans - I think they are TreeModelAdapter.java , TreeMode.java-, but did not find anything about handling collapse/expand events. I know that there is some events related to expansion/collapse of table rows, but I think they are used in some special cases. I'm new to Trinidad and today is my first day with it. Thanks in advance. Alireza
Re: [TRINIDAD] Eclipse/Ganymede has visual page editing support for Trinidad
the facelets plugin is not released yet. but it is downloadable from cvs and can easily build and installed (see http://wiki.eclipse.org/JSF_Facelets_Tools_Project) . it works fine for me. I did not know that the trinidad suport has not been anounced. this is working very well, too. Am 22.07.2008 um 21:56 schrieb Matthias Wessendorf: Hello Danny, On Tue, Jul 15, 2008 at 3:21 PM, Danny Robinson [EMAIL PROTECTED] wrote: 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. +1 can you commit that ? 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. -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
Re: [Trinidad] Nullpointer from Google Bot
Every NullPointerException is caused by a missing initialization. My first guess is an initialization error in de.tccproducts.dps.web.utils.lifecycle.ExceptionFilter.doFilter sincerely, burghard. Am 08.07.2008 um 09:18 schrieb Döring Markus: Hi List, since our application went live, we get some nullpointer during night. Some research has shown that the IP that is accessing the site is known as some “Google Bot” scanning links, ect. Don’t know why the nullpointer happens, looks like the Google Bot sends some “strange” MacOS header in the request. Can someone have a look at this? It’s not critical because it’s no real user, but it’s not nice to get a nullpointer every night. Greetings Markus Log session start time Tue Jul 08 02:32:27 CEST 2008 Time Thread Level Category Message 896715047 http-0.0.0.0-8080-4 ERROR facelets.viewhandler Error Rendering View[/error.xhtml] java.lang.NullPointerException at org .apache .myfaces .trinidadinternal .renderkit .core.skin.MacOSSwitcherIcon._getIcon(MacOSSwitcherIcon.java:104) at org .apache .myfaces .trinidadinternal .renderkit .core.skin.MacOSSwitcherIcon.renderIcon(MacOSSwitcherIcon.java:61) at org .apache .myfaces .trinidadinternal .renderkit.core.xhtml.OutputUtils.renderIcon(OutputUtils.java:284) at org .apache .myfaces .trinidadinternal .renderkit.core.xhtml.OutputUtils.renderIcon(OutputUtils.java:254) at org .apache .myfaces .trinidadinternal .renderkit .core .xhtml .ShowDetailRenderer.renderDisclosureIcon(ShowDetailRenderer.java:184) at org .apache .myfaces .trinidadinternal .renderkit .core .xhtml .ShowDetailRenderer.renderDisclosureIcon(ShowDetailRenderer.java:194) at org .apache .myfaces .trinidadinternal .renderkit .core.xhtml.ShowDetailRenderer.encodeAll(ShowDetailRenderer.java:91) at org .apache .myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224) at org .apache .myfaces .trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java: 711) at org .apache .myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java: 304) at org .apache .myfaces .trinidadinternal .renderkit .core .xhtml .PanelGroupLayoutRenderer.encodeChild(PanelGroupLayoutRenderer.java: 188) at org .apache .myfaces .trinidadinternal .renderkit .core .xhtml .PanelGroupLayoutRenderer ._encodeChildren(PanelGroupLayoutRenderer.java:154) at org .apache .myfaces .trinidadinternal .renderkit .core .xhtml .PanelGroupLayoutRenderer.encodeAll(PanelGroupLayoutRenderer.java:106) at org .apache .myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224) at org .apache .myfaces .trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java: 711) at org .apache .myfaces .trinidadinternal .uinode.UIComponentUINode._renderComponent(UIComponentUINode.java:337) at org .apache .myfaces .trinidadinternal .uinode.UIComponentUINode.render(UIComponentUINode.java:279) at org .apache .myfaces .trinidadinternal .uinode.UIComponentUINode.render(UIComponentUINode.java:256) at org.apache.myfaces.trinidadinternal.ui.composite.ContextPoppingUINode $ContextPoppingRenderer.render(ContextPoppingUINode.java:240) at org .apache .myfaces.trinidadinternal.ui.BaseUINode.render(BaseUINode.java:358) at org .apache .myfaces.trinidadinternal.ui.BaseUINode.render(BaseUINode.java:313) at org .apache .myfaces .trinidadinternal.ui.BaseRenderer.renderChild(BaseRenderer.java:425) at org .apache .myfaces .trinidadinternal .ui.BaseRenderer.renderIndexedChild(BaseRenderer.java:343) at org .apache .myfaces .trinidadinternal .ui.BaseRenderer.renderIndexedChild(BaseRenderer.java:235) at org .apache .myfaces .trinidadinternal.ui.BaseRenderer.renderContent(BaseRenderer.java:142) at org .apache .myfaces.trinidadinternal.ui.BaseRenderer.render(BaseRenderer.java:93) at org .apache .myfaces .trinidadinternal .ui.laf.base.xhtml.XhtmlLafRenderer.render(XhtmlLafRenderer.java:84) at org .apache .myfaces.trinidadinternal.ui.BaseUINode.render(BaseUINode.java:358) at org .apache .myfaces.trinidadinternal.ui.BaseUINode.render(BaseUINode.java:313) at org .apache .myfaces .trinidadinternal.ui.BaseRenderer.renderChild(BaseRenderer.java:425) at org .apache .myfaces .trinidadinternal .ui.BaseRenderer.renderIndexedChild(BaseRenderer.java:343) at org .apache .myfaces .trinidadinternal .ui.BaseRenderer.renderIndexedChild(BaseRenderer.java:235) at org .apache .myfaces .trinidadinternal.ui.BaseRenderer.renderContent(BaseRenderer.java:142) at org .apache .myfaces.trinidadinternal.ui.BaseRenderer.render(BaseRenderer.java:93) at org .apache .myfaces .trinidadinternal
Re: PPR Response Coding Problem with Glassfish
I catched the response from the server and it contains a double xml-
header
?xml version=1.0 encoding=UTF-8 ??xml version=1.0 ?
?Tr-XHR-Response-Type ?
content action=/test/faces/test.jspx fragment![CDATA[div
id=j_id_id6table cellpadding=0...
...
is there a configuration option to prevent this double header in the
ppr response?
Am 03.07.2008 um 20:12 schrieb Matthias Wessendorf:
On Thu, Jul 3, 2008 at 7:03 PM, Burghard Britzke
[EMAIL PROTECTED] wrote:
first of all, this is NOT the issue I filed with (1139) there are
only
similar symptoms.
yes, it was bad from me to hijack this email thread
but there is a significant difference: (1139) does not send a
request while
on this issue a browser is not capable of parsing the response
because it
has two xml headers.
is there a way to switch of ppr?
for table paging? no
for your statement: it does not depend on wether facelets or jsp.
it is a
pure client side problem. it depends on html or xhtml/xml (imo)
yes, but faclets sends down xhtml as well.
I noticed that in the XML case, in your demo, document.forms is
undefined.
I haven't had much time to check it deeper (yes, the 1139 issue)
-M
Am 03.07.2008 um 11:03 schrieb Matthias Wessendorf:
I did a quick look at the issue, you filed (1139).
It is strange that xhtml is causing these kinda problems.
works fine with facelets.
give me some time to verify the root issues, instead
of doing a simple getElementById. I think there are
more similar issue to your problem.
-M
On Thu, Jul 3, 2008 at 8:33 AM, Burghard Britzke
[EMAIL PROTECTED] wrote:
with the following environment:
Mac OS X 10.5.4
Sun AS 9.0.2 (Glassfish)
Java 1.5
Safari 3.1.2 and Firefox 3.0
tr:table's page navigation does not work as expected for my
configuration.
A klick on one of the navigation buttons sends a request (or two)
to the
server. But the response is routed into an empty case of a
chained if
statement in the js-function _handlePprResponse() in file
DebugCommon1_2_8.js.
20723 else
20723 {
20724 // FIXME: log an error
20725 }
20726}
This is because the rootNodeName is parseerror. I checked the
documentElement which is passed to that function as a parameter.
I found
the
following:
parseerror
XML-Verarbeitungsfehler: XML- oder Text-Deklaration nicht am
Beginn der
Entität Adresse:
http://localhost:8080/test/faces/test.jspx Zeile Nr. 1, Spalte 40:
sourcetext
?xml version=1.0 encoding=UTF-8 ??xml version=1.0 ?
---^
/sourcetext
/parsererror
For the endusers it looks like they ran into TRINIDAD-1139. The
only
difference is that the page is rendered as html 4.01 (not xhtml).
and
with a
server side logging the presence of successfull requests can be
monitored.
Is it possible to prevent double ?XML? elements in the ppr
response by
configuration?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: PPR Response Coding Problem with Glassfish
I found the following solution in the dev.mailing list:
http://mail-archives.apache.org/mod_mbox/myfaces-dev/200709.mbox/[EMAIL
PROTECTED]
when I remove the
jsp:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]/jsp:text
at my jsp the PPR response does contain only one XML-PI and no parse
error occure.
It seems that the jsp servlet pushes its jsp:text-content (in this
case the XML-PI) into the response before the PPR engine filters the
rendered page.
to give it a chance I put the jsp:text element into the f:view. So
it is rendered at the beginning of the document but is filtered out
during PPR.
May be that there is a better way?
Am 04.07.2008 um 09:22 schrieb Matthias Wessendorf:
Hi,
On Fri, Jul 4, 2008 at 9:11 AM, Burghard Britzke
[EMAIL PROTECTED] wrote:
I catched the response from the server and it contains a double xml-
header
?xml version=1.0 encoding=UTF-8 ??xml version=1.0 ?
?Tr-XHR-Response-Type ?
content action=/test/faces/test.jspx fragment![CDATA[div
id=j_id_id6table cellpadding=0...
...
?xml version=1.0 ?
?Tr-XHR-Response-Type ?
this comes from Trinidad directly.
the extra PI is from your page, I guess.
is there a configuration option to prevent this double header in
the ppr
response?
not that I am aware of.
I need to run some tests on our library.
Am 03.07.2008 um 20:12 schrieb Matthias Wessendorf:
On Thu, Jul 3, 2008 at 7:03 PM, Burghard Britzke
[EMAIL PROTECTED] wrote:
first of all, this is NOT the issue I filed with (1139) there are
only
similar symptoms.
yes, it was bad from me to hijack this email thread
but there is a significant difference: (1139) does not send a
request while
on this issue a browser is not capable of parsing the response
because it
has two xml headers.
is there a way to switch of ppr?
for table paging? no
for your statement: it does not depend on wether facelets or jsp.
it is a
pure client side problem. it depends on html or xhtml/xml (imo)
yes, but faclets sends down xhtml as well.
I noticed that in the XML case, in your demo, document.forms is
undefined.
I haven't had much time to check it deeper (yes, the 1139 issue)
-M
Am 03.07.2008 um 11:03 schrieb Matthias Wessendorf:
I did a quick look at the issue, you filed (1139).
It is strange that xhtml is causing these kinda problems.
works fine with facelets.
give me some time to verify the root issues, instead
of doing a simple getElementById. I think there are
more similar issue to your problem.
-M
On Thu, Jul 3, 2008 at 8:33 AM, Burghard Britzke
[EMAIL PROTECTED] wrote:
with the following environment:
Mac OS X 10.5.4
Sun AS 9.0.2 (Glassfish)
Java 1.5
Safari 3.1.2 and Firefox 3.0
tr:table's page navigation does not work as expected for my
configuration.
A klick on one of the navigation buttons sends a request (or two)
to the
server. But the response is routed into an empty case of a chained
if
statement in the js-function _handlePprResponse() in file
DebugCommon1_2_8.js.
20723 else
20723 {
20724 // FIXME: log an error
20725 }
20726}
This is because the rootNodeName is parseerror. I checked the
documentElement which is passed to that function as a parameter. I
found
the
following:
parseerror
XML-Verarbeitungsfehler: XML- oder Text-Deklaration nicht am Beginn
der
Entität Adresse:
http://localhost:8080/test/faces/test.jspx Zeile Nr. 1, Spalte 40:
sourcetext
?xml version=1.0 encoding=UTF-8 ??xml version=1.0 ?
---^
/sourcetext
/parsererror
For the endusers it looks like they ran into TRINIDAD-1139. The only
difference is that the page is rendered as html 4.01 (not xhtml). and
with a
server side logging the presence of successfull requests can be
monitored.
Is it possible to prevent double ?XML? elements in the ppr
response by
configuration?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: PPR Response Coding Problem with Glassfish
BUT THIS IS NOT THE ISSUE I FILED! this is a completly different one.
only the result for the user is similar to that I filed. should I file
an issue for this one, too? I think I will do it.
Am 04.07.2008 um 19:43 schrieb Matthias Wessendorf:
On Fri, Jul 4, 2008 at 7:31 PM, Burghard Britzke
[EMAIL PROTECTED] wrote:
no!
for the jsp only the first one is the XML-PI.
the second one is only CDATA.
but at the rendered page the first does not appear. only the XML-PI
which is
in the CDATA is rendered.
that is the magic of jsp.
ok, well looks like not really supported right now.
The report you forwarded has a good description;
Do you add that info to the bug you filed, so that we don't loose it ?
-M
Am 04.07.2008 um 17:54 schrieb Matthias Wessendorf:
quick question.
your test,jspx start like this:
?xml version=1.0 encoding=UTF-8 ?
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:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]/
jsp:text
isn't that already one PI too much ?
-M
On Fri, Jul 4, 2008 at 5:39 PM, Matthias Wessendorf [EMAIL PROTECTED]
wrote:
On Fri, Jul 4, 2008 at 5:31 PM, Burghard Britzke
[EMAIL PROTECTED] wrote:
I found the following solution in the dev.mailing list:
http://mail-archives.apache.org/mod_mbox/myfaces-dev/200709.mbox/[EMAIL
PROTECTED]
when I remove the
jsp:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]/
jsp:text
at my jsp the PPR response does contain only one XML-PI and no
parse
error
occure.
yes, that workaround I found as well.
But, looks not like a desired step.
It seems that the jsp servlet pushes its jsp:text-content (in
this
case
the XML-PI) into the response before the PPR engine filters the
rendered
page.
to give it a chance I put the jsp:text element into the
f:view. So
it is
rendered at the beginning of the document but is filtered out
during
PPR.
May be that there is a better way?
not sure yet. Was busy. Not looked into this in detail, at all
-Matthias
Am 04.07.2008 um 09:22 schrieb Matthias Wessendorf:
Hi,
On Fri, Jul 4, 2008 at 9:11 AM, Burghard Britzke
[EMAIL PROTECTED] wrote:
I catched the response from the server and it contains a double
xml-header
?xml version=1.0 encoding=UTF-8 ??xml version=1.0 ?
?Tr-XHR-Response-Type ?
content action=/test/faces/test.jspx fragment![CDATA[div
id=j_id_id6table cellpadding=0...
...
?xml version=1.0 ?
?Tr-XHR-Response-Type ?
this comes from Trinidad directly.
the extra PI is from your page, I guess.
is there a configuration option to prevent this double header
in the
ppr
response?
not that I am aware of.
I need to run some tests on our library.
Am 03.07.2008 um 20:12 schrieb Matthias Wessendorf:
On Thu, Jul 3, 2008 at 7:03 PM, Burghard Britzke
[EMAIL PROTECTED] wrote:
first of all, this is NOT the issue I filed with (1139) there
are only
similar symptoms.
yes, it was bad from me to hijack this email thread
but there is a significant difference: (1139) does not send a
request
while
on this issue a browser is not capable of parsing the response
because
it
has two xml headers.
is there a way to switch of ppr?
for table paging? no
for your statement: it does not depend on wether facelets or
jsp. it
is a
pure client side problem. it depends on html or xhtml/xml (imo)
yes, but faclets sends down xhtml as well.
I noticed that in the XML case, in your demo, document.forms is
undefined.
I haven't had much time to check it deeper (yes, the 1139 issue)
-M
Am 03.07.2008 um 11:03 schrieb Matthias Wessendorf:
I did a quick look at the issue, you filed (1139).
It is strange that xhtml is causing these kinda problems.
works fine with facelets.
give me some time to verify the root issues, instead
of doing a simple getElementById. I think there are
more similar issue to your problem.
-M
On Thu, Jul 3, 2008 at 8:33 AM, Burghard Britzke
[EMAIL PROTECTED] wrote:
with the following environment:
Mac OS X 10.5.4
Sun AS 9.0.2 (Glassfish)
Java 1.5
Safari 3.1.2 and Firefox 3.0
tr:table's page navigation does not work as expected for my
configuration.
A klick on one of the navigation buttons sends a request (or
two) to
the
server. But the response is routed into an empty case of a
chained if
statement in the js-function _handlePprResponse() in file
DebugCommon1_2_8.js.
20723 else
20723 {
20724 // FIXME: log an error
20725 }
20726}
This is because the rootNodeName is parseerror. I checked the
documentElement which is passed to that function as a
parameter. I
found
the
following:
parseerror
XML-Verarbeitungsfehler: XML- oder Text-Deklaration nicht am
Beginn
der
Entität Adresse:
http://localhost:8080/test/faces/test.jspx Zeile Nr. 1, Spalte
40:
sourcetext
?xml version=1.0 encoding=UTF-8 ??xml version=1.0
PPR Response Coding Problem with Glassfish
with the following environment:
Mac OS X 10.5.4
Sun AS 9.0.2 (Glassfish)
Java 1.5
Safari 3.1.2 and Firefox 3.0
tr:table's page navigation does not work as expected for my
configuration. A klick on one of the navigation buttons sends a
request (or two) to the server. But the response is routed into an
empty case of a chained if statement in the js-function
_handlePprResponse() in file DebugCommon1_2_8.js.
20723 else
20723 {
20724 // FIXME: log an error
20725 }
20726}
This is because the rootNodeName is parseerror. I checked the
documentElement which is passed to that function as a parameter. I
found the following:
parseerror
XML-Verarbeitungsfehler: XML- oder Text-Deklaration nicht am
Beginn der Entität Adresse:
http://localhost:8080/test/faces/test.jspx Zeile Nr. 1, Spalte 40:
sourcetext
?xml version=1.0 encoding=UTF-8 ??xml version=1.0 ?
---^
/sourcetext
/parsererror
For the endusers it looks like they ran into TRINIDAD-1139. The only
difference is that the page is rendered as html 4.01 (not xhtml). and
with a server side logging the presence of successfull requests can be
monitored.
Is it possible to prevent double ?XML? elements in the ppr response
by configuration?
Re: PPR Response Coding Problem with Glassfish
first of all, this is NOT the issue I filed with (1139) there are only
similar symptoms.
but there is a significant difference: (1139) does not send a request
while on this issue a browser is not capable of parsing the response
because it has two xml headers.
is there a way to switch of ppr?
for your statement: it does not depend on wether facelets or jsp. it
is a pure client side problem. it depends on html or xhtml/xml (imo)
Am 03.07.2008 um 11:03 schrieb Matthias Wessendorf:
I did a quick look at the issue, you filed (1139).
It is strange that xhtml is causing these kinda problems.
works fine with facelets.
give me some time to verify the root issues, instead
of doing a simple getElementById. I think there are
more similar issue to your problem.
-M
On Thu, Jul 3, 2008 at 8:33 AM, Burghard Britzke
[EMAIL PROTECTED] wrote:
with the following environment:
Mac OS X 10.5.4
Sun AS 9.0.2 (Glassfish)
Java 1.5
Safari 3.1.2 and Firefox 3.0
tr:table's page navigation does not work as expected for my
configuration.
A klick on one of the navigation buttons sends a request (or two)
to the
server. But the response is routed into an empty case of a chained
if
statement in the js-function _handlePprResponse() in file
DebugCommon1_2_8.js.
20723 else
20723 {
20724 // FIXME: log an error
20725 }
20726}
This is because the rootNodeName is parseerror. I checked the
documentElement which is passed to that function as a parameter. I
found the
following:
parseerror
XML-Verarbeitungsfehler: XML- oder Text-Deklaration nicht am
Beginn der
Entität Adresse:
http://localhost:8080/test/faces/test.jspx Zeile Nr. 1, Spalte 40:
sourcetext
?xml version=1.0 encoding=UTF-8 ??xml version=1.0 ?
---^
/sourcetext
/parsererror
For the endusers it looks like they ran into TRINIDAD-1139. The only
difference is that the page is rendered as html 4.01 (not xhtml).
and with a
server side logging the presence of successfull requests can be
monitored.
Is it possible to prevent double ?XML? elements in the ppr
response by
configuration?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: [trinidad] infos about /.../adf/jsLibs/DebugCommon1_2_8.js?
thank you! Am 02.07.2008 um 07:27 schrieb Matthias Wessendorf: On Wed, Jul 2, 2008 at 7:20 AM, Burghard Britzke [EMAIL PROTECTED] wrote: thank you. but is there any hint for searching (and finding) in the firebug? yes. Go to the script tab, select the Trinidad file, and do a search at the very right. Find the desired section highlighted in the content part of firebug. I attached a screenshot to this mail as well -Matthias Am 02.07.2008 um 07:11 schrieb Matthias Wessendorf: On Tue, Jul 1, 2008 at 9:13 PM, Burghard Britzke [EMAIL PROTECTED] wrote: ok! I tried it with firebug before but it is a little bit tricky to find the right location for the breakpoint in a 30,000 lines code without a search funktion. for debugging, I'd say this in my web.xml as well: context-param param-nameorg.apache.myfaces.trinidad.DEBUG_JAVASCRIPT/param- name param-valuetrue/param-value /context-param for production I'd avoid that, b/c when not present (and therefore false) we do obfuscating, due to perf. reasons. so my question is: does trinidad deliver the same script file for every request? because you told me that it is build out of many smaller files. yes, that is faster than serving 20 files. And this file will be cached by the browser of your choice. -M sincerely, burghard. Am 01.07.2008 um 09:57 schrieb Matthias Wessendorf: On Tue, Jul 1, 2008 [EMAIL PROTECTED] wrote: is it possible to get some debugging info about what is going on at the client when pressing some link or button? It seems that nearly every thing is coded in the (Debug)Common1_2_8.js. but how to get info about infos about the state of its objects at some points? This file is created out of several smaller files. And yes, therefore it has everything inside. For debugging I'd do the following: -Get Firebug -check the HTML source what JS function is executed on the click -find the func in the JS file, set a breakpoint -do the click and debug through it Greetings, Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org firebug_intro.PNG
[trinidad] _submitPartialChange() does not submitForm() for xhtml
using trinidad 1.2.8 with Firefox 3.0 (safari has the same behaviour,
too) on Mac OS X 10.5.4
xhtml rendered pages does not submit forms via _submitPartialChange()
I found the following code snippet in DebugCommon1_2_8.js in function
_submitPartialChange()
9176 // Get the actual form object
9177 if ((typeof form) == string)
9178 form = document[form];
9179
9180 if (!form)
9181 return false;
9182
the expression document[form] returns -- undefined for xhtml documents
so this function exits always without submitting.
my sample document
?xml version=1.0 encoding=UTF-8 ?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
html xmlns=http://www.w3.org/1999/xhtml;
head
titletest/title
/head
body onload=alert(document['formid']+'
'+document.getElementById('formid'))
form id=formid action=test.html/form
/body
/html
alerts the following message: undefined [object HTMLFormElement]
this seems to be a bug.
to workaround: is there a way to suppress PPR?
Re: [trinidad] _submitPartialChange() does not submitForm() for xhtml
may be that is because it is delivered as http content type text/html.
I experienced the same for safari and firefox 3.0 on mac os x.
but when I rename the file to test.xhtml it is delivered with the http
xml content type and the result is the unknown [object
HTMLFormElement]
I will try to file an issue (I found another issue this afternoon)
Am 02.07.2008 um 12:50 schrieb Matthias Wessendorf:
quick question:
why is there no name=formid on the form?
In that case it works.
On Wed, Jul 2, 2008 at 12:40 PM, Matthias Wessendorf [EMAIL PROTECTED]
wrote:
Hi,
On Wed, Jul 2, 2008 at 12:33 PM, Burghard Britzke
[EMAIL PROTECTED] wrote:
using trinidad 1.2.8 with Firefox 3.0 (safari has the same
behaviour, too)
on Mac OS X 10.5.4
FF2 on windoze as well
(and the great IE7 too...)
xhtml rendered pages does not submit forms via
_submitPartialChange()
I found the following code snippet in DebugCommon1_2_8.js in
function
_submitPartialChange()
9176 // Get the actual form object
9177 if ((typeof form) == string)
9178 form = document[form];
9179
9180 if (!form)
9181 return false;
9182
the expression document[form] returns -- undefined for xhtml
documents
so this function exits always without submitting.
my sample document
?xml version=1.0 encoding=UTF-8 ?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
head
titletest/title
/head
body onload=alert(document['formid']+'
'+document.getElementById('formid'))
form id=formid action=test.html/form
/body
/html
alerts the following message: undefined [object HTMLFormElement]
this seems to be a bug.
can you file an issue?
I try to look at it next days.
Thanks,
Matthias
to workaround: is there a way to suppress PPR?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
[trinidad] infos about /.../adf/jsLibs/DebugCommon1_2_8.js?
is it possible to get some debugging info about what is going on at the client when pressing some link or button? It seems that nearly every thing is coded in the (Debug)Common1_2_8.js. but how to get info about infos about the state of its objects at some points? burghard.
Re: [trinidad] infos about /.../adf/jsLibs/DebugCommon1_2_8.js?
ok! I tried it with firebug before but it is a little bit tricky to find the right location for the breakpoint in a 30,000 lines code without a search funktion. so my question is: does trinidad deliver the same script file for every request? because you told me that it is build out of many smaller files. sincerely, burghard. Am 01.07.2008 um 09:57 schrieb Matthias Wessendorf: On Tue, Jul 1, 2008 [EMAIL PROTECTED] wrote: is it possible to get some debugging info about what is going on at the client when pressing some link or button? It seems that nearly every thing is coded in the (Debug)Common1_2_8.js. but how to get info about infos about the state of its objects at some points? This file is created out of several smaller files. And yes, therefore it has everything inside. For debugging I'd do the following: -Get Firebug -check the HTML source what JS function is executed on the click -find the func in the JS file, set a breakpoint -do the click and debug through it Greetings, Matthias
Re: [trinidad] infos about /.../adf/jsLibs/DebugCommon1_2_8.js?
thank you. but is there any hint for searching (and finding) in the firebug? Am 02.07.2008 um 07:11 schrieb Matthias Wessendorf: On Tue, Jul 1, 2008 at 9:13 PM, Burghard Britzke [EMAIL PROTECTED] wrote: ok! I tried it with firebug before but it is a little bit tricky to find the right location for the breakpoint in a 30,000 lines code without a search funktion. for debugging, I'd say this in my web.xml as well: context-param param-nameorg.apache.myfaces.trinidad.DEBUG_JAVASCRIPT/param- name param-valuetrue/param-value /context-param for production I'd avoid that, b/c when not present (and therefore false) we do obfuscating, due to perf. reasons. so my question is: does trinidad deliver the same script file for every request? because you told me that it is build out of many smaller files. yes, that is faster than serving 20 files. And this file will be cached by the browser of your choice. -M sincerely, burghard. Am 01.07.2008 um 09:57 schrieb Matthias Wessendorf: On Tue, Jul 1, 2008 [EMAIL PROTECTED] wrote: is it possible to get some debugging info about what is going on at the client when pressing some link or button? It seems that nearly every thing is coded in the (Debug)Common1_2_8.js. but how to get info about infos about the state of its objects at some points? This file is created out of several smaller files. And yes, therefore it has everything inside. For debugging I'd do the following: -Get Firebug -check the HTML source what JS function is executed on the click -find the func in the JS file, set a breakpoint -do the click and debug through it Greetings, Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
[Trinidad] sorting
I provide the following jsp
?xml version=1.0 encoding=UTF-8 ?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.1
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:tr=http://myfaces.apache.org/trinidad;
jsp:directive.page contentType=text/html; charset=UTF-8/
jsp:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]/
jsp:text
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{ManagedBean.list}
rows=4
tr:column sortProperty=id sortable=true
align=right
f:facet name=headerh:outputText value=id/
/f:facet
tr:outputText value=#{row.id}/tr:outputText
/tr:column
tr:column sortProperty=name sortable=true
f:facet name=headerh:outputText
value=Name//f:facet
tr:outputText value=#{row.name}/
tr:outputText
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
/jsp:root
the list() method of ManagedBean delivers a list of seven rows with an
int id and String name.
the table renders 4 rows and put the row navigator widgets on the top
of the table.
but when I click on the navigator widgets it does not navigate to the
next page. but it requests a new list from the ManagedBean.
even when I try to sort - only a new list ist requested from the
ManagedBean but it is not sorted.
did I miss something?
Re: [Trinidad] sorting
I am using
sun-appserver9.1
Sun's JavaServer Faces implementation (1.2_04-b20-p03)
trinidad libs v 1.2.8
Am 30.06.2008 um 12:00 schrieb Burghard Britzke:
I provide the following jsp
?xml version=1.0 encoding=UTF-8 ?
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:directive.page contentType=text/html; charset=UTF-8/
jsp:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]/
jsp:text
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{ManagedBean.list}
rows=4
tr:column sortProperty=id sortable=true
align=right
f:facet name=headerh:outputText value=id/
/f:facet
tr:outputText value=#{row.id}/tr:outputText
/tr:column
tr:column sortProperty=name sortable=true
f:facet name=headerh:outputText
value=Name//f:facet
tr:outputText value=#{row.name}/
tr:outputText
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
/jsp:root
the list() method of ManagedBean delivers a list of seven rows with
an int id and String name.
the table renders 4 rows and put the row navigator widgets on the
top of the table.
but when I click on the navigator widgets it does not navigate to
the next page. but it requests a new list from the ManagedBean.
even when I try to sort - only a new list ist requested from the
ManagedBean but it is not sorted.
did I miss something?
Re: NoClassDefFoundError when using myfaces in my webapp
NoClassDefFoundError means an erronous class path in every case. check if the library file servlet-api.jar is in your lib folder. Am 08.12.2007 um 07:46 schrieb ying lcs: Hi, I am trying to use myfaces in my web application. i have added all the libraries in the 'lib' of the myfaces distribution. But I am still getting the following error: Can you please tell me what am i missing? Thank you. java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config at org .apache .myfaces .application .jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:249) at com .sun .rave .web .ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:320) at org .apache .myfaces .lifecycle .RenderResponseExecutor.execute(RenderResponseExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java: 132) at javax.faces.webapp.FacesServlet.service(FacesServlet.java: 138) at org .apache .catalina .core .ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java: 290) at org .apache .catalina .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:267) at org .apache .catalina .core .ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java: 235) at org .apache .catalina .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org .apache .catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java: 233) at org .apache .catalina.core.StandardContextValve.invoke(StandardContextValve.java: 175) at org .apache .catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org .apache .catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org .apache .catalina.core.StandardEngineValve.invoke(StandardEngineValve.java: 109) at org .apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java: 263) at org .apache.coyote.http11.Http11Processor.process(Http11Processor.java: 844) at org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.process(Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint $Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) D
Re: [Trinidad] Invalid XHTML produced
I posted for the same subject at http://www.mail-archive.com/ users@myfaces.apache.org/msg40586.html but got no answer. Am 08.08.2007 um 20:50 schrieb Andrew Robinson: I am trying to use the following DOCTYPE for my pages with Trinidad 1.0.2-SNAPSHOT and facelets 1.1.11: !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; So I added: f:view contentType=application/xhtml+xml / To my page. The problem is that Trinidad is producing invalid XML in the head: link rel=stylesheet charset=UTF-8 type=text/css href=/test/adf/styles/cache/minimal-desktop-496553747-en-gecko- cmp.css ... The link tag is never closed. Is there a way to get xhtml standard compliant xhtml rendered using trinidad? A4J used a hack of using Tidy to ensure the output was valid XML, is there something similar with trinidad? In the meantime it looks like I will have to use HTML as my content- type. Thanks, Andrew
Eclipse Bug ID for Faclets Support
There is a bug listet in Eclipse Bugzilla for faclets code completion in their xhtml editor. you are invited to vote for it. https://bugs.eclipse.org/bugs/show_bug.cgi?id=192393
Re: [Trinidad] design components with using css files
have a look at this
http://www.oracle.com/technology/products/adf/adffaces/11/doc/skin-
selectors.html
Am 26.07.2007 um 08:09 schrieb Okan Çetin:
Hi,
I am trying to create styles with using css files. I am trouble with
outputText component.
This code is working :
af | inputText::content {
background-image: url(../images/output.PNG);
}
But same code for outputText is not working :
af | outputText::content {
background-image: url(../images/output.PNG);
}
Is there a guide creating css styles for trinidad components?
--
~
otomatik oluşturuldu:
http://ocetin.net/log
http://linux.beykent.edu.tr
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
f.view does not have an attribute contentType. for the RI. does it have such an attribute in MyFaces? Am 23.07.2007 um 23:23 schrieb noah: I can confirm that it does. f:view contentType=text/html seems to be a necessity if you want Dojo to work. On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: In Facelets, setting contentType on f:view should do the trick, but I don't know for sure. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: and for facelets? is it possible to set the content type, too? for facelets .xhtml files it rendered html 4.01. Am 23.07.2007 um 19:58 schrieb Adam Winer: Funny, I should have remembered: https://issues.apache.org/jira/browse/TRINIDAD-78 ... since I fixed it myself... Looks like it's this simple: set the contentType of your JSP page to be XHTML, get XHTML output. And, if you fail to set a content type, then by default you get HTML for .jsp pages, XHTML for .jspx documents. -- Adam On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: As best I know, we never render XHTML, so I'm surprised to hear otherwise. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
but it is true: f:view xmlns:f=http://java.sun.com/jsf/core; xmlns:tr=http://myfaces.apache.org/trinidad; tr:document /tr:document /f:view renders as !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN ... and f:view contentType=text/xml xmlns:f=http://java.sun.com/jsf/core; xmlns:tr=http://myfaces.apache.org/trinidad; tr:document /tr:document /f:view renders as !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN ... Am 25.07.2007 um 10:00 schrieb Burghard Britzke: f.view does not have an attribute contentType. for the RI. does it have such an attribute in MyFaces? Am 23.07.2007 um 23:23 schrieb noah: I can confirm that it does. f:view contentType=text/html seems to be a necessity if you want Dojo to work. On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: In Facelets, setting contentType on f:view should do the trick, but I don't know for sure. ... On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: [Trinidad] sorting table, table range navigation...
did you test if this page works fine for you if you surround your
tr:document in template.xhtml with a f:view contentType=text/
xml element?
for me it does not!
if I force xhtml output for my pages the trinidad table paging and
sorting controls does not work properly.
can anybody repeat this observation?
Am 21.07.2007 um 12:28 schrieb Matthias Wessendorf:
Hi Burghard,
this page works fine for me
http://facesgoodies.googlecode.com/svn/trunk/src/main/webapp/all.xhtml
MyFaces 1.2.0, Trinidad 1.2.1 and Facelets
I also use a List, that contains but enties.
-Matthias
On 7/21/07, Burghard Britzke [EMAIL PROTECTED] wrote:
BTW the page does not reload in response of a click. should it?
Am 21.07.2007 um 11:10 schrieb Burghard Britzke:
I use the tr:document
the managed bean returns a java.util.List. In the docs there are
notes about
a CollectionModel and an underlying table model. what is it? is
it my
managed bean?
my page looks like this:
?xml version=1.0 encoding=UTF-8 ?
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:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]
/jsp:text
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{rulesetMB.list}
rows=3
tr:column sortProperty=id sortable=true
align=right
f:facet name=headerh:outputText
value=ID//f:facet
tr:outputText value=#{row.id}/
tr:outputText
/tr:column
tr:column sortProperty=name sortable=true
f:facet name=headerh:outputText
value=Name//f:facet
tr:outputText value=#{row.name}/
tr:outputText
/tr:column
tr:column
f:facet name=headerh:outputText
value=aktiviert//f:facet
tr:selectOneRadio value=#{row.active}
layout=horizontal
tr:selectItem value=true label=Ja/
tr:selectItem value=false label=Nein/
/tr:selectOneRadio
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
/jsp:root
Am 21.07.2007 um 03:31 schrieb Adam Winer:
Do you have a trh:body or tr:document on the page?
These are (at least for 1.0.1) required for PPR to function.
-- Adam
On 7/20/07, Burghard Britzke [EMAIL PROTECTED] wrote:
I am new to trinidad and tried to play a little bit with the
tr:table.I
enabled table paging with the attribut rows=15 for the tr:table
I enabled table sorting with the sortProperty=name
sortable=true for the
tr:column
the controls are shown as expected. but do nothing on click.
I read the FAQ at http://wiki.apache.org/myfaces/FAQ . But
yes I defined the ResourceServlet for the ADF resource mapping in
web.xml.
I read the documentation
at http://myfaces.apache.org/trinidad/devguide/table.html .
But it is not clear to me if I have to code an own underlying
table model
which supports sorting. And (if I have to) how to underly it.
has anybody done it?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad] sorting table, table range navigation...
may be this comes out of invalid xhtml
I let w3c.org check the xhtml output and it found two errors that
lets me suspect this. there are multible required attribute type
not specified for the script tags. and there is one 'value of
attribute method cannot be POST; must be one of get, post'
for the form tag. May be I trapped into an error? should I log it
into the jira?
Am 25.07.2007 um 12:17 schrieb Burghard Britzke:
did you test if this page works fine for you if you surround your
tr:document in template.xhtml with a f:view contentType=text/
xml element?
for me it does not!
if I force xhtml output for my pages the trinidad table paging and
sorting controls does not work properly.
can anybody repeat this observation?
Am 21.07.2007 um 12:28 schrieb Matthias Wessendorf:
Hi Burghard,
this page works fine for me
http://facesgoodies.googlecode.com/svn/trunk/src/main/webapp/
all.xhtml
MyFaces 1.2.0, Trinidad 1.2.1 and Facelets
I also use a List, that contains but enties.
-Matthias
On 7/21/07, Burghard Britzke [EMAIL PROTECTED] wrote:
BTW the page does not reload in response of a click. should it?
Am 21.07.2007 um 11:10 schrieb Burghard Britzke:
I use the tr:document
the managed bean returns a java.util.List. In the docs there are
notes about
a CollectionModel and an underlying table model. what is it? is
it my
managed bean?
my page looks like this:
?xml version=1.0 encoding=UTF-8 ?
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:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]
/jsp:text
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{rulesetMB.list}
rows=3
tr:column sortProperty=id sortable=true
align=right
f:facet name=headerh:outputText
value=ID//f:facet
tr:outputText value=#{row.id}/
tr:outputText
/tr:column
tr:column sortProperty=name sortable=true
f:facet name=headerh:outputText
value=Name//f:facet
tr:outputText value=#{row.name}/
tr:outputText
/tr:column
tr:column
f:facet name=headerh:outputText
value=aktiviert//f:facet
tr:selectOneRadio value=#{row.active}
layout=horizontal
tr:selectItem value=true label=Ja/
tr:selectItem value=false label=Nein/
/tr:selectOneRadio
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
/jsp:root
Am 21.07.2007 um 03:31 schrieb Adam Winer:
Do you have a trh:body or tr:document on the page?
These are (at least for 1.0.1) required for PPR to function.
-- Adam
On 7/20/07, Burghard Britzke [EMAIL PROTECTED] wrote:
I am new to trinidad and tried to play a little bit with the
tr:table.I
enabled table paging with the attribut rows=15 for the tr:table
I enabled table sorting with the sortProperty=name
sortable=true for the
tr:column
the controls are shown as expected. but do nothing on click.
I read the FAQ at http://wiki.apache.org/myfaces/FAQ . But
yes I defined the ResourceServlet for the ADF resource mapping in
web.xml.
I read the documentation
at http://myfaces.apache.org/trinidad/devguide/table.html .
But it is not clear to me if I have to code an own underlying
table model
which supports sorting. And (if I have to) how to underly it.
has anybody done it?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad] sorting table, table range navigation...
This behaviour is found with firefox 2.0.0.5 on Mac OS X
Am 25.07.2007 um 13:07 schrieb Burghard Britzke:
may be this comes out of invalid xhtml
I let w3c.org check the xhtml output and it found two errors that
lets me suspect this. there are multible required attribute type
not specified for the script tags. and there is one 'value of
attribute method cannot be POST; must be one of get, post'
for the form tag. May be I trapped into an error? should I log it
into the jira?
Am 25.07.2007 um 12:17 schrieb Burghard Britzke:
did you test if this page works fine for you if you surround your
tr:document in template.xhtml with a f:view contentType=text/
xml element?
for me it does not!
if I force xhtml output for my pages the trinidad table paging and
sorting controls does not work properly.
can anybody repeat this observation?
Am 21.07.2007 um 12:28 schrieb Matthias Wessendorf:
Hi Burghard,
this page works fine for me
http://facesgoodies.googlecode.com/svn/trunk/src/main/webapp/
all.xhtml
MyFaces 1.2.0, Trinidad 1.2.1 and Facelets
I also use a List, that contains but enties.
-Matthias
On 7/21/07, Burghard Britzke [EMAIL PROTECTED] wrote:
BTW the page does not reload in response of a click. should it?
Am 21.07.2007 um 11:10 schrieb Burghard Britzke:
I use the tr:document
the managed bean returns a java.util.List. In the docs there are
notes about
a CollectionModel and an underlying table model. what is it?
is it my
managed bean?
my page looks like this:
?xml version=1.0 encoding=UTF-8 ?
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:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]
/jsp:text
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{rulesetMB.list}
rows=3
tr:column sortProperty=id sortable=true
align=right
f:facet name=headerh:outputText
value=ID//f:facet
tr:outputText value=#{row.id}/
tr:outputText
/tr:column
tr:column sortProperty=name sortable=true
f:facet name=headerh:outputText
value=Name//f:facet
tr:outputText value=#{row.name}/
tr:outputText
/tr:column
tr:column
f:facet name=headerh:outputText
value=aktiviert//f:facet
tr:selectOneRadio value=#{row.active}
layout=horizontal
tr:selectItem value=true label=Ja/
tr:selectItem value=false
label=Nein/
/tr:selectOneRadio
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
/jsp:root
Am 21.07.2007 um 03:31 schrieb Adam Winer:
Do you have a trh:body or tr:document on the page?
These are (at least for 1.0.1) required for PPR to function.
-- Adam
On 7/20/07, Burghard Britzke [EMAIL PROTECTED] wrote:
I am new to trinidad and tried to play a little bit with the
tr:table.I
enabled table paging with the attribut rows=15 for the tr:table
I enabled table sorting with the sortProperty=name
sortable=true for the
tr:column
the controls are shown as expected. but do nothing on click.
I read the FAQ at http://wiki.apache.org/myfaces/FAQ . But
yes I defined the ResourceServlet for the ADF resource mapping
in web.xml.
I read the documentation
at http://myfaces.apache.org/trinidad/devguide/table.html .
But it is not clear to me if I have to code an own underlying
table model
which supports sorting. And (if I have to) how to underly it.
has anybody done it?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
yes, I missed it.
another thing is, that the rendered xhtml is not w3c conform. this
may be the reason why I noticed a missfunction of the paging and
sorting controls of the tr:table (see [Trinidad] sorting table,
table range navigation...)
if I let it render html 4.01 the table controls behave as expected
if I let it render xhtml the table controls shows no reaction on a click
the w3c-html validator found the following errors:
required attribute type not specified for the script tags
and
value of attribute method cannot be POST; must be one of get,
post' for the form tag
Am 26.07.2007 um 01:05 schrieb Adam Winer:
In Facelets, use contentType on f:view.
In JSP, use the contentType directive.
-- Adam
On 7/25/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
https://facelets.dev.java.net/source/browse/facelets/src/java/com/
sun/facelets/tag/jsf/core/ViewHandler.java?rev=1.4view=markup
public ViewHandler(TagConfig config) {
super(config);
...
this.encoding = this.getAttribute(encoding);
...
}
...
if (this.contentType != null) {
String v = this.contentType.getValue(ctx);
ctx.getFacesContext().getExternalContext().getRequestMap().put
(facelets.ContentType,
v);
}
On 7/25/07, Burghard Britzke [EMAIL PROTECTED] wrote:
but it is true:
f:view
xmlns:f=http://java.sun.com/jsf/core;
xmlns:tr=http://myfaces.apache.org/trinidad;
tr:document
/tr:document
/f:view
renders as
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN ...
and
f:view contentType=text/xml
xmlns:f=http://java.sun.com/jsf/core;
xmlns:tr=http://myfaces.apache.org/trinidad;
tr:document
/tr:document
/f:view
renders as
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN ...
Am 25.07.2007 um 10:00 schrieb Burghard Britzke:
f.view does not have an attribute contentType. for the RI.
does it have
such an attribute in MyFaces?
Am 23.07.2007 um 23:23 schrieb noah:
I can confirm that it does.
f:view contentType=text/html seems to be a necessity if you
want
Dojo to work.
On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote:
In Facelets, setting contentType on f:view should do
the trick, but I don't know for sure.
...
On 7/23/07, Burghard Britzke [EMAIL PROTECTED]
wrote:
hi,
sometimes the tr:document decides to render xhtml and
sometimes
html4.01. how to control it?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
[Trinidad] when it decides to render xhtml and when to render html 4.01?
hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
and for facelets? is it possible to set the content type, too? for facelets .xhtml files it rendered html 4.01. Am 23.07.2007 um 19:58 schrieb Adam Winer: Funny, I should have remembered: https://issues.apache.org/jira/browse/TRINIDAD-78 ... since I fixed it myself... Looks like it's this simple: set the contentType of your JSP page to be XHTML, get XHTML output. And, if you fail to set a content type, then by default you get HTML for .jsp pages, XHTML for .jspx documents. -- Adam On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: As best I know, we never render XHTML, so I'm surprised to hear otherwise. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: facelets vs. jsp
didn't they? it seems that all of the packages at jsf-facelets.jar are com.sun... packages. nevertheless I changed to facelets because there are most reasons for and only very few against facelets. I got my trinidad training-app running now (with facelets) and (thanks to matthias for the jsf-facesgoodies) with skin support. I noticed an error in safari beta version 3.0.2 (522.12) which I sent to apple. this error does not appear in the current production release of the safari browser. Am 22.07.2007 um 00:51 schrieb Zied Hamdi: Why didn't Sun adopt Facelets as it adopted Derby??? ... Regards, Zied
Re: facelets vs. jsp
you can mix facelets an jsp pages in one project. Am 22.07.2007 um 20:16 schrieb Zied Hamdi: Thanks guys, Now It's maybe too late to change my project to facelets (unless there's a facelets transformer I didn't hear about : jsf - facelets). I'll surely try that for my next project. Regards, Zied 2007/7/22, Matthias Wessendorf [EMAIL PROTECTED]: On 7/22/07, Burghard Britzke [EMAIL PROTECTED] wrote: didn't they? it seems that all of the packages at jsf-facelets.jar are com.sun... packages. facelets is an independent os project. the package name, that might be confusing - yes-, is com.sun. the reason for that is (a guess) that jacob is working on the RI. and hey, a package name is just a name :-) license is CDDL -M nevertheless I changed to facelets because there are most reasons for and only very few against facelets. I got my trinidad training-app running now (with facelets) and (thanks to matthias for the jsf-facesgoodies) with skin support. I noticed an error in safari beta version 3.0.2 (522.12) which I sent to apple. this error does not appear in the current production release of the safari browser. Am 22.07.2007 um 00:51 schrieb Zied Hamdi: Why didn't Sun adopt Facelets as it adopted Derby??? ... Regards, Zied -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org -- Zied Hamdi zatreex.sourceforge.net
Re: [Trinidad] sorting table, table range navigation...
I use the tr:document
the managed bean returns a java.util.List. In the docs there are
notes about a CollectionModel and an underlying table model. what
is it? is it my managed bean?
my page looks like this:
?xml version=1.0 encoding=UTF-8 ?
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:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]
/jsp:text
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{rulesetMB.list} rows=3
tr:column sortProperty=id sortable=true
align=right
f:facet name=headerh:outputText value=ID/
/f:facet
tr:outputText value=#{row.id}/tr:outputText
/tr:column
tr:column sortProperty=name sortable=true
f:facet name=headerh:outputText
value=Name//f:facet
tr:outputText value=#{row.name}/
tr:outputText
/tr:column
tr:column
f:facet name=headerh:outputText
value=aktiviert//f:facet
tr:selectOneRadio value=#{row.active}
layout=horizontal
tr:selectItem value=true label=Ja/
tr:selectItem value=false label=Nein/
/tr:selectOneRadio
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
/jsp:root
Am 21.07.2007 um 03:31 schrieb Adam Winer:
Do you have a trh:body or tr:document on the page?
These are (at least for 1.0.1) required for PPR to function.
-- Adam
On 7/20/07, Burghard Britzke [EMAIL PROTECTED] wrote:
I am new to trinidad and tried to play a little bit with the
tr:table.I
enabled table paging with the attribut rows=15 for the tr:table
I enabled table sorting with the sortProperty=name
sortable=true for the
tr:column
the controls are shown as expected. but do nothing on click.
I read the FAQ at http://wiki.apache.org/myfaces/FAQ . But
yes I defined the ResourceServlet for the ADF resource mapping in
web.xml.
I read the documentation
at http://myfaces.apache.org/trinidad/devguide/table.html .
But it is not clear to me if I have to code an own underlying
table model
which supports sorting. And (if I have to) how to underly it.
has anybody done it?
Re: [Trinidad] sorting table, table range navigation...
BTW the page does not reload in response of a click. should it?
Am 21.07.2007 um 11:10 schrieb Burghard Britzke:
I use the tr:document
the managed bean returns a java.util.List. In the docs there are
notes about a CollectionModel and an underlying table model. what
is it? is it my managed bean?
my page looks like this:
?xml version=1.0 encoding=UTF-8 ?
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:text![CDATA[?xml version=1.0 encoding=UTF-8 ?]]
/jsp:text
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{rulesetMB.list} rows=3
tr:column sortProperty=id sortable=true
align=right
f:facet name=headerh:outputText
value=ID//f:facet
tr:outputText value=#{row.id}/tr:outputText
/tr:column
tr:column sortProperty=name sortable=true
f:facet name=headerh:outputText
value=Name//f:facet
tr:outputText value=#{row.name}/
tr:outputText
/tr:column
tr:column
f:facet name=headerh:outputText
value=aktiviert//f:facet
tr:selectOneRadio value=#{row.active}
layout=horizontal
tr:selectItem value=true label=Ja/
tr:selectItem value=false label=Nein/
/tr:selectOneRadio
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
/jsp:root
Am 21.07.2007 um 03:31 schrieb Adam Winer:
Do you have a trh:body or tr:document on the page?
These are (at least for 1.0.1) required for PPR to function.
-- Adam
On 7/20/07, Burghard Britzke [EMAIL PROTECTED] wrote:
I am new to trinidad and tried to play a little bit with the
tr:table.I
enabled table paging with the attribut rows=15 for the tr:table
I enabled table sorting with the sortProperty=name
sortable=true for the
tr:column
the controls are shown as expected. but do nothing on click.
I read the FAQ at http://wiki.apache.org/myfaces/FAQ . But
yes I defined the ResourceServlet for the ADF resource mapping in
web.xml.
I read the documentation
at http://myfaces.apache.org/trinidad/devguide/table.html .
But it is not clear to me if I have to code an own underlying
table model
which supports sorting. And (if I have to) how to underly it.
has anybody done it?
[Trinidad] sorting table, table range navigation...
I am new to trinidad and tried to play a little bit with the tr:table. I enabled table paging with the attribut rows=15 for the tr:table I enabled table sorting with the sortProperty=name sortable=true for the tr:column the controls are shown as expected. but do nothing on click. I read the FAQ at http://wiki.apache.org/myfaces/FAQ . But yes I defined the ResourceServlet for the ADF resource mapping in web.xml. I read the documentation at http://myfaces.apache.org/trinidad/ devguide/table.html . But it is not clear to me if I have to code an own underlying table model which supports sorting. And (if I have to) how to underly it. has anybody done it?
[Trinidad] Could not find renderer for CoreDocument
Hi,
I tried to get a small trinidad enabled jsf running. I deployed it to
jboss. but it results in an empty page, giving some warnings at the
jboss console:
16:47:55,189 ERROR [STDERR] 15.07.2007 16:47:55
org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl
WARNUNG: Could not find renderer for CoreDocument[UIXFacesBeanImpl,
id=j_id_jsp_100897001_1] rendererType =
org.apache.myfaces.trinidad.Document
16:47:55,192 ERROR [STDERR] 15.07.2007 16:47:55
org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl
WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl,
id=j_id_jsp_100897001_2] rendererType = org.apache.myfaces.trinidad.Form
16:47:55,203 ERROR [STDERR] 15.07.2007 16:47:55
org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl
WARNUNG: Could not find renderer for CoreTable[UIXFacesBeanImpl,
id=j_id_jsp_100897001_3] rendererType =
org.apache.myfaces.trinidad.Table
the source of the jsf looks like
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;
...
f:view
tr:document title=Rulesets
tr:form
tr:table var=row value=#{rulesetsController.list}
tr:column
f:facet name=headerh:outputText
value=Name//f:facet
tr:inputText value=#{row.name}/tr:inputText
/tr:column
tr:column
f:facet name=headerh:outputText
value=aktiviert//f:facet
h:selectOneRadio value=#{row.active}
f:selectItem itemValue=Y itemLabel=Ja/
f:selectItem itemValue=N itemLabel=Nein/
/h:selectOneRadio
/tr:column
/tr:table
/tr:form
/tr:document
/f:view
what is going wrong?
do I need the trinidad-config.xml or is it optional?
is there a documentation online which advances ahead of those found
at: http://myfaces.apache.org/trinidad/devguide/index.html
Re: [Trinidad] Could not find renderer for CoreDocument
thank you! that was the fault. is there a documentation available how
to set up a trinidad jsf application? and how to work with skins?
Am 15.07.2007 um 17:19 schrieb Simon Lessard:
Hmmm,
About trinidad-config.xml, I would not consider it optional since
you'll most likely need to use a skin other than simple in a real
application. About your error, I think you might be missing the
following in your faces-config.xml:
application
default-render-kit-idorg.apache.myfaces.trinidad.core/default-
render-kit-id
/application
Regards,
~ Simon
On 7/15/07, Burghard Britzke [EMAIL PROTECTED] wrote:
Hi,
I tried to get a small trinidad enabled jsf running. I deployed it
to jboss. but it results in an empty page, giving some warnings at
the jboss console:
16:47:55,189 ERROR [STDERR] 15.07.2007 16:47:55
org.apache.myfaces.trinidad.component.UIXComponentBase
_getRendererImpl
WARNUNG: Could not find renderer for CoreDocument[UIXFacesBeanImpl,
id=j_id_jsp_100897001_1] rendererType =
org.apache.myfaces.trinidad.Document
16:47:55,192 ERROR [STDERR] 15.07.2007 16:47:55
org.apache.myfaces.trinidad.component.UIXComponentBase
_getRendererImpl
WARNUNG: Could not find renderer for CoreForm[UIXFacesBeanImpl,
id=j_id_jsp_100897001_2] rendererType =
org.apache.myfaces.trinidad.Form
16:47:55,203 ERROR [STDERR] 15.07.2007 16:47:55
org.apache.myfaces.trinidad.component.UIXComponentBase
_getRendererImpl
WARNUNG: Could not find renderer for CoreTable[UIXFacesBeanImpl,
id=j_id_jsp_100897001_3] rendererType =
org.apache.myfaces.trinidad.Table
the source of the jsf looks like
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;
...
f:view
tr:document title= Rulesets
tr:form
tr:table var= row value=#
{ rulesetsController.list}
tr:column
f:facet name= header h:outputText
value= Name // f:facet
tr:inputText value=#{ row.name} /
tr:inputText
/ tr:column
tr:column
f:facet name= header h:outputText
value= aktiviert // f:facet
h:selectOneRadio value=#{ row.active}
f:selectItem itemValue = Y itemLabel =
Ja /
f:selectItem itemValue = N itemLabel =
Nein /
/ h:selectOneRadio
/ tr:column
/ tr:table
/ tr:form
/ tr:document
/ f:view
what is going wrong?
do I need the trinidad-config.xml or is it optional?
is there a documentation online which advances ahead of those found
at: http://myfaces.apache.org/trinidad/devguide/index.html
