[
https://issues.apache.org/jira/browse/TOMAHAWK-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598564#action_12598564
]
Leonardo Uribe commented on TOMAHAWK-1253:
--
I have disabled some changes on
I found a related issue (in wicket). Looks like a JDK bug.
Let me search my archive, so that we can have a fix for 1.x9...
Sent from my iPod.
Am 21.05.2008 um 02:40 schrieb Scott O'Bryan [EMAIL PROTECTED]:
Edward, go ahead and contribute a patch to either of those bugs.
Any idea on an
[
https://issues.apache.org/jira/browse/TRINIDAD-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598581#action_12598581
]
Simon Kitching commented on TRINIDAD-73:
Apache Commons Digester also struct this
The current Trinidad demo will not work in a non-J2EE container, i.e.
Tomcat 6.0, because it does not contain the JSTL jar. Should we add a
non-J2EE demo to the distribution?
I would say yes because it simplifies the process of getting the demo
running in an not-J2EE environment.
Paul
Hi Ed,
https://issues.apache.org/jira/browse/TRINIDAD-73
there are some infos for creating a patch / fix for this.
Greetings,
Matthias
On Tue, May 20, 2008 at 10:51 PM, Edward Dowgiallo
[EMAIL PROTECTED] wrote:
I don't have a vote, but could the Too many open files problem
documented in JIRA
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598696#action_12598696
]
Joe Rossi commented on TRINIDAD-875:
This appears to be down to the version of
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598705#action_12598705
]
Scott O'Bryan commented on TRINIDAD-875:
Can others watching this thread verify
IMO this isn't necessary. We already control whether we deploy the
myfaces jars using a profile. Can't we add a profile which includes the
JSTL jars in the demo when it's built? Also, it should be easy enough
to add them to tomcat as a shared library as well.
Scott
Paul Spencer wrote:
The
Hey everyone, the long awaited myfaces-commons-configurator package is
ready to be checked in. Because I'm seeing a lot of people doing things
that might be aided by this framework, I was hoping I could check it
into the commons project and get people to help me test it and fix it
up. Do
Looks like I messed up. I changed this as I wanted to remove the
deprecation warnings produced from using ValueBinding in JSF 1.2 based
code.
Sorry about this.
I have limited internet connectivity this week, so if someone can
cover this faster than me, please do so.
-Andrew
On Tue, May 20,
Well I sort of assumed that people wanting configurations outside of the
standard supported J2EE configuration would compile the branch themselves.
Scott
Paul Spencer wrote:
Scott,
If the Demo includes JSTL, will it work on a J2EE server?
( I suspect the server will/should complain when 2
[
https://issues.apache.org/jira/browse/TRINIDAD-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-1074.
--
Resolution: Fixed
Fix Version/s: 1.2.9-core
1.0.9-core
it
Is this a regression? If not, I do not think that the release should
be held up for an existing problem and we should go ahead with the
release and plan to put the fix in 1.x.9.
On Tue, May 20, 2008 at 5:33 PM, Edward Dowgiallo [EMAIL PROTECTED] wrote:
-1
Trinidad-73/Trinidad-978 is a
Scott,
Well I sort of assumed that people wanting configurations outside of the
standard supported J2EE configuration would compile the branch themselves.
And this is document where :)
http://myfaces.apache.org/trinidad/trinidad-1_2/FAQ.html
It's not a regression.
Andrew Robinson wrote:
Is this a regression? If not, I do not think that the release should
be held up for an existing problem and we should go ahead with the
release and plan to put the fix in 1.x.9.
On Tue, May 20, 2008 at 5:33 PM, Edward Dowgiallo [EMAIL PROTECTED]
Well documentation is easy. I'm just not excited about having to
maintain two trees or wasting a lot of spacing building multiple
versions of a demo application when all someone has to do is look at the
pre-req's and make sure it's available in their environment.
Scott
Paul Spencer wrote:
It looks like the vote is going to pass. We've got our 3 +1 votes and 1
.5. I'll be sure to log the -1 vote and the reason.
Ed, when you get this fixed, ping me. I'd be open to doing another
early release to try to get this in before your deadline. Cool?
Scott O'Bryan wrote:
It's not a
Cool.
On Wed, May 21, 2008 at 3:55 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
It looks like the vote is going to pass. We've got our 3 +1 votes and 1
.5. I'll be sure to log the -1 vote and the reason.
Ed, when you get this fixed, ping me. I'd be open to doing another early
release to
This vote passed with the following spread:
+1 (x3): Paul Spencer, Scott O'Bryan, Matthias Wessendorf
+ .5 (x1): Andrew Robinson
- 1 (x1): Edward Dowgiallo
The negative one vote was for issues TRINIDAD-73 and TRINIDAD-978. We
may be looking at another release soon to address these issues but
[
https://issues.apache.org/jira/browse/TRINIDAD-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated TRINIDAD-1088:
---
Status: Patch Available (was: Open)
duplicate component id's possible with
duplicate component id's possible with client side state saving
---
Key: TRINIDAD-1088
URL: https://issues.apache.org/jira/browse/TRINIDAD-1088
Project: MyFaces Trinidad
Issue
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598789#action_12598789
]
Mehmet Akif Olcay commented on TRINIDAD-875:
Now it is ok with
Mozilla/5.0
hello,
for the patches of TRINIDAD-1088 i used the source code of the myfaces state
manager to detect duplicate component id's.
i don't like to have duplicate source code!
what's your opinion about moving all shared source code like this to a
'commons' module like the already existing
-1 Myfaces commons utils is not the place for this. MyFaces core should not
have to depend on the commons project to run. Plus the myfaces commons
utils is a snapshot and not going to release any time soon. Making Trinidad
dependent on this package would mean we can't release util the commons
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598836#action_12598836
]
Scott O'Bryan commented on TRINIDAD-875:
Ok, then let me see if we even have our
i see your point.
there are some pros and cons!
concerning the example you mentioned:
only because we already have such a situation within the code base it isn't
a legitimation to continue with this approach. (we need at least a
discussion.)
in the end we might have several parts which are
We can relatively easily create a tomcat profile that could be used to
deploy onto tomcat by changing the dependency scope from to provided
to compile right?
Just as we have the jetty profile and the jetty plugin registered, we
can do the same for tomcat I think.
The drawback of course is
Andrew,
Yeah, that's what I proposed. Paul wants us to distribute the
non-j2ee version with our examples...
Scott
Andrew Robinson wrote:
We can relatively easily create a tomcat profile that could be used to
deploy onto tomcat by changing the dependency scope from to provided
to compile
Scott and Andrew,
The goal is to make it easy for a user to get the demo up and running
with minimal frustration. Since I am not currently working in a J2EE
environment, my desire to quickly get the demo running in order to test
the 1.2.8 release did not include a J2EE server. I dropped the
Right. I'm for #3... And lets face it. The EASIEST way to run the
demo is to download the tag and in the demo directory type mvn jetty:run..
Hey Paul, do you want to contribute the documentation via the website or
wiki?
Scott
Paul Spencer wrote:
Scott and Andrew,
The goal is to make it
Hey Paul, can you do me a favor and JIRA up this improvement? It'll
allow us to track the patches for this enhancement.
For what it's worth, I *DO* think what you're trying to do has merit,
I'm just not a big fan of making binary distributions for every possible
container, especially when
not working attributes actionListener on the datatable ?? help me please
Key: TOMAHAWK-1258
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1258
Project: MyFaces
[
https://issues.apache.org/jira/browse/TOMAHAWK-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
HasunJoung updated TOMAHAWK-616:
Status: Patch Available (was: Open)
Datatable AutoSort and Facelets Bug
33 matches
Mail list logo
