From vpereira at redhat.com  Mon Mar  2 05:04:26 2015
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Mon, 2 Mar 2015 05:04:26 -0500 (EST)
Subject: [jbossdeveloper] Ticket Monster session replication
In-Reply-To: <54F093CB.3000209@redhat.com>
References: <54F08345.2030506@redhat.com>
	<1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com>
	<54F093CB.3000209@redhat.com>
Message-ID: <960867861.29909577.1425290666284.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Rafael Benevides" <benevides at redhat.com>
> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>
> Cc: jbossdeveloper at lists.jboss.org
> Sent: Friday, February 27, 2015 9:26:59 PM
> Subject: Re: Ticket Monster session replication
> 
> " I am working on demonstrating scaling of TicketMonster using a
> Kubernetes+WildFly+(MySQL/Postgres)+HAProxy"
> 
> Me too :)
> 
> Let's chat about this when you have a chance.

Anytime will do. Let's use IRC or Google Hangouts.

For the record, I've gotten a sample clustering app to work on a WildFly cluster running on Kubernetes, using the help of this article:
http://mluksa.blogspot.in/2015/01/deploying-wildfly-cluster-on-openshift_7.html

I dont intend to use OpenShift yet, because of one outstanding issue involving Kubernetes - autoregistering changes in the cluster with an upstream loadbalancer. You wouldn't run into this issue with OpenShift and other cloud platforms like GCE that use Kubernetes, since the load balancers on such platforms would be informed of changes to the cluster. But with Kubernetes alone, this becomes an issue, since you need to hand rig code to add or remove IP routes to Docker instances from the upstream load balancer.

There are a few ways to solve this:

* For a very small and static cluster configuration, manually register the IP addresses of the cluster with HAProxy or nginx. This approach obviously doesn't scale since it is manual for the most part.
* Automate the registration and discovery process for the load balancer. To do this, use etcd (the distributed key-value store in k8s) to store changes to the infrastructure. Read them in the upstream load balancer; assuming nginx, you can use nginx in conjunction with confd. As an example, refer: http://brianketelsen.com/2014/02/25/using-nginx-confd-and-docker-for-zero-downtime-web-updates/
* Or look at something more sophisticated like vulcand. vulcand is not considered production-ready by most people. But that looks to be the future. As an example refer: http://www.recorditblog.com/post/how-to-create-a-web-scale-infrastructure-based-on-docker-coreos-vulcand-and-mesos-and-why-object-storage-becomes-the-de-facto-data-repository/

I'm evaluating points 2 and 3 wrt TicketMonster. I may eventually look at Ceph (as an object storage platform) in the context of vulcand, but that is not a priority for me at the moment.

> 
> On 2/27/15 10:54, Vineet Reynolds Pereira wrote:
> > Hi Rafael,
> >
> >     I believe it should be, when you use MySQL or PostgreSQL as the
> >     database. Avoid H2 (the default DB) since each DB instance would not
> >     be shared across EAP instances. I'll verify whether the proposed
> >     config works flawlessly over the weekend, as I am working on
> >     demonstrating scaling of TicketMonster using a
> >     Kubernetes+WildFly+(MySQL/Postgres)+HAProxy.
> >
> > Vineet
> >
> >
> > ----- Original Message -----
> >> From: "Rafael Benevides" <benevides at redhat.com>
> >> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>,
> >> jbossdeveloper at lists.jboss.org
> >> Sent: Friday, February 27, 2015 8:16:29 PM
> >> Subject: Ticket Monster session replication
> >>
> >> Hi all,
> >>
> >> I'm preparing a presentation demo using Ticket Monster and I'd like to
> >> demonstrate a  failover cluster.
> >>
> >> Is TM capable of session replication ? I mean: Did someone already
> >> tested if enabling it through <distributable /> element would be
> >> sufficient for TM without any other source code modification ?
> >>
> >> --
> >>
> >> *Rafael Benevides | Senior Software Engineer*
> >> JBoss Developer
> >> M: +1-919-592-6255
> >>
> >> Red Hat
> >>
> >> Better technology. Faster innovation. Powered by community collaboration.
> >> See how it works at www.redhat.com <http://www.redhat.com/>
> >>
> >> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
> >> <https://www.youtube.com/redhatlatam>
> >>
> 
> 

From benevides at redhat.com  Mon Mar  2 15:14:39 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 02 Mar 2015 15:14:39 -0500
Subject: [jbossdeveloper] Ticket Monster session replication
In-Reply-To: <960867861.29909577.1425290666284.JavaMail.zimbra@redhat.com>
References: <54F08345.2030506@redhat.com>
	<1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com>
	<54F093CB.3000209@redhat.com>
	<960867861.29909577.1425290666284.JavaMail.zimbra@redhat.com>
Message-ID: <54F4C4AF.7040509@redhat.com>

Cool,

At this moment I'm preparing the docker images to them update it to be 
orchestrated through Kubernetes.

I'm using 4 images for the demo:

- DB: Postgres
- Webserver: Apache + modcluster
- Widlfy domain
- n wildfly servers

