I think the programming way to get the CDI bean via BeanProvider
manually can be accepted...
I would like the following will be added into the Apache DeltaSpike as
soon as possible.
1. import the CDI query aka the JPA Repository API
2. improve the JSF scopes and Conversation support(nested, @Begi
As said before, if using the javaee7 lib is easy in javaee6 no need of any
glue. That should be the case for bval, jpa...
Le 2 juin 2013 03:26, "Jason Porter" a écrit :
> FWIW I'm +1 for the BeanVal stuff and keeping it disabled by default. Just
> because Java EE 7 is soon to be released doesn't
maybe our next step should be an agreed deprecation-strategy (before we
continue with such topics).
regards,
gerhard
2013/6/1 Gerhard Petracek
> hi thomas,
>
> no - we don't have @Advanced.
> (-1 for adding it and therefore -1 for adding parts which would need such
> a qualifier.)
>
> regards
FWIW I'm +1 for the BeanVal stuff and keeping it disabled by default. Just
because Java EE 7 is soon to be released doesn't mean that people will migrate
to it over night, as has already been said. I'm sure there are quite a few
large corporations still on Java EE 5 and probably will be for a wh
hi thomas,
no - we don't have @Advanced.
(-1 for adding it and therefore -1 for adding parts which would need such a
qualifier.)
regards,
gerhard
2013/6/1 Thomas Andraschko
> Jep, there will be many EE6 users out there the next 1-3 years.
>
> there are also other possible features:
> - injec
Jep, there will be many EE6 users out there the next 1-3 years.
there are also other possible features:
- injection in other BV artifacts - e.g. MessageInterpolator
- method validation (if possible with 1.0 specs)
AFAIK all this features will be available in BV 1.1, so it would be enough
to creat
As others said, in an EE-6 container you cannot just exchange the bean
validation provider easily.
Yes, it's already possible to use the BeanProvider to achieve this goal.
But it's also nice if that would work out of the box.
An important criteria is of course that it must also work when bean
hi thomas,
yes, because we based everything on the jsf 1.2 api.
(~nothing from the jsf2+ api was needed to provide what you get with codi.)
@ "...in each validator...":
projects usually don't have that many constraint-validators which need
other services (and if so they might overuse it).
we sho
i know what you mean gerhard :)
but IMO using manual injection or getting the bean via BeanManager etc. is
just a "stupid" workaround in each validator.
It would be just user friendly to provide a small module which provides BV
injection. Also the effort to create this module is very very low.
Sur
RE Bean Validation, I agree and enthusiastically invite anyone who has an
itch to work on Bean Validation and CDI to come help out implementing BV
1.1 at Apache BVal :D
Matt
On Sat, Jun 1, 2013 at 8:20 AM, Gerhard Petracek wrote:
> as mentioned earlier i'm not sure about the bv parts (just for
@thomas:
if you are allowed to use bv 1.1, it should be possible (via
default-provider + the corresponding classloading-config for the server you
are using).
if you are not allowed to use it, have a look at my initial comments.
@hantsy:
imo that's exotic anyway and you could still use BeanProvider
I noticed JSF 2.2 canceled the DI in JSF components in final Specs, only
support in JSF backend beans.
MyFaces CODI provides @Advanced for DI in non contextual object...it is
still useful for JSF 2.2...but I do not want to add this to enable
injection on JSF validator, converter, etc.
Hantsy
On 6
Also if BV 1.1 is coming soon, many customers can't upgrade to BV 1.1 or
JavaEE 7 the next 1-2 years.
So IMO it would be a great feature which shoudl be disabled per default.
2013/6/1 Romain Manni-Bucau
> Idem, not blocking IMO and bval 1.1 is coming so would be useless soon
> Le 1 juin 2013 15
Idem, not blocking IMO and bval 1.1 is coming so would be useless soon
Le 1 juin 2013 15:56, "Gerhard Petracek" a
écrit :
> hi john,
>
> codi doesn't do auto registration. you need @Advanced to enable it.
>
> if you aren't allowed to use bv 1.1 right know, you can just use
> BeanProvider manually
hi john,
codi doesn't do auto registration. you need @Advanced to enable it.
if you aren't allowed to use bv 1.1 right know, you can just use
BeanProvider manually (usually there are just few constraint-validators
which need it at all)
or keep what your are using now in parallel or just copy thos
as mentioned earlier i'm not sure about the bv parts (just for injection).
therefore you just need to enable any bv 1.1 implementation (via
default-provider) and you get even more.
@thomas:
the only missing parts besides that are the remaining scopes (the rest is
in already).
imo it's way more im
the most important feature are propably:
- finish the extended JSF scopes
- type view navigation
- injection BV artifacts
so the most users could switch from CODI to DS. We currently do not use
more features in the most apps.
2013/6/1 Romain Manni-Bucau
> Cdi query stuff would be great too
> L
[
https://issues.apache.org/jira/browse/DELTASPIKE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672071#comment-13672071
]
Karl Kildén commented on DELTASPIKE-332:
CDI aware ConstraintFactory 1+
If th
Cdi query stuff would be great too
Le 1 juin 2013 13:12, "Mark Struberg" a écrit :
> Yes should mainly be a bugfix release with only a few new features.
>
> LieGrue,
> strub
>
>
>
>
> >
> > From: John D. Ament
> >To: dev@deltaspike.apache.org; Mark Struberg
> >Cc
Hi All
I wanted to begin introducing some level of BeanValidation Support. The
main goal that I have is to be able to create CDI aware constraint
validators, let's say you want to validate @NonExistentEmail then you
should be able to run a query against your DB using your CDI services and
determi
Yes should mainly be a bugfix release with only a few new features.
LieGrue,
strub
>
> From: John D. Ament
>To: dev@deltaspike.apache.org; Mark Struberg
>Cc: deltaspike
>Sent: Saturday, 1 June 2013, 13:07
>Subject: Re: [DISCUSS] deltaspike-0.5 features
>
>
Mark,
A little aggressive based on how long it took to get 0.4? Should this be a
small release then?
I'd like to add some level of BeanValidation support in this release, looks
like the CODI and Seam features are pretty similar; so adding support for a
ConstraintValidatorFactory that creates inj
Hi!
It's time to go for planing ds-0.5.
I'd say the release should be pretty small this time. Mostly bug fixes and a
few minor enhancements. And max 1 or 2 bigger bullet features.
The goal is to release ds-0.5 end of this month.
A few things on the list as I remember so far:
* Finish graduatio
[
https://issues.apache.org/jira/browse/DELTASPIKE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John D. Ament reassigned DELTASPIKE-332:
Assignee: John D. Ament
> Discuss introducing BeanValidation support
>
Hey Christian,
Just wondering how far you got with this. Since 0.5 is now starting up
maybe we can start entering JIRAs for the features?
On Tue, May 14, 2013 at 4:05 AM, Christian Kaltepoth wrote:
> Sure, as I already wrote I would start in a separate branch on github and
> merge later after
25 matches
Mail list logo
