[jbossdeveloper] Update JBoss Developer Materials to Java EE 7

[Pete Muir]

Looks good!

> On 2 Dec 2014, at 10:57, Rafael Benevides <benevides at redhat.com> wrote:
> 
> Thanks Arun!
> 
> Updated!
> 
> On 12/1/14 19:29, Arun Gupta wrote:
>> Good one!
>> 
>> "designed to be run on Red Hat JBoss Enterprise Application Platform 7" can be confusing.
>> Change "Wildfly" to "WildFly"
>> Change "Java SDK 6.0" to "JDK 7.0" - this is a requirement for WildFly anyway.
>> 
>> Arun
>> 
>> On Mon, Dec 1, 2014 at 6:43 AM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>> Hi all,
>> 
>> I'm pleased to announce that we have now the first Java EE 7 feature shown as a JBoss Developer Quickstart: JDF-765 - Websocket server endpoint - https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint <https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint>
>> 
>> It is published at http://websocket-benevides.rhcloud.com <http://websocket-benevides.rhcloud.com/> if you want to try it.
>> 
>> 
>> 
>> On 9/9/14 01:29, Arun Gupta wrote:
>>> Hi Rafael,
>>> 
>>> If you are looking for the top 5 features that should be highlighted in Java EE 7, then they would be:
>>> 
>>> - WebSocket server endpoint
>>> - Chunk style batch processing
>>> - Object-based JSON generation and Stream-based JSON consuming
>>> - ManagedExecutorService
>>> - JAX-RS Client API
>>> 
>>> There are samples for each one of these at:
>>> 
>>> https://github.com/javaee-samples/javaee7-samples <https://github.com/javaee-samples/javaee7-samples>
>>> 
>>> I had some basic discussions with Vineet last week on where some of these usecases can be incorporated in Ticket Monster. Please keep me involved in the design of how TiMo is going to evolve for Java EE 7 support. Some of the documents that would be very useful from that process are:
>>> 
>>> - How to migrate an existing Java EE 6 application to EE 7 ? This would be very useful to our customers as well.
>>> - Compare LOC/deployment descriptors between the EE 6 and 7 versions. These would make nice graphs.
>>> - Before/after code fragment for different pieces that were migrated.
>>> - What proprietary technologies were replaced with standards-based when using EE 7
>>> 
>>> Cheers
>>> Arun
>>> 
>>> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>> Returning the discussion about JBoss Developer Material for Java EE 7,
>>> 
>>> Arun,
>>> 
>>> Do you have the list of the 5 features/use cases/quickstarts that we want to show, right?  Can you share it? 
>>> 
>>> Thanks
>>> 
>>> Em 8/25/14, 9:25, Rafael Benevides escreveu:
>>>> Hi All,
>>>> 
>>>> We're about to start the update process of JBoss Developer Materials to Java EE 7. But before put the hands on it I talked with Pete and we decided that it's better to bring this $subject to discussion with everyone on this list.
>>>> 
>>>> Ticket Monster already started to be updated https://issues.jboss.org/browse/JDF-754 <https://issues.jboss.org/browse/JDF-754>
>>>> 
>>>> Actually our jboss-eap-quickstarts have been updated to Java EE 7.0 on https://github.com/wildfly/quickstart <https://github.com/wildfly/quickstart>. Anyway we still miss some Java EE 7 specific features/use cases on these quickstarts.
>>>> 
>>>> It seems that Arun Gupta has a list of about 5 features/use cases/quickstarts that we want to show. The idea is to have these Java EE 7 specific quickstarts to be available at www.jboss.org <http://www.jboss.org/>
>>>> 
>>>> The main point that we should discuss are:
>>>> 
>>>> - What are those quickstarts/features?
>>>> - Where will we host those Java EE 7 quickstarts?  https://github.com/jboss-developer/jboss-sandbox-quickstarts <https://github.com/jboss-developer/jboss-sandbox-quickstarts> ?
>>>> - Paul Robinson, 
>>>> 
>>>> Considering that the jboss-sandbox-quickstarts github structure, do you think that it could have any issues with it? Can we choose just specific quickstarts to be present at www.jboss.org <http://www.jboss.org/>
>>>> 
>>>> Well,
>>>> 
>>>> This is just a starting point, so we can discuss about this update process until we have a detailed plan.
>>>> 
>>>> The Google docs with the plan is available at: https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit <https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit>
>>>> 
>>>> 
>>>> -- 
>>>> 
>>>> Rafael Benevides | Senior Software Engineer
>>>> JBoss Developer
>>>> M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>> 
>>>> <Mail Attachment.jpeg>
>>>> 
>>>> Better technology. Faster innovation. Powered by community collaboration. 
>>>> See how it works at www.redhat.com <http://www.redhat.com/> 
>>>> 
>>>> <Mail Attachment.png> <http://www.linkedin.com/company/3258288> <Mail Attachment.png> <https://www.youtube.com/redhatlatam>
>>>> 
>>>>  _______________________________________________
>>>> jbossdeveloper mailing list
>>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
>>> 
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
>>> 
>>> 
>>> 
>>> -- 
>>> http://blog.arungupta.me <http://blog.arungupta.me/>
>>> http://twitter.com/arungupta <http://twitter.com/arungupta>
>> 
>> 
>> 
>> -- 
>> http://blog.arungupta.me <http://blog.arungupta.me/>
>> http://twitter.com/arungupta <http://twitter.com/arungupta>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141202/4da185ba/attachment.html