<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 7, 2013 at 1:17 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I am only +1 on this if all changes made to the client are continued to be made in the separate client repo.</div>
</blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"> 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.</div>
</blockquote><div><br></div><div>fully agree !</div><div><br></div><div>-M</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><div class="h5"><div><br><div><div>On Aug 7, 2013, at 1:43 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">
<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 7, 2013 at 8:34 AM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Folks !<div><br></div><div>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).</div>
<div>Once we got the code stable, we decided to move it to it's own repo : <a href="https://github.com/aerogear/aerogear-push-quickstart-web" target="_blank">https://github.com/aerogear/aerogear-push-quickstart-web</a>. But I kept it testing by copying it each time into the deployed aerodoc war.</div>
<div><br></div><div>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.</div>
<div><br></div><div>So, for now we decided to embed again the client with the backend, we've got a working branch here : <a href="https://github.com/sebastienblanc/aerogear-push-quickstart-backend/tree/webinar" target="_blank">https://github.com/sebastienblanc/aerogear-push-quickstart-backend/tree/webinar</a> and for the August release it seems the way to go (I will PR this branch against master).</div>
<div><br></div><div>Once, we have resolved the remaining issues, the Client will move back to his repo.</div></div></blockquote><div><br></div><div>+1</div><div><br></div><div>I have no problems in moving the 'web client' code into the WAR file project, for now</div>
<div><br></div><div>-Matthias</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Any questions, feedback are welcome.</div>
<div><br></div><div>
Seb</div><div> </div><div><br></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br></div></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>