[
https://issues.apache.org/jira/browse/TRINIDAD-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803211#action_12803211
]
Matthias Weßendorf commented on TRINIDAD-1690:
--
hrm, committing this to bot
On Wed, Jan 20, 2010 at 8:34 PM, Ali Ok wrote:
> Hi all,
> I sent a couple of mails about "MyFaces on Google App Engine" GSOC proposal.
> But after some progress and a conversation with Matthias, I realized that it
> is too small for GSOC.
>
> And I am willing to implement HTML5 Renderkit.
sounds
[
https://issues.apache.org/jira/browse/TRINIDAD-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-1572:
-
Resolution: Fixed
Fix Version/s: 1.0.12-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803203#action_12803203
]
Marius Petoi commented on TRINIDAD-1689:
I added a new patch with a small correc
Hi all,
I have a few patches that need to be reviewed before I can commit it.
All but one patches are related to mobile development:
TRINIDAD-1619 - This patch applies to both desktop as well as mobile.
The issue is a column's width is not rendered when all the columns of a
table have empty
remove newlines in css file if in compressed mode
-
Key: TRINIDAD-1692
URL: https://issues.apache.org/jira/browse/TRINIDAD-1692
Project: MyFaces Trinidad
Issue Type: Improvement
Compo
Thanks Blake, that works for me.
On Wed, Jan 20, 2010 at 5:41 PM, Blake Sullivan
wrote:
> Matt,
>
> I don't think that an explicit versioning scheme should be necessary. In
> your example, we have the base skin A, a version with big enough changes
> that the designer feels that it should have a
Hi folks!
I'm not sure if the following is a desired behaviour, so please comment.
I'm using the latest MyFaces-2.0.0-SNAPSHOT together with facelets-1.1.15b1,
jetty-6.1.22 and RichFaces-3.3.3-Beta1.
When I invoke a page, let's say localhost:8080/page.jsf the first time I call
it all is ok. I
Matt,
I don't think that an explicit versioning scheme should be necessary.
In your example, we have the base skin A, a version with big enough
changes that the designer feels that it should have an new name, B, that
extends A and an application extension of A, C. The issue is that the
user
+1
2010/1/20 Ali Ok
> Hi all,
> I sent a couple of mails about "MyFaces on Google App Engine" GSOC
> proposal. But after some progress and a conversation with Matthias, I
> realized that it is too small for GSOC.
>
> And I am willing to implement HTML5 Renderkit.
>
> Meanwhile, I will work on GA
[
https://issues.apache.org/jira/browse/TRINIDAD-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803068#action_12803068
]
Matt Cooper commented on TRINIDAD-1691:
---
See a thread on this topic here:
http://m
[
https://issues.apache.org/jira/browse/TRINIDAD-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803065#action_12803065
]
Jeanne Waldman commented on TRINIDAD-1691:
--
Why isn't putting the version into
ResponseWriter clone should not include itself
--
Key: MYFACES-2500
URL: https://issues.apache.org/jira/browse/MYFACES-2500
Project: MyFaces Core
Issue Type: Bug
Components: General
A
Just wanted to mention that I have logged this issue here:
https://issues.apache.org/jira/browse/MYFACES-2500
Issue 2500. Pretty cool! :-)
Andy
If the application developer is injecting a skin addition into skin "A" and
if skin "B" (aka version 2) extends from skin "B" then this is not an issue.
However, if the application developer has created their own skin that
extends skin "A" then the end user cannot choose skin "B" (aka version 2)
b
Do they? I always get confused by which is which between skin
additions and skin extensions. Anyway, why wouldn't skin A' that
extends Skin A pick up all of the extensions and additions to A? Or, is
the case you are worried about that the customer has their own skin B
that extends skin A bu
Hi Blake,
Aside from the opt-in setting for end users choosing which skin to display,
application developers would also be impacted. Application developers would
need to extend all skins instead of just extending 1 skin whose version
number could be arbitrarily changed by the end user.
Thanks,
M
[
https://issues.apache.org/jira/browse/TRINIDAD-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Sullivan updated TRINIDAD-1668:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Implement JIRA-1668
[
https://issues.apache.org/jira/browse/TRINIDAD-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Sullivan updated TRINIDAD-1668:
-
Status: Patch Available (was: Open)
> Speed up UIXComponent.getId()
> ---
f:validateBean disabled="true" not processed correctly
--
Key: MYFACES-2499
URL: https://issues.apache.org/jira/browse/MYFACES-2499
Project: MyFaces Core
Issue Type: Bug
Component
Matt,
Why wouldn't it be sufficient for the new skin the extend the old? What
problems does this add other than forcing customers to modify their
trinidad-config to use the new skin name in order to opt in?
-- Blake Sullivan
Matt Cooper (JIRA) said the following On 1/20/2010 2:09 PM PT:
Sk
[
https://issues.apache.org/jira/browse/MYFACES-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr resolved MYFACES-2410.
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
Fixed this issue. However, there ar
[
https://issues.apache.org/jira/browse/TRINIDAD-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803018#action_12803018
]
Yee-Wah Lee commented on TRINIDAD-1550:
---
Agreed that in the case when type="time",
Skinning framework support for skin versioning
--
Key: TRINIDAD-1691
URL: https://issues.apache.org/jira/browse/TRINIDAD-1691
Project: MyFaces Trinidad
Issue Type: New Feature
Components:
The vote has passed with the following results:
+1
matzew (binding)
weber (binding)
lofwyr (binding)
bommel (binding)
I will proceed with the next steps.
Regards
Bernd
On Mon, Jan 18, 2010 at 11:30 AM, Udo Schnurpfeil wrote:
> +1
>
> Bernd Bohmann schrieb:
>>
>> Here is my
>>
>> +1
>>
>> On S
[
https://issues.apache.org/jira/browse/MYFACES-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Concini resolved MYFACES-2498.
--
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
> Myfaces should be able to gra
Myfaces should be able to gracefully handle a runtime with the bean validation
API on the classpath but no impl
---
Key: MYFACES-2498
URL: https://issues.a
Hi all,
I sent a couple of mails about "MyFaces on Google App Engine" GSOC proposal.
But after some progress and a conversation with Matthias, I realized that it
is too small for GSOC.
And I am willing to implement HTML5 Renderkit.
Meanwhile, I will work on GAE support in parallel. I will post my
ResourceLoader has protected method protected String
getContentType(URLConnection conn) that is never called
--
Key: TRINIDAD-1690
URL: https://issues.ap
[
https://issues.apache.org/jira/browse/MYFACES-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802791#action_12802791
]
Matthias Weßendorf commented on MYFACES-2497:
-
MyFAces implements the exact a
[
https://issues.apache.org/jira/browse/MYFACES-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802782#action_12802782
]
Ingo Hofmann commented on MYFACES-2497:
---
Fix:
Add in myfaces-api - javax.faces.com
when i use apache-ode-jbi component invoke a external webservice in
servicemix,error is unknown endpoint
-
Key: MYFACESTEST-2
URL: https://issues.apache.org/j
INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL on required fields
--
Key: MYFACES-2497
URL: https://issues.apache.org/jira/browse/MYFACES-2497
Project: MyFaces Core
Issue Type:
[
https://issues.apache.org/jira/browse/MYFACES-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802739#action_12802739
]
Michael Kurz commented on MYFACES-2431:
---
The problem is fixed with current version
34 matches
Mail list logo
