IMO, the @Context annotation allows an SCA Java component to receive injection
of some contexts which cannot be modeled as a regular @Reference. In my use
cases, I would like to be able to do something like:
@Context
private ServletContext servletContext; // My component is running as part of
Raymond,
Can you explain why you prefer strobgly types context extensions?
Why is this JAX-RS mechanism a good thing?
Can you paint a picture of what this would look like:
a) for the application components
b) for the runtime/binding components
Yours, Mike.
On 15/07/2011 17:35, Raymond Feng
Raymond Feng wrote:
I prefer to have strongly-typed context extensions. JAX-RS has the
similar mechanism to allow custom context to be injected via @Context.
The context can be resolved via:
*http://jsr311.java.net/nonav/javadoc/javax/ws/rs/ext/ContextResolver.html*
*
*
+1 for this, if we can
Simon Laws wrote:
On Fri, Jul 15, 2011 at 12:42 PM, Mike Edwards
wrote:
On 15/07/2011 12:08, Simon Laws wrote:
Commenting on the last two posts. Generally I prefer the strong typing
of context and the ability to have that type injected into an
implementation. I do though accept that there is n
I prefer to have strongly-typed context extensions. JAX-RS has the similar
mechanism to allow custom context to be injected via @Context. The context can
be resolved via:
http://jsr311.java.net/nonav/javadoc/javax/ws/rs/ext/ContextResolver.html
Thanks,
Raymond
__
Simon,
Commentary inline...
On 15/07/2011 13:38, Simon Laws wrote:
On Fri, Jul 15, 2011 at 12:42 PM, Mike Edwards
wrote:
On 15/07/2011 12:08, Simon Laws wrote:
Commenting on the last two posts. Generally I prefer the strong typing
of context and the ability to have that type injected into
On Fri, Jul 15, 2011 at 12:42 PM, Mike Edwards
wrote:
> On 15/07/2011 12:08, Simon Laws wrote:
>>
>> Commenting on the last two posts. Generally I prefer the strong typing
>> of context and the ability to have that type injected into an
>> implementation. I do though accept that there is no API al
On 15/07/2011 12:08, Simon Laws wrote:
Commenting on the last two posts. Generally I prefer the strong typing
of context and the ability to have that type injected into an
implementation. I do though accept that there is no API alternative to
injection for anything other than RequestContext or d
On Fri, Jul 15, 2011 at 11:36 AM, Mike Edwards
wrote:
>>
>> PS Next I think we should look at context information being passed from
>> the application code to the
>> code involved in a reference invocation...
>>
> Folks,
>
> OK, time to delve into this piece of function.
>
> The basic capability o
PS Next I think we should look at context information being passed from the
application code to the
code involved in a reference invocation...
Folks,
OK, time to delve into this piece of function.
The basic capability of both ComponentContext and RequestContext is to supply information to an
[
https://issues.apache.org/jira/browse/TUSCANY-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065786#comment-13065786
]
Simon Laws commented on TUSCANY-3898:
-
Hi Guilherme.
I committed this patch but su
On Wed, Jul 13, 2011 at 3:01 PM, Simon Laws wrote:
> On Wed, Jul 13, 2011 at 2:44 PM, Mike Edwards
> wrote:
>> Folks,
>>
>> I understand that there are some problems with the standard OASIS Java
>> Client API that are affecting Tuscany.
>>
>> I'd be grateful if people who know about these problem
On Fri, Jul 15, 2011 at 3:15 AM, Guilherme Moraes Armigliatto (JIRA)
wrote:
>
> [
> https://issues.apache.org/jira/browse/TUSCANY-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Guilherme Moraes Armigliatto updated TUSCANY-3898:
> --
13 matches
Mail list logo
