|
|
Re: Scout and E4? [message #532109 is a reply to message #531569] |
Fri, 07 May 2010 08:25 |
Werner Keil Messages: 1087 Registered: July 2009 |
Senior Member |
|
|
"Ivan" <ivan.motsch@bsiag.com> schrieb im Newsbeitrag
news:hrrpfr$8ff$1@build.eclipse.org...
> Hi Werner,
>
> thanks for the input. Yes, we are focusing on DI concepts.
> However so far we felt not ready to get set with a certain DI
> implementation. As with regard to JSR-330 eclipse scout is open to such
> annotations as it bases on plain java coding concepts.
> The issues we face are not in the specification of jsr 330 but in the
> field of Injector (implementations):
> - server side: java ee 6 has DI, server-side equinox has not (yet), how
> can these be combined?
> - server side: server-side equinox stand-alone, what injector impl should
> be used / can be used, what is planned there?
> - gui side: DI in forms (IForm) and pages (IPage) are solved for now using
> the scout "getConfigured" and "exec" methods with annotations therefor.
> This way scout in fact creates a base for later DI capabilities without
> change of existing code.
>
> Do you know CDI/WELD ?
Sure, I was among those reviewing and accepting it at JCP (EC member ;-)
Plus I'm also in JSR-316, the Java EE 6 Umbrella.
Which is why our Spec Lead there (or legal departments at least while it was
still Sun) is pretty sensitive to terms like J2EE or JEE ;-)
> What are the plans for e4 with respect to osgi services DI and server-side
> equinox (if any) ?
Please ask Boris Bokovski from E4, he's both in the 330 EG and leads part of
E4
Werner
|
|
|
|
|
|
|
Re: Scout and E4? [message #580497 is a reply to message #580486] |
Fri, 07 May 2010 08:25 |
Werner Keil Messages: 1087 Registered: July 2009 |
Senior Member |
|
|
"Ivan" <ivan.motsch@bsiag.com> schrieb im Newsbeitrag
news:hrrpfr$8ff$1@build.eclipse.org...
> Hi Werner,
>
> thanks for the input. Yes, we are focusing on DI concepts.
> However so far we felt not ready to get set with a certain DI
> implementation. As with regard to JSR-330 eclipse scout is open to such
> annotations as it bases on plain java coding concepts.
> The issues we face are not in the specification of jsr 330 but in the
> field of Injector (implementations):
> - server side: java ee 6 has DI, server-side equinox has not (yet), how
> can these be combined?
> - server side: server-side equinox stand-alone, what injector impl should
> be used / can be used, what is planned there?
> - gui side: DI in forms (IForm) and pages (IPage) are solved for now using
> the scout "getConfigured" and "exec" methods with annotations therefor.
> This way scout in fact creates a base for later DI capabilities without
> change of existing code.
>
> Do you know CDI/WELD ?
Sure, I was among those reviewing and accepting it at JCP (EC member ;-)
Plus I'm also in JSR-316, the Java EE 6 Umbrella.
Which is why our Spec Lead there (or legal departments at least while it was
still Sun) is pretty sensitive to terms like J2EE or JEE ;-)
> What are the plans for e4 with respect to osgi services DI and server-side
> equinox (if any) ?
Please ask Boris Bokovski from E4, he's both in the 330 EG and leads part of
E4
Werner
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05103 seconds