Deltaspike-0.3-incubating is now already available on maven.central.
I'll go on pushing the tag and stuff and upgrade to 0.4-incubating.
LieGrue,
strub
- Forwarded Message -
From: Mark Struberg strub...@yahoo.de
To: gene...@incubator.apache.org gene...@incubator.apache.org
Cc:
Hi folks!
It's time to start working on ds-0.4-incubating.
Here is my personal list of things I like to work on:
* review/cleanup our JPA module
* review ConfigurableDataSource in hindsight of JPA in EE6
* add JSF module
* migrate over @ViewScoped
* add ComparableQualifier to the core
I'd
Thanks for your feedback!
I don't know all the details but the list look good so far.
* ProjectStage
Automatically bind to JSF projectStage
That should work even with 0.3 as we already check the property, environment
and JNDI locations for it. What does _not_ work is defining the
Hello,
Does DS provides a requestScopes em ?
I tried to to something like https://cwiki.apache.org/EXTCDI/jpa-usage.html,
but I had an error (don't remember which one, I think it was because em wasn't
associated with current tx)
For the moment, I'm using softwaremill
Hi Mark,
What does _not_ work is defining the ProjectStage via web.xml.
Is there a way to tell JSF to use DS projectStage instead of web.xml ?
(in this way if I want during development mode to modify current projectStage
from Development to Production, I only have to modify it in one
Well, we might miss some explanation for this lines
@PersistenceContext(unitName=default)
private EntityManager entityManager;
This only works in SE. In an EE container you will get a Container Managed EM,
which is not manageable by the user, but strictly bound to EJBs.
Even the sample of
No, there is no way. We use the same configuration, thus it will be the 'same'.
The Problem is that the JSF ProjectStage is a simple Enum and thus cannot be
extended. Whereas DS ProjectStage is extensible. If you configure such an
extended ProjectStage then JSF will fallback to 'Production' for
Well I actually would NOT recommend setting the ProjectStage via web.xml at all!
Please either use an environment variable
-Djavax.faces.ProjectStage=Development
or via JNDI, in tomcat e.g. in conf/context.xml :
Environment name=jsf/ProjectStage value=SystemTest
If you are using EJB and EE then you should be fine with just using an
Extended EM.
LieGrue,
strub
- Original Message -
From: Adrian Gonzalez adr_gonza...@yahoo.fr
To: deltaspike-dev@incubator.apache.org
deltaspike-dev@incubator.apache.org; Mark Struberg strub...@yahoo.de
Cc:
Seam Application Framework
Or something similar / simple to use and understand.
http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/framework.htmlBestregards,
I think we have something similar to this already developed by Thomas
Hughttps://plus.google.com/100910414952656230590which is
No, there is no portable way to set this in JSF afaik.
But if bot DS and JSF use the _same_ source for determining the ProjectStage,
then they basically will get the same results.
LieGrue,
strub
- Original Message -
From: Adrian Gonzalez adr_gonza...@yahoo.fr
To:
As I mentioned, Jason is on vacation atm, so I'll just insert a placeholder
that he was planning on migrating the XML config from Seam into DeltaSpike.
If we can refrain from an extensive discussion until he is back from vacation,
that will make the discussion flow a lot better :-) I just
12 matches
Mail list logo
