Sorry,
was on holidays. Should I still fill in a Jira issue to keep track of it?
Regards,
Karsten
On Fri, Jun 27, 2008 at 10:33 PM, David Blevins [EMAIL PROTECTED] wrote:
In general, we don't check isAssignable on injection types, primarily cause
it gets very hairy around business
On Jul 5, 2008, at 2:06 PM, Jacek Laskowski wrote:
On Fri, Jun 27, 2008 at 10:33 PM, David Blevins [EMAIL PROTECTED]
wrote:
In general, we don't check isAssignable on injection types,
primarily cause
it gets very hairy around business interfaces. But we could probably
support this
On Fri, Jun 27, 2008 at 10:33 PM, David Blevins [EMAIL PROTECTED] wrote:
In general, we don't check isAssignable on injection types, primarily cause
it gets very hairy around business interfaces. But we could probably
support this particular use case.
I think we have to as 16.15 EJBContext
Hi,
I can inject the session context successfully with:
@Resource
private SessionContext ctx;
But when I only what to have the EJBContext
@Resource
private EJBContext ctx;
it cannot be injected.
Is this intended? Well, SessionContext is fine, but I was wondering why
the super
On Jun 27, 2008, at 7:24 AM, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi,
I can inject the session context successfully with:
@Resource
private SessionContext ctx;
But when I only what to have the EJBContext
@Resource
private EJBContext ctx;
it cannot be injected.
Is
