Re: Regarding Trinidad 2.0
We are trying to make it backwards compatible. If you can devote some
time to running your application on Trinidad 2 and if there are any
issues, please let us know.
-Andrew
On Tue, Feb 23, 2010 at 9:09 PM, venkat.rama...@thomsonreuters.com wrote:
Thanks. Currently we use trinidad 1.2. Is trinidad 2 backward portable with
1.2? Can we retain those pages and components as such while developing newer
ones with 2.0?
Thanks again
- Original Message -
From: mwessend...@gmail.com mwessend...@gmail.com
To: MyFaces Discussion users@myfaces.apache.org
Sent: Wed Feb 24 08:56:34 2010
Subject: Re: Regarding Trinidad 2.0
I'd not say production ready, but we use it.
currently the ajax jsf2.0 is not in there.
(therefore we labeled it as alpha...)
On Tue, Feb 23, 2010 at 6:36 PM, venkat.rama...@thomsonreuters.com wrote:
Hi
Is Trinidad 2 production quality ? Is the alpha release of Trinidad
compatible with JSF 2.0 ?
Thanks
Venkat
-Original Message-
From: mwessend...@gmail.com [mailto:mwessend...@gmail.com] On Behalf Of
Matthias Wessendorf
Sent: Tuesday, February 23, 2010 2:55 PM
To: MyFaces Discussion
Subject: Re: AW: Stuck making JSF 2.0 work with MyFaces
use Trinidad2 :-)
On Tue, Feb 23, 2010 at 7:25 AM, cristiJ cristi_ju...@yahoo.com wrote:
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so far.
I hope you willl have time to upgrade Tomahawk soon
Jakob Korherr wrote:
Maybe tomahawk is causing the problems, because there is currently no real
working branch of tomahawk for JSF 2.0. However there will be one soon.
Please remove tomahawk completely from your webapp and try again!
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
yes, I just tried it. For both of theses URLs :
http://localhost:8080/app02/faces/index.xhtml
http://localhost:8080/app02
the file does not get translated to XHTML, it arrives in the browser with
the f and h customs.
This happens only when I add MyFaces.
I tried adding my self a custom component, defined by this class :
import javax.faces.component.FacesComponent;
import javax.faces.component.html.HtmlInputText;
@FacesComponent(value = HtmlInputFile)
public class HtmlInputFile extends HtmlInputText {
�...@override
public String getRendererType() {
return javax.faces.File;
}
}
with this balusc.taglib.xml config file
?xml version=1.0 encoding=UTF-8?
facelet-taglib
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd;
version=2.0
namespacehttp://balusc.net/jsf/html/namespace
tag
tag-nameinputFile/tag-name
component
component-typeHtmlInputFile/component-type
/component
/tag
/facelet-taglib
and with the web.xml as such:
context-param
param-namejavax.faces.FACELETS_LIBRARIES/param-name
param-value/WEB-INF/balusc.taglib.xml/param-value
/context-param
The page is:
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:hh=http://balusc.net/jsf/html;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br /
pic : hh:inputFileUpload id=file value=#{user.file}/br
/
h:commandButton action=#{user.createUser} value=Create
user/
/h:form
/body
/html
and the xhtml is translated properly. I can't understand what is the
conflict for MyFaces!?
Jakob Korherr wrote:
Hi,
Does your URL in your browser include /faces/index.xhtml?
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
Yes, you understood correctly, neither of h: or f: components are not
processed.
I have a very simple index.xhtml file :
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:t=http://myfaces.apache.org/tomahawk;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br
Regarding Trinidad 2.0
Hi
Is Trinidad 2 production quality ? Is the alpha release of Trinidad compatible
with JSF 2.0 ?
Thanks
Venkat
-Original Message-
From: mwessend...@gmail.com [mailto:mwessend...@gmail.com] On Behalf Of
Matthias Wessendorf
Sent: Tuesday, February 23, 2010 2:55 PM
To: MyFaces Discussion
Subject: Re: AW: Stuck making JSF 2.0 work with MyFaces
use Trinidad2 :-)
On Tue, Feb 23, 2010 at 7:25 AM, cristiJ cristi_ju...@yahoo.com wrote:
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so far.
I hope you willl have time to upgrade Tomahawk soon
Jakob Korherr wrote:
Maybe tomahawk is causing the problems, because there is currently no real
working branch of tomahawk for JSF 2.0. However there will be one soon.
Please remove tomahawk completely from your webapp and try again!
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
yes, I just tried it. For both of theses URLs :
http://localhost:8080/app02/faces/index.xhtml
http://localhost:8080/app02
the file does not get translated to XHTML, it arrives in the browser with
the f and h customs.
This happens only when I add MyFaces.
I tried adding my self a custom component, defined by this class :
import javax.faces.component.FacesComponent;
import javax.faces.component.html.HtmlInputText;
@FacesComponent(value = HtmlInputFile)
public class HtmlInputFile extends HtmlInputText {
�...@override
public String getRendererType() {
return javax.faces.File;
}
}
with this balusc.taglib.xml config file
?xml version=1.0 encoding=UTF-8?
facelet-taglib
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd;
version=2.0
namespacehttp://balusc.net/jsf/html/namespace
tag
tag-nameinputFile/tag-name
component
component-typeHtmlInputFile/component-type
/component
/tag
/facelet-taglib
and with the web.xml as such:
context-param
param-namejavax.faces.FACELETS_LIBRARIES/param-name
param-value/WEB-INF/balusc.taglib.xml/param-value
/context-param
The page is:
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:hh=http://balusc.net/jsf/html;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br /
pic : hh:inputFileUpload id=file value=#{user.file}/br
/
h:commandButton action=#{user.createUser} value=Create
user/
/h:form
/body
/html
and the xhtml is translated properly. I can't understand what is the
conflict for MyFaces!?
Jakob Korherr wrote:
Hi,
Does your URL in your browser include /faces/index.xhtml?
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
Yes, you understood correctly, neither of h: or f: components are not
processed.
I have a very simple index.xhtml file :
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:t=http://myfaces.apache.org/tomahawk;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br /
pic : t:inputFileUpload id=file storage=file
accept=image/* styleClass=myStyle value=#{user.file}/br /
h:commandButton action=#{user.createUser} value=Create
user/
/h:form
/body
/html
The web.xml file for it is:
?xml version=1.0 encoding=UTF-8?
web-app version=3.0 xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;
context-param
param-namejavax.faces.PROJECT_STAGE/param-name
param-valueDevelopment/param-value!-- Debugging
information
is
printed --
/context-param
servlet
servlet-nameFaces Servlet/servlet-name
servlet-classjavax.faces.webapp.FacesServlet/servlet-class
Re: Regarding Trinidad 2.0
I'd not say production ready, but we use it.
currently the ajax jsf2.0 is not in there.
(therefore we labeled it as alpha...)
On Tue, Feb 23, 2010 at 6:36 PM, venkat.rama...@thomsonreuters.com wrote:
Hi
Is Trinidad 2 production quality ? Is the alpha release of Trinidad
compatible with JSF 2.0 ?
Thanks
Venkat
-Original Message-
From: mwessend...@gmail.com [mailto:mwessend...@gmail.com] On Behalf Of
Matthias Wessendorf
Sent: Tuesday, February 23, 2010 2:55 PM
To: MyFaces Discussion
Subject: Re: AW: Stuck making JSF 2.0 work with MyFaces
use Trinidad2 :-)
On Tue, Feb 23, 2010 at 7:25 AM, cristiJ cristi_ju...@yahoo.com wrote:
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so far.
I hope you willl have time to upgrade Tomahawk soon
Jakob Korherr wrote:
Maybe tomahawk is causing the problems, because there is currently no real
working branch of tomahawk for JSF 2.0. However there will be one soon.
Please remove tomahawk completely from your webapp and try again!
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
yes, I just tried it. For both of theses URLs :
http://localhost:8080/app02/faces/index.xhtml
http://localhost:8080/app02
the file does not get translated to XHTML, it arrives in the browser with
the f and h customs.
This happens only when I add MyFaces.
I tried adding my self a custom component, defined by this class :
import javax.faces.component.FacesComponent;
import javax.faces.component.html.HtmlInputText;
@FacesComponent(value = HtmlInputFile)
public class HtmlInputFile extends HtmlInputText {
�...@override
public String getRendererType() {
return javax.faces.File;
}
}
with this balusc.taglib.xml config file
?xml version=1.0 encoding=UTF-8?
facelet-taglib
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd;
version=2.0
namespacehttp://balusc.net/jsf/html/namespace
tag
tag-nameinputFile/tag-name
component
component-typeHtmlInputFile/component-type
/component
/tag
/facelet-taglib
and with the web.xml as such:
context-param
param-namejavax.faces.FACELETS_LIBRARIES/param-name
param-value/WEB-INF/balusc.taglib.xml/param-value
/context-param
The page is:
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:hh=http://balusc.net/jsf/html;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br /
pic : hh:inputFileUpload id=file value=#{user.file}/br
/
h:commandButton action=#{user.createUser} value=Create
user/
/h:form
/body
/html
and the xhtml is translated properly. I can't understand what is the
conflict for MyFaces!?
Jakob Korherr wrote:
Hi,
Does your URL in your browser include /faces/index.xhtml?
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
Yes, you understood correctly, neither of h: or f: components are not
processed.
I have a very simple index.xhtml file :
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:t=http://myfaces.apache.org/tomahawk;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br /
pic : t:inputFileUpload id=file storage=file
accept=image/* styleClass=myStyle value=#{user.file}/br /
h:commandButton action=#{user.createUser} value=Create
user/
/h:form
/body
/html
The web.xml file for it is:
?xml version=1.0 encoding=UTF-8?
web-app version=3.0 xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;
context-param
param-namejavax.faces.PROJECT_STAGE/param-name
param-valueDevelopment/param-value!--
Re: Regarding Trinidad 2.0
Thanks. Currently we use trinidad 1.2. Is trinidad 2 backward portable with
1.2? Can we retain those pages and components as such while developing newer
ones with 2.0?
Thanks again
- Original Message -
From: mwessend...@gmail.com mwessend...@gmail.com
To: MyFaces Discussion users@myfaces.apache.org
Sent: Wed Feb 24 08:56:34 2010
Subject: Re: Regarding Trinidad 2.0
I'd not say production ready, but we use it.
currently the ajax jsf2.0 is not in there.
(therefore we labeled it as alpha...)
On Tue, Feb 23, 2010 at 6:36 PM, venkat.rama...@thomsonreuters.com wrote:
Hi
Is Trinidad 2 production quality ? Is the alpha release of Trinidad
compatible with JSF 2.0 ?
Thanks
Venkat
-Original Message-
From: mwessend...@gmail.com [mailto:mwessend...@gmail.com] On Behalf Of
Matthias Wessendorf
Sent: Tuesday, February 23, 2010 2:55 PM
To: MyFaces Discussion
Subject: Re: AW: Stuck making JSF 2.0 work with MyFaces
use Trinidad2 :-)
On Tue, Feb 23, 2010 at 7:25 AM, cristiJ cristi_ju...@yahoo.com wrote:
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so far.
I hope you willl have time to upgrade Tomahawk soon
Jakob Korherr wrote:
Maybe tomahawk is causing the problems, because there is currently no real
working branch of tomahawk for JSF 2.0. However there will be one soon.
Please remove tomahawk completely from your webapp and try again!
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
yes, I just tried it. For both of theses URLs :
http://localhost:8080/app02/faces/index.xhtml
http://localhost:8080/app02
the file does not get translated to XHTML, it arrives in the browser with
the f and h customs.
This happens only when I add MyFaces.
I tried adding my self a custom component, defined by this class :
import javax.faces.component.FacesComponent;
import javax.faces.component.html.HtmlInputText;
@FacesComponent(value = HtmlInputFile)
public class HtmlInputFile extends HtmlInputText {
�...@override
public String getRendererType() {
return javax.faces.File;
}
}
with this balusc.taglib.xml config file
?xml version=1.0 encoding=UTF-8?
facelet-taglib
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd;
version=2.0
namespacehttp://balusc.net/jsf/html/namespace
tag
tag-nameinputFile/tag-name
component
component-typeHtmlInputFile/component-type
/component
/tag
/facelet-taglib
and with the web.xml as such:
context-param
param-namejavax.faces.FACELETS_LIBRARIES/param-name
param-value/WEB-INF/balusc.taglib.xml/param-value
/context-param
The page is:
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:hh=http://balusc.net/jsf/html;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br /
pic : hh:inputFileUpload id=file value=#{user.file}/br
/
h:commandButton action=#{user.createUser} value=Create
user/
/h:form
/body
/html
and the xhtml is translated properly. I can't understand what is the
conflict for MyFaces!?
Jakob Korherr wrote:
Hi,
Does your URL in your browser include /faces/index.xhtml?
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
Yes, you understood correctly, neither of h: or f: components are not
processed.
I have a very simple index.xhtml file :
?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;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:t=http://myfaces.apache.org/tomahawk;
body
h:form enctype=multipart/form-data id=myForm
firstName : h:inputText value=#{user.firstName} /br /
lastName : h:inputText value=#{user.lastName} /br /
city : h:inputText value=#{user.city} /br /
price : h:inputText value=#{user.price} /br /
pic : t:inputFileUpload id=file storage=file
accept=image/* styleClass=myStyle value=#{user.file}/br /
h:commandButton action=#{user.createUser} value=Create
user/
/h:form
/body
/html
The web.xml file
