[jira] Updated: (TRINIDAD-1466) Support xinclude'd property metadata

[ https://issues.apache.org/jira/browse/TRINIDAD-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1466: - Resolution: Fixed Fix Version/s: 1.2.10-plugins Status:

[jira] Commented: (TRINIDAD-1467) missing _en stub resources in trinidad-api and trinidad-impl.jar

[ https://issues.apache.org/jira/browse/TRINIDAD-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705967#action_12705967 ] Matthias Weßendorf commented on TRINIDAD-1467: -- fix is easy. We just need

[jira] Created: (TRINIDAD-1467) missing _en stub resources in trinidad-api and trinidad-impl.jar

missing _en stub resources in trinidad-api and trinidad-impl.jar Key: TRINIDAD-1467 URL: https://issues.apache.org/jira/browse/TRINIDAD-1467 Project: MyFaces Trinidad Issue

[jira] Resolved: (TRINIDAD-1467) missing _en stub resources in trinidad-api and trinidad-impl.jar

[ https://issues.apache.org/jira/browse/TRINIDAD-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-1467. -- Resolution: Fixed Fix Version/s: 1.2.12-core missing _en stub

Re: h:head and h:body in JSF 2.0

Looks ok to me, the parsing is not omitted but instead the option to render the head and body without parsing is added. Either way, I have the parser in place now and will commit it tomorrow. So we have the harder part in place and working and it is fast enoguh. 80.000 characters are handled

[MyFaces 2.0] UIViewParameter

Hi, looking at: -https://issues.apache.org/jira/browse/MYFACES-2206 -https://issues.apache.org/jira/browse/MYFACES-2221 I have the impression that the the f:viewParam/ and f:metadata/ are almost there, right ? Exception is (only?) the ViewMetadataImpl.createMetadataView() ? -- Matthias

[jira] Commented: (ORCHESTRA-40) A transaction token component inspired by the struts transaction processor

[ https://issues.apache.org/jira/browse/ORCHESTRA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12706086#action_12706086 ] Manfred Geiler commented on ORCHESTRA-40: - The LOG.error should be replaced by a

Fwd: FYI: javax.inject* standard ...

FYI -- Forwarded message -- From: Matthias Wessendorf mat...@apache.org Date: Tue, May 5, 2009 at 7:34 PM Subject: FYI: javax.inject* standard ... To: openwebbeans-...@incubator.apache.org Cc: Pete Muir pm...@redhat.com FYI:

Re: FYI: javax.inject* standard ...

the big failure of the JSR 299 is that it just lives in JavaEE land. Best would have been to introduce a flexible DI API in SE land. This could be extended in all the different profiles. So, 299 could have just been a *consumer* of that flexible DI in order to extend it and add the things that

Re: FYI: javax.inject* standard ...

That's true, but I think most JSR-299 impl can run outside JEE environment already. Many specs started in EE and ended in SE 1 or 2 version of the SDK later. On Tue, May 5, 2009 at 1:57 PM, Matthias Wessendorf mat...@apache.orgwrote: the big failure of the JSR 299 is that it just lives in

[jira] Created: (PORTLETBRIDGE-71) Add META-INF/services javax.faces.application.ApplicationFactory file

Add META-INF/services javax.faces.application.ApplicationFactory file - Key: PORTLETBRIDGE-71 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-71 Project: MyFaces Portlet

Re: [jira] Commented: (TRINIDAD-1464) max upload size cannot be reconfigured after app is deployed

Hi Blake, the idea is to change the upload-config during runtime. Not sure how moving it to trinidad-config helps to change it via an Java API. -Matthias On Fri, May 1, 2009 at 7:18 PM, Blake Sullivan blake.sulli...@oracle.com wrote: Matthias, Would things be improved if we moved the