Re: [Trinidad][Skinning] Introduce include-Property in CSS

For example the definition of the following style sheet: //. These are styles defined only for quirks mode. But in CSS this feature is not implemented... Marius On Fri, Feb 19, 2010 at 12:13 AM, Jeanne Waldman wrote: > What do you mean by 'mode' dependent? > > Marius Petoi wrote, On

[jira] Updated: (TRINIDAD-1732) Code Cleanup: Move to using generics in the trinidad-maven project

[ https://issues.apache.org/jira/browse/TRINIDAD-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Kaval updated TRINIDAD-1732: -- Status: Patch Available (was: Open) > Code Cleanup: Move to using generics in the trinidad

[jira] Created: (TRINIDAD-1732) Code Cleanup: Move to using generics in the trinidad-maven project

Code Cleanup: Move to using generics in the trinidad-maven project --- Key: TRINIDAD-1732 URL: https://issues.apache.org/jira/browse/TRINIDAD-1732 Project: MyFaces Trinidad Iss

[jira] Updated: (TRINIDAD-1731) Improve Formatting of Tag Doc Summary section

[ https://issues.apache.org/jira/browse/TRINIDAD-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Kaval updated TRINIDAD-1731: -- Status: Patch Available (was: Open) > Improve Formatting of Tag Doc Summary section > -

[jira] Commented: (TOMAHAWK-1472) Add Support for new Resource API in tomahawk 2.0 module

[ https://issues.apache.org/jira/browse/TOMAHAWK-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835438#action_12835438 ] Leonardo Uribe commented on TOMAHAWK-1472: -- Trying to do this issue I found the

Re: [Trinidad][Skinning] Introduce include-Property in CSS

What do you mean by 'mode' dependent? Marius Petoi wrote, On 2/3/2010 11:17 PM PT: Ok Jeanne. Thank you! One more question, in order to transform the XSS files in CSS files, in base-desktop.xss there are some styles which are mode-dependent. Should we add @mode in the CSS? Or do you have an

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835430#action_12835430 ] Jakob Korherr commented on MYFACES-2561: To solve the problem with the MethodExpr

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835428#action_12835428 ] Leonardo Uribe commented on MYFACES-2561: - Thinking more about it maybe we need a

Re: Result (was: [VOTE] release for myfaces core 2.0.0-beta-2)

yeah! :) On Thu, Feb 18, 2010 at 9:27 PM, Leonardo Uribe wrote: > Hi > > Thanks to all people who vote. > > We have 7 +1 > > Bernd Bohmann > Gerhard Petracek > Matthias Wessendorf > Grant Smith > Werner Punz > Jakob Korherr > Leonardo Uribe > > so we can continue with the necessary steps to relea

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835391#action_12835391 ] Jakob Korherr commented on MYFACES-2561: OK I finally solved the MethodExpression

Result (was: [VOTE] release for myfaces core 2.0.0-beta-2)

Hi Thanks to all people who vote. We have 7 +1 Bernd Bohmann Gerhard Petracek Matthias Wessendorf Grant Smith Werner Punz Jakob Korherr Leonardo Uribe so we can continue with the necessary steps to release myfaces core 2.0.0-beta-2 regards, Leonardo Uribe

[jira] Commented: (TRINIDAD-1415) allow :alias support to merge in -tr- custom skin properties as well

[ https://issues.apache.org/jira/browse/TRINIDAD-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835366#action_12835366 ] Jeanne Waldman commented on TRINIDAD-1415: -- I reformatted your patch because th

[jira] Created: (MYFACES-2565) BeanValidator throws Exception if external ExpressionLanguageFactory is being used

BeanValidator throws Exception if external ExpressionLanguageFactory is being used -- Key: MYFACES-2565 URL: https://issues.apache.org/jira/browse/MYFACES-2565 Project: M

Re: BeanValidator throws Exception if external ExpressionLanguage implementation is used,

Thanks Jakob! Since this sounds like there is something more to do (and not only being me who is to dumb/lazy to properly read documentation or code), I'll better open an Jiraffe on this topic. txs and LieGrue, strub --- Jakob Korherr schrieb am Do, 18.2.2010: > Von: Jakob Korherr > Betreff

Re: BeanValidator throws Exception if external ExpressionLanguage implementation is used

Hi Mark, I myself did not write this code, but I think it was written because it was/is not known if all things will work with Java EE6's EL. So I guess it's a kind of a reminder. Furthermore I don't think that there are any web.xml parameters to change this behavior. Can you or someone else con

BeanValidator throws Exception if external ExpressionLanguage implementation is used

Hi! Currently the BeanValidator has the following code: if (_ExternalSpecifications.isUnifiedELAvailable()) { //TODO: Implement when Unified EL for Java EE6 is available. throw new FacesException("Unified EL for Java EE6 support is not yet implemented"); } I'm using EL-2.2 in MyFaces-2.0.

Re: MYFACES-2564

On Thu, Feb 18, 2010 at 6:05 PM, Jakob Korherr wrote: > I just reopend the issue, because it has nothing to do with the facelets > taglibs version problem as Michael said. :-) I just saw "...If the answer to this question is "no", Facelets in JSF 2" and closed it :-) > > However the changes

Re: MYFACES-2564

Jakob, I"m not sure I understand what about the fix you think is incorrect. I could use a little more specific explanation. In particular, why would you have to or want to use facelets 1.1.x in this case? The spec says nothing other than that facelets in JSF 2.0 is backwards compatible and

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835299#action_12835299 ] Jakob Korherr commented on MYFACES-2561: Good point, I haven't thought of that. O

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835296#action_12835296 ] Leonardo Uribe commented on MYFACES-2561: - The problem is do something like this

Re: MYFACES-2564

I just reopend the issue, because it has nothing to do with the facelets taglibs version problem as Michael said. However the changes are incorrect. Please see my comment in jira and please revert the changes. Regards, Jakob 2010/2/18 Michael Concini > I'm aware of the previous discussion, how

[jira] Reopened: (MYFACES-2564) facelets in an app with a 1.2 level faces-config do not work

[ https://issues.apache.org/jira/browse/MYFACES-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr reopened MYFACES-2564: > facelets in an app with a 1.2 level faces-config do not work >

[jira] Commented: (MYFACES-2564) facelets in an app with a 1.2 level faces-config do not work

[ https://issues.apache.org/jira/browse/MYFACES-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835289#action_12835289 ] Jakob Korherr commented on MYFACES-2564: Please revert the changes, because on an

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835286#action_12835286 ] Jakob Korherr commented on MYFACES-2561: I don't see the problem with #{component

Re: MYFACES-2564

I'm aware of the previous discussion, however my understanding was that it related more to supporting the using the legacy facelets library and doesn't appear to have anything to do with faces-config versioning. My fix in MYFACES-2564 just brings us into consistent behavior with how verseion i

[jira] Created: (TOBAGO-852) Popup is not modal enough

Popup is not modal enough - Key: TOBAGO-852 URL: https://issues.apache.org/jira/browse/TOBAGO-852 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.0.24 Environment:

MYFACES-2564

Hey Michael, I closed your MYFACES-2564 ticket, as we discussed this already. There is another open ticket for the problem -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835261#action_12835261 ] Leonardo Uribe commented on MYFACES-2561: - The reason why it is better to change

[jira] Commented: (MYFACES-2458) Miscellaneous AJAX bugs

[ https://issues.apache.org/jira/browse/MYFACES-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835259#action_12835259 ] Curtiss Howard commented on MYFACES-2458: - Fixed: * If calling jsf.ajax.request(

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835257#action_12835257 ] Leonardo Uribe commented on MYFACES-2561: - I look ri code to find if they change

[jira] Created: (MYFACES-2564) facelets in an app with a 1.2 level faces-config do not work

facelets in an app with a 1.2 level faces-config do not work Key: MYFACES-2564 URL: https://issues.apache.org/jira/browse/MYFACES-2564 Project: MyFaces Core Issue Type: Bug

[jira] Created: (EXTSCRIPT-67) concurrency bug

concurrency bug --- Key: EXTSCRIPT-67 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-67 Project: MyFaces Extensions Scripting Issue Type: Bug Reporter: Werner Punz Assignee: Werner Punz P

[jira] Resolved: (EXTSCRIPT-62) Dependency detection - interfaces not entirely correctly detected

[ https://issues.apache.org/jira/browse/EXTSCRIPT-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-62. -- Resolution: Fixed > Dependency detection - interfaces not entirely correctly detected > -

[jira] Created: (EXTSCRIPT-66) Concurrency problem - startup servlet filter

Concurrency problem - startup servlet filter Key: EXTSCRIPT-66 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-66 Project: MyFaces Extensions Scripting Issue Type: Bug Reporter: W

[jira] Resolved: (EXTSCRIPT-64) NPE in JSR199Compiler in certain situations

[ https://issues.apache.org/jira/browse/EXTSCRIPT-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-64. -- Resolution: Fixed > NPE in JSR199Compiler in certain situations > ---

[jira] Resolved: (EXTSCRIPT-61) Fix parent pom relations before tagging alpha

[ https://issues.apache.org/jira/browse/EXTSCRIPT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-61. -- Resolution: Fixed > Fix parent pom relations before tagging alpha > -

[jira] Resolved: (EXTSCRIPT-65) add optional compile whitelist

[ https://issues.apache.org/jira/browse/EXTSCRIPT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-65. -- Resolution: Fixed > add optional compile whitelist > -- > >

[jira] Resolved: (TOBAGO-844) Change type of the markup attribute from String[] to new class Markup

[ https://issues.apache.org/jira/browse/TOBAGO-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-844. Resolution: Fixed Fix Version/s: 1.5.0 1.5.0-alpha-2 > Change typ

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[ https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835159#action_12835159 ] Jakob Korherr commented on MYFACES-2561: Thanks for all your ideas, Leonardo, but

Re: [ExtVal] Cross Validations and duplicate messages

hi rudy, you mentioned it correctly. it's a specific functionality of AbstractCompareStrategy. as alternative it's possible to provide a custom FacesMessageStorage which filters messages before they get added (directly in FacesMessageStorage#addFacesMessage). that would allow a better performance

[jira] Commented: (MYFACES-2563) Trinidad 1.2.x generates on POSTBACK a NullPointerException on MyFAces2

[ https://issues.apache.org/jira/browse/MYFACES-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835148#action_12835148 ] Matthias Weßendorf commented on MYFACES-2563: - as we are on JSP, the getViewM

Re: [core] Backwards compatibility (e.g. MYFACES-2543)

Yes.- this is a BUG it needs to support more than just 2.0 (Dan/Ed commented on the "open" list) -Matthias On Thu, Feb 11, 2010 at 2:35 PM, Matthias Wessendorf wrote: > nope, but the web.xml setting for Trinidad's alternate view handler; > > it is complaining about the facelets embedded face

[jira] Created: (MYFACES-2563) Trinidad 1.2.x generates on POSTBACK a NullPointerException on MyFAces2

Trinidad 1.2.x generates on POSTBACK a NullPointerException on MyFAces2 --- Key: MYFACES-2563 URL: https://issues.apache.org/jira/browse/MYFACES-2563 Project: MyFaces Core I

[jira] Resolved: (MYFACES-2562) javax.el.PropertyNotFoundException: The class 'javax.faces.component.UIViewRoot' does not have the property 'example'.

[ https://issues.apache.org/jira/browse/MYFACES-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved MYFACES-2562. - Resolution: Invalid ok... I close it for now... but I am not sure (yes, the spe

[jira] Commented: (MYFACES-2562) javax.el.PropertyNotFoundException: The class 'javax.faces.component.UIViewRoot' does not have the property 'example'.

[ https://issues.apache.org/jira/browse/MYFACES-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835144#action_12835144 ] Matthias Weßendorf commented on MYFACES-2562: - problem is this part of the js

[jira] Created: (MYFACES-2562) javax.el.PropertyNotFoundException: The class 'javax.faces.component.UIViewRoot' does not have the property 'example'.

javax.el.PropertyNotFoundException: The class 'javax.faces.component.UIViewRoot' does not have the property 'example'. -- Key: MYFACES-2562 URL: ht