Hey guys,
background:
https://issues.apache.org/jira/browse/TRINIDAD-1724
Max, so you are saying the changed the API (XSD) file for the
facelettaglibrary
(not the faces-config, right?)
But the online version of it, simply lacks the method-signature:
Ok,
here is the bug:
https://issues.apache.org/jira/browse/MYFACES-2554
-Matthias
On Sat, Feb 13, 2010 at 10:45 AM, Matthias Wessendorf mat...@apache.org wrote:
Hey guys,
background:
https://issues.apache.org/jira/browse/TRINIDAD-1724
Max, so you are saying the changed the API (XSD) file
myfaces's facelettaglibrary XSD incomplete
--
Key: MYFACES-2554
URL: https://issues.apache.org/jira/browse/MYFACES-2554
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects
Component metadata is still going against JSF version 1.2
-
Key: TRINIDAD-1725
URL: https://issues.apache.org/jira/browse/TRINIDAD-1725
Project: MyFaces Trinidad
Issue Type: Bug
[
https://issues.apache.org/jira/browse/MYFACES-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12833370#action_12833370
]
Jakob Korherr commented on MYFACES-2553:
A really good solution, Leonardo :)
Hi Gerhard,
Did you mean i used UserTransaction? If not, how do you receive your
EntityTransaction?
I am working on a solution to get request-scoped EntityManagers injected within
a servlet-container that does not even support the web-profile (which are the
current jetty and the current
hi arne,
i used the EntityManager to get an EntityTransaction.
you have to use cdi to create and inject it.
(i used some producer methods.)
i created @PersistenceUnit which is a cdi qualifier and
@Transactional which is a cdi interceptor binding.
basically it works and it isn't hard to use.
Hi Gerhard,
OK, I got what you did, basically I did the same. You are right, that was
pretty straight-forward, but I had to hard-code the persistence-unit name.
I have two ideas to inject the persistence-unit name into the producer-method
for the EntityManager:
First idea: A
Hi!
The JSR-299 spec defines that we have to support injection of EE-Resources.
This was more explicit in the old version of the spec, but unless the wording
got shortened, I still think injection of @PersistenceUnit and
@PersistenceContext must be supported by any JSR-299 container (at least
Hi Mark,
thank you for your feedback. I was aware of the requirement of CDI-containers
to inject JavaEE resources in a JavaEE-environment, but Gerhard and I are
thinking about a generic non-JavaEE-solution for EntityManager-injection. And
at least weld does no injection of JavaEE-resources in
I am afraid supporting multiple persistence-units in that
scenario is very difficult...
Nope, it's really easy. I simply use Qualifiers to distinguish between them.
@Qualifier
public @instance Core {}
@Qualifier
public @instance Other {}
@RequestScoped
public class EMProducer {
Hi Mark,
yes, that is simple when you have a working @PersistenceContext(unitName=...)
annotation. In none-EE-environments you don't have that and generic
producer-methods are more complicated since you have to inject your unit-name.
Regards,
Arne
--
Arne Limburg - Enterprise Developer
org.apache.myfaces.config.annotation.LifecycleProvider context parameter is
ignored
---
Key: MYFACES-2555
URL: https://issues.apache.org/jira/browse/MYFACES-2555
[
https://issues.apache.org/jira/browse/MYFACES-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ali Ok updated MYFACES-2555:
Status: Patch Available (was: Open)
org.apache.myfaces.config.annotation.LifecycleProvider context
Hi,
On Jsp2.0 environment using Myfaces 2.0 beta, users should provide the
ExpressionFactory implementation.
And if Jasper EL Impl or Sun's RI is available on the classpath, they are
automatically set.
However, impl class name of RI may be wrong.
Until revision 761982, it was
15 matches
Mail list logo