I'm facing some issues with the DB internal ip change (when db container 
is restarted) but I believe that Kubernetes services can solve this.

I'll keep you informed

On 3/2/15 05:04, Vineet Reynolds Pereira wrote:
>
> ----- Original Message -----
>> From: "Rafael Benevides" <benevides at redhat.com>
>> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>
>> Cc: jbossdeveloper at lists.jboss.org
>> Sent: Friday, February 27, 2015 9:26:59 PM
>> Subject: Re: Ticket Monster session replication
>>
>> " I am working on demonstrating scaling of TicketMonster using a
>> Kubernetes+WildFly+(MySQL/Postgres)+HAProxy"
>>
>> Me too :)
>>
>> Let's chat about this when you have a chance.
> Anytime will do. Let's use IRC or Google Hangouts.
>
> For the record, I've gotten a sample clustering app to work on a WildFly cluster running on Kubernetes, using the help of this article:
> http://mluksa.blogspot.in/2015/01/deploying-wildfly-cluster-on-openshift_7.html
>
> I dont intend to use OpenShift yet, because of one outstanding issue involving Kubernetes - autoregistering changes in the cluster with an upstream loadbalancer. You wouldn't run into this issue with OpenShift and other cloud platforms like GCE that use Kubernetes, since the load balancers on such platforms would be informed of changes to the cluster. But with Kubernetes alone, this becomes an issue, since you need to hand rig code to add or remove IP routes to Docker instances from the upstream load balancer.
>
> There are a few ways to solve this:
>
> * For a very small and static cluster configuration, manually register the IP addresses of the cluster with HAProxy or nginx. This approach obviously doesn't scale since it is manual for the most part.
> * Automate the registration and discovery process for the load balancer. To do this, use etcd (the distributed key-value store in k8s) to store changes to the infrastructure. Read them in the upstream load balancer; assuming nginx, you can use nginx in conjunction with confd. As an example, refer: http://brianketelsen.com/2014/02/25/using-nginx-confd-and-docker-for-zero-downtime-web-updates/
> * Or look at something more sophisticated like vulcand. vulcand is not considered production-ready by most people. But that looks to be the future. As an example refer: http://www.recorditblog.com/post/how-to-create-a-web-scale-infrastructure-based-on-docker-coreos-vulcand-and-mesos-and-why-object-storage-becomes-the-de-facto-data-repository/
>
> I'm evaluating points 2 and 3 wrt TicketMonster. I may eventually look at Ceph (as an object storage platform) in the context of vulcand, but that is not a priority for me at the moment.
>
>> On 2/27/15 10:54, Vineet Reynolds Pereira wrote:
>>> Hi Rafael,
>>>
>>>      I believe it should be, when you use MySQL or PostgreSQL as the
>>>      database. Avoid H2 (the default DB) since each DB instance would not
>>>      be shared across EAP instances. I'll verify whether the proposed
>>>      config works flawlessly over the weekend, as I am working on
>>>      demonstrating scaling of TicketMonster using a
>>>      Kubernetes+WildFly+(MySQL/Postgres)+HAProxy.
>>>
>>> Vineet
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Rafael Benevides" <benevides at redhat.com>
>>>> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>,
>>>> jbossdeveloper at lists.jboss.org
>>>> Sent: Friday, February 27, 2015 8:16:29 PM
>>>> Subject: Ticket Monster session replication
>>>>
>>>> Hi all,
>>>>
>>>> I'm preparing a presentation demo using Ticket Monster and I'd like to
>>>> demonstrate a  failover cluster.
>>>>
>>>> Is TM capable of session replication ? I mean: Did someone already
>>>> tested if enabling it through <distributable /> element would be
>>>> sufficient for TM without any other source code modification ?
>>>>
>>>> --
>>>>
>>>> *Rafael Benevides | Senior Software Engineer*
>>>> JBoss Developer
>>>> M: +1-919-592-6255
>>>>
>>>> Red Hat
>>>>
>>>> Better technology. Faster innovation. Powered by community collaboration.
>>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>>
>>>> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>> <https://www.youtube.com/redhatlatam>
>>>>
>>


From vpereira at redhat.com  Tue Mar  3 10:30:24 2015
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Tue, 3 Mar 2015 10:30:24 -0500 (EST)
Subject: [jbossdeveloper] Ticket Monster session replication
In-Reply-To: <54F4C4AF.7040509@redhat.com>
References: <54F08345.2030506@redhat.com>
	<1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com>
	<54F093CB.3000209@redhat.com>
	<960867861.29909577.1425290666284.JavaMail.zimbra@redhat.com>
	<54F4C4AF.7040509@redhat.com>
