[
http://issues.apache.org/jira/browse/TOMAHAWK-503?page=comments#action_12431082
]
Kevin Galligan commented on TOMAHAWK-503:
-
I've been playing around with this for a little bit and have some thoughts.
The first thought is this is gre
[
http://issues.apache.org/jira/browse/MYFACES-730?page=comments#action_12431079
]
Steve Peterson commented on MYFACES-730:
We're still on 1.1.1; I'll try it out on 1.1.3 when I get an opportunity.
> 1.1.1RC3 jar interferes with Tomcat
[
http://issues.apache.org/jira/browse/TOBAGO-89?page=comments#action_12431057 ]
Bernd Bohmann commented on TOBAGO-89:
-
May be the required retrotranslator plugin is not released before the next
tobago release.
Therefore the retrotranslated
[ http://issues.apache.org/jira/browse/TOBAGO-118?page=all ]
Bernd Bohmann resolved TOBAGO-118.
--
Resolution: Fixed
> Increase the version of the facelets dependency to 1.1.11
> -
>
>
Thanks for the Information!
I also like the Idea of having a single "Enhancing PPRPanelGroup" issue.
But I'll put not all of the suggestions in there to
be sure I'll be able to finish them within reasonable time ( weeks ).
And also because, there are some points for which I don't have any Ideas
h
On 8/26/06, Ernst Fastl <[EMAIL PROTECTED]> wrote:
If I understood the recent discussions correctly we should
create JIRA Issues seperately for every change we want to make
rather than Issues like "Enhancing component x".
No, that's not really what's being said.
Every change should be associate
Hi again,
after updating and looking through the code again, I found out that
Mario already fixed the most important issues. Thanks for that.
Still open are:
1. Update the JSF sequence when doing partial updates
2. Support Client-Side State-Saving
3. Don't render the JS-Code for registering th
[ http://issues.apache.org/jira/browse/TOMAHAWK-640?page=all ]
Ernst Fastl updated TOMAHAWK-640:
-
Status: Patch Available (was: Open)
> Javascript-Code broken when using 2 or more PPRPanelGroups
>
Javascript-Code broken when using 2 or more PPRPanelGroups
--
Key: TOMAHAWK-640
URL: http://issues.apache.org/jira/browse/TOMAHAWK-640
Project: MyFaces Tomahawk
Issue Type: Bug
[ http://issues.apache.org/jira/browse/TOMAHAWK-639?page=all ]
Peter Mahoney updated TOMAHAWK-639:
---
Status: Patch Available (was: Open)
> Improve overlap detection for zero length events in the detailed view
> -
Improve overlap detection for zero length events in the detailed view
-
Key: TOMAHAWK-639
URL: http://issues.apache.org/jira/browse/TOMAHAWK-639
Project: MyFaces Tomahawk
Is
Increase the version of the facelets dependency to 1.1.11
-
Key: TOBAGO-118
URL: http://issues.apache.org/jira/browse/TOBAGO-118
Project: MyFaces Tobago
Issue Type: Improvement
Matthias Wessendorf schrieb:
Thomas fixed something inside MyFAces/Tomahawk.
Not Trinidad. If that was you question
Tomahawk only was affected to my knowledge and some sandbox components!
(the dojo based ones)
Tomahawk Schedule style class attributes are ignored under facelets. (Ex:
dayClass, entryClass, etc)
Key: TOMAHAWK-638
URL: http://issues.apache.org/jira/browse/T
forceId on tomahawk components causes waring when running under facelets
Key: TOMAHAWK-637
URL: http://issues.apache.org/jira/browse/TOMAHAWK-637
Project: MyFaces Tomahawk
This mail is sent from time to time and is meant to remind you, that
the users@myfaces.apache.org and dev@myfaces.apache.org mailing lists
- like most of the ASF lists - are "subscribers only". This means that
you are only allowed to post to this list if you have subscribed
before.
Please make sur
ViewTag makes wrong class cast when using locale attribute
--
Key: MYFACES-1394
URL: http://issues.apache.org/jira/browse/MYFACES-1394
Project: MyFaces Core
Issue Type: Bug
Co
17 matches
Mail list logo
