Marvin,
What you are suggesting is not required imo. Some strategy configuration
like suggested from Thomas would give the same benefits.
On 14 August 2015 at 13:39, Marvin Toll wrote:
> At the moment, I don't see a way to specify and implement save()
> in a way that is logically consistent *a
Hello,
I have not really noticed any perf issues with deltaspike data but then
again I did not measure it either. We use it a lot. Would be great to learn
more about it for sure.
I always assumed the method name query syntax and the other static stuff
would be cached etc so I don't really get why
The do it yourself:
http://stackoverflow.com/questions/13239975/depedency-inject-request-parameter-with-cdi-and-jsf2
On 7 January 2015 at 10:50, Karl Kildén wrote:
> Hello,
>
> You can also use: http://showcase.omnifaces.org/cdi/Param
>
>
>
> On 7 January 2015 at 10
Hello,
You can also use: http://showcase.omnifaces.org/cdi/Param
On 7 January 2015 at 10:47, Gerhard Petracek
wrote:
> hi damien,
>
> we dropped it, because we consider it as anti-pattern.
> if you >really< need it, you just need to create a std. cdi-producer with
> your own RequestParam anno
I use TomEE with Eclipselink and have no issues. I do not recognize nor use
the eclipselink properties you have in persistence.xml. Otherwise we have
very similar configuration.
On 5 October 2014 16:58, hwaastad wrote:
> Hi TH,
> and thanks for answering.
>
> I'm running JTA datasource and run
Can you try this?
@PersistenceContext(unitName = APP_NAME)
private EntityManager entityManager;
@Produces
@RequestScoped
protected EntityManager createEntityManager() {
return this.entityManager;
}
On 3 October 2014 08:02, hwaastad wrote:
> Hi,
> maybe a little late on this but I've been testi
long since the api is so nice and concise. Anyway thanks I had a good
run with it ;)
cheers
[1] https://issues.apache.org/jira/browse/DELTASPIKE-577
On 20 September 2014 19:26, Karl Kildén wrote:
> If it was TomEEConfig.java rather than Properties I would understand your
> objection.
ty as well.
>
> we could move ContainerAwareTestContext to the spi which would allow to
> customize different areas.
> then you can decide on your own if you would like to use an implementation
> which isn't portable.
>
> regards,
> gerhard
>
>
>
> 2014-09-
to
> features provided by tomee.
> imo it doesn't make sense to add something only for one container (to the
> api) which is supported by the test-module of that container already.
>
> regards,
> gerhard
>
>
>
> 2014-09-20 16:24 GMT+02:00 Karl Kildén :
>
> &g
FYI Gerhard said on the list that the boot(Properties p) in CdiContainer
was a mistake and supporting it in test-control is thus wrong.
I disagree and will branch test-control over n out
On 20 September 2014 16:15, Karl Kildén wrote:
> All those suggestions use properties so I am not sure w
we support right now don't support such
> properties anyway).
>
> regards,
> gerhard
>
> [1] http://tomee.apache.org/alternate-descriptors.html
>
>
>
> 2014-09-20 15:28 GMT+02:00 Karl Kildén :
>
> > Hello,
> >
> > Test-Control will bootstrap the
Hello,
Test-Control will bootstrap the CdiContainer for me using the #boot()
constructor. However I want it to use #boot(Properties p)
This seems logical since CdiContainer contract has that boot method. My
suggestion is:
public interface PropertiesProvider {
Properties properties();
}
@TestCo
Hrrmm I have not used the scheduler, but it looks like you don't really
start scopes in the docs?
For test-control it feels pretty natural the way it is now imo. No idea
about the Servlet Listener, what module / feature is that?
On 10 September 2014 10:10, Gerhard Petracek
wrote:
> #1
> the tes
What a great page! I did not know about Double-Submit prevention feature
and I was actually investigating how to solve it just now :-)
On 7 September 2014 17:06, John D. Ament wrote:
> Hi all
>
> I was looking at other apache projects and noted that many of them include
> dedicated pages for ea
ni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-18 18:08 GMT+02:00 Karl Kildén :
> > So isNew is broken for openjpa and one should live with it? Thi
(just don't name it save ;-)
>
>
>
> On Tue, Jun 17, 2014 at 4:41 PM, Romain Manni-Bucau >
> wrote:
>
> > Yes, but that s not an issue since you can get it injected
> >
> > Le lundi 16 juin 2014, Karl Kildén a écrit :
> > > But then I need to use the enti
Feels like it should default to @ApplicationScoped? I see no reason why not
at least
On 18 June 2014 13:12, Thomas Andraschko
wrote:
> or: @Repository(scope = ApplicationScoped.class)
>
>
> 2014-06-18 12:25 GMT+02:00 Thomas Andraschko >:
>
> > Hi Thomas,
> >
> > my problem is that when i injec
But then I need to use the entityManager in the mapper or am I missing
something?
On 16 June 2014 11:17, Romain Manni-Bucau wrote:
> Yes you need to merge it but the responsability is yours (user) IMO.
> Le 16 juin 2014 09:56, "Karl Kildén" a écrit :
>
> > Hrmm ma
;Thomas Andraschko" a
> écrit :
>
> > Why don't we use entityManager#contains instead of checking the ID?
> >
> >
> > 2014-06-16 10:22 GMT+02:00 Karl Kildén :
> >
> > > Hi,
> > >
> > > On could argue that the real probl
> I guess that would even work if the group is not persisted if you adapt
> cascading.
>
> Makes sense?
>
> On Fri, Jun 13, 2014 at 5:56 PM, Karl Kildén
> wrote:
>
> > Not sure I get myself ;)
> >
> > Lets walk through how I see it:
> >
> > 1. Us
Hi,
Thomas do you think our recent discussions [1] about the mapper api for the
data module will break the API? It seems it will not imo. Possibly add a
new method or change visibility but nothing contract breaking right?
In that case I am +1 because all my apps run fine with snapshot
[1]
http:/
ne 2014 17:09, Thomas Hug wrote:
> Hi Karl
> Sorry not sure if I get you right. Why would user.getGroup() be stale? As
> in the update case user has just been fetched by the PK, user.getGroup()
> should lazyload the group - right?
>
>
> On Fri, Jun 13, 2014 at 2:51 PM, Karl Ki
ager fetch).
> How does that look? Better ideas?
>
>
>
> On Fri, Jun 13, 2014 at 8:42 AM, Karl Kildén
> wrote:
>
> > I wrote a response to the users list but not sure it came through. It
> kinda
> > belongs in this thread so here it goes.
> >
> >
>
I wrote a response to the users list but not sure it came through. It kinda
belongs in this thread so here it goes.
So I ran into issues with the DTO mapper api and voiced my concerns in irc.
I saw this discussion and now I am trying the solution present in the
current SNAPSHOT. However I have on
Sounds awesome :-)
ConversationScoped is a do it yourself and could cover any need for this
reason but whenever you have data that is supposed to be unique per tab
then WindowScoped is very nice and a ready to use solution.
For example a text editor with the content saved in WindowScoped bean so
Hi,
The gain is that the collective behind the data module are pretty much the
people I would hire to write my base class if I could ;)
It also unifies how stuff is done etc...
On 20 May 2014 13:03, Romain Manni-Bucau wrote:
> Hi
>
> +-0 nothing particular against but not sure the real gain i
"Design help for the logo"
Saw that mail just now, sounds great :-)
On 19 May 2014 12:37, Karl Kildén wrote:
> +0 because I would really like to see a logotype selected before 1.0.
>
> I am aware of https://issues.jboss.org/browse/DESIGN-520 and I am also
> fine with
+0 because I would really like to see a logotype selected before 1.0.
I am aware of https://issues.jboss.org/browse/DESIGN-520 and I am also fine
with going with one already proposed. I just feel that every project needs
a good logo
On 19 May 2014 11:55, Christian Kaltepoth wrote:
> +1
>
>
> 2
Hello!
Sometimes odd use cases makes it hard to mock out stuff when you use
Test-Control. For that reason Gerhard wrote a test-control addon for
mocking. I think it should be added as a feature in Test-Control. Example
is for example to be able to mock Repositories from data-module.
http://os890.
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://deltaspike.apache.org/container-control.mdtext
Karl Kildén
Index: trunk/content/container-control.mdtext
===
--- trunk/content
Hello,
PreViewConfigNavigateEvent getFromView() gives
me org.apache.deltaspike.core.api.config.view.ViewRef$Manual rather then my
actual source. toView works as expected.
This is a very simple demo app running on TomEE.
Should I create a jira and attach my project?
cheers
I am also curious about best practice for this (right now) and perhaps in
the future. The thing is the Deltaspike /CDI style is very nice to work
with and it would be a preferred API for me.
On 8 April 2014 13:33, Rafael Meireles wrote:
> Hello everyone, I would like to know if you think about
Big congratulations and thanks!
-- Forwarded message --
From: Gerhard Petracek
Date: 20 March 2014 09:38
Subject: [ANNOUNCE] Release of Apache DeltaSpike 0.6
To: "dev@deltaspike.apache.org" ,
us...@deltaspike.apache.org
The Apache DeltaSpike team is pleased to announce the 6th r
>> > >>
> > >> > >> On Mon, Feb 10, 2014 at 5:47 AM, Romain Manni-Bucau
> > >> > >> wrote:
> > >> > >> > test-control could be renamed cdi-unit or something like it
> IMHO
> > >> > >> > Romain
Hello! By following the discussions you seem to draw closer and closer to
1.0. I think it would be appropriate to end the project name (or was that
settled?) and logotype discussions before.
I myself is -1 for name change and +1 for the logotype that's currently in
the header
Cheers!
Hello,
I know it's been discussed before but now with a module called test-control
it just feel unnecessary to be inconsistent even though cdiCtrl is not a
module it's not so pretty...
Cheers / Karl
I apologize for my last email, currently babysitting...
On 6 February 2014 19:30, Karl Kildén wrote:
> /*q
>
>
> On 6 February 2014 18:08, Jean-Louis MONTEIRO wrote:
>
>> Hello guys,
>>
>> I'm currently facing a regression on Securty module.
>> Just
/*q
On 6 February 2014 18:08, Jean-Louis MONTEIRO wrote:
> Hello guys,
>
> I'm currently facing a regression on Securty module.
> Just wanted to know if you are aware of?
>
> I was using 0.5 with the following
> @View(basePath = "/", extension = "xhtml", navigation =
> View.NavigationMode.REDIR
If I ever were to post a meme to this mail list it would probably be:
"If my application could have just one of dsRid and windowId and no loading
splash I would be so happy"
cheers
On 9 January 2014 22:52, Thomas Andraschko wrote:
> Hi,
>
> currently the default rendering mode is our windowhan
This is my summary:
By following the discussion it seems to be seen as convenient vs
inconvenient and the vote is kinda even. What I would like to see is
cohesion in Deltaspike overall. Either you use namespaces or you don't. My
point is basically that it feels more like a project-wide decision.
I really like this idea! 1+
cheers / Karl
On 16 December 2013 17:55, Gerhard Petracek wrote:
> hi @ all,
>
> we could also combine it with [1].
>
> regards,
> gerhard
>
> [1] http://s.apache.org/MOc
>
>
>
> 2013/12/6 Thomas Andraschko
>
> > Arne, can i rework it and provide a patch?
> > Do you
I think 1.0 sounds great. Improving docs would be the best way to move
deltaspike forward imo. My major concern right now is the windowId stuff. I
like many want the functionality but struggles with dual ids (windowId &
dsRid) a loading splash. Would love docs here that covers the different
strateg
Hi. It works for OWB.
See: https://issues.apache.org/jira/browse/DELTASPIKE-284
On 13 October 2013 21:29, John D. Ament wrote:
> Hey guys,
>
> Just wanted to check with everyone. Looking at the documentation
> around context control, it seems a little puzzling and wanted to get
> others opi
Hello!
I have some trouble understanding why it's bad to destroy the instance with
that example. What about this example, does it make sense?
DependentProvider ctxControl =
BeanProvider.getDependent(ContextControl.class);
ctxControl.get().startContext(ApplicationScoped.cl
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://deltaspike.apache.org/documentation.mdtext
Karl Kildén
Index: trunk/content/documentation.mdtext
===
--- trunk/content
John,
always worked for me
so it sounds pretty weird I think but then again it's IE...
Regarding this whole feature and the decisions and configuration one must
do I feel it's a bit tough. I have not read the current docs for this but I
tried it in CODI and felt uncomfortable with it. Good doc
if it works? You'd need at
> > least JPA, CDI runtime to get it working.
> >
> >
> > On Fri, Jun 14, 2013 at 7:40 AM, Karl Kildén
> > wrote:
> >
> > > Hi Thomas! I got that from the third link (temp docs)
> > >
> > > "In or
sible but currently not supported."
cheers
2013/6/14 Thomas Andraschko
> sorry for this question, i didn't read other posts but why can't this be
> used on a plain servlet container?
>
>
> 2013/6/14 Karl Kildén
>
> > Sorry if I missed out on some of
Sorry if I missed out on some of the discussions about this but I think the
lack of support for a plain servlet container is a big disappointment and a
big loss of potential users in my immediate network.
I really like the module though, can't wait etc. Thanks for doing it
Cheers
2013/6/14 Thom
1+ For JSF stuff The bridge between JSF ExceptionHandler and DS Exception
Handling feels like pretty low hanging fruit? The implementation from Seam
Faces seems good to me, maybe use BeanManagerProvider to fire the event
instead.
1+ For JPA Generic Repository. But if it hinders the plan to releas
50 matches
Mail list logo