Message-ID: <1153702300.31535604.1425396624933.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Rafael Benevides" <benevides at redhat.com>
> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>
> Cc: jbossdeveloper at lists.jboss.org
> Sent: Tuesday, March 3, 2015 1:44:39 AM
> Subject: Re: Ticket Monster session replication
> 
> Cool,
> 
> At this moment I'm preparing the docker images to them update it to be
> orchestrated through Kubernetes.
> 
> I'm using 4 images for the demo:
> 
> - DB: Postgres
> - Webserver: Apache + modcluster
> - Widlfy domain
> - n wildfly servers
> 
> I'm facing some issues with the DB internal ip change (when db container
> is restarted) but I believe that Kubernetes services can solve this.

A DNS based service discovery helps here. Check out SkyDock (https://github.com/crosbymichael/skydock) and Consul (https://www.consul.io/).

There is also an ambassador pattern for this use case, but it does not solve the problem if you link the client to the ambassador; it is there just to prevent restarting the client when the client to the service (db in this case) goes down. The pattern is documented @ https://docs.docker.com/articles/ambassador_pattern_linking/

> 
> I'll keep you informed
> 
> On 3/2/15 05:04, Vineet Reynolds Pereira wrote:
> >
> > ----- Original Message -----
> >> From: "Rafael Benevides" <benevides at redhat.com>
> >> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>
> >> Cc: jbossdeveloper at lists.jboss.org
> >> Sent: Friday, February 27, 2015 9:26:59 PM
> >> Subject: Re: Ticket Monster session replication
> >>
> >> " I am working on demonstrating scaling of TicketMonster using a
> >> Kubernetes+WildFly+(MySQL/Postgres)+HAProxy"
> >>
> >> Me too :)
> >>
> >> Let's chat about this when you have a chance.
> > Anytime will do. Let's use IRC or Google Hangouts.
> >
> > For the record, I've gotten a sample clustering app to work on a WildFly
> > cluster running on Kubernetes, using the help of this article:
> > http://mluksa.blogspot.in/2015/01/deploying-wildfly-cluster-on-openshift_7.html
> >
> > I dont intend to use OpenShift yet, because of one outstanding issue
> > involving Kubernetes - autoregistering changes in the cluster with an
> > upstream loadbalancer. You wouldn't run into this issue with OpenShift and
> > other cloud platforms like GCE that use Kubernetes, since the load
> > balancers on such platforms would be informed of changes to the cluster.
> > But with Kubernetes alone, this becomes an issue, since you need to hand
> > rig code to add or remove IP routes to Docker instances from the upstream
> > load balancer.
> >
> > There are a few ways to solve this:
> >
> > * For a very small and static cluster configuration, manually register the
> > IP addresses of the cluster with HAProxy or nginx. This approach obviously
> > doesn't scale since it is manual for the most part.
> > * Automate the registration and discovery process for the load balancer. To
> > do this, use etcd (the distributed key-value store in k8s) to store
> > changes to the infrastructure. Read them in the upstream load balancer;
> > assuming nginx, you can use nginx in conjunction with confd. As an
> > example, refer:
> > http://brianketelsen.com/2014/02/25/using-nginx-confd-and-docker-for-zero-downtime-web-updates/
> > * Or look at something more sophisticated like vulcand. vulcand is not
> > considered production-ready by most people. But that looks to be the
> > future. As an example refer:
> > http://www.recorditblog.com/post/how-to-create-a-web-scale-infrastructure-based-on-docker-coreos-vulcand-and-mesos-and-why-object-storage-becomes-the-de-facto-data-repository/
> >
> > I'm evaluating points 2 and 3 wrt TicketMonster. I may eventually look at
> > Ceph (as an object storage platform) in the context of vulcand, but that
> > is not a priority for me at the moment.
> >
> >> On 2/27/15 10:54, Vineet Reynolds Pereira wrote:
> >>> Hi Rafael,
> >>>
> >>>      I believe it should be, when you use MySQL or PostgreSQL as the
> >>>      database. Avoid H2 (the default DB) since each DB instance would not
> >>>      be shared across EAP instances. I'll verify whether the proposed
> >>>      config works flawlessly over the weekend, as I am working on
> >>>      demonstrating scaling of TicketMonster using a
> >>>      Kubernetes+WildFly+(MySQL/Postgres)+HAProxy.
> >>>
> >>> Vineet
> >>>
> >>>
> >>> ----- Original Message -----
> >>>> From: "Rafael Benevides" <benevides at redhat.com>
> >>>> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>,
> >>>> jbossdeveloper at lists.jboss.org
> >>>> Sent: Friday, February 27, 2015 8:16:29 PM
> >>>> Subject: Ticket Monster session replication
> >>>>
> >>>> Hi all,
> >>>>
> >>>> I'm preparing a presentation demo using Ticket Monster and I'd like to
> >>>> demonstrate a  failover cluster.
> >>>>
> >>>> Is TM capable of session replication ? I mean: Did someone already
> >>>> tested if enabling it through <distributable /> element would be
> >>>> sufficient for TM without any other source code modification ?
> >>>>
> >>>> --
> >>>>
> >>>> *Rafael Benevides | Senior Software Engineer*
> >>>> JBoss Developer
> >>>> M: +1-919-592-6255
> >>>>
> >>>> Red Hat
> >>>>
> >>>> Better technology. Faster innovation. Powered by community
> >>>> collaboration.
> >>>> See how it works at www.redhat.com <http://www.redhat.com/>
> >>>>
> >>>> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
> >>>> <https://www.youtube.com/redhatlatam>
> >>>>
> >>
> 
> 

