[aerogear-dev] Embedding Aerodoc Simple Push Web Client into Aerodoc Back End

Matthias Wessendorf matzew at apache.org
Wed Aug 7 07:26:36 EDT 2013


On Wed, Aug 7, 2013 at 1:17 PM, Kris Borchers <kris at redhat.com> wrote:

> I am only +1 on this if all changes made to the client are continued to be
> made in the separate client repo.
>

+1


> That way, the history is maintained and we don't have a mess trying to
> merge it back in. Yes, this involves the extra copy step but it's the price
> we have to pay to stay open.
>

fully agree !

-M


>
> On Aug 7, 2013, at 1:43 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>
>
>
>
> On Wed, Aug 7, 2013 at 8:34 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>
>> Hi Folks !
>>
>> When we started the Aerodoc Quickstart project, the Simple Push Web
>> Client was part of the Aerodoc Backend project, hosted in a sub path
>> (/client).
>> Once we got the code stable, we decided to move it to it's own repo :
>> https://github.com/aerogear/aerogear-push-quickstart-web. But I kept it
>> testing by copying it each time into the deployed aerodoc war.
>>
>> These last days, while helping for the webinar and started using the web
>> client as "standalone" meaning  deployed apart from the backend, I started
>> to face some issues that I won't elaborate here but the TL;DR  : using CORS
>> with secured JAX-RS endpoints isn't working, be sure I will open a thread
>> and related JIRAs about this.
>>
>> So, for now we decided to embed again the client with the backend, we've
>> got a working branch here :
>> https://github.com/sebastienblanc/aerogear-push-quickstart-backend/tree/webinar and
>> for the August release it seems the way to go (I will PR this branch
>> against master).
>>
>> Once, we have resolved the remaining issues, the Client will move back to
>> his repo.
>>
>
> +1
>
> I have no problems in moving the 'web client' code into the WAR file
> project, for now
>
> -Matthias
>
>
>
>>
>> Any questions, feedback are welcome.
>>
>> Seb
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130807/e7109ebe/attachment.html 


More information about the aerogear-dev mailing list