I did start with the implementation of tomahawk using the faces plugin
(not the old generator that Mario may be refering). The efforts are
done in a tomahawk branch, but due to lack of time I haven't got the
time to continue (I hope to do so :)). Configuring the
maven-faces-plugin to do something,
On 22/10/2007, Mike Kienenberger [EMAIL PROTECTED] wrote:
There are already tomahawk-facelets.jar files out there if you want
to use something with drop-in support. See the wiki page for a link
to Bruno's http://code.google.com/p/tomahawk-facelets project.
Yes, I decided to make available
Hi,
Thomas Spiegl added a demo of Orchestra+JPA(Hibernate)+Tomahawk (see [1]).
I updated my Trinidad FacesGoodies to use Orchestra and JPA
(OpenJPA) (see [2]).
-Matthias
PS: You need to build Orchestra first on your own...
[1] http://facesgoodies.googlecode.com/svn/orchestra/trunk/
[2]
hi,
I am not aware that the shale vc has something like a configuration. Doesn't it
just use the viewId mapping?
Well, I can live with an extra configuration, but then, we should have a look
how the shale dialog scxml fits in here - just that any eventual adaption of
shale dialog in the
I think Simon was talking about the dialog config, where a flow is configured.
The entry of the flow is responsible to start conversation, etc
On 10/23/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
hi,
I am not aware that the shale vc has something like a configuration. Doesn't
it just use
Hi,
a year ago i was playing with OLD generator to make it work again for
Tomahawk's core components - see
https://issues.apache.org/jira/browse/TOMAHAWK-819
- attachment tomahawk(no roleSelectionMode).patch
I withdrove the issue mainly because it become invalid in a matter of
weeks AND in
Evaluation of EL-Expression fails with custom PropertyResolver
--
Key: MYFACES-1750
URL: https://issues.apache.org/jira/browse/MYFACES-1750
Project: MyFaces Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/TRINIDAD-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535940
]
mstarets edited comment on TRINIDAD-771 at 10/23/07 7:14 AM:
For now, we should
Wow, I missed that one! I suppose the rest of the EG has been keeping me in
the dark..
I sent them an e-mail...
~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and
As Scott has pointed out, JSR-301 had to make some difficult choices
here because of the lack of flexibility in JSF 1.2. We wanted where
ever possible to have the JSF artifact running in a portlet environment
to run in a NamingContainer that took the portlet namespace id into
account
[
https://issues.apache.org/jira/browse/TRINIDAD-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Robinson resolved TRINIDAD-777.
-
Resolution: Fixed
Fix Version/s: 1.0.4-core
Assignee: Danny Robinson
[
https://issues.apache.org/jira/browse/TRINIDAD-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-757.
-
Resolution: Fixed
changed documentation, demo, and RequestContextImpl.java
Completed:
A Wizard-Tag to create dynamic wizard pages with low effort
---
Key: TOBAGO-518
URL: https://issues.apache.org/jira/browse/TOBAGO-518
Project: MyFaces Tobago
Issue Type: New Feature
Hi!
Please consider adding the following handler for the AliasBean to your
project:
(This is my first Tag-Handler, so I am not sure if there is a more
elegant way - at least the AliasBean works here now)
import com.sun.facelets.FaceletContext;
import com.sun.facelets.FaceletException;
import
Hey Mario,
The reason that there is no alias bean handler is because it's not
needed with facelets.
Instead you'd use a Facelets composition and ui:include statement.
On 10/23/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Please consider adding the following handler for the AliasBean to
Hi!
The reason that there is no alias bean handler is because it's not
needed with facelets.
Still, the tag is not working as it should, so providing a tag handler
will fix this.
Instead you'd use a Facelets composition and ui:include statement.
That is not true for my use-case. As you
Wow. No, I somehow missed the relevence of aliasBean on the facelets
mailing list.
For what it's worth, you're the first person in the history of
facelets to need it, at least as far as I've read on mailing lists.
Would it maybe be better to create a rendertime-compatible version of
ui:include
I can do it on Thursday.
Matthias, if you are able to spend some time earlier, then: please, thanks.
-Manfred
On 10/23/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Yeah, let Manfred do it.
If he is to busy, I'll do it...
-M
On 10/22/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
So who
Hi!
For what it's worth, you're the first person in the history of
facelets to need it, at least as far as I've read on mailing lists.
Yep, sometimes I have some strange ideas :-)
Would it maybe be better to create a rendertime-compatible version of
ui:include tag?
That is what I have
Hey Mario,
Thanks for keeping me honest :-)
You've been correcting a number of my misconceptions recently :-)
I went back and reread your facelets thread, and it does appear to be
a good dynamic ui:include. Why not use ui:param instead of f:param?
ui:param is already defined for facelets.
On
That is, of course, unless you want to implement your own ViewRoot
according to the JSR-301 spec which is certainly a possibility.
Scott
Michael Freedman wrote:
As Scott has pointed out, JSR-301 had to make some difficult choices
here because of the lack of flexibility in JSF 1.2. We wanted
Hi!
I went back and reread your facelets thread, and it does appear to be
a good dynamic ui:include. Why not use ui:param instead of f:param?
ui:param is already defined for facelets.
Thanks for the tip. I am not that familiar with facelets yet, at all
just 3 days :-(, I'll look into this
Dennis Byrne schrieb:
Caucho claims to have implemented and released JSF 2.0 [1] before the
spec was finished!
huh, I thought they dont even have a fully working jee5 spec ;-)
I assume they mean jsf 1.2
Cheers
Werner
[
https://issues.apache.org/jira/browse/TRINIDAD-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-666:
---
Status: Patch Available (was: Open)
Make ExternalContextUtils part of the public API
[
https://issues.apache.org/jira/browse/TRINIDAD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537174
]
Scott O'Bryan commented on TRINIDAD-134:
This is a 1.2 only patch. Can we get this into 1.2.3 before it
25 matches
Mail list logo