From benevides at redhat.com  Tue Mar  3 10:32:48 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 03 Mar 2015 10:32:48 -0500
Subject: [jbossdeveloper] Ticket Monster session replication
In-Reply-To: <1153702300.31535604.1425396624933.JavaMail.zimbra@redhat.com>
References: <54F08345.2030506@redhat.com>
	<1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com>
	<54F093CB.3000209@redhat.com>
	<960867861.29909577.1425290666284.JavaMail.zimbra@redhat.com>
	<54F4C4AF.7040509@redhat.com>
	<1153702300.31535604.1425396624933.JavaMail.zimbra@redhat.com>
Message-ID: <54F5D420.4010501@redhat.com>

Awesome tip.

Thanks Vineet. I'll start to evaluate all possible solutions today!

On 3/3/15 10:30, Vineet Reynolds Pereira wrote:
>
> ----- Original Message -----
>> From: "Rafael Benevides" <benevides at redhat.com>
>> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>
>> Cc: jbossdeveloper at lists.jboss.org
>> Sent: Tuesday, March 3, 2015 1:44:39 AM
>> Subject: Re: Ticket Monster session replication
>>
>> Cool,
>>
>> At this moment I'm preparing the docker images to them update it to be
>> orchestrated through Kubernetes.
>>
>> I'm using 4 images for the demo:
>>
>> - DB: Postgres
>> - Webserver: Apache + modcluster
>> - Widlfy domain
>> - n wildfly servers
>>
>> I'm facing some issues with the DB internal ip change (when db container
>> is restarted) but I believe that Kubernetes services can solve this.
> A DNS based service discovery helps here. Check out SkyDock (https://github.com/crosbymichael/skydock) and Consul (https://www.consul.io/).
>
> There is also an ambassador pattern for this use case, but it does not solve the problem if you link the client to the ambassador; it is there just to prevent restarting the client when the client to the service (db in this case) goes down. The pattern is documented @ https://docs.docker.com/articles/ambassador_pattern_linking/
>
>> I'll keep you informed
>>
>> On 3/2/15 05:04, Vineet Reynolds Pereira wrote:
>>> ----- Original Message -----
>>>> From: "Rafael Benevides" <benevides at redhat.com>
>>>> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>
>>>> Cc: jbossdeveloper at lists.jboss.org
>>>> Sent: Friday, February 27, 2015 9:26:59 PM
>>>> Subject: Re: Ticket Monster session replication
>>>>
>>>> " I am working on demonstrating scaling of TicketMonster using a
>>>> Kubernetes+WildFly+(MySQL/Postgres)+HAProxy"
>>>>
>>>> Me too :)
>>>>
>>>> Let's chat about this when you have a chance.
>>> Anytime will do. Let's use IRC or Google Hangouts.
>>>
>>> For the record, I've gotten a sample clustering app to work on a WildFly
>>> cluster running on Kubernetes, using the help of this article:
>>> http://mluksa.blogspot.in/2015/01/deploying-wildfly-cluster-on-openshift_7.html
>>>
>>> I dont intend to use OpenShift yet, because of one outstanding issue
>>> involving Kubernetes - autoregistering changes in the cluster with an
>>> upstream loadbalancer. You wouldn't run into this issue with OpenShift and
>>> other cloud platforms like GCE that use Kubernetes, since the load
>>> balancers on such platforms would be informed of changes to the cluster.
>>> But with Kubernetes alone, this becomes an issue, since you need to hand
>>> rig code to add or remove IP routes to Docker instances from the upstream
>>> load balancer.
>>>
>>> There are a few ways to solve this:
>>>
>>> * For a very small and static cluster configuration, manually register the
>>> IP addresses of the cluster with HAProxy or nginx. This approach obviously
>>> doesn't scale since it is manual for the most part.
>>> * Automate the registration and discovery process for the load balancer. To
>>> do this, use etcd (the distributed key-value store in k8s) to store
>>> changes to the infrastructure. Read them in the upstream load balancer;
>>> assuming nginx, you can use nginx in conjunction with confd. As an
>>> example, refer:
>>> http://brianketelsen.com/2014/02/25/using-nginx-confd-and-docker-for-zero-downtime-web-updates/
>>> * Or look at something more sophisticated like vulcand. vulcand is not
>>> considered production-ready by most people. But that looks to be the
>>> future. As an example refer:
>>> http://www.recorditblog.com/post/how-to-create-a-web-scale-infrastructure-based-on-docker-coreos-vulcand-and-mesos-and-why-object-storage-becomes-the-de-facto-data-repository/
>>>
>>> I'm evaluating points 2 and 3 wrt TicketMonster. I may eventually look at
>>> Ceph (as an object storage platform) in the context of vulcand, but that
>>> is not a priority for me at the moment.
>>>
>>>> On 2/27/15 10:54, Vineet Reynolds Pereira wrote:
>>>>> Hi Rafael,
>>>>>
>>>>>       I believe it should be, when you use MySQL or PostgreSQL as the
>>>>>       database. Avoid H2 (the default DB) since each DB instance would not
>>>>>       be shared across EAP instances. I'll verify whether the proposed
>>>>>       config works flawlessly over the weekend, as I am working on
>>>>>       demonstrating scaling of TicketMonster using a
>>>>>       Kubernetes+WildFly+(MySQL/Postgres)+HAProxy.
>>>>>
>>>>> Vineet
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Rafael Benevides" <benevides at redhat.com>
>>>>>> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>,
>>>>>> jbossdeveloper at lists.jboss.org
>>>>>> Sent: Friday, February 27, 2015 8:16:29 PM
>>>>>> Subject: Ticket Monster session replication
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I'm preparing a presentation demo using Ticket Monster and I'd like to
>>>>>> demonstrate a  failover cluster.
>>>>>>
>>>>>> Is TM capable of session replication ? I mean: Did someone already
>>>>>> tested if enabling it through <distributable /> element would be
>>>>>> sufficient for TM without any other source code modification ?
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *Rafael Benevides | Senior Software Engineer*
>>>>>> JBoss Developer
>>>>>> M: +1-919-592-6255
>>>>>>
>>>>>> Red Hat
>>>>>>
>>>>>> Better technology. Faster innovation. Powered by community
>>>>>> collaboration.
>>>>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>>>>
>>>>>> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>>>> <https://www.youtube.com/redhatlatam>
>>>>>>
>>


