Eclipse Community Forums: Eclipse Scout

Home » Eclipse Projects » Eclipse Scout » Scout and E4?

Wed, 05 May 2010 05:56

Eclipse User

Hi,

I noticed in your Wiki examples an example using FilterConfigInjection.

E4 is quoted several times in the proposal. and as you know, parts of E4 use
JSR-330 (DI Standard) already.
So what are the plans for Scout in this direction? Are you working to get
@Inject into such examples, too?
Using the class here makes a very familiar impression on people who worked
with Guice and/or other DI frameworks anyway ;-)

Werner

Re: Scout and E4? [message #531569 is a reply to message #531521]

Wed, 05 May 2010 08:48

Eclipse User

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 ?

What are the plans for e4 with respect to osgi services DI and server-side equinox (if any) ?

Re: Scout and E4? [message #532109 is a reply to message #531569]

Fri, 07 May 2010 04:25

Eclipse User

"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 #532110 is a reply to message #532109]

Fri, 07 May 2010 04:28

Eclipse User

P.s.: I was just trying to point a TA Exec (responsible for the CRM project
I mentioned with loads of interesting concepts, Logging via Apache MINA and
SWT PageFlows are the only 2 I wanna mention, since they are based on
neutral concepts or Open Source technologies)

Finding, the list of Eclipse projects under Technology doesn't even "know"
Scout ?!

Please fix that, else people really think it doesn't exist or is some kind
of "Area 51" within Eclipse ;-)

Re: Scout and E4? [message #541808 is a reply to message #532110]

Tue, 22 June 2010 11:13

Eclipse User

"Area 51" issue finally fixed, thanks Wink