"alesj" wrote : Why would we have something like this in MC?
Isn't it MC which knows how to treat that the "jndi:" prefix defines a
dependency upon a JNDI entry?
Otherwise it's just some magic string?
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=419
"ALRubinger" wrote : Is there an equivalent to my DEPENDS_JNDI_PREFIX
(=="jndi:") so I don't have to define it myself?
|
Not to my knowledge.
But/and why would we have something like this in MC?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197273#419727
Nice.
public class AbstractEjbReferenceValueMetadata extends
AbstractDependencyValueMetaData
...and...
/**
| * Used in defining the dependency
| */
|@Override
|public Object getUnderlyingValue()
|{
| return DEPENDS_JNDI_PREFIX + this.getTargetJndiName();
"ALRubinger" wrote :
| Possible? This is so that the target value is available before I inject
via an annotation plugin.
|
Sure, we do it all the time.
Check AbstractDependencyValueMetaData on how it's done.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p