From benevides at redhat.com  Tue Mar  3 19:40:11 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 03 Mar 2015 19:40:11 -0500
Subject: [jbossdeveloper] JBoss Developer Materials Jira Reorg
Message-ID: <54F6546B.2030603@redhat.com>

Hi all,

Today I started a cleanup on JDF Jira ( 
https://issues.jboss.org/browse/JDF ).

All unresolved issues were reviewed and most of them were reassigned or 
closed (51 issues). If a Jira was assigned to you, please make sure that 
it still valid or close it otherwise. Thanks Sande for helping me 
closing some very old issues.

Some other issues related to jboss.org (JBossDeveloper) were moved to 
https://issues.jboss.org/browse/DEVELOPER

Actually JBoss Developer Materials should be used to track Quickstarts, 
Archetypes, Stacks (file and client), Ticket-Monster and QSTools. I've 
created new versions that represents its components version. Examples: 
quickstarts-eap-6.4.x, ticket-monster-2.6.x, ticket-monster-2.7.x. That 
way we can identify which version is causing the issue and when it will 
be fixed (hopefully on next version :D ).

This cleanup will ease to track each bug and feature request and place 
them at the right hands and roadmap.

Thanks
-- 

*Rafael Benevides | Senior Software Engineer*
JBoss Developer
M: +1-919-592-6255

Red Hat

Better technology. Faster innovation. Powered by community collaboration.
See how it works at www.redhat.com <http://www.redhat.com/>

LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
<https://www.youtube.com/redhatlatam>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150303/523c3669/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: {a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150303/523c3669/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin.png
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150303/523c3669/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube.png
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150303/523c3669/attachment-0001.png 

From sgilda at redhat.com  Wed Mar  4 07:03:04 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 04 Mar 2015 07:03:04 -0500
Subject: [jbossdeveloper] JBoss Developer Materials Jira Reorg
In-Reply-To: <54F6546B.2030603@redhat.com>
References: <54F6546B.2030603@redhat.com>
Message-ID: <54F6F478.40208@redhat.com>

As a reminder, QE reports on JBoss EAP 6.4 quickstart issues using 
Bugzilla, so there is a possibility of duplicate issues across that 
system and JIRA. My understanding is they are going back to JIRA for the 
next release.


On 03/03/2015 07:40 PM, Rafael Benevides wrote:
> Hi all,
>
> Today I started a cleanup on JDF Jira ( 
> https://issues.jboss.org/browse/JDF ).
>
> All unresolved issues were reviewed and most of them were reassigned 
> or closed (51 issues). If a Jira was assigned to you, please make sure 
> that it still valid or close it otherwise. Thanks Sande for helping me 
> closing some very old issues.
>
> Some other issues related to jboss.org (JBossDeveloper) were moved to 
> https://issues.jboss.org/browse/DEVELOPER
>
> Actually JBoss Developer Materials should be used to track 
> Quickstarts, Archetypes, Stacks (file and client), Ticket-Monster and 
> QSTools. I've created new versions that represents its components 
> version. Examples: quickstarts-eap-6.4.x, ticket-monster-2.6.x, 
> ticket-monster-2.7.x. That way we can identify which version is 
> causing the issue and when it will be fixed (hopefully on next version 
> :D ).
>
> This cleanup will ease to track each bug and feature request and place 
> them at the right hands and roadmap.
>
> Thanks
> -- 
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +1-919-592-6255
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com <http://www.redhat.com/>
>
> LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
> <https://www.youtube.com/redhatlatam>
>
>
> _______________________________________________
> 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/20150304/94c7f141/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150304/94c7f141/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150304/94c7f141/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150304/94c7f141/attachment-0003.png 

From benevides at redhat.com  Thu Mar  5 20:02:31 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 05 Mar 2015 20:02:31 -0500
Subject: [jbossdeveloper] Ticket Monster session replication
In-Reply-To: <54F093CB.3000209@redhat.com>
References: <54F08345.2030506@redhat.com>
	<1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com>
	<54F093CB.3000209@redhat.com>
Message-ID: <54F8FCA7.3040607@redhat.com>

Vineet,

I'd like to share with you the Kubernetes files and Docker images that I 
have at this moment: 
https://github.com/rafabene/devops-demo/blob/master/Readme-Kubernetes.md

It's good because we can compare the approaches use on the same solution 
(Kubernetes+WildFly+Postgres+Ticket Monster) and different technologies:

- HAProxy vs ModProxy
- Kubernetes Services vs SkyDock or Consul
- etc...

On 2/27/15 10:56, Rafael Benevides wrote:
> " I am working on demonstrating scaling of TicketMonster using a 
> Kubernetes+WildFly+(MySQL/Postgres)+HAProxy"
>
> Me too :)
>
> Let's chat about this when you have a chance.
>
> On 2/27/15 10:54, Vineet Reynolds Pereira wrote:
>> Hi Rafael,
>>
>>     I believe it should be, when you use MySQL or PostgreSQL as the 
>> database. Avoid H2 (the default DB) since each DB instance would not 
>> be shared across EAP instances. I'll verify whether the proposed 
>> config works flawlessly over the weekend, as I am working on 
>> demonstrating scaling of TicketMonster using a 
>> Kubernetes+WildFly+(MySQL/Postgres)+HAProxy.
>>
>> Vineet
>>
>>
>> ----- Original Message -----
>>> From: "Rafael Benevides" <benevides at redhat.com>
>>> To: "Vineet Reynolds Pereira" <vpereira at redhat.com>, 
>>> jbossdeveloper at lists.jboss.org
>>> Sent: Friday, February 27, 2015 8:16:29 PM
>>> Subject: Ticket Monster session replication
>>>
>>> Hi all,
>>>
>>> I'm preparing a presentation demo using Ticket Monster and I'd like to
>>> demonstrate a  failover cluster.
>>>
>>> Is TM capable of session replication ? I mean: Did someone already
>>> tested if enabling it through <distributable /> element would be
>>> sufficient for TM without any other source code modification ?
>>>
>>> -- 
>>>
>>> *Rafael Benevides | Senior Software Engineer*
>>> JBoss Developer
>>> M: +1-919-592-6255
>>>
>>> Red Hat
>>>
>>> Better technology. Faster innovation. Powered by community 
>>> collaboration.
>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>
>>> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>> <https://www.youtube.com/redhatlatam>
>>>
>


From benevides at redhat.com  Tue Mar 10 17:38:48 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 10 Mar 2015 17:38:48 -0400
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <540EF853.9080405@redhat.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
	<540EF853.9080405@redhat.com>
Message-ID: <54FF6468.80307@redhat.com>

https://issues.jboss.org/browse/JDF-767 - Object-based JSON generation 
and Stream-based JSON consuming  was just commited.

You can try it online at http://jsonp-benevides.rhcloud.com/

More 1 to go!

On 9/9/14 08:53, Rafael Benevides wrote:
> I create a ticket for each one of them in case some of you want to 
> follow the progress.
>
> - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
> - Chunk style batch processing - https://issues.jboss.org/browse/JDF-766
> - Object-based JSON generation and Stream-based JSON consuming - 
> https://issues.jboss.org/browse/JDF-767
> - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
> - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>
>
> Em 9/9/14, 1:29, Arun Gupta escreveu:
>> 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
>>
>> 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
>>>
>>>     Actually our jboss-eap-quickstarts have been updated to Java EE
>>>     7.0 on 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 ?
>>>     - 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
>>>
>>>
>>>     -- 
>>>
>>>     *Rafael Benevides | Senior Software Engineer*
>>>     JBoss Developer
>>>     M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>
>>>     Red Hat
>>>
>>>     Better technology. Faster innovation. Powered by community
>>>     collaboration.
>>>     See how it works at www.redhat.com <http://www.redhat.com/>
>>>
>>>     LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>     <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
>>
>>
>>     _______________________________________________
>>     jbossdeveloper mailing list
>>     jbossdeveloper at lists.jboss.org
>>     <mailto:jbossdeveloper at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>>
>>
>>
>> -- 
>> http://blog.arungupta.me
>> 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/20150310/2b19502f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150310/2b19502f/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150310/2b19502f/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150310/2b19502f/attachment-0003.png 

From benevides at redhat.com  Mon Mar 23 10:50:24 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 23 Mar 2015 10:50:24 -0400
Subject: [jbossdeveloper] QSTools 1.6.0.Final released
Message-ID: <55102830.2080308@redhat.com>

Hi all,

Since 1.5.x version, these are the new features and bugfixes:

- A new fixer for groupId (makes all groupIds the same)
- Checks for valid XML schemas.
- It runs on Maven 3.0.x, 3.1.x, 3.2.x and 3.3.x

It should reach Maven Central in some hours but you can try it now buy 
adding https://repository.jboss.org/nexus/content/repositories/public/ 
to your settings.xml and running: mvn 
org.jboss.maven.plugins:qstools:1.6.0.Final:check

Thanks

-- 

*Rafael Benevides | Senior Software Engineer*
JBoss Developer
M: +1-919-592-6255

Red Hat

Better technology. Faster innovation. Powered by community collaboration.
See how it works at www.redhat.com <http://www.redhat.com/>

LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
<https://www.youtube.com/redhatlatam>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150323/d6a42b4e/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: {a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150323/d6a42b4e/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin.png
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150323/d6a42b4e/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube.png
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150323/d6a42b4e/attachment-0001.png 

From benevides at redhat.com  Thu Mar 26 16:56:55 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 26 Mar 2015 16:56:55 -0400
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <540EF853.9080405@redhat.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
	<540EF853.9080405@redhat.com>
Message-ID: <55147297.5010708@redhat.com>

I'm pleased to announce that we have now the Java EE 7 Batch 1.0 
Quickstart: JDF-766 - Create a Chunk oriented batch processing Quickstart

The source code is available here: 
https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/batch-processing

And you can also try it online here: http://batch-benevides.rhcloud.com/


On 9/9/14 08:53, Rafael Benevides wrote:
> I create a ticket for each one of them in case some of you want to 
> follow the progress.
>
> - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
> - Chunk style batch processing - https://issues.jboss.org/browse/JDF-766
> - Object-based JSON generation and Stream-based JSON consuming - 
> https://issues.jboss.org/browse/JDF-767
> - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
> - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>
>
> Em 9/9/14, 1:29, Arun Gupta escreveu:
>> 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
>>
>> 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
>>>
>>>     Actually our jboss-eap-quickstarts have been updated to Java EE
>>>     7.0 on 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 ?
>>>     - 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
>>>
>>>
>>>     -- 
>>>
>>>     *Rafael Benevides | Senior Software Engineer*
>>>     JBoss Developer
>>>     M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>
>>>     Red Hat
>>>
>>>     Better technology. Faster innovation. Powered by community
>>>     collaboration.
>>>     See how it works at www.redhat.com <http://www.redhat.com/>
>>>
>>>     LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>     <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
>>
>>
>>     _______________________________________________
>>     jbossdeveloper mailing list
>>     jbossdeveloper at lists.jboss.org
>>     <mailto:jbossdeveloper at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>>
>>
>>
>> -- 
>> http://blog.arungupta.me
>> 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/20150326/6ab3a703/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/6ab3a703/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/6ab3a703/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/6ab3a703/attachment-0003.png 

From sgilda at redhat.com  Thu Mar 26 17:01:47 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 26 Mar 2015 17:01:47 -0400
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <55147297.5010708@redhat.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>	<540EF853.9080405@redhat.com>
	<55147297.5010708@redhat.com>
Message-ID: <551473BB.2050409@redhat.com>

Congratulations! I need to find time to look at all the latest work 
you're doing.

On 03/26/2015 04:56 PM, Rafael Benevides wrote:
> I'm pleased to announce that we have now the Java EE 7 Batch 1.0 
> Quickstart: JDF-766 - Create a Chunk oriented batch processing Quickstart
>
> The source code is available here: 
> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/batch-processing
>
> And you can also try it online here: http://batch-benevides.rhcloud.com/
>
>
> On 9/9/14 08:53, Rafael Benevides wrote:
>> I create a ticket for each one of them in case some of you want to 
>> follow the progress.
>>
>> - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
>> - Chunk style batch processing - https://issues.jboss.org/browse/JDF-766
>> - Object-based JSON generation and Stream-based JSON consuming - 
>> https://issues.jboss.org/browse/JDF-767
>> - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
>> - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>>
>>
>> Em 9/9/14, 1:29, Arun Gupta escreveu:
>>> 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
>>>
>>> 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
>>>>
>>>>     Actually our jboss-eap-quickstarts have been updated to Java EE
>>>>     7.0 on 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 ?
>>>>     - 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
>>>>
>>>>
>>>>     -- 
>>>>
>>>>     *Rafael Benevides | Senior Software Engineer*
>>>>     JBoss Developer
>>>>     M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>>
>>>>     Red Hat
>>>>
>>>>     Better technology. Faster innovation. Powered by community
>>>>     collaboration.
>>>>     See how it works at www.redhat.com <http://www.redhat.com/>
>>>>
>>>>     LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>>     <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
>>>
>>>
>>>     _______________________________________________
>>>     jbossdeveloper mailing list
>>>     jbossdeveloper at lists.jboss.org
>>>     <mailto:jbossdeveloper at lists.jboss.org>
>>>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>
>>>
>>>
>>>
>>> -- 
>>> http://blog.arungupta.me
>>> http://twitter.com/arungupta
>>
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
>
> _______________________________________________
> 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/20150326/8c3241ea/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/8c3241ea/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/8c3241ea/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/8c3241ea/attachment-0003.png 

From benevides at redhat.com  Thu Mar 26 17:03:28 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Thu, 26 Mar 2015 17:03:28 -0400
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <551473BB.2050409@redhat.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>	<540EF853.9080405@redhat.com>
	<55147297.5010708@redhat.com> <551473BB.2050409@redhat.com>
Message-ID: <55147420.1030101@redhat.com>

Thank you :)

