+1, good for both projects. And to reply to a comment in the original email
- I'm not sure that we really need an explicit vote for this can just assume
from all the positive comments so far and lazy consensus that its fine
unless someone complains (which i'm sure they wont).
...ant
On Tue,
Hi Simon,
Thanks for your elaborate answer.
It's good to hear that these topics are work in progress!
This is my view of where we are.
Service lookup - We are moving to a domain model now that
doesn't rely on service lookup internally. If you take a look
at the workspace code and
Hi Daniel.
Some more comments inline
Simon
On Wed, Apr 9, 2008 at 5:25 PM, [EMAIL PROTECTED] wrote:
Hi Simon,
Thanks for your elaborate answer.
It's good to hear that these topics are work in progress!
This is my view of where we are.
Service lookup - We are moving to a domain
Stéphane Drapeau wrote:
Hi,
I created an entry [0] in the Eclipse bugzilla with the proposal.
Your comments are welcome.
Best regards
Stéphane Drapeau
Obeo
[0]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=225956
The proposal looks pretty good to me. I have a few comments/questions:
-
I am curious why the destroy method was not called for @Scope(REQUEST).
Service Definition:
=
@Scope(REQUEST)
public class AServiceImpl implements AService {
@Init
public void init() {
System.out.println(init());
}
@Destroy
public void destroy() {
haleh mahbod wrote:
1 - [] Put V2 doc changes in V1 pages and mark them as such
2 - [] Create SCA Java 1.x/ SCA Java 2.x documentation pages on our current
site wiki
3 - [] Create separate SCA Java 1.x/ SCA Java 2.x wiki spaces
Option 2 seems reasonable. Option 3 can be considered in the
Hi,
It seems to be a bug. The @Init method should be called upon the end of the
scope. For request, it's the thread. Can you open a JIRA to track it?
Thanks,
Raymond
--
From: Gilbert Kwan [EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 12:26
On Thu, Apr 10, 2008 at 8:36 AM, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
It seems to be a bug. The @Init method
You mean the @Destroy method!
should be called upon the end of the scope. For request, it's the thread.
Can you open a JIRA to track it?
Thanks,
Raymond
I have noticed that the approach we used for GSoC, where we described
small project ideas, with a proper description and a suggested
scenario to guide the development of the idea is generating much more
interest from the community.
I'd like us to keep on this path, and I have created a page for