Hello Stan,
welcome back. We do understand that you can not make any promise on that topic.
The fact that some folks at JBoss are thinking about shipping MyFaces
(as an alternative option)
is a good news for this entire community here. Especially it is a
great motivation for the
folks that did
Hi,
Great news! It would be very nice if JBoss ships with MyFaces 2. This also
opens up possibilities to do some enhancements to increase developer
productivity in JBoss, like better resource reloading and so on. Or doing
some things more efficient by plugging into the JBoss infrastructure. Just
At Apache we can not have code that contains (L)GPL code; or depends on it.
We had discussion(s) about this in the past. The below link contains references
to other (Apache) documents:
http://markmail.org/message/qtc4g6vsracgzbok
-Matthias
On Thu, Aug 5, 2010 at 9:55 AM, Jan-Kees van Andel
Hi guys,
sure we would want to have this!
@Leonardo: can you take care of this high priority (next to your
optimization and performance improvement work)?
best regards,
Martin
On 8/4/10, ssilv...@redhat.com ssilv...@redhat.com wrote:
Hi guys,
Would you like to see MyFaces Core ship with
[
https://issues.apache.org/jira/browse/MYFACES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895632#action_12895632
]
Martin Kočí commented on MYFACES-2855:
--
Hi, with today's build a javascript error
Hi do we have a bug here, I have not really dug into the root of the
problem but I assume we have a hole in what the mockups provide.
I am working on the oamsubmit issue, and also because it is connected I
am working on double include prevention code for the ppr case.
But now I have run into
[
https://issues.apache.org/jira/browse/MYFACES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895635#action_12895635
]
Werner Punz commented on MYFACES-2855:
--
uups sorry about that...
it is fixed...
[
https://issues.apache.org/jira/browse/MYFACES-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Punz updated MYFACES-2859:
-
Status: Resolved (was: Patch Available)
Fix Version/s: 2.0.2-SNAPSHOT
have you done an svn up on the test project?
Last week it caused also a build failure.
-M
On Thu, Aug 5, 2010 at 12:09 PM, Werner Punz werner.p...@gmail.com wrote:
Hi do we have a bug here, I have not really dug into the root of the problem
but I assume we have a hole in what the mockups
Nada, I just use whatever is defined by the maven poms in the core project.
The failure occurred due to my code, but the code from me is correct
the test fails illegally here because it cannot get the
PartialViewContextFactory, which should be present by JSF2 definition.
My code just triggered
Hi guys,
I am saying this in a broader scope - not only for the AJAX features.
But our AJAX features which do make sense out of the box (and this one
does) could also be enabled like this.
best regards,
Martin
On 8/2/10, Werner Punz werner.p...@gmail.com wrote:
Hi Martin this would make only
Btw. Martin, I already gave Ed all the needed info and code on how to
implement it so that they can get everything into the spec for 2.1
(which hopefully will happen)
I think the entire issue of not being able to support a fileupload in
the non ajax and ajax case in stock jsf has been going
That's OK. I guess I can do the SPI implementations on my end but it
might not make it into JBoss AS6 GA. Let's concentrate on the MyFaces
SPI's for now. How does MyFaces handle the SPI's like Mojarra has?
I'm sure it's OK to look at Mojarra code since it's GPL2, right? If
not, you can
Well, looking at the RI is for sure not OK.
I didn't see a problem with the previous provided links (the JBoss
code), however
I have not opened any of the provided links yet.
-Matthias
On Thu, Aug 5, 2010 at 1:54 PM, ssilv...@redhat.com wrote:
That's OK. I guess I can do the SPI
Somehow I think there was already work/discussion about it, based on a
Tomcat interface.
It for sure does bring back some fragile memory. Let me think...
On Thu, Aug 5, 2010 at 2:09 PM, Matthias Wessendorf mat...@apache.org wrote:
Well, looking at the RI is for sure not OK.
I didn't see a
Can you look at javadoc comments?
Quoting Matthias Wessendorf mat...@apache.org:
Well, looking at the RI is for sure not OK.
I didn't see a problem with the previous provided links (the JBoss
code), however
I have not opened any of the provided links yet.
-Matthias
On Thu, Aug 5, 2010 at
Hi
2010/8/4 ssilv...@redhat.com
Hi guys,
Would you like to see MyFaces Core ship with JBoss AS6? If so, read on.
This is top priority for me.
If you've been around MyFaces awhile, you probably remember that JBoass AS
used to ship with MyFaces instead of Mojarra. It was regrettable,
Provide AnnotationScanner interface
---
Key: MYFACES-2860
URL: https://issues.apache.org/jira/browse/MYFACES-2860
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-314
Affects
Quoting David Jencks david_jen...@yahoo.com:
I haven't and wont look at the mojarra code but I think you are looking for
org.apache.myfaces.config.annotation.LifecycleProvider
Looks like that takes care of spec section 5.4 (injection,
@PreDestroy, @PostConstruct).
How do you deal with
Portlet 2.0 Bridge doesn't properly encode portlet:resource syntax to a faces
View
--
Key: PORTLETBRIDGE-161
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-161
MyFaces has an AnnotationConfigurator [1] which scans the classpath using a
simple bytecode scanning mechanism [2] (comparable with the one in
Javassist). It's pretty fast, but it's true that classes might be scanned
twice.
Regards,
Jan-Kees
[1]
[
https://issues.apache.org/jira/browse/MYFACES-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2861.
-
Fix Version/s: 2.0.2-SNAPSHOT
Resolution: Fixed
Remove commons-discovery
Improve efficiency of Application.createComponent(FacesContext,Resource) in
production
--
Key: MYFACES-2862
URL: https://issues.apache.org/jira/browse/MYFACES-2862
Hi,
success!
myfaces + MYFACES-2854-2.patch + MYFACES-2862 = ~ 70 ms in restore view
phase. It was *750 ms* before.
Thanks,
Martin Kočí
Leonardo Uribe píše v St 04. 08. 2010 v 22:09 -0500:
Hi
I implemented a proposal for this one on MYFACES-2854-2.patch using
the suggestion
proposed (do
[
https://issues.apache.org/jira/browse/MYFACES-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-2854:
Status: Resolved (was: Patch Available)
Assignee: Leonardo Uribe
Fix
Hi
Ok, good to know that. I closed MYFACES-2854. Maybe on MYFACES-2862 we can
use FacesContext.isProjectStage(ProjectStage).
regards,
Leonardo
2010/8/5 Martin Koci martin.k...@aura.cz
Hi,
success!
myfaces + MYFACES-2854-2.patch + MYFACES-2862 = ~ 70 ms in restore view
phase. It was *750
Portlet 2.0 Bridge: Resource as source of iFrame doesn't render in Pluto
Key: PORTLETBRIDGE-162
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-162
Project: MyFaces
Portlet 2.0 Bridge should establish child request scopes if rendering a
resource from a different view (in an iFrame)
-
Key: PORTLETBRIDGE-163
Bridge shouldn't notify (bridge) request scope attrbiutes that they are being
destroyed if only updating the scope at the end of a request
--
Birdge explicit scope removal doesn't cause its attributes to be notified but
should
-
Key: PORTLETBRIDGE-165
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-165
[
https://issues.apache.org/jira/browse/TRINIDAD-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-17.
Assignee: Jeanne Waldman
Fix Version/s: 2.0.0.3-core
Resolution: Fixed
Create a new package org.apache.myfaces.spi and implement Providers for
integration points with application containers
--
Key: MYFACES-2863
URL:
[
https://issues.apache.org/jira/browse/TRINIDAD-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895885#action_12895885
]
Jeanne Waldman commented on TRINIDAD-17:
Note, in my comment on 19/Jul/2010, I
[
https://issues.apache.org/jira/browse/TRINIDAD-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895892#action_12895892
]
Jeanne Waldman commented on TRINIDAD-17:
I thought of a COMMON usecase where we
34 matches
Mail list logo