On 3/26/15 17:01, Sande Gilda wrote:
> Congratulations! I need to find time to look at all the latest work 
> you're doing.
>
> On 03/26/2015 04:56 PM, Rafael Benevides wrote:
>> I'm pleased to announce that we have now the Java EE 7 Batch 1.0 
>> Quickstart: JDF-766 - Create a Chunk oriented batch processing Quickstart
>>
>> The source code is available here: 
>> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/batch-processing
>>
>> And you can also try it online here: http://batch-benevides.rhcloud.com/
>>
>>
>> On 9/9/14 08:53, Rafael Benevides wrote:
>>> I create a ticket for each one of them in case some of you want to 
>>> follow the progress.
>>>
>>> - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
>>> - Chunk style batch processing - https://issues.jboss.org/browse/JDF-766
>>> - Object-based JSON generation and Stream-based JSON consuming - 
>>> https://issues.jboss.org/browse/JDF-767
>>> - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
>>> - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>>>
>>>
>>> Em 9/9/14, 1:29, Arun Gupta escreveu:
>>>> 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
>>>>
>>>> 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
>>>>>
>>>>>     Actually our jboss-eap-quickstarts have been updated to Java
>>>>>     EE 7.0 on 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 ?
>>>>>     - 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
>>>>>
>>>>>
>>>>>     -- 
>>>>>
>>>>>     *Rafael Benevides | Senior Software Engineer*
>>>>>     JBoss Developer
>>>>>     M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>>>
>>>>>     Red Hat
>>>>>
>>>>>     Better technology. Faster innovation. Powered by community
>>>>>     collaboration.
>>>>>     See how it works at www.redhat.com <http://www.redhat.com/>
>>>>>
>>>>>     LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>>>     <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
>>>>
>>>>
>>>>     _______________________________________________
>>>>     jbossdeveloper mailing list
>>>>     jbossdeveloper at lists.jboss.org
>>>>     <mailto:jbossdeveloper at lists.jboss.org>
>>>>     https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> http://blog.arungupta.me
>>>> http://twitter.com/arungupta
>>>
>>>
>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>>
>>
>> _______________________________________________
>> 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/20150326/a73bcd18/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/a73bcd18/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/a73bcd18/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150326/a73bcd18/attachment-0003.png 

