to do this soon. Should we instead move it to
0.6?
Add XML Config from Seam
Key: DELTASPIKE-269
URL: https://issues.apache.org/jira/browse/DELTASPIKE-269
Project: DeltaSpike
Issue Type: Task
XML Config from Seam
Key: DELTASPIKE-269
URL: https://issues.apache.org/jira/browse/DELTASPIKE-269
Project: DeltaSpike
Issue Type: Task
Components: Configuration
Affects Versions: 0.4-incubating
XML Config Introductions
In addition to being an OSGi spec, supporting XML namespace
extensions (with Apache Camel support) and included in JBoss Fuse /
Apache Karaf by default, it has an added advantage of having a
current implementation too (around 300Kb only depends on slf4j
mproc...@redhat.com, Jason Porter
jpor...@redhat.com, Brad Davis bda...@redhat.com, Brad
Davis
bradsda...@gmail.com, Guillaume Nodet
gno...@redhat.com
Sent: Tuesday, January 15, 2013 11:06:12 AM
Subject: Re: CDI XML Config Introductions
In addition to being an OSGi spec
lincolnbax...@gmail.com, Mark
Proctor
mproc...@redhat.com, Jason Porter
jpor...@redhat.com, Brad Davis bda...@redhat.com, Brad
Davis
bradsda...@gmail.com, Guillaume Nodet
gno...@redhat.com
Sent: Tuesday, January 15, 2013 11:06:12 AM
Subject: Re: CDI XML Config
, Guillaume Nodet
gno...@redhat.com
Sent: Tuesday, January 15, 2013 11:06:12 AM
Subject: Re: CDI XML Config Introductions
In addition to being an OSGi spec, supporting XML namespace
extensions (with Apache Camel support) and included in JBoss Fuse
/
Apache Karaf by default
Yes, basically native XML configuration of CDI in addition to custom
schemas and parsers for domain-specific configuration. Excellent.
On Thu, Jan 17, 2013 at 12:19 PM, Jason Porter lightguard...@gmail.comwrote:
There have been some interesting developments with regards to the need of
an XML
...@gmail.com, Guillaume Nodet
gno...@redhat.com
Sent: Tuesday, January 15, 2013 11:06:12 AM
Subject: Re: CDI XML Config Introductions
In addition to being an OSGi spec, supporting XML namespace
extensions (with Apache Camel support) and included in JBoss Fuse /
Apache Karaf by default, it has
Subject: Re: CDI XML Config Introductions
In addition to being an OSGi spec, supporting XML namespace
extensions (with Apache Camel support) and included in JBoss Fuse /
Apache Karaf by default, it has an added advantage of having a
current implementation too (around 300Kb only depends
-dev@incubator.apache.org
Cc: Jason Porter lightguard...@gmail.com; Mark Struberg strub...@yahoo.de
Sent: Friday, October 12, 2012 1:01 AM
Subject: Re: Seam XML config
I think we have to support creation of new beans. Take a look at [1],
which is a blog post on configuring Drools within
:01 AM
Subject: Re: Seam XML config
I think we have to support creation of new beans. Take a look at [1],
which is a blog post on configuring Drools within Spring. A little way
down, under the sessions.xml heading he has an example showing a Drools
configuration. We need to be able
Subject: Re: Seam XML config
Hi,
IMO that's the needed case (at least to start): make cdi friendly legacy
libs
Le 12 oct. 2012 08:38, Mark Struberg strub...@yahoo.de a
écrit :
well, there is an important distinction between creating new beans for
classes which are in a BDA and others who
@incubator.apache.org
Cc:
Sent: Friday, October 12, 2012 9:39 AM
Subject: Re: Seam XML config
Hi,
IMO that's the needed case (at least to start): make cdi friendly legacy
libs
Le 12 oct. 2012 08:38, Mark Struberg strub...@yahoo.de a
écrit :
well, there is an important distinction between creating new
@incubator.apache.org
Cc: deltaspike-dev@incubator.apache.org
deltaspike-dev@incubator.apache.org
Sent: Friday, October 12, 2012 4:54 PM
Subject: Re: Seam XML config
On Oct 12, 2012, at 7:58, Mark Struberg strub...@yahoo.de wrote:
oki, it seems we have a start.
The only technical
: Friday, October 12, 2012 4:54 PM
Subject: Re: Seam XML config
On Oct 12, 2012, at 7:58, Mark Struberg strub...@yahoo.de wrote:
oki, it seems we have a start.
The only technical restriction so far is that there is only 1 bean per
class possible in CDI-1.0.
Apart from that I would
Mark, do you have an example for InterDyn (or whatever it's called?)
We also need to decide if we're going to allow creation of new beans or
simply configure existing beans (adding / removing metadata) using this
configuration.
On Fri, Sep 28, 2012 at 9:54 AM, Pete Muir pm...@redhat.com wrote:
@incubator.apache.org
Cc:
Sent: Thursday, October 11, 2012 10:58 PM
Subject: Re: Seam XML config
Mark, do you have an example for InterDyn (or whatever it's called?)
We also need to decide if we're going to allow creation of new beans or
simply configure existing beans (adding / removing metadata) using
the readme:
https://github.com/struberg/InterDyn
LieGrue,
strub
- Original Message -
From: Jason Porter lightguard...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Thursday, October 11, 2012 10:58 PM
Subject: Re: Seam XML config
Mark, do you have an example for InterDyn
Original inspiration for xml came from Gavin's design for CDI 1.0. I don't know
more details about why they went this direction.
On 25 Sep 2012, at 00:19, Jason Porter wrote:
It did (maybe it still does), but at some point we decided that wasn't
recommended, I don't recall why though, perhaps
this thread will be done?
2) do we want it extensible to let the user add 'shortcuts' (webservices,
camel context...)?
Le 19 sept. 2012 00:09, Jason Porter lightguard...@gmail.com a écrit :
Let's start listing requirements and use cases for what we want the XML
config module to do. I know I have
' (webservices,
camel context...)?
Le 19 sept. 2012 00:09, Jason Porter lightguard...@gmail.com a écrit :
Let's start listing requirements and use cases for what we want the XML
config module to do. I know I have heard of two:
1) Bean configuration and wiring to allow another integration point
, Jason Porter lightguard...@gmail.com a
écrit :
Let's start listing requirements and use cases for what we want the
XML
config module to do. I know I have heard of two:
1) Bean configuration and wiring to allow another integration point
with
CDI for things such as Drools
it extensible to let the user add 'shortcuts'
(webservices,
camel context...)?
Le 19 sept. 2012 00:09, Jason Porter lightguard...@gmail.com a
écrit :
Let's start listing requirements and use cases for what we want the
XML
config module to do. I know I have heard of two
00:09, Jason Porter lightguard...@gmail.com a
écrit :
Let's start listing requirements and use cases for what we want
the
XML
config module to do. I know I have heard of two:
1) Bean configuration and wiring to allow another integration
point
with
CDI
: Romain Manni-Bucau rmannibu...@gmail.com
Sent: Monday, September 24, 2012 9:54 PM
Subject: Re: XML Config requirements
Hm, hadn't thought about JAXB. That may be a good way to go. We'd still
need to translate the JAXB objects into the CDI metamodel though (probably,
unless we created our own
each time i read this kind of conf i think it should be the opposite
why not extending beans.xml (just in the spirit, not in the same file)
adding qualfiiers etc?
*Romain Manni-Bucau*
*Twitter: @rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn:
It did (maybe it still does), but at some point we decided that wasn't
recommended, I don't recall why though, perhaps Stuart or Pete remembers.
On Mon, Sep 24, 2012 at 5:11 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
each time i read this kind of conf i think it should be the opposite
with 1
line of XML config.
Other sample:
app-config:PBESpecImpl
algorithmJNDI=java:/appName/encryption/algorithm
iterationCountJNDI=java:/appName/encryption/iterationCount
passwordJNDI=java:/appName
I know that I could write @Produces method, but I like
this way. It's
also
cool to turn some bean from non CDI library into CDI
bean simply with 1
line of XML config.
Other sample
bean simply with 1
line of XML config.
Other sample:
app-config:PBESpecImpl
algorithmJNDI=java:/appName/**encryption/algorithm
iterationCountJNDI=java:/**appName/encryption/**iterationCount
passwordJNDI=java
agree.
We shall also identify all features which are non-portable in CDI-1.0
LieGrue,
strub
- Original Message -
From: Gerhard Petracek gerhard.petra...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Tuesday, September 18, 2012 10:38 AM
Subject: Re: XML Config
-
From: Gerhard Petracek gerhard.petra...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Tuesday, September 18, 2012 10:38 AM
Subject: Re: XML Config
@ shane: +1
regards,
gerhard
2012/9/18 Shane Bryzak sbry...@redhat.com
Oh, and just to be clear I think we should
some bean from non CDI library into CDI bean simply with 1
line of XML config.
Other sample:
app-config:PBESpecImpl
algorithmJNDI=java:/appName/encryption/algorithm
iterationCountJNDI=java:/appName/encryption/iterationCount
passwordJNDI=java:/appName/encryption/password
bean simply with 1
line of XML config.
Other sample:
app-config:PBESpecImpl
algorithmJNDI=java:/appName/encryption/algorithm
iterationCountJNDI=java:/appName/encryption/iterationCount
passwordJNDI=java:/appName/encryption/password
saltJNDI=java:/appName/encryption/salt
s:modifies
like this way. It's
also
cool to turn some bean from non CDI library into CDI bean simply with 1
line of XML config.
Other sample:
app-config:PBESpecImpl
algorithmJNDI=java:/appName/**encryption/algorithm
iterationCountJNDI=java:/**appName/encryption/**iterationCount
passwordJNDI
)
Today i find other use case the translation of bad design
...just my opinion maybe
Le 7 sept. 2012 23:01, Jason Porter lightguard...@gmail.com a écrit
:
Mark, Pete and I discussed a little bit about the XML config (from
Solder)
on IRC today. We quickly decided that we needed to move over
s:modifies/
/pf-converter:EntityConverter
I know that I could write @Produces method, but I like this way. It's also
cool to turn some bean from non CDI library into CDI bean simply with 1
line of XML config.
Other sample:
app-config:PBESpecImpl
algorithmJNDI=java:/appName/encryption/algorithm
bean simply with 1
line of XML config.
Other sample:
app-config:PBESpecImpl
algorithmJNDI=java:/appName/encryption/algorithm
iterationCountJNDI=java:/appName/encryption/iterationCount
passwordJNDI=java:/appName/encryption/password
saltJNDI=java:/appName/encryption/salt
s:modifies
discussed a little bit about the XML config (from
Solder)
on IRC today. We quickly decided that we needed to move over to the
mailing
list for more input, and to make things official.
As things currently exist in the Solder XML Config, it's probably not
portable and would really need
about the XML config (from
Solder)
on IRC today. We quickly decided that we needed to move over to the
mailing
list for more input, and to make things official.
As things currently exist in the Solder XML Config, it's probably not
portable and would really need some
the translation of bad design
...just my opinion maybe
Le 7 sept. 2012 23:01, Jason Porter lightguard...@gmail.com a
écrit
:
Mark, Pete and I discussed a little bit about the XML config (from
Solder)
on IRC today. We quickly decided that we needed to move over to the
mailing
list for more input
It is prudent to provide something similar to what Seam Solder provided. As
Marius says, there needs to be a path for legacy apps to migrate to CDI
without recompilation of libraries.
The XML config can be a low priority task and probably the documentation
should be hidden away from the main
...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc: Romain Manni-Bucau rmannibu...@gmail.com
Sent: Monday, September 10, 2012 3:20 PM
Subject: Re: XML Config
G enerally speaking, I think it would be good to have a mechanism for
configuring beans that does not require re-compilation - may
, September 10, 2012 3:20 PM
Subject: Re: XML Config
G enerally speaking, I think it would be good to have a mechanism for
configuring beans that does not require re-compilation - may be of
limited use in greenfield applications, but above all with
brownfield/legacy code. In fairness
: Romain Manni-Bucau rmannibu...@gmail.com
Sent: Monday, September 10, 2012 3:20 PM
Subject: Re: XML Config
G enerally speaking, I think it would be good to have a mechanism for
configuring beans that does not require re-compilation - may be of
limited use in greenfield applications, but above all
:41 PM
Subject: Re: XML Config
Ok, what If I have library with CDI beans that send emails and need to have
JNDI of mail session configured?
When I attach this library to project A that is deployed on JBoss AS7 it
may have different jndi then in some other project or server.
2012/9/10
-
From: Marius Bogoevici marius.bogoev...@gmail.com
To: deltaspike-dev@incubator.**apache.org
deltaspike-dev@incubator.apache.org
Cc: Romain Manni-Bucau rmannibu...@gmail.com
Sent: Monday, September 10, 2012 3:20 PM
Subject: Re: XML Config
G enerally speaking, I think it would be good
To: deltaspike-dev@incubator.**apache.org
deltaspike-dev@incubator.apache.org
Cc: Romain Manni-Bucau rmannibu...@gmail.com
Sent: Monday, September 10, 2012 3:20 PM
Subject: Re: XML Config
G enerally speaking, I think it would be good to have a mechanism for
configuring beans that does
Mark Struberg
11 September 2012
1:59 AM
One of the credos is that you MUST NOT repackage for just
moving to a new server.Either this is in JNDI (same location) or
just use @Inject ProjectStage ps; to check on which server you are
running. I see no benefit of
I hate xml simply because it is too verbose.
Imo config on top of cdi is not the right place. It will often be over
engineered.
Properties will often be enough IMO (class name. Attribute = value for
instance)
Le 11 sept. 2012 01:31, Stuart Douglas sdoug...@redhat.com a écrit :
Mark
and I discussed a little bit about the XML config (from Solder)
on IRC today. We quickly decided that we needed to move over to the mailing
list for more input, and to make things official.
As things currently exist in the Solder XML Config, it's probably not
portable and would really need some
Mark, Pete and I discussed a little bit about the XML config (from Solder)
on IRC today. We quickly decided that we needed to move over to the mailing
list for more input, and to make things official.
As things currently exist in the Solder XML Config, it's probably not
portable and would really
+1 to adding it from me.
XML config is probably the feature (as opposed to enhancement to existing
feature or bug fix) most requested for CDI. I think we need something like
this in DeltaSpike, in order to fulfil our goals.
A non compiled format such as XML (or YAML or ...) makes a lot
-
From: Pete Muir pm...@redhat.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Saturday, July 7, 2012 12:33 PM
Subject: Re: v0.4-incubating adding Seam Config (xml config)
+1 to adding it from me.
XML config is probably the feature (as opposed to enhancement to existing
feature
:
Sent: Saturday, July 7, 2012 12:33 PM
Subject: Re: v0.4-incubating adding Seam Config (xml config)
+1 to adding it from me.
XML config is probably the feature (as opposed to enhancement to
existing
feature or bug fix) most requested for CDI. I think we need
something like
Struberg strub...@yahoo.de
Hmm, nope not really.
The idea is to take an arbitrary 3rd party source - most probably some
legacy project - and add the xml config from 'outside' to make those
classes usable.
Requiring some annotation on them would trash this imo.
LieGrue,
strub
provide the core + different
bindings:
1. the 'old' CDI spec XML config
2. a Spring style XML config
3. ...
LieGrue,
strub
- Original Message -
From: Romain Manni-Bucau rmannibu...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Friday, July 6, 2012 10
Hmm, nope not really.
The idea is to take an arbitrary 3rd party source - most probably some legacy
project - and add the xml config from 'outside' to make those classes usable.
Requiring some annotation on them would trash this imo.
LieGrue,
strub
- Original Message -
From: Romain
of) of the older xml config that was to be part of
spec but was later pulled.
what we have in Seam
3 with package name changes. It's currently the only implementation in
existence (that we know of) of the older xml config that was to be part of
spec but was later pulled.
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software
currently the only implementation in
existence (that we know of) of the older xml config that was to be part
of
spec but was later pulled.
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam
with some annotation.
LieGrue,
strub
- Original Message -
From: Marius Bogoevici marius.bogoev...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc: Jason Porter lightguard...@gmail.com
Sent: Friday, July 6, 2012 9:55 PM
Subject: Re: v0.4-incubating adding Seam Config (xml config
Struberg strub...@yahoo.de wrote:
Hmm just another idea:
If we do an own config module, we could provide the core + different bindings:
1. the 'old' CDI spec XML config
2. a Spring style XML config
3. ...
LieGrue,
strub
- Original Message -
From: Romain Manni-Bucau
63 matches
Mail list logo
