Arjan, thanx for feedback.
Currently, the JIRA is not accessible so I can't read the comments.
I think REST or SOAP can't replace the current EJB remote model.
I think transaction propagation feature is very important, current WS-Tx specs are too heavy (SOAP itself is heavy) and are not suitable protocol for heavy object processing.
(My opinion is that even REST is suitable for some coarse granularity operations)
Java EE are about middlewares and the fine granularity functions will be implemented in POJOs, and IMHO we need seamless and high performance options. But I'm not sure if we should standardize on that.
Lambda can have much relevance with EE concurrency the new spec emerged in Java EE 7.
I think Java EE 8 can (or should) have more options on parallel stream which Java SE 8 does not provide and more parallel/aggregate functions can be supported in EE 8.
Regards
Yoon Kyung Koo
--
--------------------
Software Innovation Driver
Researcher & Executive Director / WAS Lab / TmaxSoft R&D Center
PGP http://www.javadom.com/personal/yoonforhatgmaildotcom.asc
2013. 9. 25., 오후 2:43, arjan tijms <arjan.tijms_at_gmail.com> 작성:
>
> Hi,
>
> On Tue, Sep 24, 2013 at 11:46 PM, Yoon Kyung Koo <kyungkoo_yoon_at_tmax.co.kr> wrote:
>
> 1. CDI and EJB
> In the long term, the whole EJB features can be replaced by CDI.
> Currently, only the distributed (or remote) object model cannot be replaced by CDI.
> I think if Clustered or Distributed CDI bean is possible and can be standardized, then the old EJB model can be removed.
>
> In this light it's maybe interesting to note that the spec lead Bill Shannon has suggested moving away from the binary remote object model, and exclusively using REST (JAX-RS) and SOAP (JAX-WS) instead. See https://java.net/jira/browse/JAVAEE_SPEC-16
>
> As I mentioned in that JIRA issue, I'd personally rather see a native high performance and convenient/transparent distributed object model for Java to Java solutions, and then have JAX-RS as an option for interoperability between Java and non-Java solutions, or between less tightly coupled Java solutions.
>
> Upgrading the remoting support of EJB is not worth it at this point anymore, but I agree with Yoon that moving the component model to CDI offers new opportunities to standardize a modern (native) interoperability facility.
>
>
> 4. lambda support
> I didn't think much about the lambda support of Java EE 8 platform, but it would be a great challenge.
>
> It would be a challenge indeed, but there are several opportunities throughout the platform.
>
> In JSF for example it would be ideal for several of the tree visiting APIs or for running a (small) amount of code within its own scope. In OmniFaces for example we have a utility method that would be perfectly suited for lambdas that does exactly that (see https://code.google.com/p/omnifaces/source/browse/src/org/omnifaces/el/ScopedRunner.java#60).
>
> For event handling they would be great as well. In OmniFaces again we're already using a lambda like construct for that, see e.g. https://code.google.com/p/omnifaces/source/browse/src/org/omnifaces/util/Events.java#95
>
> We're using this as follows now:
>
> Events.addBeforePhaseListener(PROCESS_VALIDATIONS, new Callback.Void() {
>
> @Override
> public void invoke() {
> if (Components.hasInvokedSubmit(parent)) {
> Faces.setContextAttribute(IgnoreValidationFailed.class.getName(), true);
> }
> }
> });
>
> (see https://code.google.com/p/omnifaces/source/browse/src/org/omnifaces/taghandler/IgnoreValidationFailed.java#92)
>
> Such code will look much better when using lambdas. I think I would be great to have such API taking lambdas readily available in Java EE.
>
> Kind regards,
> Arjan Tijms
>
>
>
>
>
>
> Have a great time, everyone.
>
> Regards,
> Yoon Kyung Koo (TmaxSoft)
>
> --
> --------------------
> Software Innovation Driver
> Researcher & Executive Director / WAS Lab / TmaxSoft R&D Center
> PGP http://www.javadom.com/personal/yoonforhatgmaildotcom.asc
>
>
>
>
>
> 2013. 9. 11., 오후 4:30, Linda DeMichiel <linda.demichiel_at_oracle.com> 작성:
>
>>
>> Greetings,
>>
>> As requested, we've reserved a spot where we can meet up
>> at JavaOne to talk about ideas for Java EE 8.
>>
>> We've reserved the Lombard room in Parc 55 on Wednesday Sept 25
>> for a 2:30-4:30 meeting.
>>
>> While we're not limiting attendance to Expert Group members, the room
>> itself is of limited size, so please let us know if you are planning
>> to attend.
>>
>> We're expecting that the first item for the meeting will be to
>> converge on the meeting agenda. As another item (possibly to get the
>> ball rolling), we'd like to suggest that we discuss the wish-lists
>> that were posted to the group earlier, namely:
>>
>> http://arjan-tijms.blogspot.de/2013/07/java-ee-8-wish-list.html
>> and
>> http://antoniogoncalves.org/2013/07/18/java-ee-8-whislist/
>>
>> thanks,
>>
>> -Linda
>>
>
>