From manderse at redhat.com  Fri Mar 27 11:58:28 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 27 Mar 2015 16:58:28 +0100
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
In-Reply-To: <55147297.5010708@redhat.com>
References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com>
	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>
	<540EF853.9080405@redhat.com> <55147297.5010708@redhat.com>
Message-ID: <2E3AE807-92E1-4D96-88E3-905C283ABF85@redhat.com>

cool!

Alexey/Slava - another use/test case for the Batch tooling ;)

/max

> I'm pleased to announce that we have now the Java EE 7 Batch 1.0 
> Quickstart: JDF-766 - Create a Chunk oriented batch processing 
> Quickstart
>
> The source code is available here: 
> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/batch-processing
>
> And you can also try it online here: 
> http://batch-benevides.rhcloud.com/
>
>
> On 9/9/14 08:53, Rafael Benevides wrote:
>> I create a ticket for each one of them in case some of you want to 
>> follow the progress.
>>
>> - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
>> - Chunk style batch processing - 
>> https://issues.jboss.org/browse/JDF-766
>> - Object-based JSON generation and Stream-based JSON consuming - 
>> https://issues.jboss.org/browse/JDF-767
>> - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
>> - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>>
>>
>> Em 9/9/14, 1:29, Arun Gupta escreveu:
>>> 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
>>>
>>> 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
>>>>
>>>> Actually our jboss-eap-quickstarts have been updated to Java EE
>>>> 7.0 on 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 ?
>>>> - 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
>>>>
>>>>
>>>> --
>>>> *Rafael Benevides | Senior Software Engineer*
>>>> JBoss Developer
>>>> M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>>
>>>> Red Hat
>>>>
>>>> Better technology. Faster innovation. Powered by community
>>>> collaboration.
>>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>>
>>>> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>> <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
>>>
>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> <mailto:jbossdeveloper at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>
>>>
>>>
>>>
>>> -- 
>>> http://blog.arungupta.me
>>> http://twitter.com/arungupta
>>
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


/max
http://about.me/maxandersen