On Mon, 30 Mar 2015 06:27:13 -0300, Adam X wrote:
read exec environment (prod, read, dev, local)
detect all files with above extension (.prod .read .dev .local)
read properties from every file
contribute key as symbol, value as value
Have you seen
http://tapestry.apache.org/configuration.ht
Okay - implemented environmental property loader translation mechanism to
symbol contribution. All works well. For completeness of this thread, in a
nutshell:
/**
* Valid values for deploy environment hosting a running code. One of these
* values is passed as JVM arg via {@link
JvmArgugments#DEP
What I mean we do not want have as tightly coupled code with things like
EjbProviderEnum and BusinessServicesLocator with if-then for each
container's JNDI format - and we'd like to keep it this way. Rather we
would like to externalize these things (JNDIs, idealy into property files
somehow transla
I'm not sure I understand your question, but see if BusinessServicesLocator in
the example is what you're after:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/state/atejb
BTW, this isn't just theoretical. I develop with OpenEJB but usually deploy in
JBoss - eg. the JumpStar
We have a different way of hooking up EJBs, and it and works great - that's
not the issue. Our EJBs are further decoupled from Tapestry that what
Jumpstart has done and we prefer to keep it this way. We just need a way of
telling tapestry that for this environment we have a this set of ejb
properti
For T5.4: http://jumpstart.doublenegative.com.au/jumpstart7/examples/state/atejb
Soon I'll modify EJBProviderUtil to read a system property provided at runtime
(eg. -Djumpstart.ejb-provider=OPENEJB_4_LOCAL), because it's getting too hard
to keep EJBProviderUtil's detection technique working reli
http://jumpstart.doublenegative.com.au/jumpstart/
&
http://jumpstart.doublenegative.com.au/jumpstart/examples/state/atejb
Download jumpstart and have a look how Geoff has done it.
On Mon, 30 Mar 2015 19:34:29 +1100, Adam X wrote:
Hi,
I have a different JNDI lookup depending on exec en
Hi,
I have a different JNDI lookup depending on exec env. I have an AppModule
with EJB sub:
@SubModule(EjbModule.class)
AppModule
And my EJB mod does all the EJB plumbing building the context and
delegating the looking up of EJBs to EjbLocatorModule. As far as building
my beans I would like to i
