From ggastald at redhat.com  Wed Dec  4 11:56:46 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Wed, 04 Dec 2013 14:56:46 -0200
Subject: [forge-dev] Forge Meeting Minutes - 2013-12-04
Message-ID: <529F5ECE.7010706@redhat.com>

==============
#forge Meeting
==============


Meeting started by gastaldi at 15:57:44 UTC. The full logs are available
at
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2013/forge.2013-12-04-15.57.log.html
.



Meeting summary
---------------
* Agenda  (gastaldi, 15:58:00)
   * Forge 2 Roadmap and Progress  (gastaldi, 15:58:39)
   * Test Harness  (gastaldi, 15:58:46)

* Forge 2 Roadmap and Progress  (gastaldi, 15:59:28)
   * Forge 2.0.0.Beta4 should be released in December  (gastaldi,
     16:32:28)

* Test harness  (gastaldi, 16:34:44)
   * we should have a scaffold test harness  (gastaldi, 16:45:13)
   * the scaffold test harness should not be a blocker for 2.0.0.Beta4
     (gastaldi, 16:45:25)

Meeting ended at 16:46:28 UTC.




Action Items
------------





Action Items, by person
-----------------------
* **UNASSIGNED**
   * (none)




People Present (lines said)
---------------------------
* gastaldi (74)
* vineetreynolds (62)
* agoncal (26)
* jbossbot (3)
* jbott (3)
* dbeer (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 

*George Gastaldi | Senior Software Engineer*
JBoss Forge Team
T: +55 11 3524-6169
M: +55 47 9711-1000

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/forge-dev/attachments/20131204/a1abcfe4/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/forge-dev/attachments/20131204/a1abcfe4/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/forge-dev/attachments/20131204/a1abcfe4/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/forge-dev/attachments/20131204/a1abcfe4/attachment-0001.png 

From rmpestano at gmail.com  Mon Dec  9 09:11:03 2013
From: rmpestano at gmail.com (Rafael Pestano)
Date: Mon, 9 Dec 2013 12:11:03 -0200
Subject: [forge-dev] ClassNotFoundException:
	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>
	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>
	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
Message-ID: <CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>

Hi guys, im getting this exception too but im using 1.4.3-Final.

Can it be related to proxy settings?


although i get the exception Forge starts and i can run commands without
problems:

java.lang.IllegalStateException: Plugin entry.getApiVersion() must not be
null.
        at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
        at
org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
        at
org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
        at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
        at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
        at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
        at java.lang.Thread.run(Thread.java:724)
    _____
   |  ___|__  _ __ __ _  ___
   | |_ / _ \| `__/ _` |/ _ \  \\
   |  _| (_) | | | (_| |  __/  //
   |_|  \___/|_|  \__, |\___|
                   |___/

  Windows? Really? Okay...

thanks in advance


2013/11/24 Ivan St. Ivanov <ivan.st.ivanov at gmail.com>

> Hi George,
>
> The problem was that my FORGE_HOME environment var was still pointing to
> the 1.4 version of Forge. Sorry for disturbing!
>
> Cheers,
> Ivan
> On Nov 24, 2013 1:11 AM, "George Gastaldi" <ggastald at redhat.com> wrote:
>
>> This is odd. Are you running on which OS?
>>
>> Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" <ivan.st.ivanov at gmail.com>
>> escreveu:
>>
>> Hi folks,
>>
>> I just downloaded the Forge 2 distribution from
>> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
>>
>> When I try to start it by running the forge script, I get the following
>> exception:
>>
>> Caused by: java.lang.ClassNotFoundException:
>> org.jboss.forge.bootstrap.Bootstrap
>>
>>         at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>>         at java.security.AccessController.doPrivileged(Native Method)
>>         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>>         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>>         at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> Could not find the main class: org.jboss.forge.bootstrap.Bootstrap.
>>  Program will exit.
>>
>> Am I missing something?
>>
>> Thanks,
>> Ivan
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
<http://www.advancedit.com.br/>Att,

Rafael M. Pestano

Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
Graduando em Ci?ncia da Computa??o UFRGS
http://conventionsframework.org <http://conventions.github.io/home/>
http://rpestano.wordpress.com/
@realpestano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131209/b387f4de/attachment.html 

From vpereira at redhat.com  Mon Dec  9 09:34:27 2013
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Mon, 9 Dec 2013 09:34:27 -0500 (EST)
Subject: [forge-dev]
	ClassNotFoundException:	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>
	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>
	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
	<CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>
Message-ID: <57560927.37116823.1386599667527.JavaMail.root@redhat.com>



----- Original Message -----
> From: "Rafael Pestano" <rmpestano at gmail.com>
> To: "forge-dev List" <forge-dev at lists.jboss.org>
> Sent: Monday, December 9, 2013 7:41:03 PM
> Subject: Re: [forge-dev] ClassNotFoundException:	org.jboss.forge.bootstrap.Bootstrap
> 
> Hi guys, im getting this exception too but im using 1.4.3-Final.
> 
> Can it be related to proxy settings?

Hey Rafael,

    This doesn't look like a proxy issue. Could you please verify that you're indeed using 1.4.3.Final ?

    The stack trace seems to indicate you're on 1.2.0.Final or earlier.

Thanks,
Vineet

> 
> 
> although i get the exception Forge starts and i can run commands without
> problems:
> 
> java.lang.IllegalStateException: Plugin entry.getApiVersion() must not be
> null.
> at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
> at
> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
> at
> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
> at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
> at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
> at java.lang.Thread.run(Thread.java:724)
> _____
> | ___|__ _ __ __ _ ___
> | |_ / _ \| `__/ _` |/ _ \ \\
> | _| (_) | | | (_| | __/ //
> |_| \___/|_| \__, |\___|
> |___/
> 
> Windows? Really? Okay...
> 
> thanks in advance
> 
> 
> 2013/11/24 Ivan St. Ivanov < ivan.st.ivanov at gmail.com >
> 
> 
> 
> 
> Hi George,
> 
> The problem was that my FORGE_HOME environment var was still pointing to the
> 1.4 version of Forge. Sorry for disturbing!
> 
> Cheers,
> Ivan
> On Nov 24, 2013 1:11 AM, "George Gastaldi" < ggastald at redhat.com > wrote:
> 
> 
> 
> This is odd. Are you running on which OS?
> 
> Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" < ivan.st.ivanov at gmail.com >
> escreveu:
> 
> 
> 
> 
> Hi folks,
> 
> I just downloaded the Forge 2 distribution from
> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
> 
> When I try to start it by running the forge script, I get the following
> exception:
> 
> Caused by: java.lang.ClassNotFoundException:
> org.jboss.forge.bootstrap.Bootstrap
> 
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> Could not find the main class: org.jboss.forge.bootstrap.Bootstrap. Program
> will exit.
> 
> Am I missing something?
> 
> Thanks,
> Ivan
> 
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> --
> Att,
> 
> Rafael M. Pestano
> 
> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
> Graduando em Ci?ncia da Computa??o UFRGS
> http://conventionsframework.org
> http://rpestano.wordpress.com/
> @realpestano
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev


From ivan.st.ivanov at gmail.com  Mon Dec  9 09:43:01 2013
From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov)
Date: Mon, 9 Dec 2013 16:43:01 +0200
Subject: [forge-dev] ClassNotFoundException:
	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <57560927.37116823.1386599667527.JavaMail.root@redhat.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>
	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>
	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
	<CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>
	<57560927.37116823.1386599667527.JavaMail.root@redhat.com>
Message-ID: <CACYLA9EQGkO3vrO-67d3i-3xWqqXF-O0PL4rJdg3JSCEHCbtRQ@mail.gmail.com>

Hi Rafael,

Where does your $FORGE_HOME variable point to?

Cheers,
Ivan


On Mon, Dec 9, 2013 at 4:34 PM, Vineet Reynolds Pereira <vpereira at redhat.com
> wrote:

>
>
> ----- Original Message -----
> > From: "Rafael Pestano" <rmpestano at gmail.com>
> > To: "forge-dev List" <forge-dev at lists.jboss.org>
> > Sent: Monday, December 9, 2013 7:41:03 PM
> > Subject: Re: [forge-dev] ClassNotFoundException:
>  org.jboss.forge.bootstrap.Bootstrap
> >
> > Hi guys, im getting this exception too but im using 1.4.3-Final.
> >
> > Can it be related to proxy settings?
>
> Hey Rafael,
>
>     This doesn't look like a proxy issue. Could you please verify that
> you're indeed using 1.4.3.Final ?
>
>     The stack trace seems to indicate you're on 1.2.0.Final or earlier.
>
> Thanks,
> Vineet
>
> >
> >
> > although i get the exception Forge starts and i can run commands without
> > problems:
> >
> > java.lang.IllegalStateException: Plugin entry.getApiVersion() must not be
> > null.
> > at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
> > at
> >
> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
> > at
> >
> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
> > at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
> > at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
> > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
> > at java.lang.Thread.run(Thread.java:724)
> > _____
> > | ___|__ _ __ __ _ ___
> > | |_ / _ \| `__/ _` |/ _ \ \\
> > | _| (_) | | | (_| | __/ //
> > |_| \___/|_| \__, |\___|
> > |___/
> >
> > Windows? Really? Okay...
> >
> > thanks in advance
> >
> >
> > 2013/11/24 Ivan St. Ivanov < ivan.st.ivanov at gmail.com >
> >
> >
> >
> >
> > Hi George,
> >
> > The problem was that my FORGE_HOME environment var was still pointing to
> the
> > 1.4 version of Forge. Sorry for disturbing!
> >
> > Cheers,
> > Ivan
> > On Nov 24, 2013 1:11 AM, "George Gastaldi" < ggastald at redhat.com >
> wrote:
> >
> >
> >
> > This is odd. Are you running on which OS?
> >
> > Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" < ivan.st.ivanov at gmail.com >
> > escreveu:
> >
> >
> >
> >
> > Hi folks,
> >
> > I just downloaded the Forge 2 distribution from
> >
> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
> >
> > When I try to start it by running the forge script, I get the following
> > exception:
> >
> > Caused by: java.lang.ClassNotFoundException:
> > org.jboss.forge.bootstrap.Bootstrap
> >
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> > Could not find the main class: org.jboss.forge.bootstrap.Bootstrap.
> Program
> > will exit.
> >
> > Am I missing something?
> >
> > Thanks,
> > Ivan
> >
> >
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> >
> >
> > --
> > Att,
> >
> > Rafael M. Pestano
> >
> > Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
> > Graduando em Ci?ncia da Computa??o UFRGS
> > http://conventionsframework.org
> > http://rpestano.wordpress.com/
> > @realpestano
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131209/861c8a30/attachment.html 

From rmpestano at gmail.com  Mon Dec  9 10:25:05 2013
From: rmpestano at gmail.com (Rafael Pestano)
Date: Mon, 9 Dec 2013 13:25:05 -0200
Subject: [forge-dev] ClassNotFoundException:
	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <CACYLA9EQGkO3vrO-67d3i-3xWqqXF-O0PL4rJdg3JSCEHCbtRQ@mail.gmail.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>
	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>
	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
	<CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>
	<57560927.37116823.1386599667527.JavaMail.root@redhat.com>
	<CACYLA9EQGkO3vrO-67d3i-3xWqqXF-O0PL4rJdg3JSCEHCbtRQ@mail.gmail.com>
Message-ID: <CADjFuPpFe_vBRSOuo=+_CHB2Rcb6Vn3OkM4KvMC8L_ot8Hdqag@mail.gmail.com>

my forge home is C:\Pestano\forge-distribution-1.4.3.Final and in path i
have: %FORGE_HOME%/bin


"The stack trace seems to indicate you're on 1.2.0.Final or earlier." i
indeed have used forge-distribution-1.2.2.Final some time ago, maybe
there's some dirty from early version. Should i clean .forge folder?



2013/12/9 Ivan St. Ivanov <ivan.st.ivanov at gmail.com>

> Hi Rafael,
>
> Where does your $FORGE_HOME variable point to?
>
> Cheers,
> Ivan
>
>
> On Mon, Dec 9, 2013 at 4:34 PM, Vineet Reynolds Pereira <
> vpereira at redhat.com> wrote:
>
>>
>>
>> ----- Original Message -----
>> > From: "Rafael Pestano" <rmpestano at gmail.com>
>> > To: "forge-dev List" <forge-dev at lists.jboss.org>
>> > Sent: Monday, December 9, 2013 7:41:03 PM
>> > Subject: Re: [forge-dev] ClassNotFoundException:
>>  org.jboss.forge.bootstrap.Bootstrap
>> >
>> > Hi guys, im getting this exception too but im using 1.4.3-Final.
>> >
>> > Can it be related to proxy settings?
>>
>> Hey Rafael,
>>
>>     This doesn't look like a proxy issue. Could you please verify that
>> you're indeed using 1.4.3.Final ?
>>
>>     The stack trace seems to indicate you're on 1.2.0.Final or earlier.
>>
>> Thanks,
>> Vineet
>>
>> >
>> >
>> > although i get the exception Forge starts and i can run commands without
>> > problems:
>> >
>> > java.lang.IllegalStateException: Plugin entry.getApiVersion() must not
>> be
>> > null.
>> > at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
>> > at
>> >
>> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
>> > at
>> >
>> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
>> > at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
>> > at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
>> > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
>> > at java.lang.Thread.run(Thread.java:724)
>> > _____
>> > | ___|__ _ __ __ _ ___
>> > | |_ / _ \| `__/ _` |/ _ \ \\
>> > | _| (_) | | | (_| | __/ //
>> > |_| \___/|_| \__, |\___|
>> > |___/
>> >
>> > Windows? Really? Okay...
>> >
>> > thanks in advance
>> >
>> >
>> > 2013/11/24 Ivan St. Ivanov < ivan.st.ivanov at gmail.com >
>> >
>> >
>> >
>> >
>> > Hi George,
>> >
>> > The problem was that my FORGE_HOME environment var was still pointing
>> to the
>> > 1.4 version of Forge. Sorry for disturbing!
>> >
>> > Cheers,
>> > Ivan
>> > On Nov 24, 2013 1:11 AM, "George Gastaldi" < ggastald at redhat.com >
>> wrote:
>> >
>> >
>> >
>> > This is odd. Are you running on which OS?
>> >
>> > Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" < ivan.st.ivanov at gmail.com >
>> > escreveu:
>> >
>> >
>> >
>> >
>> > Hi folks,
>> >
>> > I just downloaded the Forge 2 distribution from
>> >
>> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
>> >
>> > When I try to start it by running the forge script, I get the following
>> > exception:
>> >
>> > Caused by: java.lang.ClassNotFoundException:
>> > org.jboss.forge.bootstrap.Bootstrap
>> >
>> > at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>> > at java.security.AccessController.doPrivileged(Native Method)
>> > at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>> > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> > Could not find the main class: org.jboss.forge.bootstrap.Bootstrap.
>> Program
>> > will exit.
>> >
>> > Am I missing something?
>> >
>> > Thanks,
>> > Ivan
>> >
>> >
>> >
>> > _______________________________________________
>> > forge-dev mailing list
>> > forge-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>> >
>> > _______________________________________________
>> > forge-dev mailing list
>> > forge-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>> >
>> > _______________________________________________
>> > forge-dev mailing list
>> > forge-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>> >
>> >
>> >
>> > --
>> > Att,
>> >
>> > Rafael M. Pestano
>> >
>> > Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
>> > Graduando em Ci?ncia da Computa??o UFRGS
>> > http://conventionsframework.org
>> > http://rpestano.wordpress.com/
>> > @realpestano
>> >
>> > _______________________________________________
>> > forge-dev mailing list
>> > forge-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
<http://www.advancedit.com.br/>Att,

Rafael M. Pestano

Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
Graduando em Ci?ncia da Computa??o UFRGS
http://conventionsframework.org <http://conventions.github.io/home/>
http://rpestano.wordpress.com/
@realpestano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131209/a186edf5/attachment.html 

From rmpestano at gmail.com  Mon Dec  9 10:27:39 2013
From: rmpestano at gmail.com (Rafael Pestano)
Date: Mon, 9 Dec 2013 13:27:39 -0200
Subject: [forge-dev] ClassNotFoundException:
	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <CADjFuPpFe_vBRSOuo=+_CHB2Rcb6Vn3OkM4KvMC8L_ot8Hdqag@mail.gmail.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>
	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>
	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
	<CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>
	<57560927.37116823.1386599667527.JavaMail.root@redhat.com>
	<CACYLA9EQGkO3vrO-67d3i-3xWqqXF-O0PL4rJdg3JSCEHCbtRQ@mail.gmail.com>
	<CADjFuPpFe_vBRSOuo=+_CHB2Rcb6Vn3OkM4KvMC8L_ot8Hdqag@mail.gmail.com>
Message-ID: <CADjFuPrqpXPG0S7UaVg+1BRSWSN68=tG_aUCULgq9N-FswhxEA@mail.gmail.com>

ok im using 1.2.2 final ;(

the version command prints: JBoss Forge, version [ 1.2.2.Final ] - JBoss,
by Red Hat, Inc. [ http://jboss.org/forge ]

but i dont know how to change it, any ideas?

thanks for the quick reply




2013/12/9 Rafael Pestano <rmpestano at gmail.com>

> my forge home is C:\Pestano\forge-distribution-1.4.3.Final and in path i
> have: %FORGE_HOME%/bin
>
>
> "The stack trace seems to indicate you're on 1.2.0.Final or earlier." i
> indeed have used forge-distribution-1.2.2.Final some time ago, maybe
> there's some dirty from early version. Should i clean .forge folder?
>
>
>
> 2013/12/9 Ivan St. Ivanov <ivan.st.ivanov at gmail.com>
>
> Hi Rafael,
>>
>> Where does your $FORGE_HOME variable point to?
>>
>> Cheers,
>> Ivan
>>
>>
>> On Mon, Dec 9, 2013 at 4:34 PM, Vineet Reynolds Pereira <
>> vpereira at redhat.com> wrote:
>>
>>>
>>>
>>> ----- Original Message -----
>>> > From: "Rafael Pestano" <rmpestano at gmail.com>
>>> > To: "forge-dev List" <forge-dev at lists.jboss.org>
>>> > Sent: Monday, December 9, 2013 7:41:03 PM
>>> > Subject: Re: [forge-dev] ClassNotFoundException:
>>>  org.jboss.forge.bootstrap.Bootstrap
>>> >
>>> > Hi guys, im getting this exception too but im using 1.4.3-Final.
>>> >
>>> > Can it be related to proxy settings?
>>>
>>> Hey Rafael,
>>>
>>>     This doesn't look like a proxy issue. Could you please verify that
>>> you're indeed using 1.4.3.Final ?
>>>
>>>     The stack trace seems to indicate you're on 1.2.0.Final or earlier.
>>>
>>> Thanks,
>>> Vineet
>>>
>>> >
>>> >
>>> > although i get the exception Forge starts and i can run commands
>>> without
>>> > problems:
>>> >
>>> > java.lang.IllegalStateException: Plugin entry.getApiVersion() must not
>>> be
>>> > null.
>>> > at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
>>> > at
>>> >
>>> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
>>> > at
>>> >
>>> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
>>> > at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
>>> > at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
>>> > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
>>> > at java.lang.Thread.run(Thread.java:724)
>>> > _____
>>> > | ___|__ _ __ __ _ ___
>>> > | |_ / _ \| `__/ _` |/ _ \ \\
>>> > | _| (_) | | | (_| | __/ //
>>> > |_| \___/|_| \__, |\___|
>>> > |___/
>>> >
>>> > Windows? Really? Okay...
>>> >
>>> > thanks in advance
>>> >
>>> >
>>> > 2013/11/24 Ivan St. Ivanov < ivan.st.ivanov at gmail.com >
>>> >
>>> >
>>> >
>>> >
>>> > Hi George,
>>> >
>>> > The problem was that my FORGE_HOME environment var was still pointing
>>> to the
>>> > 1.4 version of Forge. Sorry for disturbing!
>>> >
>>> > Cheers,
>>> > Ivan
>>> > On Nov 24, 2013 1:11 AM, "George Gastaldi" < ggastald at redhat.com >
>>> wrote:
>>> >
>>> >
>>> >
>>> > This is odd. Are you running on which OS?
>>> >
>>> > Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" < ivan.st.ivanov at gmail.com>
>>> > escreveu:
>>> >
>>> >
>>> >
>>> >
>>> > Hi folks,
>>> >
>>> > I just downloaded the Forge 2 distribution from
>>> >
>>> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
>>> >
>>> > When I try to start it by running the forge script, I get the following
>>> > exception:
>>> >
>>> > Caused by: java.lang.ClassNotFoundException:
>>> > org.jboss.forge.bootstrap.Bootstrap
>>> >
>>> > at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>>> > at java.security.AccessController.doPrivileged(Native Method)
>>> > at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>> > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>> > Could not find the main class: org.jboss.forge.bootstrap.Bootstrap.
>>> Program
>>> > will exit.
>>> >
>>> > Am I missing something?
>>> >
>>> > Thanks,
>>> > Ivan
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > forge-dev mailing list
>>> > forge-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>> >
>>> > _______________________________________________
>>> > forge-dev mailing list
>>> > forge-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>> >
>>> > _______________________________________________
>>> > forge-dev mailing list
>>> > forge-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>> >
>>> >
>>> >
>>> > --
>>> > Att,
>>> >
>>> > Rafael M. Pestano
>>> >
>>> > Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
>>> > Graduando em Ci?ncia da Computa??o UFRGS
>>> > http://conventionsframework.org
>>> > http://rpestano.wordpress.com/
>>> > @realpestano
>>> >
>>> > _______________________________________________
>>> > forge-dev mailing list
>>> > forge-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
>
> --
>  <http://www.advancedit.com.br/>Att,
>
> Rafael M. Pestano
>
> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
> Graduando em Ci?ncia da Computa??o UFRGS
> http://conventionsframework.org <http://conventions.github.io/home/>
> http://rpestano.wordpress.com/
> @realpestano
>



-- 
<http://www.advancedit.com.br/>Att,

Rafael M. Pestano

Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
Graduando em Ci?ncia da Computa??o UFRGS
http://conventionsframework.org <http://conventions.github.io/home/>
http://rpestano.wordpress.com/
@realpestano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131209/3b4fca51/attachment-0001.html 

From rmpestano at gmail.com  Mon Dec  9 10:59:41 2013
From: rmpestano at gmail.com (Rafael Pestano)
Date: Mon, 9 Dec 2013 13:59:41 -0200
Subject: [forge-dev] ClassNotFoundException:
	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <CADjFuPrqpXPG0S7UaVg+1BRSWSN68=tG_aUCULgq9N-FswhxEA@mail.gmail.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>
	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>
	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
	<CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>
	<57560927.37116823.1386599667527.JavaMail.root@redhat.com>
	<CACYLA9EQGkO3vrO-67d3i-3xWqqXF-O0PL4rJdg3JSCEHCbtRQ@mail.gmail.com>
	<CADjFuPpFe_vBRSOuo=+_CHB2Rcb6Vn3OkM4KvMC8L_ot8Hdqag@mail.gmail.com>
	<CADjFuPrqpXPG0S7UaVg+1BRSWSN68=tG_aUCULgq9N-FswhxEA@mail.gmail.com>
Message-ID: <CADjFuPoHkV+5VFQkJEcRsYEmOxX--+t1CdPkAHodt6Wy-QemeA@mail.gmail.com>

restarted machine and now version command returns 1.4.3 but still got the
exception:

C:\>forge
java.lang.IllegalStateException: Plugin entry.getApiVersion() must not be
null.
        at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
        at
org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:300)
        at
org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:86)
        at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:247)
        at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
        at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:139)
        at java.lang.Thread.run(Thread.java:724)
    _____
   |  ___|__  _ __ __ _  ___
   | |_ / _ \| `__/ _` |/ _ \  \\
   |  _| (_) | | | (_| |  __/  //
   |_|  \___/|_|  \__, |\___|
                   |___/

  Windows? Really? Okay...

[no project]  $ version[]
***ERROR*** No such command: version[]
[no project]  $ version
JBoss Forge, version [ 1.4.3.Final ] - JBoss, by Red Hat, Inc. [
http://jboss.org/forge ]
[no project]  $


2013/12/9 Rafael Pestano <rmpestano at gmail.com>

> ok im using 1.2.2 final ;(
>
> the version command prints: JBoss Forge, version [ 1.2.2.Final ] - JBoss,
> by Red Hat, Inc. [ http://jboss.org/forge ]
>
> but i dont know how to change it, any ideas?
>
> thanks for the quick reply
>
>
>
>
> 2013/12/9 Rafael Pestano <rmpestano at gmail.com>
>
>> my forge home is C:\Pestano\forge-distribution-1.4.3.Final and in path i
>> have: %FORGE_HOME%/bin
>>
>>
>> "The stack trace seems to indicate you're on 1.2.0.Final or earlier." i
>> indeed have used forge-distribution-1.2.2.Final some time ago, maybe
>> there's some dirty from early version. Should i clean .forge folder?
>>
>>
>>
>> 2013/12/9 Ivan St. Ivanov <ivan.st.ivanov at gmail.com>
>>
>> Hi Rafael,
>>>
>>> Where does your $FORGE_HOME variable point to?
>>>
>>> Cheers,
>>> Ivan
>>>
>>>
>>> On Mon, Dec 9, 2013 at 4:34 PM, Vineet Reynolds Pereira <
>>> vpereira at redhat.com> wrote:
>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>> > From: "Rafael Pestano" <rmpestano at gmail.com>
>>>> > To: "forge-dev List" <forge-dev at lists.jboss.org>
>>>> > Sent: Monday, December 9, 2013 7:41:03 PM
>>>> > Subject: Re: [forge-dev] ClassNotFoundException:
>>>>  org.jboss.forge.bootstrap.Bootstrap
>>>> >
>>>> > Hi guys, im getting this exception too but im using 1.4.3-Final.
>>>> >
>>>> > Can it be related to proxy settings?
>>>>
>>>> Hey Rafael,
>>>>
>>>>     This doesn't look like a proxy issue. Could you please verify that
>>>> you're indeed using 1.4.3.Final ?
>>>>
>>>>     The stack trace seems to indicate you're on 1.2.0.Final or earlier.
>>>>
>>>> Thanks,
>>>> Vineet
>>>>
>>>> >
>>>> >
>>>> > although i get the exception Forge starts and i can run commands
>>>> without
>>>> > problems:
>>>> >
>>>> > java.lang.IllegalStateException: Plugin entry.getApiVersion() must
>>>> not be
>>>> > null.
>>>> > at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
>>>> > at
>>>> >
>>>> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
>>>> > at
>>>> >
>>>> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
>>>> > at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
>>>> > at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
>>>> > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
>>>> > at java.lang.Thread.run(Thread.java:724)
>>>> > _____
>>>> > | ___|__ _ __ __ _ ___
>>>> > | |_ / _ \| `__/ _` |/ _ \ \\
>>>> > | _| (_) | | | (_| | __/ //
>>>> > |_| \___/|_| \__, |\___|
>>>> > |___/
>>>> >
>>>> > Windows? Really? Okay...
>>>> >
>>>> > thanks in advance
>>>> >
>>>> >
>>>> > 2013/11/24 Ivan St. Ivanov < ivan.st.ivanov at gmail.com >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > Hi George,
>>>> >
>>>> > The problem was that my FORGE_HOME environment var was still pointing
>>>> to the
>>>> > 1.4 version of Forge. Sorry for disturbing!
>>>> >
>>>> > Cheers,
>>>> > Ivan
>>>> > On Nov 24, 2013 1:11 AM, "George Gastaldi" < ggastald at redhat.com >
>>>> wrote:
>>>> >
>>>> >
>>>> >
>>>> > This is odd. Are you running on which OS?
>>>> >
>>>> > Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" < ivan.st.ivanov at gmail.com>
>>>> > escreveu:
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > Hi folks,
>>>> >
>>>> > I just downloaded the Forge 2 distribution from
>>>> >
>>>> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
>>>> >
>>>> > When I try to start it by running the forge script, I get the
>>>> following
>>>> > exception:
>>>> >
>>>> > Caused by: java.lang.ClassNotFoundException:
>>>> > org.jboss.forge.bootstrap.Bootstrap
>>>> >
>>>> > at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>>>> > at java.security.AccessController.doPrivileged(Native Method)
>>>> > at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>>>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>>> > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>>>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>> > Could not find the main class: org.jboss.forge.bootstrap.Bootstrap.
>>>> Program
>>>> > will exit.
>>>> >
>>>> > Am I missing something?
>>>> >
>>>> > Thanks,
>>>> > Ivan
>>>> >
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > forge-dev mailing list
>>>> > forge-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >
>>>> > _______________________________________________
>>>> > forge-dev mailing list
>>>> > forge-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >
>>>> > _______________________________________________
>>>> > forge-dev mailing list
>>>> > forge-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Att,
>>>> >
>>>> > Rafael M. Pestano
>>>> >
>>>> > Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
>>>> > Graduando em Ci?ncia da Computa??o UFRGS
>>>> > http://conventionsframework.org
>>>> > http://rpestano.wordpress.com/
>>>> > @realpestano
>>>> >
>>>> > _______________________________________________
>>>> > forge-dev mailing list
>>>> > forge-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>
>>>> _______________________________________________
>>>> forge-dev mailing list
>>>> forge-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>
>>
>>
>> --
>>  <http://www.advancedit.com.br/>Att,
>>
>> Rafael M. Pestano
>>
>> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
>> Graduando em Ci?ncia da Computa??o UFRGS
>> http://conventionsframework.org <http://conventions.github.io/home/>
>> http://rpestano.wordpress.com/
>> @realpestano
>>
>
>
>
> --
> <http://www.advancedit.com.br/>Att,
>
> Rafael M. Pestano
>
> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
> Graduando em Ci?ncia da Computa??o UFRGS
> http://conventionsframework.org <http://conventions.github.io/home/>
> http://rpestano.wordpress.com/
> @realpestano
>



-- 
<http://www.advancedit.com.br/>Att,

Rafael M. Pestano

Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
Graduando em Ci?ncia da Computa??o UFRGS
http://conventionsframework.org <http://conventions.github.io/home/>
http://rpestano.wordpress.com/
@realpestano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131209/313d0ad0/attachment.html 

From ggastald at redhat.com  Mon Dec  9 11:01:24 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 09 Dec 2013 14:01:24 -0200
Subject: [forge-dev] ClassNotFoundException:
	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <CADjFuPoHkV+5VFQkJEcRsYEmOxX--+t1CdPkAHodt6Wy-QemeA@mail.gmail.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>	<CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>	<57560927.37116823.1386599667527.JavaMail.root@redhat.com>	<CACYLA9EQGkO3vrO-67d3i-3xWqqXF-O0PL4rJdg3JSCEHCbtRQ@mail.gmail.com>	<CADjFuPpFe_vBRSOuo=+_CHB2Rcb6Vn3OkM4KvMC8L_ot8Hdqag@mail.gmail.com>	<CADjFuPrqpXPG0S7UaVg+1BRSWSN68=tG_aUCULgq9N-FswhxEA@mail.gmail.com>
	<CADjFuPoHkV+5VFQkJEcRsYEmOxX--+t1CdPkAHodt6Wy-QemeA@mail.gmail.com>
Message-ID: <52A5E954.20100@redhat.com>

Rafael,

please remove your ~/.forge folder and try again.

On 12/09/2013 01:59 PM, Rafael Pestano wrote:
> restarted machine and now version command returns 1.4.3 but still got 
> the exception:
>
> C:\>forge
> java.lang.IllegalStateException: Plugin entry.getApiVersion() must not 
> be null.
>         at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
>         at 
> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:300)
>         at 
> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:86)
>         at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:247)
>         at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
>         at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:139)
>         at java.lang.Thread.run(Thread.java:724)
>     _____
>    |  ___|__  _ __ __ _  ___
>    | |_ / _ \| `__/ _` |/ _ \  \\
>    |  _| (_) | | | (_| |  __/  //
>    |_|  \___/|_|  \__, |\___|
>                    |___/
>
>   Windows? Really? Okay...
>
> [no project]  $ version[]
> ***ERROR*** No such command: version[]
> [no project]  $ version
> JBoss Forge, version [ 1.4.3.Final ] - JBoss, by Red Hat, Inc. [ 
> http://jboss.org/forge ]
> [no project]  $
>
>
> 2013/12/9 Rafael Pestano <rmpestano at gmail.com 
> <mailto:rmpestano at gmail.com>>
>
>     ok im using 1.2.2 final ;(
>
>     the version command prints: JBoss Forge, version [ 1.2.2.Final ] -
>     JBoss, by Red Hat, Inc. [ http://jboss.org/forge ]
>
>     but i dont know how to change it, any ideas?
>
>     thanks for the quick reply
>
>
>
>
>     2013/12/9 Rafael Pestano <rmpestano at gmail.com
>     <mailto:rmpestano at gmail.com>>
>
>         my forge home is C:\Pestano\forge-distribution-1.4.3.Final and
>         in path i have: %FORGE_HOME%/bin
>
>
>         "The stack trace seems to indicate you're on 1.2.0.Final or
>         earlier." i indeed have used forge-distribution-1.2.2.Final
>         some time ago, maybe there's some dirty from early version.
>         Should i clean .forge folder?
>
>
>
>         2013/12/9 Ivan St. Ivanov <ivan.st.ivanov at gmail.com
>         <mailto:ivan.st.ivanov at gmail.com>>
>
>             Hi Rafael,
>
>             Where does your $FORGE_HOME variable point to?
>
>             Cheers,
>             Ivan
>
>
>             On Mon, Dec 9, 2013 at 4:34 PM, Vineet Reynolds Pereira
>             <vpereira at redhat.com <mailto:vpereira at redhat.com>> wrote:
>
>
>
>                 ----- Original Message -----
>                 > From: "Rafael Pestano" <rmpestano at gmail.com
>                 <mailto:rmpestano at gmail.com>>
>                 > To: "forge-dev List" <forge-dev at lists.jboss.org
>                 <mailto:forge-dev at lists.jboss.org>>
>                 > Sent: Monday, December 9, 2013 7:41:03 PM
>                 > Subject: Re: [forge-dev] ClassNotFoundException:
>                  org.jboss.forge.bootstrap.Bootstrap
>                 >
>                 > Hi guys, im getting this exception too but im using
>                 1.4.3-Final.
>                 >
>                 > Can it be related to proxy settings?
>
>                 Hey Rafael,
>
>                     This doesn't look like a proxy issue. Could you
>                 please verify that you're indeed using 1.4.3.Final ?
>
>                     The stack trace seems to indicate you're on
>                 1.2.0.Final or earlier.
>
>                 Thanks,
>                 Vineet
>
>                 >
>                 >
>                 > although i get the exception Forge starts and i can
>                 run commands without
>                 > problems:
>                 >
>                 > java.lang.IllegalStateException: Plugin
>                 entry.getApiVersion() must not be
>                 > null.
>                 > at
>                 org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
>                 > at
>                 >
>                 org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
>                 > at
>                 >
>                 org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
>                 > at
>                 org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
>                 > at
>                 org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
>                 > at
>                 org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
>                 > at java.lang.Thread.run(Thread.java:724)
>                 > _____
>                 > | ___|__ _ __ __ _ ___
>                 > | |_ / _ \| `__/ _` |/ _ \ \\
>                 > | _| (_) | | | (_| | __/ //
>                 > |_| \___/|_| \__, |\___|
>                 > |___/
>                 >
>                 > Windows? Really? Okay...
>                 >
>                 > thanks in advance
>                 >
>                 >
>                 > 2013/11/24 Ivan St. Ivanov <
>                 ivan.st.ivanov at gmail.com
>                 <mailto:ivan.st.ivanov at gmail.com> >
>                 >
>                 >
>                 >
>                 >
>                 > Hi George,
>                 >
>                 > The problem was that my FORGE_HOME environment var
>                 was still pointing to the
>                 > 1.4 version of Forge. Sorry for disturbing!
>                 >
>                 > Cheers,
>                 > Ivan
>                 > On Nov 24, 2013 1:11 AM, "George Gastaldi" <
>                 ggastald at redhat.com <mailto:ggastald at redhat.com> > wrote:
>                 >
>                 >
>                 >
>                 > This is odd. Are you running on which OS?
>                 >
>                 > Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" <
>                 ivan.st.ivanov at gmail.com
>                 <mailto:ivan.st.ivanov at gmail.com> >
>                 > escreveu:
>                 >
>                 >
>                 >
>                 >
>                 > Hi folks,
>                 >
>                 > I just downloaded the Forge 2 distribution from
>                 >
>                 https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
>                 >
>                 > When I try to start it by running the forge script,
>                 I get the following
>                 > exception:
>                 >
>                 > Caused by: java.lang.ClassNotFoundException:
>                 > org.jboss.forge.bootstrap.Bootstrap
>                 >
>                 > at
>                 java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>                 > at
>                 java.security.AccessController.doPrivileged(Native Method)
>                 > at
>                 java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>                 > at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>                 > at
>                 sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>                 > at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>                 > Could not find the main class:
>                 org.jboss.forge.bootstrap.Bootstrap. Program
>                 > will exit.
>                 >
>                 > Am I missing something?
>                 >
>                 > Thanks,
>                 > Ivan
>                 >
>                 >
>                 >
>                 > _______________________________________________
>                 > forge-dev mailing list
>                 > forge-dev at lists.jboss.org
>                 <mailto:forge-dev at lists.jboss.org>
>                 > https://lists.jboss.org/mailman/listinfo/forge-dev
>                 >
>                 > _______________________________________________
>                 > forge-dev mailing list
>                 > forge-dev at lists.jboss.org
>                 <mailto:forge-dev at lists.jboss.org>
>                 > https://lists.jboss.org/mailman/listinfo/forge-dev
>                 >
>                 > _______________________________________________
>                 > forge-dev mailing list
>                 > forge-dev at lists.jboss.org
>                 <mailto:forge-dev at lists.jboss.org>
>                 > https://lists.jboss.org/mailman/listinfo/forge-dev
>                 >
>                 >
>                 >
>                 > --
>                 > Att,
>                 >
>                 > Rafael M. Pestano
>                 >
>                 > Desenvolvedor Java Cia. de Processamento de Dados do
>                 Rio Grande do Sul
>                 > Graduando em Ci?ncia da Computa??o UFRGS
>                 > http://conventionsframework.org
>                 > http://rpestano.wordpress.com/
>                 > @realpestano
>                 >
>                 > _______________________________________________
>                 > forge-dev mailing list
>                 > forge-dev at lists.jboss.org
>                 <mailto:forge-dev at lists.jboss.org>
>                 > https://lists.jboss.org/mailman/listinfo/forge-dev
>
>                 _______________________________________________
>                 forge-dev mailing list
>                 forge-dev at lists.jboss.org
>                 <mailto:forge-dev at lists.jboss.org>
>                 https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>             _______________________________________________
>             forge-dev mailing list
>             forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>             https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
>         -- 
>         <http://www.advancedit.com.br/>Att,
>
>         Rafael M. Pestano
>
>         Desenvolvedor Java Cia. de Processamento de Dados do Rio
>         Grande do Sul
>         Graduando em Ci?ncia da Computa??o UFRGS
>         http://conventionsframework.org
>         <http://conventions.github.io/home/>
>         http://rpestano.wordpress.com/
>         @realpestano
>
>
>
>
>     -- 
>     <http://www.advancedit.com.br/>Att,
>
>     Rafael M. Pestano
>
>     Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
>     Graduando em Ci?ncia da Computa??o UFRGS
>     http://conventionsframework.org <http://conventions.github.io/home/>
>     http://rpestano.wordpress.com/
>     @realpestano
>
>
>
>
> -- 
> <http://www.advancedit.com.br/>Att,
>
> Rafael M. Pestano
>
> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
> Graduando em Ci?ncia da Computa??o UFRGS
> http://conventionsframework.org <http://conventions.github.io/home/>
> http://rpestano.wordpress.com/
> @realpestano
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131209/879ac943/attachment-0001.html 

From rmpestano at gmail.com  Mon Dec  9 15:02:56 2013
From: rmpestano at gmail.com (Rafael Pestano)
Date: Mon, 9 Dec 2013 18:02:56 -0200
Subject: [forge-dev] ClassNotFoundException:
	org.jboss.forge.bootstrap.Bootstrap
In-Reply-To: <52A5E954.20100@redhat.com>
References: <CACYLA9FpbXa2Zfmc8tK+wQ4TMwa_Rvruj6vVkWwqbgXT6OgmUQ@mail.gmail.com>
	<B53EFC86-FF5E-4BB1-97CC-31CBA9C9FFE5@redhat.com>
	<CACYLA9HRvmcMcM7DFr3AG7i0pZvtZ5zoUJHea1WM58XDe-Qpug@mail.gmail.com>
	<CADjFuPrCmRzqhKtw=qnSQHsSCjMavw81rtFaHRwDMpX1HM7T6Q@mail.gmail.com>
	<57560927.37116823.1386599667527.JavaMail.root@redhat.com>
	<CACYLA9EQGkO3vrO-67d3i-3xWqqXF-O0PL4rJdg3JSCEHCbtRQ@mail.gmail.com>
	<CADjFuPpFe_vBRSOuo=+_CHB2Rcb6Vn3OkM4KvMC8L_ot8Hdqag@mail.gmail.com>
	<CADjFuPrqpXPG0S7UaVg+1BRSWSN68=tG_aUCULgq9N-FswhxEA@mail.gmail.com>
	<CADjFuPoHkV+5VFQkJEcRsYEmOxX--+t1CdPkAHodt6Wy-QemeA@mail.gmail.com>
	<52A5E954.20100@redhat.com>
Message-ID: <CADjFuPpZv+QooZ-T6Cy-L1F8A2X+jtRzQO70R4A16UuoVCa3Mg@mail.gmail.com>

thanks George, that was the issue.

C:\Users\rafael-pestano>forge
    _____
   |  ___|__  _ __ __ _  ___
   | |_ / _ \| `__/ _` |/ _ \  \\
   |  _| (_) | | | (_| |  __/  //
   |_|  \___/|_|  \__, |\___|
                   |___/

JBoss Forge, version [ 1.4.3.Final ] - JBoss, by Red Hat, Inc. [
http://forge.jboss.org ]
 ? Will you allow the Forge team to receive anonymous usage statistics for
this instance of JBoss Forge? [y/N] y
[no project] rafael-pestano $


2013/12/9 George Gastaldi <ggastald at redhat.com>

>  Rafael,
>
> please remove your ~/.forge folder and try again.
>
>
> On 12/09/2013 01:59 PM, Rafael Pestano wrote:
>
> restarted machine and now version command returns 1.4.3 but still got the
> exception:
>
> C:\>forge
> java.lang.IllegalStateException: Plugin entry.getApiVersion() must not be
> null.
>         at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
>         at
> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:300)
>         at
> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:86)
>         at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:247)
>         at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
>         at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:139)
>         at java.lang.Thread.run(Thread.java:724)
>     _____
>    |  ___|__  _ __ __ _  ___
>    | |_ / _ \| `__/ _` |/ _ \  \\
>    |  _| (_) | | | (_| |  __/  //
>    |_|  \___/|_|  \__, |\___|
>                    |___/
>
>   Windows? Really? Okay...
>
> [no project]  $ version[]
> ***ERROR*** No such command: version[]
> [no project]  $ version
> JBoss Forge, version [ 1.4.3.Final ] - JBoss, by Red Hat, Inc. [
> http://jboss.org/forge ]
> [no project]  $
>
>
> 2013/12/9 Rafael Pestano <rmpestano at gmail.com>
>
>>   ok im using 1.2.2 final ;(
>>
>>  the version command prints: JBoss Forge, version [ 1.2.2.Final ] -
>> JBoss, by Red Hat, Inc. [ http://jboss.org/forge ]
>>
>>  but i dont know how to change it, any ideas?
>>
>>  thanks for the quick reply
>>
>>
>>
>>
>>  2013/12/9 Rafael Pestano <rmpestano at gmail.com>
>>
>>>  my forge home is C:\Pestano\forge-distribution-1.4.3.Final and in path
>>> i have: %FORGE_HOME%/bin
>>>
>>>
>>> "The stack trace seems to indicate you're on 1.2.0.Final or earlier." i
>>> indeed have used forge-distribution-1.2.2.Final some time ago, maybe
>>> there's some dirty from early version. Should i clean .forge folder?
>>>
>>>
>>>
>>> 2013/12/9 Ivan St. Ivanov <ivan.st.ivanov at gmail.com>
>>>
>>>  Hi Rafael,
>>>>
>>>>  Where does your $FORGE_HOME variable point to?
>>>>
>>>>  Cheers,
>>>> Ivan
>>>>
>>>>
>>>> On Mon, Dec 9, 2013 at 4:34 PM, Vineet Reynolds Pereira <
>>>> vpereira at redhat.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>> > From: "Rafael Pestano" <rmpestano at gmail.com>
>>>>> > To: "forge-dev List" <forge-dev at lists.jboss.org>
>>>>> > Sent: Monday, December 9, 2013 7:41:03 PM
>>>>> > Subject: Re: [forge-dev] ClassNotFoundException:
>>>>>  org.jboss.forge.bootstrap.Bootstrap
>>>>> >
>>>>> > Hi guys, im getting this exception too but im using 1.4.3-Final.
>>>>> >
>>>>> > Can it be related to proxy settings?
>>>>>
>>>>>  Hey Rafael,
>>>>>
>>>>>     This doesn't look like a proxy issue. Could you please verify that
>>>>> you're indeed using 1.4.3.Final ?
>>>>>
>>>>>     The stack trace seems to indicate you're on 1.2.0.Final or earlier.
>>>>>
>>>>> Thanks,
>>>>> Vineet
>>>>>
>>>>> >
>>>>> >
>>>>> > although i get the exception Forge starts and i can run commands
>>>>> without
>>>>> > problems:
>>>>> >
>>>>> > java.lang.IllegalStateException: Plugin entry.getApiVersion() must
>>>>> not be
>>>>> > null.
>>>>> > at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:35)
>>>>> > at
>>>>> >
>>>>> org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:268)
>>>>> > at
>>>>> >
>>>>> org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:85)
>>>>> > at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:233)
>>>>> > at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
>>>>> > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
>>>>> > at java.lang.Thread.run(Thread.java:724)
>>>>> > _____
>>>>> > | ___|__ _ __ __ _ ___
>>>>> > | |_ / _ \| `__/ _` |/ _ \ \\
>>>>> > | _| (_) | | | (_| | __/ //
>>>>> > |_| \___/|_| \__, |\___|
>>>>> > |___/
>>>>> >
>>>>> > Windows? Really? Okay...
>>>>> >
>>>>> > thanks in advance
>>>>> >
>>>>> >
>>>>> > 2013/11/24 Ivan St. Ivanov < ivan.st.ivanov at gmail.com >
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > Hi George,
>>>>> >
>>>>> > The problem was that my FORGE_HOME environment var was still
>>>>> pointing to the
>>>>> > 1.4 version of Forge. Sorry for disturbing!
>>>>> >
>>>>> > Cheers,
>>>>> > Ivan
>>>>> > On Nov 24, 2013 1:11 AM, "George Gastaldi" < ggastald at redhat.com >
>>>>> wrote:
>>>>> >
>>>>> >
>>>>> >
>>>>> > This is odd. Are you running on which OS?
>>>>> >
>>>>> > Em 23/11/2013, ?s 19:19, "Ivan St. Ivanov" <
>>>>> ivan.st.ivanov at gmail.com >
>>>>> > escreveu:
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > Hi folks,
>>>>> >
>>>>> > I just downloaded the Forge 2 distribution from
>>>>> >
>>>>> https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=releases&g=org.jboss.forge&a=forge-distribution&v=2.0.0.Beta3&e=zip
>>>>> >
>>>>> > When I try to start it by running the forge script, I get the
>>>>> following
>>>>> > exception:
>>>>> >
>>>>> > Caused by: java.lang.ClassNotFoundException:
>>>>> > org.jboss.forge.bootstrap.Bootstrap
>>>>> >
>>>>> > at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>>>>> > at java.security.AccessController.doPrivileged(Native Method)
>>>>> > at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>>>>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>>>> > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>>>>> > at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>>> > Could not find the main class: org.jboss.forge.bootstrap.Bootstrap.
>>>>> Program
>>>>> > will exit.
>>>>> >
>>>>> > Am I missing something?
>>>>> >
>>>>> > Thanks,
>>>>> > Ivan
>>>>> >
>>>>> >
>>>>> >
>>>>> > _______________________________________________
>>>>> > forge-dev mailing list
>>>>> > forge-dev at lists.jboss.org
>>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>> >
>>>>> > _______________________________________________
>>>>> > forge-dev mailing list
>>>>> > forge-dev at lists.jboss.org
>>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>> >
>>>>> > _______________________________________________
>>>>> > forge-dev mailing list
>>>>> > forge-dev at lists.jboss.org
>>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Att,
>>>>> >
>>>>> > Rafael M. Pestano
>>>>> >
>>>>> > Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do
>>>>> Sul
>>>>> > Graduando em Ci?ncia da Computa??o UFRGS
>>>>> > http://conventionsframework.org
>>>>> > http://rpestano.wordpress.com/
>>>>> > @realpestano
>>>>> >
>>>>> > _______________________________________________
>>>>> > forge-dev mailing list
>>>>> > forge-dev at lists.jboss.org
>>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>>
>>>>> _______________________________________________
>>>>> forge-dev mailing list
>>>>> forge-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> forge-dev mailing list
>>>> forge-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>
>>>
>>>
>>>
>>> --
>>>  <http://www.advancedit.com.br/>Att,
>>>
>>> Rafael M. Pestano
>>>
>>> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
>>> Graduando em Ci?ncia da Computa??o UFRGS
>>> http://conventionsframework.org <http://conventions.github.io/home/>
>>>  http://rpestano.wordpress.com/
>>> @realpestano
>>>
>>
>>
>>
>> --
>>  <http://www.advancedit.com.br/>Att,
>>
>> Rafael M. Pestano
>>
>> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
>> Graduando em Ci?ncia da Computa??o UFRGS
>> http://conventionsframework.org <http://conventions.github.io/home/>
>>  http://rpestano.wordpress.com/
>> @realpestano
>>
>
>
>
> --
>  <http://www.advancedit.com.br/>Att,
>
> Rafael M. Pestano
>
> Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
> Graduando em Ci?ncia da Computa??o UFRGS
> http://conventionsframework.org <http://conventions.github.io/home/>
>  http://rpestano.wordpress.com/
> @realpestano
>
>
> _______________________________________________
> forge-dev mailing listforge-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
<http://www.advancedit.com.br/>Att,

Rafael M. Pestano

Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul
Graduando em Ci?ncia da Computa??o UFRGS
http://conventionsframework.org <http://conventions.github.io/home/>
http://rpestano.wordpress.com/
@realpestano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131209/64d56939/attachment-0001.html 

From lbaxter at redhat.com  Tue Dec 10 14:05:02 2013
From: lbaxter at redhat.com (Lincoln Baxter)
Date: Tue, 10 Dec 2013 14:05:02 -0500 (EST)
Subject: [forge-dev] Forge Teamcity build linking
In-Reply-To: <001e01cee9f3$b3029a20$1907ce60$@redhat.com>
References: <660624658.6929585.1385149587345.JavaMail.root@redhat.com>
	<177774015.6931157.1385149719419.JavaMail.root@redhat.com>
	<001e01cee9f3$b3029a20$1907ce60$@redhat.com>
Message-ID: <2028394091.14638924.1386702302568.JavaMail.root@redhat.com>

Thanks Tomaz,

We have another question.

We've started seeing this error. Any ideas what this is about?

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=6826&buildTypeId=Forge_FurnaceCdi_Linux&tab=buildLog#_focus=291

And a snippit for you:


------------------
[13:38:57][org.jboss.forge.furnace.container:cdi] Downloaded: http://repo1.maven.org/maven2/org/jboss/jboss-parent/12/jboss-parent-12.pom (0 B at 0.0 KB/sec)
[13:38:57][org.jboss.forge.furnace.container:cdi] [main] WARN org.eclipse.aether.internal.impl.DefaultUpdateCheckManager - Failed to write tracking file /store/repository/org/jboss/jboss-parent/12/jboss-parent-12.pom.lastUpdated
[13:38:57][org.jboss.forge.furnace.container:cdi] java.io.FileNotFoundException: /store/repository/org/jboss/jboss-parent/12/jboss-parent-12.pom.lastUpdated (Permission denied)
[13:38:57][org.jboss.forge.furnace.container:cdi] 	at java.io.RandomAccessFile.open(Native Method)
[13:38:57][org.jboss.forge.furnace.container:cdi] 	at java.io.RandomAccessFile.<init>(RandomAccessFile.java:233)
------------------


Thanks!

----- Original Message -----
From: "Tomaz Cerar" <tcerar at redhat.com>
To: "Lincoln Baxter" <lbaxter at redhat.com>
Sent: Monday, November 25, 2013 10:33:31 AM
Subject: RE: Forge Teamcity build linking

Hey,

All you need to do is add dependencies under build configuration.

Ping me on IRC 

--
tomaz

> -----Original Message-----
> From: Lincoln Baxter [mailto:lbaxter at redhat.com]
> Sent: Friday, November 22, 2013 8:49 PM
> To: Tomaz Cerar
> Cc: George Gastaldi
> Subject: Forge Teamcity build linking
> 
> Hey Tomaz,
> 
> I have a question about Teamcity. We are experiencing new build failures
> (apparently due to the addition of a new build module "Furnace - Container
> Simple").
> 
> How can we link the builds so that the Core - 2.0 build has access to the build
> result artifacts of this build, like you did with the Furnace Runtime and
> Container CDI builds?
> 
> I'm hoping we can learn enough to prevent the need for you to have to do
> this for us again in the future.
> 
> Thanks very much!
> 
> --
> Lincoln Baxter, III
> JBoss, by Red Hat
> lbaxter at redhat.com
> 
> "If you want something, you'll find a way; if you don't, you'll find an excuse."


From tcerar at redhat.com  Wed Dec 11 08:00:11 2013
From: tcerar at redhat.com (Tomaz Cerar)
Date: Wed, 11 Dec 2013 14:00:11 +0100
Subject: [forge-dev] Forge Teamcity build linking
In-Reply-To: <2028394091.14638924.1386702302568.JavaMail.root@redhat.com>
References: <660624658.6929585.1385149587345.JavaMail.root@redhat.com>
	<177774015.6931157.1385149719419.JavaMail.root@redhat.com>
	<001e01cee9f3$b3029a20$1907ce60$@redhat.com>
	<2028394091.14638924.1386702302568.JavaMail.root@redhat.com>
Message-ID: <01aa01cef670$f2024c50$d606e4f0$@redhat.com>

Hi,

I think this was intermittent issue that should be solved. I was doing some mentainence work on few build agents
Where I also dropped local maven cache. Not sure how this permission issue could have occurred.

Btw brontes now has local nexus mirror to speed up building on clean local repositories. 
You can configure to use it under maven build step settings. If not already configured.

--
tomaz

> -----Original Message-----
> From: Lincoln Baxter [mailto:lbaxter at redhat.com]
> Sent: Tuesday, December 10, 2013 8:05 PM
> To: Tomaz Cerar
> Cc: Forge Dev List
> Subject: Re: Forge Teamcity build linking
> 
> Thanks Tomaz,
> 
> We have another question.
> 
> We've started seeing this error. Any ideas what this is about?
> 
> http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=6826&buildTy
> peId=Forge_FurnaceCdi_Linux&tab=buildLog#_focus=291
> 
> And a snippit for you:
> 
> 
> ------------------
> [13:38:57][org.jboss.forge.furnace.container:cdi] Downloaded:
> http://repo1.maven.org/maven2/org/jboss/jboss-parent/12/jboss-parent-
> 12.pom (0 B at 0.0 KB/sec)
> [13:38:57][org.jboss.forge.furnace.container:cdi] [main] WARN
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager - Failed to
> write tracking file /store/repository/org/jboss/jboss-parent/12/jboss-parent-
> 12.pom.lastUpdated
> [13:38:57][org.jboss.forge.furnace.container:cdi]
> java.io.FileNotFoundException: /store/repository/org/jboss/jboss-
> parent/12/jboss-parent-12.pom.lastUpdated (Permission denied)
> [13:38:57][org.jboss.forge.furnace.container:cdi] 	at
> java.io.RandomAccessFile.open(Native Method)
> [13:38:57][org.jboss.forge.furnace.container:cdi] 	at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:233)
> ------------------
> 
> 
> Thanks!
> 
> ----- Original Message -----
> From: "Tomaz Cerar" <tcerar at redhat.com>
> To: "Lincoln Baxter" <lbaxter at redhat.com>
> Sent: Monday, November 25, 2013 10:33:31 AM
> Subject: RE: Forge Teamcity build linking
> 
> Hey,
> 
> All you need to do is add dependencies under build configuration.
> 
> Ping me on IRC
> 
> --
> tomaz
> 
> > -----Original Message-----
> > From: Lincoln Baxter [mailto:lbaxter at redhat.com]
> > Sent: Friday, November 22, 2013 8:49 PM
> > To: Tomaz Cerar
> > Cc: George Gastaldi
> > Subject: Forge Teamcity build linking
> >
> > Hey Tomaz,
> >
> > I have a question about Teamcity. We are experiencing new build failures
> > (apparently due to the addition of a new build module "Furnace -
> Container
> > Simple").
> >
> > How can we link the builds so that the Core - 2.0 build has access to the
> build
> > result artifacts of this build, like you did with the Furnace Runtime and
> > Container CDI builds?
> >
> > I'm hoping we can learn enough to prevent the need for you to have to do
> > this for us again in the future.
> >
> > Thanks very much!
> >
> > --
> > Lincoln Baxter, III
> > JBoss, by Red Hat
> > lbaxter at redhat.com
> >
> > "If you want something, you'll find a way; if you don't, you'll find an
> excuse."




From lincolnbaxter at gmail.com  Wed Dec 11 12:00:12 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 11 Dec 2013 12:00:12 -0500
Subject: [forge-dev] Meeting minutes 2013-12-11
Message-ID: <CAEp_U4HKsjheMA3VYP9VFmfh12+NAhCxaj1eXu_Q=ret=_DrJA@mail.gmail.com>

Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2013/forge.2013-12-11-15.53.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2013/forge.2013-12-11-15.53.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2013/forge.2013-12-11-15.53.log.html

Meeting summary
---------------
* Agenda  (lincolnthree, 15:54:08)
  * Forge 2 Status  (lincolnthree, 15:54:08)
  * Forge 2 Website  (lincolnthree, 15:54:18)
  * Github Repository organization  (vineetreynolds, 15:56:41)
  * AngularJS scaffolding Status  (vineetreynolds, 15:57:13)

* Forge 2 Status  (lincolnthree, 15:57:45)
  * gastaldi and I will be pair programming the ui-controller today
    (lincolnthree, 15:58:09)
  * Forge 2 now requires JDK 7  (gastaldi, 15:58:42)

* Forge 2 Website  (lincolnthree, 16:03:57)

* Github Repository organization  (vineetreynolds, 16:16:05)
  * LINK: http://paste2.org/31bZ7GdV   (lincolnthree, 16:22:28)

* AngularJS scaffolding Status  (vineetreynolds, 16:47:19)

Meeting ended at 16:50:55 UTC.




Action Items
------------





Action Items, by person
-----------------------
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* lincolnthree (119)
* gastaldi (92)
* vineetreynolds (54)
* koentsje (26)
* dbeer (5)
* jbossbot (4)
* jbott (4)
* crobson (2)


-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131211/fc483949/attachment.html 

From lincolnbaxter at gmail.com  Thu Dec 12 15:06:28 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 12 Dec 2013 15:06:28 -0500
Subject: [forge-dev] Problems building connection-profiles branch of
	jbosstools-forge
Message-ID: <CAEp_U4Hfa-MDUZhBp21b9e3CXZ0xQH27q5hUK8=jV0obo6UX5w@mail.gmail.com>

Any ideas?


------------------


[ERROR] Cannot resolve project dependencies:

[ERROR]   Software being installed: org.jboss.tools.forge.ui.ext
1.1.0.qualifier

[ERROR]   Missing requirement: org.jboss.tools.forge.ui.ext 1.1.0.qualifier
requires 'bundle org.eclipse.datatools.connectivity 1.2.9' but it could not
be found

[ERROR]

[ERROR] Internal error: java.lang.RuntimeException: No solution found
because the problem is unsatisfiable.: [Unable to satisfy dependency from
org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
problem is unsatisfiable.] -> [Help 1]

org.apache.maven.InternalErrorException: Internal error:
java.lang.RuntimeException: No solution found because the problem is
unsatisfiable.: [Unable to satisfy dependency from
org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
problem is unsatisfiable.]

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:601)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: java.lang.RuntimeException: No solution found because the
problem is unsatisfiable.: [Unable to satisfy dependency from
org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
problem is unsatisfiable.]

at
org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)

at
org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)

at
org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)

at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134)

at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87)

at
org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369)

at
org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345)

at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)

at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)

... 11 more

[ERROR]

-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131212/f78ca7cb/attachment.html 

From ggastald at redhat.com  Thu Dec 12 15:16:16 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 12 Dec 2013 15:16:16 -0500 (EST)
Subject: [forge-dev] Problems building connection-profiles branch
	of	jbosstools-forge
In-Reply-To: <CAEp_U4Hfa-MDUZhBp21b9e3CXZ0xQH27q5hUK8=jV0obo6UX5w@mail.gmail.com>
References: <CAEp_U4Hfa-MDUZhBp21b9e3CXZ0xQH27q5hUK8=jV0obo6UX5w@mail.gmail.com>
Message-ID: <4FBFED3F-BB78-4A32-8D86-2905EAFDB65F@redhat.com>

Looks like self-explanatory.
Tycho couldn't resolve the dependency from the current environment. Do you have this dependency installed in Eclipse?

> Em 12/12/2013, ?s 18:06, "Lincoln Baxter, III" <lincolnbaxter at gmail.com> escreveu:
> 
> Any ideas?
> 
> 
> 
> ------------------
> 
> 
> 
> [ERROR] Cannot resolve project dependencies:
> 
> [ERROR]   Software being installed: org.jboss.tools.forge.ui.ext 1.1.0.qualifier
> 
> [ERROR]   Missing requirement: org.jboss.tools.forge.ui.ext 1.1.0.qualifier requires 'bundle org.eclipse.datatools.connectivity 1.2.9' but it could not be found
> 
> [ERROR] 
> 
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.] -> [Help 1]
> 
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.]
> 
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
> 
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> 
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> 
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 
> at java.lang.reflect.Method.invoke(Method.java:601)
> 
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 
> Caused by: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.]
> 
> at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)
> 
> at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)
> 
> at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
> 
> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134)
> 
> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87)
> 
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369)
> 
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345)
> 
> at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)
> 
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
> 
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
> 
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> 
> ... 11 more
> 
> [ERROR] 
> 
> 
> -- 
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131212/eb76ffbd/attachment-0001.html 

From lincolnbaxter at gmail.com  Thu Dec 12 15:19:33 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 12 Dec 2013 15:19:33 -0500
Subject: [forge-dev] Problems building connection-profiles branch of
	jbosstools-forge
In-Reply-To: <4FBFED3F-BB78-4A32-8D86-2905EAFDB65F@redhat.com>
References: <CAEp_U4Hfa-MDUZhBp21b9e3CXZ0xQH27q5hUK8=jV0obo6UX5w@mail.gmail.com>
	<4FBFED3F-BB78-4A32-8D86-2905EAFDB65F@redhat.com>
Message-ID: <CAEp_U4FXsPvnZMd45oBGoNPaGpHcLA9PXdj4o4_3_+BTxiBmKQ@mail.gmail.com>

This is from the maven build.


On Thu, Dec 12, 2013 at 3:16 PM, George Gastaldi <ggastald at redhat.com>wrote:

> Looks like self-explanatory.
> Tycho couldn't resolve the dependency from the current environment. Do you
> have this dependency installed in Eclipse?
>
> Em 12/12/2013, ?s 18:06, "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
> escreveu:
>
> Any ideas?
>
>
> ------------------
>
>
> [ERROR] Cannot resolve project dependencies:
>
> [ERROR]   Software being installed: org.jboss.tools.forge.ui.ext
> 1.1.0.qualifier
>
> [ERROR]   Missing requirement: org.jboss.tools.forge.ui.ext
> 1.1.0.qualifier requires 'bundle org.eclipse.datatools.connectivity 1.2.9'
> but it could not be found
>
> [ERROR]
>
> [ERROR] Internal error: java.lang.RuntimeException: No solution found
> because the problem is unsatisfiable.: [Unable to satisfy dependency from
> org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
> org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
> problem is unsatisfiable.] -> [Help 1]
>
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.RuntimeException: No solution found because the problem is
> unsatisfiable.: [Unable to satisfy dependency from
> org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
> org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
> problem is unsatisfiable.]
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:601)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: java.lang.RuntimeException: No solution found because the
> problem is unsatisfiable.: [Unable to satisfy dependency from
> org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
> org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
> problem is unsatisfiable.]
>
> at
> org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)
>
> at
> org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)
>
> at
> org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
>
> at
> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134)
>
> at
> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87)
>
> at
> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369)
>
> at
> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345)
>
> at
> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)
>
> at
> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
>
> ... 11 more
>
> [ERROR]
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131212/7f89349f/attachment.html 

From lincolnbaxter at gmail.com  Thu Dec 12 15:20:06 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 12 Dec 2013 15:20:06 -0500
Subject: [forge-dev] Problems building connection-profiles branch of
	jbosstools-forge
In-Reply-To: <CAEp_U4FXsPvnZMd45oBGoNPaGpHcLA9PXdj4o4_3_+BTxiBmKQ@mail.gmail.com>
References: <CAEp_U4Hfa-MDUZhBp21b9e3CXZ0xQH27q5hUK8=jV0obo6UX5w@mail.gmail.com>
	<4FBFED3F-BB78-4A32-8D86-2905EAFDB65F@redhat.com>
	<CAEp_U4FXsPvnZMd45oBGoNPaGpHcLA9PXdj4o4_3_+BTxiBmKQ@mail.gmail.com>
Message-ID: <CAEp_U4GrpQTqh5Pb8_w8myH97n=qyHmDQu6P214WyCWnC4k5og@mail.gmail.com>

And I don't know if it's needed or not for what Koen is working on :)


On Thu, Dec 12, 2013 at 3:19 PM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> This is from the maven build.
>
>
> On Thu, Dec 12, 2013 at 3:16 PM, George Gastaldi <ggastald at redhat.com>wrote:
>
>> Looks like self-explanatory.
>> Tycho couldn't resolve the dependency from the current environment. Do
>> you have this dependency installed in Eclipse?
>>
>> Em 12/12/2013, ?s 18:06, "Lincoln Baxter, III" <lincolnbaxter at gmail.com>
>> escreveu:
>>
>>  Any ideas?
>>
>>
>> ------------------
>>
>>
>> [ERROR] Cannot resolve project dependencies:
>>
>> [ERROR]   Software being installed: org.jboss.tools.forge.ui.ext
>> 1.1.0.qualifier
>>
>> [ERROR]   Missing requirement: org.jboss.tools.forge.ui.ext
>> 1.1.0.qualifier requires 'bundle org.eclipse.datatools.connectivity 1.2.9'
>> but it could not be found
>>
>> [ERROR]
>>
>> [ERROR] Internal error: java.lang.RuntimeException: No solution found
>> because the problem is unsatisfiable.: [Unable to satisfy dependency from
>> org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
>> org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
>> problem is unsatisfiable.] -> [Help 1]
>>
>> org.apache.maven.InternalErrorException: Internal error:
>> java.lang.RuntimeException: No solution found because the problem is
>> unsatisfiable.: [Unable to satisfy dependency from
>> org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
>> org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
>> problem is unsatisfiable.]
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:601)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>> Caused by: java.lang.RuntimeException: No solution found because the
>> problem is unsatisfiable.: [Unable to satisfy dependency from
>> org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle
>> org.eclipse.datatools.connectivity 1.2.9.; No solution found because the
>> problem is unsatisfiable.]
>>
>> at
>> org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)
>>
>> at
>> org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)
>>
>> at
>> org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
>>
>> at
>> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134)
>>
>> at
>> org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87)
>>
>> at
>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369)
>>
>> at
>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345)
>>
>> at
>> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)
>>
>> at
>> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
>>
>> ... 11 more
>>
>> [ERROR]
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131212/09c977a8/attachment.html 

From ggastald at redhat.com  Thu Dec 12 15:20:54 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 12 Dec 2013 15:20:54 -0500 (EST)
Subject: [forge-dev] Problems building connection-profiles branch
	of	jbosstools-forge
In-Reply-To: <CAEp_U4FXsPvnZMd45oBGoNPaGpHcLA9PXdj4o4_3_+BTxiBmKQ@mail.gmail.com>
References: <CAEp_U4Hfa-MDUZhBp21b9e3CXZ0xQH27q5hUK8=jV0obo6UX5w@mail.gmail.com>
	<4FBFED3F-BB78-4A32-8D86-2905EAFDB65F@redhat.com>
	<CAEp_U4FXsPvnZMd45oBGoNPaGpHcLA9PXdj4o4_3_+BTxiBmKQ@mail.gmail.com>
Message-ID: <20DF6197-2051-47E3-9D56-ACD6C54AE11A@redhat.com>

Hum, then perhaps some configuration is missing from the JBT parent POM

> Em 12/12/2013, ?s 18:19, "Lincoln Baxter, III" <lincolnbaxter at gmail.com> escreveu:
> 
> This is from the maven build.
> 
> 
>> On Thu, Dec 12, 2013 at 3:16 PM, George Gastaldi <ggastald at redhat.com> wrote:
>> Looks like self-explanatory.
>> Tycho couldn't resolve the dependency from the current environment. Do you have this dependency installed in Eclipse?
>> 
>>> Em 12/12/2013, ?s 18:06, "Lincoln Baxter, III" <lincolnbaxter at gmail.com> escreveu:
>>> 
>> 
>>> Any ideas?
>>> 
>>> 
>>> 
>>> ------------------
>>> 
>>> 
>>> 
>>> [ERROR] Cannot resolve project dependencies:
>>> 
>>> [ERROR]   Software being installed: org.jboss.tools.forge.ui.ext 1.1.0.qualifier
>>> 
>>> [ERROR]   Missing requirement: org.jboss.tools.forge.ui.ext 1.1.0.qualifier requires 'bundle org.eclipse.datatools.connectivity 1.2.9' but it could not be found
>>> 
>>> [ERROR] 
>>> 
>>> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.] -> [Help 1]
>>> 
>>> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.]
>>> 
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
>>> 
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>>> 
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>>> 
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>>> 
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> 
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> 
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> 
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> 
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>> 
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>> 
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>> 
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>> 
>>> Caused by: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.]
>>> 
>>> at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)
>>> 
>>> at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)
>>> 
>>> at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
>>> 
>>> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134)
>>> 
>>> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87)
>>> 
>>> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369)
>>> 
>>> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345)
>>> 
>>> at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)
>>> 
>>> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
>>> 
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
>>> 
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
>>> 
>>> ... 11 more
>>> 
>>> [ERROR] 
>>> 
>>> 
>>> -- 
>>> Lincoln Baxter, III
>>> http://ocpsoft.org
>>> "Simpler is better."
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> -- 
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131212/b1b2cecb/attachment-0001.html 

From vpereira at redhat.com  Mon Dec 16 16:25:53 2013
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Mon, 16 Dec 2013 16:25:53 -0500 (EST)
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
Message-ID: <1928607956.40560513.1387229153309.JavaMail.root@redhat.com>

Adding forge-dev.

----- Original Message -----
> From: "Burr Sutter" <bsutter at redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Tuesday, December 17, 2013 1:59:41 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> That seems to do the trick - now, where do we apply the fix? :-)

Well, ideally this would be a feature request in Forge to support a new type
of a REST resource. But a couple of modified lines might not warrant it.

It would be better to treat this as a flag to be enabled during REST resource
scaffolding. It would allow users to choose how the resource behaves -
 * send a 201 response with Location header, 
 * send a 201 response with Location header and also a response entity.

It would most likely be addressed in Forge 2.

> 
> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> 
> 
> ----- Original Message -----
> 
> 
> From: "Lucas Holmquist" < lholmqui at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
> Sent: Tuesday, December 17, 2013 12:53:25 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> 
> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
> 
> 
> 
> Adding Vineet as he has spent time on the Forge REST scaffolding.
> 
> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
> 
> 
> 
> Burr,
> I've added some logs statements on the client and basically it seems it
> can not parse the response from the server :
> 
> I/Web Console( 1386): textStatus: parsererror at
> file:///android_asset/www/js/index.js:103
> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
> file:///android_asset/www/js/index.js:104
> 
> If I do a CURL like this :
> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
> "Content-type: application/json" -X POST -d
> '{"phoneNumber":"1234567890","email":"newTest at test.com","name":"newTest"}'
> http://agmobile-html5.rhcloud.com/rest/forge/members
> 
> I should have pointed to the sources to the REST endpoint:
> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
> This was generated by Forge as I am too lazy to type up a full CRUD REST
> endpoint myself :-)
> 
> 
> 
> I got an correct answer but the content type is 'text/plain' , please
> check your rest endpoint to be sure it's producing json as output, that
> should solve your issue.
> It says
> @POST
> @Consumes("application/json")
> 
> needs a @Produces("application/json")
> 
> I'm not sure that will help. The response is a HTTP 201 with a Location
> header.
> Is the client expecting an entity of type application/json in the response ?
> 
> If yes, then the method should look like:
> 
> @POST
> @Consumes("application/json")
> public Response create(MemberDTO dto)
> {
> Member entity = dto.fromDTO(null, em);
> em.persist(entity);
> return
> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
> }
> 
> I've added : .entity(entity) in the above method to populate the response
> with the entity.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Could you also paste the commands you used in Forge to scaffold the REST
> endpoints so that we can check there hasn't been an incompatibility
> introduced ?
> I just used the Forge Wizard that is built into JBDS/Tools
> http://screencast.com/t/QrKkCoFZMUn
> 
> error.status is 201
> error.responseText is blank
> 
> 
> 
> 
> 
> 
> 
> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter at redhat.com> wrote:
> I am having a problem with pipe.save(), likely user error :-)
> 
> For some reason, the POST is occurring, the save seems to work but the
> error callback is invoked, not the success method.
> 
> And I am doing all of this in the context of our tooling which has some
> limitations (auto-closing console/firebug lite)
> 
> http://screencast.com/t/gosd7Qnhz
> 
> REST endpoint:
> http://agmobile-html5.rhcloud.com/rest/forge/members
> Use of Forge, with the Member.java entity to offer full CRUD capabilities
> 
> Sources:
> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
> 
> 
> _______________________________________________
> 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
> 
> _______________________________________________
> 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
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

From vpereira at redhat.com  Mon Dec 16 16:27:10 2013
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Mon, 16 Dec 2013 16:27:10 -0500 (EST)
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
Message-ID: <1835599751.40562229.1387229230777.JavaMail.root@redhat.com>


I missed something: raised https://issues.jboss.org/browse/FORGE-1361 to track this.

If there is anything more specific to Aerogear clients that can be done, I'd like to know about them as well.

----- Original Message -----
> From: "Vineet Reynolds Pereira" <vpereira at redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Cc: "forge-dev List" <forge-dev at lists.jboss.org>
> Sent: Tuesday, December 17, 2013 2:55:53 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> Adding forge-dev.
> 
> ----- Original Message -----
> > From: "Burr Sutter" <bsutter at redhat.com>
> > To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> > Sent: Tuesday, December 17, 2013 1:59:41 AM
> > Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> > 
> > That seems to do the trick - now, where do we apply the fix? :-)
> 
> Well, ideally this would be a feature request in Forge to support a new type
> of a REST resource. But a couple of modified lines might not warrant it.
> 
> It would be better to treat this as a flag to be enabled during REST resource
> scaffolding. It would allow users to choose how the resource behaves -
>  * send a 201 response with Location header,
>  * send a 201 response with Location header and also a response entity.
> 
> It would most likely be addressed in Forge 2.
> 
> > 
> > On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com
> > >
> > wrote:
> > 
> > 
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> > 
> > 
> > From: "Lucas Holmquist" < lholmqui at redhat.com >
> > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> > Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
> > Sent: Tuesday, December 17, 2013 12:53:25 AM
> > Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> > 
> > 
> > On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
> > 
> > 
> > 
> > Adding Vineet as he has spent time on the Forge REST scaffolding.
> > 
> > On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
> > 
> > 
> > 
> > Burr,
> > I've added some logs statements on the client and basically it seems it
> > can not parse the response from the server :
> > 
> > I/Web Console( 1386): textStatus: parsererror at
> > file:///android_asset/www/js/index.js:103
> > I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
> > file:///android_asset/www/js/index.js:104
> > 
> > If I do a CURL like this :
> > curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
> > "Content-type: application/json" -X POST -d
> > '{"phoneNumber":"1234567890","email":"newTest at test.com","name":"newTest"}'
> > http://agmobile-html5.rhcloud.com/rest/forge/members
> > 
> > I should have pointed to the sources to the REST endpoint:
> > https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
> > This was generated by Forge as I am too lazy to type up a full CRUD REST
> > endpoint myself :-)
> > 
> > 
> > 
> > I got an correct answer but the content type is 'text/plain' , please
> > check your rest endpoint to be sure it's producing json as output, that
> > should solve your issue.
> > It says
> > @POST
> > @Consumes("application/json")
> > 
> > needs a @Produces("application/json")
> > 
> > I'm not sure that will help. The response is a HTTP 201 with a Location
> > header.
> > Is the client expecting an entity of type application/json in the response
> > ?
> > 
> > If yes, then the method should look like:
> > 
> > @POST
> > @Consumes("application/json")
> > public Response create(MemberDTO dto)
> > {
> > Member entity = dto.fromDTO(null, em);
> > em.persist(entity);
> > return
> > Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
> > }
> > 
> > I've added : .entity(entity) in the above method to populate the response
> > with the entity.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Could you also paste the commands you used in Forge to scaffold the REST
> > endpoints so that we can check there hasn't been an incompatibility
> > introduced ?
> > I just used the Forge Wizard that is built into JBDS/Tools
> > http://screencast.com/t/QrKkCoFZMUn
> > 
> > error.status is 201
> > error.responseText is blank
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter at redhat.com> wrote:
> > I am having a problem with pipe.save(), likely user error :-)
> > 
> > For some reason, the POST is occurring, the save seems to work but the
> > error callback is invoked, not the success method.
> > 
> > And I am doing all of this in the context of our tooling which has some
> > limitations (auto-closing console/firebug lite)
> > 
> > http://screencast.com/t/gosd7Qnhz
> > 
> > REST endpoint:
> > http://agmobile-html5.rhcloud.com/rest/forge/members
> > Use of Forge, with the Member.java entity to offer full CRUD capabilities
> > 
> > Sources:
> > https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
> > 
> > 
> > _______________________________________________
> > 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
> > 
> > _______________________________________________
> > 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
> > 
> > 
> > _______________________________________________
> > 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
> 

From bsutter at redhat.com  Mon Dec 16 17:41:54 2013
From: bsutter at redhat.com (Burr Sutter)
Date: Mon, 16 Dec 2013 17:41:54 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
Message-ID: <E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>

I need to find my REST bible - what is typical to respond to the POST with the JSON-serialized entity that was originally POST'd or to simply respond with a basic acknowledgement (http 201)?


On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira <vpereira at redhat.com> wrote:

> Adding forge-dev.
> 
> ----- Original Message -----
>> From: "Burr Sutter" <bsutter at redhat.com>
>> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
>> Sent: Tuesday, December 17, 2013 1:59:41 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>> 
>> That seems to do the trick - now, where do we apply the fix? :-)
> 
> Well, ideally this would be a feature request in Forge to support a new type
> of a REST resource. But a couple of modified lines might not warrant it.
> 
> It would be better to treat this as a flag to be enabled during REST resource
> scaffolding. It would allow users to choose how the resource behaves -
> * send a 201 response with Location header, 
> * send a 201 response with Location header and also a response entity.
> 
> It would most likely be addressed in Forge 2.
> 
>> 
>> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
>> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> ----- Original Message -----
>> 
>> 
>> From: "Lucas Holmquist" < lholmqui at redhat.com >
>> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
>> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
>> Sent: Tuesday, December 17, 2013 12:53:25 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>> 
>> 
>> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
>> 
>> 
>> 
>> Adding Vineet as he has spent time on the Forge REST scaffolding.
>> 
>> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
>> 
>> 
>> 
>> Burr,
>> I've added some logs statements on the client and basically it seems it
>> can not parse the response from the server :
>> 
>> I/Web Console( 1386): textStatus: parsererror at
>> file:///android_asset/www/js/index.js:103
>> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
>> file:///android_asset/www/js/index.js:104
>> 
>> If I do a CURL like this :
>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
>> "Content-type: application/json" -X POST -d
>> '{"phoneNumber":"1234567890","email":"newTest at test.com","name":"newTest"}'
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>> 
>> I should have pointed to the sources to the REST endpoint:
>> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
>> This was generated by Forge as I am too lazy to type up a full CRUD REST
>> endpoint myself :-)
>> 
>> 
>> 
>> I got an correct answer but the content type is 'text/plain' , please
>> check your rest endpoint to be sure it's producing json as output, that
>> should solve your issue.
>> It says
>> @POST
>> @Consumes("application/json")
>> 
>> needs a @Produces("application/json")
>> 
>> I'm not sure that will help. The response is a HTTP 201 with a Location
>> header.
>> Is the client expecting an entity of type application/json in the response ?
>> 
>> If yes, then the method should look like:
>> 
>> @POST
>> @Consumes("application/json")
>> public Response create(MemberDTO dto)
>> {
>> Member entity = dto.fromDTO(null, em);
>> em.persist(entity);
>> return
>> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
>> }
>> 
>> I've added : .entity(entity) in the above method to populate the response
>> with the entity.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Could you also paste the commands you used in Forge to scaffold the REST
>> endpoints so that we can check there hasn't been an incompatibility
>> introduced ?
>> I just used the Forge Wizard that is built into JBDS/Tools
>> http://screencast.com/t/QrKkCoFZMUn
>> 
>> error.status is 201
>> error.responseText is blank
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter at redhat.com> wrote:
>> I am having a problem with pipe.save(), likely user error :-)
>> 
>> For some reason, the POST is occurring, the save seems to work but the
>> error callback is invoked, not the success method.
>> 
>> And I am doing all of this in the context of our tooling which has some
>> limitations (auto-closing console/firebug lite)
>> 
>> http://screencast.com/t/gosd7Qnhz
>> 
>> REST endpoint:
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>> Use of Forge, with the Member.java entity to offer full CRUD capabilities
>> 
>> Sources:
>> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
>> 
>> 
>> _______________________________________________
>> 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
>> 
>> _______________________________________________
>> 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
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131216/2c37d994/attachment-0001.html 

From lincolnbaxter at gmail.com  Mon Dec 16 17:58:42 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Mon, 16 Dec 2013 17:58:42 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
Message-ID: <CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>

Either is typical, but I think that most "pure" restifarians would favor
the 201.


On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter <bsutter at redhat.com> wrote:

> I need to find my REST bible - what is typical to respond to the POST with
> the JSON-serialized entity that was originally POST'd or to simply respond
> with a basic acknowledgement (http 201)?
>
>
> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira <vpereira at redhat.com>
> wrote:
>
> Adding forge-dev.
>
> ----- Original Message -----
>
> From: "Burr Sutter" <bsutter at redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Tuesday, December 17, 2013 1:59:41 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>
> That seems to do the trick - now, where do we apply the fix? :-)
>
>
> Well, ideally this would be a feature request in Forge to support a new
> type
> of a REST resource. But a couple of modified lines might not warrant it.
>
> It would be better to treat this as a flag to be enabled during REST
> resource
> scaffolding. It would allow users to choose how the resource behaves -
> * send a 201 response with Location header,
> * send a 201 response with Location header and also a response entity.
>
> It would most likely be addressed in Forge 2.
>
>
> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com>
> wrote:
>
>
>
>
>
>
> ----- Original Message -----
>
>
> From: "Lucas Holmquist" < lholmqui at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
> Sent: Tuesday, December 17, 2013 12:53:25 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>
>
> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
>
>
>
> Adding Vineet as he has spent time on the Forge REST scaffolding.
>
> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com >
> wrote:
>
>
>
> Burr,
> I've added some logs statements on the client and basically it seems it
> can not parse the response from the server :
>
> I/Web Console( 1386): textStatus: parsererror at
> file:///android_asset/www/js/index.js:103
> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
> file:///android_asset/www/js/index.js:104
>
> If I do a CURL like this :
> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
> "Content-type: application/json" -X POST -d
> '{"phoneNumber":"1234567890","email":"newTest at test.com","name":"newTest"}'
> http://agmobile-html5.rhcloud.com/rest/forge/members
>
> I should have pointed to the sources to the REST endpoint:
>
> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
> This was generated by Forge as I am too lazy to type up a full CRUD REST
> endpoint myself :-)
>
>
>
> I got an correct answer but the content type is 'text/plain' , please
> check your rest endpoint to be sure it's producing json as output, that
> should solve your issue.
> It says
> @POST
> @Consumes("application/json")
>
> needs a @Produces("application/json")
>
> I'm not sure that will help. The response is a HTTP 201 with a Location
> header.
> Is the client expecting an entity of type application/json in the response
> ?
>
> If yes, then the method should look like:
>
> @POST
> @Consumes("application/json")
> public Response create(MemberDTO dto)
> {
> Member entity = dto.fromDTO(null, em);
> em.persist(entity);
> return
>
> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
> }
>
> I've added : .entity(entity) in the above method to populate the response
> with the entity.
>
>
>
>
>
>
>
>
>
>
> Could you also paste the commands you used in Forge to scaffold the REST
> endpoints so that we can check there hasn't been an incompatibility
> introduced ?
> I just used the Forge Wizard that is built into JBDS/Tools
> http://screencast.com/t/QrKkCoFZMUn
>
> error.status is 201
> error.responseText is blank
>
>
>
>
>
>
>
> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter at redhat.com> wrote:
> I am having a problem with pipe.save(), likely user error :-)
>
> For some reason, the POST is occurring, the save seems to work but the
> error callback is invoked, not the success method.
>
> And I am doing all of this in the context of our tooling which has some
> limitations (auto-closing console/firebug lite)
>
> http://screencast.com/t/gosd7Qnhz
>
> REST endpoint:
> http://agmobile-html5.rhcloud.com/rest/forge/members
> Use of Forge, with the Member.java entity to offer full CRUD capabilities
>
> Sources:
> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
>
>
> _______________________________________________
> 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
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131216/243c8f6d/attachment.html 

From ivan.st.ivanov at gmail.com  Tue Dec 17 03:58:44 2013
From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov)
Date: Tue, 17 Dec 2013 10:58:44 +0200
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
Message-ID: <CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>

Hi!

I think that the 'right' approach is to respond with 201 (created) and
return a URI to the newly created resource.

Cheers,
Ivan


On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> Either is typical, but I think that most "pure" restifarians would favor
> the 201.
>
>
> On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
>
>> I need to find my REST bible - what is typical to respond to the POST
>> with the JSON-serialized entity that was originally POST'd or to simply
>> respond with a basic acknowledgement (http 201)?
>>
>>
>> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira <vpereira at redhat.com>
>> wrote:
>>
>> Adding forge-dev.
>>
>> ----- Original Message -----
>>
>> From: "Burr Sutter" <bsutter at redhat.com>
>> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
>> Sent: Tuesday, December 17, 2013 1:59:41 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>>
>> That seems to do the trick - now, where do we apply the fix? :-)
>>
>>
>> Well, ideally this would be a feature request in Forge to support a new
>> type
>> of a REST resource. But a couple of modified lines might not warrant it.
>>
>> It would be better to treat this as a flag to be enabled during REST
>> resource
>> scaffolding. It would allow users to choose how the resource behaves -
>> * send a 201 response with Location header,
>> * send a 201 response with Location header and also a response entity.
>>
>> It would most likely be addressed in Forge 2.
>>
>>
>> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira <
>> vpereira at redhat.com >
>> wrote:
>>
>>
>>
>>
>>
>>
>> ----- Original Message -----
>>
>>
>> From: "Lucas Holmquist" < lholmqui at redhat.com >
>> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
>> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
>> Sent: Tuesday, December 17, 2013 12:53:25 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>>
>>
>> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
>>
>>
>>
>> Adding Vineet as he has spent time on the Forge REST scaffolding.
>>
>> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com >
>> wrote:
>>
>>
>>
>> Burr,
>> I've added some logs statements on the client and basically it seems it
>> can not parse the response from the server :
>>
>> I/Web Console( 1386): textStatus: parsererror at
>> file:///android_asset/www/js/index.js:103
>> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
>> file:///android_asset/www/js/index.js:104
>>
>> If I do a CURL like this :
>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
>> "Content-type: application/json" -X POST -d
>> '{"phoneNumber":"1234567890","email":"newTest at test.com
>> ","name":"newTest"}'
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>>
>> I should have pointed to the sources to the REST endpoint:
>>
>> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
>> This was generated by Forge as I am too lazy to type up a full CRUD REST
>> endpoint myself :-)
>>
>>
>>
>> I got an correct answer but the content type is 'text/plain' , please
>> check your rest endpoint to be sure it's producing json as output, that
>> should solve your issue.
>> It says
>> @POST
>> @Consumes("application/json")
>>
>> needs a @Produces("application/json")
>>
>> I'm not sure that will help. The response is a HTTP 201 with a Location
>> header.
>> Is the client expecting an entity of type application/json in the
>> response ?
>>
>> If yes, then the method should look like:
>>
>> @POST
>> @Consumes("application/json")
>> public Response create(MemberDTO dto)
>> {
>> Member entity = dto.fromDTO(null, em);
>> em.persist(entity);
>> return
>>
>> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
>> }
>>
>> I've added : .entity(entity) in the above method to populate the response
>> with the entity.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Could you also paste the commands you used in Forge to scaffold the REST
>> endpoints so that we can check there hasn't been an incompatibility
>> introduced ?
>> I just used the Forge Wizard that is built into JBDS/Tools
>> http://screencast.com/t/QrKkCoFZMUn
>>
>> error.status is 201
>> error.responseText is blank
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter at redhat.com> wrote:
>> I am having a problem with pipe.save(), likely user error :-)
>>
>> For some reason, the POST is occurring, the save seems to work but the
>> error callback is invoked, not the success method.
>>
>> And I am doing all of this in the context of our tooling which has some
>> limitations (auto-closing console/firebug lite)
>>
>> http://screencast.com/t/gosd7Qnhz
>>
>> REST endpoint:
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>> Use of Forge, with the Member.java entity to offer full CRUD capabilities
>>
>> Sources:
>> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
>>
>>
>> _______________________________________________
>> 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
>>
>> _______________________________________________
>> 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
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131217/2dfdb349/attachment-0001.html 

From sblanc at redhat.com  Tue Dec 17 04:25:14 2013
From: sblanc at redhat.com (Sebastien Blanc)
Date: Tue, 17 Dec 2013 10:25:14 +0100
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
	<CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
Message-ID: <52B0187A.9020903@redhat.com>

Adding again aerogear list.
I think that we must discuss with the team (aerogear) on how we can/must 
handle a proper 201 response.

On 12/17/2013 09:58 AM, Ivan St. Ivanov wrote:
> Hi!
>
> I think that the 'right' approach is to respond with 201 (created) and 
> return a URI to the newly created resource.
>
> Cheers,
> Ivan
>
>
> On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III 
> <lincolnbaxter at gmail.com <mailto:lincolnbaxter at gmail.com>> wrote:
>
>     Either is typical, but I think that most "pure" restifarians would
>     favor the 201.
>
>
>     On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter <bsutter at redhat.com
>     <mailto:bsutter at redhat.com>> wrote:
>
>         I need to find my REST bible - what is typical to respond to
>         the POST with the JSON-serialized entity that was originally
>         POST'd or to simply respond with a basic acknowledgement (http
>         201)?
>
>
>         On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira
>         <vpereira at redhat.com <mailto:vpereira at redhat.com>> wrote:
>
>>         Adding forge-dev.
>>
>>         ----- Original Message -----
>>>         From: "Burr Sutter" <bsutter at redhat.com
>>>         <mailto:bsutter at redhat.com>>
>>>         To: "AeroGear Developer Mailing List"
>>>         <aerogear-dev at lists.jboss.org
>>>         <mailto:aerogear-dev at lists.jboss.org>>
>>>         Sent: Tuesday, December 17, 2013 1:59:41 AM
>>>         Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>>>
>>>         That seems to do the trick - now, where do we apply the fix? :-)
>>
>>         Well, ideally this would be a feature request in Forge to
>>         support a new type
>>         of a REST resource. But a couple of modified lines might not
>>         warrant it.
>>
>>         It would be better to treat this as a flag to be enabled
>>         during REST resource
>>         scaffolding. It would allow users to choose how the resource
>>         behaves -
>>         * send a 201 response with Location header,
>>         * send a 201 response with Location header and also a
>>         response entity.
>>
>>         It would most likely be addressed in Forge 2.
>>
>>>
>>>         On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira <
>>>         vpereira at redhat.com <mailto:vpereira at redhat.com> >
>>>         wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>         ----- Original Message -----
>>>
>>>
>>>         From: "Lucas Holmquist" < lholmqui at redhat.com
>>>         <mailto:lholmqui at redhat.com> >
>>>         To: "AeroGear Developer Mailing List" <
>>>         aerogear-dev at lists.jboss.org
>>>         <mailto:aerogear-dev at lists.jboss.org> >
>>>         Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com
>>>         <mailto:vpereira at redhat.com> >
>>>         Sent: Tuesday, December 17, 2013 12:53:25 AM
>>>         Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>>>
>>>
>>>         On Dec 16, 2013, at 1:52 PM, Burr Sutter <
>>>         bsutter at redhat.com <mailto:bsutter at redhat.com> > wrote:
>>>
>>>
>>>
>>>         Adding Vineet as he has spent time on the Forge REST
>>>         scaffolding.
>>>
>>>         On Dec 16, 2013, at 7:01 AM, Sebastien Blanc <
>>>         scm.blanc at gmail.com <mailto:scm.blanc at gmail.com> > wrote:
>>>
>>>
>>>
>>>         Burr,
>>>         I've added some logs statements on the client and basically
>>>         it seems it
>>>         can not parse the response from the server :
>>>
>>>         I/Web Console( 1386): textStatus: parsererror at
>>>         file:///android_asset/www/js/index.js:103
>>>         I/Web Console( 1386): error: SyntaxError: Unexpected end of
>>>         input at
>>>         file:///android_asset/www/js/index.js:104
>>>
>>>         If I do a CURL like this :
>>>         curl -v -b cookies.txt -c cookies.txt -H "Accept:
>>>         application/json" -H
>>>         "Content-type: application/json" -X POST -d
>>>         '{"phoneNumber":"1234567890","email":"newTest at test.com
>>>         <mailto:newTest at test.com>","name":"newTest"}'
>>>         http://agmobile-html5.rhcloud.com/rest/forge/members
>>>
>>>         I should have pointed to the sources to the REST endpoint:
>>>         https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
>>>         This was generated by Forge as I am too lazy to type up a
>>>         full CRUD REST
>>>         endpoint myself :-)
>>>
>>>
>>>
>>>         I got an correct answer but the content type is 'text/plain'
>>>         , please
>>>         check your rest endpoint to be sure it's producing json as
>>>         output, that
>>>         should solve your issue.
>>>         It says
>>>         @POST
>>>         @Consumes("application/json")
>>>
>>>         needs a @Produces("application/json")
>>>
>>>         I'm not sure that will help. The response is a HTTP 201 with
>>>         a Location
>>>         header.
>>>         Is the client expecting an entity of type application/json
>>>         in the response ?
>>>
>>>         If yes, then the method should look like:
>>>
>>>         @POST
>>>         @Consumes("application/json")
>>>         public Response create(MemberDTO dto)
>>>         {
>>>         Member entity = dto.fromDTO(null, em);
>>>         em.persist(entity);
>>>         return
>>>         Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
>>>         }
>>>
>>>         I've added : .entity(entity) in the above method to populate
>>>         the response
>>>         with the entity.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>         Could you also paste the commands you used in Forge to
>>>         scaffold the REST
>>>         endpoints so that we can check there hasn't been an
>>>         incompatibility
>>>         introduced ?
>>>         I just used the Forge Wizard that is built into JBDS/Tools
>>>         http://screencast.com/t/QrKkCoFZMUn
>>>
>>>         error.status is 201
>>>         error.responseText is blank
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>         On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter
>>>         <bsutter at redhat.com <mailto:bsutter at redhat.com>> wrote:
>>>         I am having a problem with pipe.save(), likely user error :-)
>>>
>>>         For some reason, the POST is occurring, the save seems to
>>>         work but the
>>>         error callback is invoked, not the success method.
>>>
>>>         And I am doing all of this in the context of our tooling
>>>         which has some
>>>         limitations (auto-closing console/firebug lite)
>>>
>>>         http://screencast.com/t/gosd7Qnhz
>>>
>>>         REST endpoint:
>>>         http://agmobile-html5.rhcloud.com/rest/forge/members
>>>         Use of Forge, with the Member.java entity to offer full CRUD
>>>         capabilities
>>>
>>>         Sources:
>>>         https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
>>>
>>>
>>>         _______________________________________________
>>>         aerogear-dev mailing list
>>>         aerogear-dev at lists.jboss.org
>>>         <mailto:aerogear-dev at lists.jboss.org>
>>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>         _______________________________________________
>>>         aerogear-dev mailing list
>>>         aerogear-dev at lists.jboss.org
>>>         <mailto:aerogear-dev at lists.jboss.org>
>>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>         _______________________________________________
>>>         aerogear-dev mailing list
>>>         aerogear-dev at lists.jboss.org
>>>         <mailto:aerogear-dev at lists.jboss.org>
>>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>         _______________________________________________
>>>         aerogear-dev mailing list
>>>         aerogear-dev at lists.jboss.org
>>>         <mailto:aerogear-dev at lists.jboss.org>
>>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>         _______________________________________________
>>>         aerogear-dev mailing list
>>>         aerogear-dev at lists.jboss.org
>>>         <mailto:aerogear-dev at lists.jboss.org>
>>>         https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>         _______________________________________________
>>         forge-dev mailing list
>>         forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>         _______________________________________________
>         forge-dev mailing list
>         forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>         https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
>     -- 
>     Lincoln Baxter, III
>     http://ocpsoft.org
>     "Simpler is better."
>
>     _______________________________________________
>     forge-dev mailing list
>     forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131217/d7ee0700/attachment-0001.html 

From vpereira at redhat.com  Tue Dec 17 04:36:14 2013
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Tue, 17 Dec 2013 04:36:14 -0500 (EST)
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <52B0187A.9020903@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
	<CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
	<52B0187A.9020903@redhat.com>
Message-ID: <521510137.40738790.1387272974513.JavaMail.root@redhat.com>



----- Original Message -----
> From: "Sebastien Blanc" <sblanc at redhat.com>
> To: forge-dev at lists.jboss.org, aerogear-dev at lists.jboss.org
> Sent: Tuesday, December 17, 2013 2:55:14 PM
> Subject: Re: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
> 
> Adding again aerogear list.
> I think that we must discuss with the team (aerogear) on how we can/must
> handle a proper 201 response.

I'd concur. Both of these are 'correct'. But it would be better to indicate 
if the client or consumers of the client should do anything more for 201 responses.

Several clients (Backbone.js [1], AngularJS[2] etc.) expect that responses to POST contain
the entity in the response. Consumers are expected to fetch the updated resource for a 201
with an empty body.

1: https://github.com/jashkenas/backbone/issues/1660
2: https://github.com/angular/angular.js/issues/2572


> 
> On 12/17/2013 09:58 AM, Ivan St. Ivanov wrote:
> 
> 
> 
> Hi!
> 
> I think that the 'right' approach is to respond with 201 (created) and return
> a URI to the newly created resource.
> 
> Cheers,
> Ivan
> 
> 
> On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III <
> lincolnbaxter at gmail.com > wrote:
> 
> 
> 
> Either is typical, but I think that most "pure" restifarians would favor the
> 201.
> 
> 
> On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter < bsutter at redhat.com > wrote:
> 
> 
> 
> I need to find my REST bible - what is typical to respond to the POST with
> the JSON-serialized entity that was originally POST'd or to simply respond
> with a basic acknowledgement (http 201)?
> 
> 
> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> Adding forge-dev.
> 
> ----- Original Message -----
> 
> 
> From: "Burr Sutter" < bsutter at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Sent: Tuesday, December 17, 2013 1:59:41 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> That seems to do the trick - now, where do we apply the fix? :-)
> 
> Well, ideally this would be a feature request in Forge to support a new type
> of a REST resource. But a couple of modified lines might not warrant it.
> 
> It would be better to treat this as a flag to be enabled during REST resource
> scaffolding. It would allow users to choose how the resource behaves -
> * send a 201 response with Location header,
> * send a 201 response with Location header and also a response entity.
> 
> It would most likely be addressed in Forge 2.
> 
> 
> 
> 
> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> 
> 
> ----- Original Message -----
> 
> 
> From: "Lucas Holmquist" < lholmqui at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
> Sent: Tuesday, December 17, 2013 12:53:25 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> 
> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
> 
> 
> 
> Adding Vineet as he has spent time on the Forge REST scaffolding.
> 
> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
> 
> 
> 
> Burr,
> I've added some logs statements on the client and basically it seems it
> can not parse the response from the server :
> 
> I/Web Console( 1386): textStatus: parsererror at
> file:///android_asset/www/js/index.js:103
> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
> file:///android_asset/www/js/index.js:104
> 
> If I do a CURL like this :
> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
> "Content-type: application/json" -X POST -d
> '{"phoneNumber":"1234567890","email":" newTest at test.com ","name":"newTest"}'
> http://agmobile-html5.rhcloud.com/rest/forge/members
> 
> I should have pointed to the sources to the REST endpoint:
> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
> This was generated by Forge as I am too lazy to type up a full CRUD REST
> endpoint myself :-)
> 
> 
> 
> I got an correct answer but the content type is 'text/plain' , please
> check your rest endpoint to be sure it's producing json as output, that
> should solve your issue.
> It says
> @POST
> @Consumes("application/json")
> 
> needs a @Produces("application/json")
> 
> I'm not sure that will help. The response is a HTTP 201 with a Location
> header.
> Is the client expecting an entity of type application/json in the response ?
> 
> If yes, then the method should look like:
> 
> @POST
> @Consumes("application/json")
> public Response create(MemberDTO dto)
> {
> Member entity = dto.fromDTO(null, em);
> em.persist(entity);
> return
> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
> }
> 
> I've added : .entity(entity) in the above method to populate the response
> with the entity.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Could you also paste the commands you used in Forge to scaffold the REST
> endpoints so that we can check there hasn't been an incompatibility
> introduced ?
> I just used the Forge Wizard that is built into JBDS/Tools
> http://screencast.com/t/QrKkCoFZMUn
> 
> error.status is 201
> error.responseText is blank
> 
> 
> 
> 
> 
> 
> 
> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter < bsutter at redhat.com > wrote:
> I am having a problem with pipe.save(), likely user error :-)
> 
> For some reason, the POST is occurring, the save seems to work but the
> error callback is invoked, not the success method.
> 
> And I am doing all of this in the context of our tooling which has some
> limitations (auto-closing console/firebug lite)
> 
> http://screencast.com/t/gosd7Qnhz
> 
> REST endpoint:
> http://agmobile-html5.rhcloud.com/rest/forge/members
> Use of Forge, with the Member.java entity to offer full CRUD capabilities
> 
> Sources:
> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
> 
> 
> _______________________________________________
> 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
> 
> _______________________________________________
> 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
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> _______________________________________________
> forge-dev mailing list forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

From lholmqui at redhat.com  Tue Dec 17 08:29:10 2013
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 17 Dec 2013 08:29:10 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <52B0187A.9020903@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
	<CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
	<52B0187A.9020903@redhat.com>
Message-ID: <98682D8D-478E-4D4E-87FE-C4F08B4F67AF@redhat.com>


On Dec 17, 2013, at 4:25 AM, Sebastien Blanc <sblanc at redhat.com> wrote:

> Adding again aerogear list.
> I think that we must discuss with the team (aerogear) on how we can/must handle a proper 201 response.

i don't see this as a client issue at all.  jQuery ajax is used under the hood here and it is handling the 201 fine,  but it is choking on parsing the response since it is not in the correct format, thus calling back in the error callback.

this should really be handled on the server

>  
> On 12/17/2013 09:58 AM, Ivan St. Ivanov wrote:
>> Hi!
>> 
>> I think that the 'right' approach is to respond with 201 (created) and return a URI to the newly created resource.
>> 
>> Cheers,
>> Ivan
>> 
>> 
>> On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
>> Either is typical, but I think that most "pure" restifarians would favor the 201.
>> 
>> 
>> On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
>> I need to find my REST bible - what is typical to respond to the POST with the JSON-serialized entity that was originally POST'd or to simply respond with a basic acknowledgement (http 201)?
>> 
>> 
>> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira <vpereira at redhat.com> wrote:
>> 
>>> Adding forge-dev.
>>> 
>>> ----- Original Message -----
>>>> From: "Burr Sutter" <bsutter at redhat.com>
>>>> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
>>>> Sent: Tuesday, December 17, 2013 1:59:41 AM
>>>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>>>> 
>>>> That seems to do the trick - now, where do we apply the fix? :-)
>>> 
>>> Well, ideally this would be a feature request in Forge to support a new type
>>> of a REST resource. But a couple of modified lines might not warrant it.
>>> 
>>> It would be better to treat this as a flag to be enabled during REST resource
>>> scaffolding. It would allow users to choose how the resource behaves -
>>> * send a 201 response with Location header, 
>>> * send a 201 response with Location header and also a response entity.
>>> 
>>> It would most likely be addressed in Forge 2.
>>> 
>>>> 
>>>> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
>>>> wrote:
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> ----- Original Message -----
>>>> 
>>>> 
>>>> From: "Lucas Holmquist" < lholmqui at redhat.com >
>>>> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
>>>> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
>>>> Sent: Tuesday, December 17, 2013 12:53:25 AM
>>>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>>>> 
>>>> 
>>>> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
>>>> 
>>>> 
>>>> 
>>>> Adding Vineet as he has spent time on the Forge REST scaffolding.
>>>> 
>>>> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
>>>> 
>>>> 
>>>> 
>>>> Burr,
>>>> I've added some logs statements on the client and basically it seems it
>>>> can not parse the response from the server :
>>>> 
>>>> I/Web Console( 1386): textStatus: parsererror at
>>>> file:///android_asset/www/js/index.js:103
>>>> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
>>>> file:///android_asset/www/js/index.js:104
>>>> 
>>>> If I do a CURL like this :
>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
>>>> "Content-type: application/json" -X POST -d
>>>> '{"phoneNumber":"1234567890","email":"newTest at test.com","name":"newTest"}'
>>>> http://agmobile-html5.rhcloud.com/rest/forge/members
>>>> 
>>>> I should have pointed to the sources to the REST endpoint:
>>>> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
>>>> This was generated by Forge as I am too lazy to type up a full CRUD REST
>>>> endpoint myself :-)
>>>> 
>>>> 
>>>> 
>>>> I got an correct answer but the content type is 'text/plain' , please
>>>> check your rest endpoint to be sure it's producing json as output, that
>>>> should solve your issue.
>>>> It says
>>>> @POST
>>>> @Consumes("application/json")
>>>> 
>>>> needs a @Produces("application/json")
>>>> 
>>>> I'm not sure that will help. The response is a HTTP 201 with a Location
>>>> header.
>>>> Is the client expecting an entity of type application/json in the response ?
>>>> 
>>>> If yes, then the method should look like:
>>>> 
>>>> @POST
>>>> @Consumes("application/json")
>>>> public Response create(MemberDTO dto)
>>>> {
>>>> Member entity = dto.fromDTO(null, em);
>>>> em.persist(entity);
>>>> return
>>>> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
>>>> }
>>>> 
>>>> I've added : .entity(entity) in the above method to populate the response
>>>> with the entity.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Could you also paste the commands you used in Forge to scaffold the REST
>>>> endpoints so that we can check there hasn't been an incompatibility
>>>> introduced ?
>>>> I just used the Forge Wizard that is built into JBDS/Tools
>>>> http://screencast.com/t/QrKkCoFZMUn
>>>> 
>>>> error.status is 201
>>>> error.responseText is blank
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>>> I am having a problem with pipe.save(), likely user error :-)
>>>> 
>>>> For some reason, the POST is occurring, the save seems to work but the
>>>> error callback is invoked, not the success method.
>>>> 
>>>> And I am doing all of this in the context of our tooling which has some
>>>> limitations (auto-closing console/firebug lite)
>>>> 
>>>> http://screencast.com/t/gosd7Qnhz
>>>> 
>>>> REST endpoint:
>>>> http://agmobile-html5.rhcloud.com/rest/forge/members
>>>> Use of Forge, with the Member.java entity to offer full CRUD capabilities
>>>> 
>>>> Sources:
>>>> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
>>>> 
>>>> _______________________________________________
>>>> 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
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> 
>> -- 
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131217/b9e04973/attachment-0001.html 

From bsutter at redhat.com  Tue Dec 17 08:55:02 2013
From: bsutter at redhat.com (Burr Sutter)
Date: Tue, 17 Dec 2013 08:55:02 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <521510137.40738790.1387272974513.JavaMail.root@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
	<CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
	<52B0187A.9020903@redhat.com>
	<521510137.40738790.1387272974513.JavaMail.root@redhat.com>
Message-ID: <1479565A-A100-48B2-A05F-9351EC223443@redhat.com>


On Dec 17, 2013, at 4:36 AM, Vineet Reynolds Pereira <vpereira at redhat.com> wrote:

> 
> 
> ----- Original Message -----
>> From: "Sebastien Blanc" <sblanc at redhat.com>
>> To: forge-dev at lists.jboss.org, aerogear-dev at lists.jboss.org
>> Sent: Tuesday, December 17, 2013 2:55:14 PM
>> Subject: Re: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
>> 
>> Adding again aerogear list.
>> I think that we must discuss with the team (aerogear) on how we can/must
>> handle a proper 201 response.
> 
> I'd concur. Both of these are 'correct'. But it would be better to indicate 
> if the client or consumers of the client should do anything more for 201 responses.
> 
> Several clients (Backbone.js [1], AngularJS[2] etc.) expect that responses to POST contain
> the entity in the response. Consumers are expected to fetch the updated resource for a 201
> with an empty body.
These statements seem almost contradict each other.
If Backbone/Angular assume that the response to a POST is a 201 with the entire entity from the server then that suggests that Aerogear's default is also correct behavior, in which case, the Forge scaffolding should be corrected.  
If "Consumers are expected to fetch the updated resource for a 201with an empty body", then no JSON serialized entity is needed in the response.

My definitions (which may be different than yours)
- 201 is the http response header/status
- entity is the entire object (e.g. Person, Customer, Part, Order) that was originally POST'd/INSERTed + any default values returned by the ORM+RDBMS (e.g. auto-inc id, pre-populated fields from triggers, etc)
- response body is where the JSON-serialized entity payload would be

> 
> 1: https://github.com/jashkenas/backbone/issues/1660
> 2: https://github.com/angular/angular.js/issues/2572
> 
> 
>> 
>> On 12/17/2013 09:58 AM, Ivan St. Ivanov wrote:
>> 
>> 
>> 
>> Hi!
>> 
>> I think that the 'right' approach is to respond with 201 (created) and return
>> a URI to the newly created resource.
>> 
>> Cheers,
>> Ivan
>> 
>> 
>> On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III <
>> lincolnbaxter at gmail.com > wrote:
>> 
>> 
>> 
>> Either is typical, but I think that most "pure" restifarians would favor the
>> 201.
>> 
>> 
>> On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter < bsutter at redhat.com > wrote:
>> 
>> 
>> 
>> I need to find my REST bible - what is typical to respond to the POST with
>> the JSON-serialized entity that was originally POST'd or to simply respond
>> with a basic acknowledgement (http 201)?
>> 
>> 
>> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
>> wrote:
>> 
>> 
>> 
>> 
>> Adding forge-dev.
>> 
>> ----- Original Message -----
>> 
>> 
>> From: "Burr Sutter" < bsutter at redhat.com >
>> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
>> Sent: Tuesday, December 17, 2013 1:59:41 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>> 
>> That seems to do the trick - now, where do we apply the fix? :-)
>> 
>> Well, ideally this would be a feature request in Forge to support a new type
>> of a REST resource. But a couple of modified lines might not warrant it.
>> 
>> It would be better to treat this as a flag to be enabled during REST resource
>> scaffolding. It would allow users to choose how the resource behaves -
>> * send a 201 response with Location header,
>> * send a 201 response with Location header and also a response entity.
>> 
>> It would most likely be addressed in Forge 2.
>> 
>> 
>> 
>> 
>> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
>> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> ----- Original Message -----
>> 
>> 
>> From: "Lucas Holmquist" < lholmqui at redhat.com >
>> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
>> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
>> Sent: Tuesday, December 17, 2013 12:53:25 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>> 
>> 
>> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
>> 
>> 
>> 
>> Adding Vineet as he has spent time on the Forge REST scaffolding.
>> 
>> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
>> 
>> 
>> 
>> Burr,
>> I've added some logs statements on the client and basically it seems it
>> can not parse the response from the server :
>> 
>> I/Web Console( 1386): textStatus: parsererror at
>> file:///android_asset/www/js/index.js:103
>> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
>> file:///android_asset/www/js/index.js:104
>> 
>> If I do a CURL like this :
>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
>> "Content-type: application/json" -X POST -d
>> '{"phoneNumber":"1234567890","email":" newTest at test.com ","name":"newTest"}'
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>> 
>> I should have pointed to the sources to the REST endpoint:
>> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
>> This was generated by Forge as I am too lazy to type up a full CRUD REST
>> endpoint myself :-)
>> 
>> 
>> 
>> I got an correct answer but the content type is 'text/plain' , please
>> check your rest endpoint to be sure it's producing json as output, that
>> should solve your issue.
>> It says
>> @POST
>> @Consumes("application/json")
>> 
>> needs a @Produces("application/json")
>> 
>> I'm not sure that will help. The response is a HTTP 201 with a Location
>> header.
>> Is the client expecting an entity of type application/json in the response ?
>> 
>> If yes, then the method should look like:
>> 
>> @POST
>> @Consumes("application/json")
>> public Response create(MemberDTO dto)
>> {
>> Member entity = dto.fromDTO(null, em);
>> em.persist(entity);
>> return
>> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
>> }
>> 
>> I've added : .entity(entity) in the above method to populate the response
>> with the entity.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Could you also paste the commands you used in Forge to scaffold the REST
>> endpoints so that we can check there hasn't been an incompatibility
>> introduced ?
>> I just used the Forge Wizard that is built into JBDS/Tools
>> http://screencast.com/t/QrKkCoFZMUn
>> 
>> error.status is 201
>> error.responseText is blank
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter < bsutter at redhat.com > wrote:
>> I am having a problem with pipe.save(), likely user error :-)
>> 
>> For some reason, the POST is occurring, the save seems to work but the
>> error callback is invoked, not the success method.
>> 
>> And I am doing all of this in the context of our tooling which has some
>> limitations (auto-closing console/firebug lite)
>> 
>> http://screencast.com/t/gosd7Qnhz
>> 
>> REST endpoint:
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>> Use of Forge, with the Member.java entity to offer full CRUD capabilities
>> 
>> Sources:
>> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
>> 
>> 
>> _______________________________________________
>> 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
>> 
>> _______________________________________________
>> 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
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> 
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131217/8fce662e/attachment.html 

From vpereira at redhat.com  Tue Dec 17 09:43:50 2013
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Tue, 17 Dec 2013 09:43:50 -0500 (EST)
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <98682D8D-478E-4D4E-87FE-C4F08B4F67AF@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
	<CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
	<52B0187A.9020903@redhat.com>
	<98682D8D-478E-4D4E-87FE-C4F08B4F67AF@redhat.com>
Message-ID: <2032951163.40864303.1387291430377.JavaMail.root@redhat.com>



----- Original Message -----
> From: "Lucas Holmquist" <lholmqui at redhat.com>
> To: "forge-dev List" <forge-dev at lists.jboss.org>
> Cc: aerogear-dev at lists.jboss.org
> Sent: Tuesday, December 17, 2013 6:59:10 PM
> Subject: Re: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
> 
> 
> On Dec 17, 2013, at 4:25 AM, Sebastien Blanc < sblanc at redhat.com > wrote:
> 
> 
> 
> 
> Adding again aerogear list.
> I think that we must discuss with the team (aerogear) on how we can/must
> handle a proper 201 response.
> 
> i don't see this as a client issue at all. jQuery ajax is used under the hood
> here and it is handling the 201 fine, but it is choking on parsing the
> response since it is not in the correct format, thus calling back in the
> error callback.

Ah, you mean this problem:

http://jquery.com/upgrade-guide/1.9/#jquery-ajax-returning-a-json-result-of-an-empty-string

This would definitely require the server to not send empty responses when the client expects JSON.

> 
> this should really be handled on the server
> 
> 
> 
> 
> 
> On 12/17/2013 09:58 AM, Ivan St. Ivanov wrote:
> 
> 
> 
> Hi!
> 
> I think that the 'right' approach is to respond with 201 (created) and return
> a URI to the newly created resource.
> 
> Cheers,
> Ivan
> 
> 
> On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III <
> lincolnbaxter at gmail.com > wrote:
> 
> 
> 
> Either is typical, but I think that most "pure" restifarians would favor the
> 201.
> 
> 
> On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter < bsutter at redhat.com > wrote:
> 
> 
> 
> I need to find my REST bible - what is typical to respond to the POST with
> the JSON-serialized entity that was originally POST'd or to simply respond
> with a basic acknowledgement (http 201)?
> 
> 
> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> Adding forge-dev.
> 
> ----- Original Message -----
> 
> 
> From: "Burr Sutter" < bsutter at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Sent: Tuesday, December 17, 2013 1:59:41 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> That seems to do the trick - now, where do we apply the fix? :-)
> 
> Well, ideally this would be a feature request in Forge to support a new type
> of a REST resource. But a couple of modified lines might not warrant it.
> 
> It would be better to treat this as a flag to be enabled during REST resource
> scaffolding. It would allow users to choose how the resource behaves -
> * send a 201 response with Location header,
> * send a 201 response with Location header and also a response entity.
> 
> It would most likely be addressed in Forge 2.
> 
> 
> 
> 
> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> 
> 
> ----- Original Message -----
> 
> 
> From: "Lucas Holmquist" < lholmqui at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
> Sent: Tuesday, December 17, 2013 12:53:25 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> 
> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
> 
> 
> 
> Adding Vineet as he has spent time on the Forge REST scaffolding.
> 
> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
> 
> 
> 
> Burr,
> I've added some logs statements on the client and basically it seems it
> can not parse the response from the server :
> 
> I/Web Console( 1386): textStatus: parsererror at
> file:///android_asset/www/js/index.js:103
> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
> file:///android_asset/www/js/index.js:104
> 
> If I do a CURL like this :
> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
> "Content-type: application/json" -X POST -d
> '{"phoneNumber":"1234567890","email":" newTest at test.com ","name":"newTest"}'
> http://agmobile-html5.rhcloud.com/rest/forge/members
> 
> I should have pointed to the sources to the REST endpoint:
> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
> This was generated by Forge as I am too lazy to type up a full CRUD REST
> endpoint myself :-)
> 
> 
> 
> I got an correct answer but the content type is 'text/plain' , please
> check your rest endpoint to be sure it's producing json as output, that
> should solve your issue.
> It says
> @POST
> @Consumes("application/json")
> 
> needs a @Produces("application/json")
> 
> I'm not sure that will help. The response is a HTTP 201 with a Location
> header.
> Is the client expecting an entity of type application/json in the response ?
> 
> If yes, then the method should look like:
> 
> @POST
> @Consumes("application/json")
> public Response create(MemberDTO dto)
> {
> Member entity = dto.fromDTO(null, em);
> em.persist(entity);
> return
> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
> }
> 
> I've added : .entity(entity) in the above method to populate the response
> with the entity.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Could you also paste the commands you used in Forge to scaffold the REST
> endpoints so that we can check there hasn't been an incompatibility
> introduced ?
> I just used the Forge Wizard that is built into JBDS/Tools
> http://screencast.com/t/QrKkCoFZMUn
> 
> error.status is 201
> error.responseText is blank
> 
> 
> 
> 
> 
> 
> 
> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter < bsutter at redhat.com > wrote:
> I am having a problem with pipe.save(), likely user error :-)
> 
> For some reason, the POST is occurring, the save seems to work but the
> error callback is invoked, not the success method.
> 
> And I am doing all of this in the context of our tooling which has some
> limitations (auto-closing console/firebug lite)
> 
> http://screencast.com/t/gosd7Qnhz
> 
> REST endpoint:
> http://agmobile-html5.rhcloud.com/rest/forge/members
> Use of Forge, with the Member.java entity to offer full CRUD capabilities
> 
> Sources:
> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
> 
> 
> _______________________________________________
> 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
> 
> _______________________________________________
> 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
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> _______________________________________________
> forge-dev mailing list forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

From jbalunas at redhat.com  Tue Dec 17 10:05:22 2013
From: jbalunas at redhat.com (Jay Balunas)
Date: Tue, 17 Dec 2013 10:05:22 -0500
Subject: [forge-dev] [aerogear-dev]   Aerogear.js for CRUD
In-Reply-To: <2032951163.40864303.1387291430377.JavaMail.root@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
	<CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
	<52B0187A.9020903@redhat.com>
	<98682D8D-478E-4D4E-87FE-C4F08B4F67AF@redhat.com>
	<2032951163.40864303.1387291430377.JavaMail.root@redhat.com>
Message-ID: <AB765343-58F4-454F-9C4B-33DBEA9E1E92@redhat.com>


On Dec 17, 2013, at 9:43 AM, Vineet Reynolds Pereira <vpereira at redhat.com> wrote:

> 
> 
> ----- Original Message -----
>> From: "Lucas Holmquist" <lholmqui at redhat.com>
>> To: "forge-dev List" <forge-dev at lists.jboss.org>
>> Cc: aerogear-dev at lists.jboss.org
>> Sent: Tuesday, December 17, 2013 6:59:10 PM
>> Subject: Re: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
>> 
>> 
>> On Dec 17, 2013, at 4:25 AM, Sebastien Blanc < sblanc at redhat.com > wrote:
>> 
>> 
>> 
>> 
>> Adding again aerogear list.
>> I think that we must discuss with the team (aerogear) on how we can/must
>> handle a proper 201 response.
>> 
>> i don't see this as a client issue at all. jQuery ajax is used under the hood
>> here and it is handling the 201 fine, but it is choking on parsing the
>> response since it is not in the correct format, thus calling back in the
>> error callback.
> 
> Ah, you mean this problem:
> 
> http://jquery.com/upgrade-guide/1.9/#jquery-ajax-returning-a-json-result-of-an-empty-string
> 
> This would definitely require the server to not send empty responses when the client expects JSON.

So in this case, with jQuery 1.9+ what is the best way for the us to handle this.  Is this a chance in AeroGear.js to help handle this situation, or do we need to make sure the server impls reply with content, even with a 201?

> 
>> 
>> this should really be handled on the server
>> 
>> 
>> 
>> 
>> 
>> On 12/17/2013 09:58 AM, Ivan St. Ivanov wrote:
>> 
>> 
>> 
>> Hi!
>> 
>> I think that the 'right' approach is to respond with 201 (created) and return
>> a URI to the newly created resource.
>> 
>> Cheers,
>> Ivan
>> 
>> 
>> On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III <
>> lincolnbaxter at gmail.com > wrote:
>> 
>> 
>> 
>> Either is typical, but I think that most "pure" restifarians would favor the
>> 201.
>> 
>> 
>> On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter < bsutter at redhat.com > wrote:
>> 
>> 
>> 
>> I need to find my REST bible - what is typical to respond to the POST with
>> the JSON-serialized entity that was originally POST'd or to simply respond
>> with a basic acknowledgement (http 201)?
>> 
>> 
>> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
>> wrote:
>> 
>> 
>> 
>> 
>> Adding forge-dev.
>> 
>> ----- Original Message -----
>> 
>> 
>> From: "Burr Sutter" < bsutter at redhat.com >
>> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
>> Sent: Tuesday, December 17, 2013 1:59:41 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>> 
>> That seems to do the trick - now, where do we apply the fix? :-)
>> 
>> Well, ideally this would be a feature request in Forge to support a new type
>> of a REST resource. But a couple of modified lines might not warrant it.
>> 
>> It would be better to treat this as a flag to be enabled during REST resource
>> scaffolding. It would allow users to choose how the resource behaves -
>> * send a 201 response with Location header,
>> * send a 201 response with Location header and also a response entity.
>> 
>> It would most likely be addressed in Forge 2.
>> 
>> 
>> 
>> 
>> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
>> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> ----- Original Message -----
>> 
>> 
>> From: "Lucas Holmquist" < lholmqui at redhat.com >
>> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
>> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
>> Sent: Tuesday, December 17, 2013 12:53:25 AM
>> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
>> 
>> 
>> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
>> 
>> 
>> 
>> Adding Vineet as he has spent time on the Forge REST scaffolding.
>> 
>> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
>> 
>> 
>> 
>> Burr,
>> I've added some logs statements on the client and basically it seems it
>> can not parse the response from the server :
>> 
>> I/Web Console( 1386): textStatus: parsererror at
>> file:///android_asset/www/js/index.js:103
>> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
>> file:///android_asset/www/js/index.js:104
>> 
>> If I do a CURL like this :
>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
>> "Content-type: application/json" -X POST -d
>> '{"phoneNumber":"1234567890","email":" newTest at test.com ","name":"newTest"}'
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>> 
>> I should have pointed to the sources to the REST endpoint:
>> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
>> This was generated by Forge as I am too lazy to type up a full CRUD REST
>> endpoint myself :-)
>> 
>> 
>> 
>> I got an correct answer but the content type is 'text/plain' , please
>> check your rest endpoint to be sure it's producing json as output, that
>> should solve your issue.
>> It says
>> @POST
>> @Consumes("application/json")
>> 
>> needs a @Produces("application/json")
>> 
>> I'm not sure that will help. The response is a HTTP 201 with a Location
>> header.
>> Is the client expecting an entity of type application/json in the response ?
>> 
>> If yes, then the method should look like:
>> 
>> @POST
>> @Consumes("application/json")
>> public Response create(MemberDTO dto)
>> {
>> Member entity = dto.fromDTO(null, em);
>> em.persist(entity);
>> return
>> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
>> }
>> 
>> I've added : .entity(entity) in the above method to populate the response
>> with the entity.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Could you also paste the commands you used in Forge to scaffold the REST
>> endpoints so that we can check there hasn't been an incompatibility
>> introduced ?
>> I just used the Forge Wizard that is built into JBDS/Tools
>> http://screencast.com/t/QrKkCoFZMUn
>> 
>> error.status is 201
>> error.responseText is blank
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter < bsutter at redhat.com > wrote:
>> I am having a problem with pipe.save(), likely user error :-)
>> 
>> For some reason, the POST is occurring, the save seems to work but the
>> error callback is invoked, not the success method.
>> 
>> And I am doing all of this in the context of our tooling which has some
>> limitations (auto-closing console/firebug lite)
>> 
>> http://screencast.com/t/gosd7Qnhz
>> 
>> REST endpoint:
>> http://agmobile-html5.rhcloud.com/rest/forge/members
>> Use of Forge, with the Member.java entity to offer full CRUD capabilities
>> 
>> Sources:
>> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
>> 
>> 
>> _______________________________________________
>> 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
>> 
>> _______________________________________________
>> 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
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> 
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131217/2b73d90b/attachment.html 

From vpereira at redhat.com  Tue Dec 17 10:57:31 2013
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Tue, 17 Dec 2013 10:57:31 -0500 (EST)
Subject: [forge-dev] [aerogear-dev]   Aerogear.js for CRUD
In-Reply-To: <AB765343-58F4-454F-9C4B-33DBEA9E1E92@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<E399803E-B950-4D6B-84DA-C11A9481EB37@redhat.com>
	<CAEp_U4FgQBs4Pc2oeovGUM5nJ5D9qx5Q-0k6+zhKMQ5w3JhnxQ@mail.gmail.com>
	<CACYLA9FG=c_c8oOd75HuAqc3n1wd7L5iG4T1zv7m42W74ATzAw@mail.gmail.com>
	<52B0187A.9020903@redhat.com>
	<98682D8D-478E-4D4E-87FE-C4F08B4F67AF@redhat.com>
	<2032951163.40864303.1387291430377.JavaMail.root@redhat.com>
	<AB765343-58F4-454F-9C4B-33DBEA9E1E92@redhat.com>
Message-ID: <262480495.40914157.1387295851386.JavaMail.root@redhat.com>



----- Original Message -----
> From: "Jay Balunas" <jbalunas at redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Cc: "forge-dev List" <forge-dev at lists.jboss.org>
> Sent: Tuesday, December 17, 2013 8:35:22 PM
> Subject: Re: [aerogear-dev] [forge-dev]  Aerogear.js for CRUD
> 
> 
> On Dec 17, 2013, at 9:43 AM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> 
> 
> ----- Original Message -----
> 
> 
> From: "Lucas Holmquist" < lholmqui at redhat.com >
> To: "forge-dev List" < forge-dev at lists.jboss.org >
> Cc: aerogear-dev at lists.jboss.org
> Sent: Tuesday, December 17, 2013 6:59:10 PM
> Subject: Re: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
> 
> 
> On Dec 17, 2013, at 4:25 AM, Sebastien Blanc < sblanc at redhat.com > wrote:
> 
> 
> 
> 
> Adding again aerogear list.
> I think that we must discuss with the team (aerogear) on how we can/must
> handle a proper 201 response.
> 
> i don't see this as a client issue at all. jQuery ajax is used under the hood
> here and it is handling the 201 fine, but it is choking on parsing the
> response since it is not in the correct format, thus calling back in the
> error callback.
> 
> Ah, you mean this problem:
> 
> http://jquery.com/upgrade-guide/1.9/#jquery-ajax-returning-a-json-result-of-an-empty-string
> 
> This would definitely require the server to not send empty responses when the
> client expects JSON.
> 
> So in this case, with jQuery 1.9+ what is the best way for the us to handle
> this. Is this a chance in AeroGear.js to help handle this situation, or do
> we need to make sure the server impls reply with content, even with a 201?

I'm not aware of what Aerogear does but the question that would lead to the answer is
- Does Aerogear expect that the response contain JSON?

The rationale behind jQuery's decision to treat empty responses as errors is - the expected 
datatype was JSON, and thus an empty response body for a response with content/type 
application/json is an error.

If the AG client expects a JSON response, then I'd agree that the
server must not respond with an empty response body. For instance, Backbone.js does this:
https://github.com/jashkenas/backbone/blob/master/backbone.js#L1140
and thus the REST API is expected to send JSON in the response body on Model.save().

On the other hand, if the client does not expect a JSON response, then it must not 
set the datatype when invoking $.ajax(). This may not be practical - Backbone.js doesn't
do this and instead allows users to swap in custom Backbone.sync or Backbone.ajax 
implementations to get around this.

I'll try and address this in FORGE-1361 taking this behavior into account.
It looks like we need a different type of a REST resource for AG clients.


> 
> 
> 
> 
> 
> 
> 
> 
> this should really be handled on the server
> 
> 
> 
> 
> 
> On 12/17/2013 09:58 AM, Ivan St. Ivanov wrote:
> 
> 
> 
> Hi!
> 
> I think that the 'right' approach is to respond with 201 (created) and return
> a URI to the newly created resource.
> 
> Cheers,
> Ivan
> 
> 
> On Tue, Dec 17, 2013 at 12:58 AM, Lincoln Baxter, III <
> lincolnbaxter at gmail.com > wrote:
> 
> 
> 
> Either is typical, but I think that most "pure" restifarians would favor the
> 201.
> 
> 
> On Mon, Dec 16, 2013 at 5:41 PM, Burr Sutter < bsutter at redhat.com > wrote:
> 
> 
> 
> I need to find my REST bible - what is typical to respond to the POST with
> the JSON-serialized entity that was originally POST'd or to simply respond
> with a basic acknowledgement (http 201)?
> 
> 
> On Dec 16, 2013, at 4:25 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> Adding forge-dev.
> 
> ----- Original Message -----
> 
> 
> From: "Burr Sutter" < bsutter at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Sent: Tuesday, December 17, 2013 1:59:41 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> That seems to do the trick - now, where do we apply the fix? :-)
> 
> Well, ideally this would be a feature request in Forge to support a new type
> of a REST resource. But a couple of modified lines might not warrant it.
> 
> It would be better to treat this as a flag to be enabled during REST resource
> scaffolding. It would allow users to choose how the resource behaves -
> * send a 201 response with Location header,
> * send a 201 response with Location header and also a response entity.
> 
> It would most likely be addressed in Forge 2.
> 
> 
> 
> 
> On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira at redhat.com >
> wrote:
> 
> 
> 
> 
> 
> 
> ----- Original Message -----
> 
> 
> From: "Lucas Holmquist" < lholmqui at redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> Cc: "Vineet Reynolds Pereira" < vpereira at redhat.com >
> Sent: Tuesday, December 17, 2013 12:53:25 AM
> Subject: Re: [aerogear-dev] Aerogear.js for CRUD
> 
> 
> On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter at redhat.com > wrote:
> 
> 
> 
> Adding Vineet as he has spent time on the Forge REST scaffolding.
> 
> On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc at gmail.com > wrote:
> 
> 
> 
> Burr,
> I've added some logs statements on the client and basically it seems it
> can not parse the response from the server :
> 
> I/Web Console( 1386): textStatus: parsererror at
> file:///android_asset/www/js/index.js:103
> I/Web Console( 1386): error: SyntaxError: Unexpected end of input at
> file:///android_asset/www/js/index.js:104
> 
> If I do a CURL like this :
> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
> "Content-type: application/json" -X POST -d
> '{"phoneNumber":"1234567890","email":" newTest at test.com ","name":"newTest"}'
> http://agmobile-html5.rhcloud.com/rest/forge/members
> 
> I should have pointed to the sources to the REST endpoint:
> https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burrsutter/agmobile/rest/MemberEndpoint.java
> This was generated by Forge as I am too lazy to type up a full CRUD REST
> endpoint myself :-)
> 
> 
> 
> I got an correct answer but the content type is 'text/plain' , please
> check your rest endpoint to be sure it's producing json as output, that
> should solve your issue.
> It says
> @POST
> @Consumes("application/json")
> 
> needs a @Produces("application/json")
> 
> I'm not sure that will help. The response is a HTTP 201 with a Location
> header.
> Is the client expecting an entity of type application/json in the response ?
> 
> If yes, then the method should look like:
> 
> @POST
> @Consumes("application/json")
> public Response create(MemberDTO dto)
> {
> Member entity = dto.fromDTO(null, em);
> em.persist(entity);
> return
> Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build();
> }
> 
> I've added : .entity(entity) in the above method to populate the response
> with the entity.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Could you also paste the commands you used in Forge to scaffold the REST
> endpoints so that we can check there hasn't been an incompatibility
> introduced ?
> I just used the Forge Wizard that is built into JBDS/Tools
> http://screencast.com/t/QrKkCoFZMUn
> 
> error.status is 201
> error.responseText is blank
> 
> 
> 
> 
> 
> 
> 
> On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter < bsutter at redhat.com > wrote:
> I am having a problem with pipe.save(), likely user error :-)
> 
> For some reason, the POST is occurring, the save seems to work but the
> error callback is invoked, not the success method.
> 
> And I am doing all of this in the context of our tooling which has some
> limitations (auto-closing console/firebug lite)
> 
> http://screencast.com/t/gosd7Qnhz
> 
> REST endpoint:
> http://agmobile-html5.rhcloud.com/rest/forge/members
> Use of Forge, with the Member.java entity to offer full CRUD capabilities
> 
> Sources:
> https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js
> 
> 
> _______________________________________________
> 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
> 
> _______________________________________________
> 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
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> 
> _______________________________________________
> forge-dev mailing list forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> _______________________________________________
> 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

From bsutter at redhat.com  Wed Dec 18 10:54:42 2013
From: bsutter at redhat.com (Burr Sutter)
Date: Wed, 18 Dec 2013 10:54:42 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <20131218164733.43acae54@kapy-ntb-x220>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<20131218164733.43acae54@kapy-ntb-x220>
Message-ID: <9588A9EB-BDA3-4D42-B778-396BBED53C2E@redhat.com>

It sounds like, at a minimum, we have a bug in the Forge scaffolding to support Aerogear.js

My next concern would be that since this "feature" was introduced with jQuery 1.9, it could be that a LOT of the world's REST endpoints are no longer POST compatible with Aerogear.js, nothing to be done about that except to document it well for Aerogear.js when the time to promote it heavily comes up.

Aerogear.js doc issues also include confusion of datamanager/store (getting started guide is not clear for when those are needed) and the seemingly missing docs for Pipe.  Plus, the first example seen by the end-user should include the use of iteration through the results, not an underscore template which hides some of the details.



On Dec 18, 2013, at 10:47 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> To my understanding, HTTP 201 should always return created entity and its
> content should be based on Content-Type header field.
> 
> See http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
> 
> On Mon, 16 Dec 2013 16:25:53 -0500 (EST)
> Vineet Reynolds Pereira <vpereira at redhat.com> wrote:
> 
>> It would be better to treat this as a flag to be enabled during REST resource
>> scaffolding. It would allow users to choose how the resource behaves -
>> * send a 201 response with Location header, 
>> * send a 201 response with Location header and also a response entity.
>> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From lincolnbaxter at gmail.com  Wed Dec 18 11:11:58 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 18 Dec 2013 11:11:58 -0500
Subject: [forge-dev] Meeting cancelled today
Message-ID: <CAEp_U4EAyLj2TgUJUhfLQcUu8NJrTv8Lb6rUYSNvjHmb4MFGfw@mail.gmail.com>

Few participants, the holidays begin to take their toll :)

We will continue working toward 2.0 Final, and work on the website will
commence once we have the wireframes and HTML.

-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131218/7ad6b6e6/attachment.html 

From kpiwko at redhat.com  Wed Dec 18 10:47:33 2013
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 18 Dec 2013 16:47:33 +0100
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
Message-ID: <20131218164733.43acae54@kapy-ntb-x220>

To my understanding, HTTP 201 should always return created entity and its
content should be based on Content-Type header field.

See http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

On Mon, 16 Dec 2013 16:25:53 -0500 (EST)
Vineet Reynolds Pereira <vpereira at redhat.com> wrote:

> It would be better to treat this as a flag to be enabled during REST resource
> scaffolding. It would allow users to choose how the resource behaves -
>  * send a 201 response with Location header, 
>  * send a 201 response with Location header and also a response entity.
> 

From lincolnbaxter at gmail.com  Wed Dec 18 11:14:29 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 18 Dec 2013 11:14:29 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <9588A9EB-BDA3-4D42-B778-396BBED53C2E@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<20131218164733.43acae54@kapy-ntb-x220>
	<9588A9EB-BDA3-4D42-B778-396BBED53C2E@redhat.com>
Message-ID: <CAEp_U4EAv9PDTmVcu5VQ11Fcp0_ntROs4yv7U=d6rB5WX3N5MQ@mail.gmail.com>

I'm a little confused. Is this a bug in the Forge scaffolding, or a new
requirement because of the upgrade to jQuery 1.9 in the AeroGear client?
The Forge scaffolding seems to work fine. Is this something that prevents
the current forge scaffolding or REST endpoints from working correctly, or
only when paired with something from Aerogear? Is this something that
exists and can be tried? Just curious because I'd like to know if we broke
something, or missed a requirement.


On Wed, Dec 18, 2013 at 10:54 AM, Burr Sutter <bsutter at redhat.com> wrote:

> It sounds like, at a minimum, we have a bug in the Forge scaffolding to
> support Aerogear.js
>
> My next concern would be that since this "feature" was introduced with
> jQuery 1.9, it could be that a LOT of the world's REST endpoints are no
> longer POST compatible with Aerogear.js, nothing to be done about that
> except to document it well for Aerogear.js when the time to promote it
> heavily comes up.
>
> Aerogear.js doc issues also include confusion of datamanager/store
> (getting started guide is not clear for when those are needed) and the
> seemingly missing docs for Pipe.  Plus, the first example seen by the
> end-user should include the use of iteration through the results, not an
> underscore template which hides some of the details.
>
>
>
> On Dec 18, 2013, at 10:47 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>
> > To my understanding, HTTP 201 should always return created entity and its
> > content should be based on Content-Type header field.
> >
> > See http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
> >
> > On Mon, 16 Dec 2013 16:25:53 -0500 (EST)
> > Vineet Reynolds Pereira <vpereira at redhat.com> wrote:
> >
> >> It would be better to treat this as a flag to be enabled during REST
> resource
> >> scaffolding. It would allow users to choose how the resource behaves -
> >> * send a 201 response with Location header,
> >> * send a 201 response with Location header and also a response entity.
> >>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131218/428cbf6c/attachment.html 

From lincolnbaxter at gmail.com  Wed Dec 18 11:20:47 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 18 Dec 2013 11:20:47 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <20131218164733.43acae54@kapy-ntb-x220>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<20131218164733.43acae54@kapy-ntb-x220>
Message-ID: <CAEp_U4FiqfE4MR-ePhr+NOZRD-GV8Je+ZbYt2UvPgGe=WGXigQ@mail.gmail.com>

I disagree, if you read the section from the link you just posted. This
clearly states that "the newly created resource can be referenced by the
URI(s) returned in the entity of the response, with the most specific URI
for the resource given by a Location header field.

The response should include an entity containing a list of resource
***characteristics and locations*** from which the user or user agent can
choose the one most appropriate.

10.2.2 201 Created

The request has been fulfilled and resulted in a new resource being
created. The newly created resource can be referenced by the URI(s)
returned in the entity of the response, with the most specific URI for the
resource given by a Location header field. The response SHOULD include an
entity containing a list of resource characteristics and location(s) from
which the user or user agent can choose the one most appropriate. The
entity format is specified by the media type given in the Content-Type
header field. The origin server MUST create the resource before returning
the 201 status code. If the action cannot be carried out immediately, the
server SHOULD respond with 202 (Accepted) response instead.

A 201 response MAY contain an ETag response header field indicating the
current value of the entity tag for the requested variant just created, see
section 14.19<http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.19>
.


On Wed, Dec 18, 2013 at 10:47 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> To my understanding, HTTP 201 should always return created entity and its
> content should be based on Content-Type header field.
>
> See http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>
> On Mon, 16 Dec 2013 16:25:53 -0500 (EST)
> Vineet Reynolds Pereira <vpereira at redhat.com> wrote:
>
> > It would be better to treat this as a flag to be enabled during REST
> resource
> > scaffolding. It would allow users to choose how the resource behaves -
> >  * send a 201 response with Location header,
> >  * send a 201 response with Location header and also a response entity.
> >
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131218/01ee7f06/attachment.html 

From lincolnbaxter at gmail.com  Wed Dec 18 11:21:26 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Wed, 18 Dec 2013 11:21:26 -0500
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <CAEp_U4FiqfE4MR-ePhr+NOZRD-GV8Je+ZbYt2UvPgGe=WGXigQ@mail.gmail.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<20131218164733.43acae54@kapy-ntb-x220>
	<CAEp_U4FiqfE4MR-ePhr+NOZRD-GV8Je+ZbYt2UvPgGe=WGXigQ@mail.gmail.com>
Message-ID: <CAEp_U4Ep21-dPMnJ=_hBd0w6aDiDQZN+nPbBPBYkvBgnpOFGdQ@mail.gmail.com>

I disagree, if you read the section from the link you just posted. This
clearly states that "the newly created resource can be referenced by the
URI(s) returned in the entity of the response, with the most specific URI
for the resource given by a Location header field.

The response should include an entity containing a list of resource
***characteristics and locations*** from which the user or user agent can
choose the one most appropriate.

10.2.2 201 Created

The request has been fulfilled and resulted in a new resource being
created. The newly created resource can be referenced by the URI(s)
returned in the entity of the response, with the most specific URI for the
resource given by a Location header field. The response SHOULD include an
entity containing a list of resource characteristics and location(s) from
which the user or user agent can choose the one most appropriate. The
entity format is specified by the media type given in the Content-Type
header field. The origin server MUST create the resource before returning
the 201 status code. If the action cannot be carried out immediately, the
server SHOULD respond with 202 (Accepted) response instead.

A 201 response MAY contain an ETag response header field indicating the
current value of the entity tag for the requested variant just created, see
section 14.19<http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.19>
.




>
> On Wed, Dec 18, 2013 at 10:47 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> To my understanding, HTTP 201 should always return created entity and its
>> content should be based on Content-Type header field.
>>
>> See http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>>
>> On Mon, 16 Dec 2013 16:25:53 -0500 (EST)
>> Vineet Reynolds Pereira <vpereira at redhat.com> wrote:
>>
>> > It would be better to treat this as a flag to be enabled during REST
>> resource
>> > scaffolding. It would allow users to choose how the resource behaves -
>> >  * send a 201 response with Location header,
>> >  * send a 201 response with Location header and also a response entity.
>> >
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131218/325a03ff/attachment-0001.html 

From scm.blanc at gmail.com  Thu Dec 19 03:57:53 2013
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 19 Dec 2013 09:57:53 +0100
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <9588A9EB-BDA3-4D42-B778-396BBED53C2E@redhat.com>
References: <A8BAFC51-0EA5-4E7A-92DC-43A133A457D7@redhat.com>
	<CAD_dpu3JDteFW51tmoLdomsQa8c+kMkxEJUhsLzmuCxwbCCmvw@mail.gmail.com>
	<504FFE44-06CE-4C05-A8A6-D049D2D41E00@redhat.com>
	<A16F0824-BD46-44A2-AB1D-B22C84BF1C4A@redhat.com>
	<1445599908.40527893.1387224418368.JavaMail.root@redhat.com>
	<F7491625-38D4-489C-ABE9-6F11DF592655@redhat.com>
	<1928607956.40560513.1387229153309.JavaMail.root@redhat.com>
	<20131218164733.43acae54@kapy-ntb-x220>
	<9588A9EB-BDA3-4D42-B778-396BBED53C2E@redhat.com>
Message-ID: <CAD_dpu1K77P2s29SawgU_iSd7OOwfewN7W-3Nuj2g5YuTL+UJg@mail.gmail.com>

On Wed, Dec 18, 2013 at 4:54 PM, Burr Sutter <bsutter at redhat.com> wrote:

> It sounds like, at a minimum, we have a bug in the Forge scaffolding to
> support Aerogear.js
>
> My next concern would be that since this "feature" was introduced with
> jQuery 1.9, it could be that a LOT of the world's REST endpoints are no
> longer POST compatible with Aerogear.js, nothing to be done about that
> except to document it well for Aerogear.js when the time to promote it
> heavily comes up.
>

Before you used Aerogear, you had also a version using only jquery, right ?
Did you had the same behavior when doing a POST ? If yes, it's not
only Aerogear based apps that have an issue but all the webapps around the
world using jquery's ajax 1.9 stuff.



>
> Aerogear.js doc issues also include confusion of datamanager/store
> (getting started guide is not clear for when those are needed) and the
> seemingly missing docs for Pipe.  Plus, the first example seen by the
> end-user should include the use of iteration through the results, not an
> underscore template which hides some of the details.
>

Could you open a new thread/jiras for the doc issues so that we don't mix
all the things in one thread ?


>
>
> On Dec 18, 2013, at 10:47 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>
> > To my understanding, HTTP 201 should always return created entity and its
> > content should be based on Content-Type header field.
> >
> > See http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
> >
> > On Mon, 16 Dec 2013 16:25:53 -0500 (EST)
> > Vineet Reynolds Pereira <vpereira at redhat.com> wrote:
> >
> >> It would be better to treat this as a flag to be enabled during REST
> resource
> >> scaffolding. It would allow users to choose how the resource behaves -
> >> * send a 201 response with Location header,
> >> * send a 201 response with Location header and also a response entity.
> >>
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131219/d2a8edc2/attachment.html 

From forge-dev at lists.jboss.org  Thu Dec 19 08:31:46 2013
From: forge-dev at lists.jboss.org (forge-dev at lists.jboss.org)
Date: Thu, 19 Dec 2013 08:31:46 EST
Subject: [forge-dev] [aerogear-dev] Aerogear.js for CRUD
In-Reply-To: <CAEp_U4Ep21-dPMnJ=_hBd0w6aDiDQZN+nPbBPBYkvBgnpOFGdQ@mail.gmail.com>
Message-ID: <1783658492.171387461475188.JavaMail.jive@jive-app01.app.mwc.hst.phx2.redhat.com>

Thanks Lincoln, you're right!

I must have been reading that part wrong.

Karel

Posted by forums
Original post: https://community.jboss.org/message/850343#850343

From lincolnbaxter at gmail.com  Thu Dec 19 10:33:20 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 19 Dec 2013 10:33:20 -0500
Subject: [forge-dev] Forge Roadmap Update for Jan 15th release and beyond
Message-ID: <CAEp_U4EeQxGawjzVP+Ke4P3v9nhVtdbTxmVSAQ759uwCtN5GEw@mail.gmail.com>

Please feel free to add or comment if I've missed anything or if there's
anything you'd like to discuss.


   - Forge 2.0.0.FInal to be released Jan 15th



   - (Does not include plugins - to be released separately as completed as
   other projects/individuals can spend time working with us, or as we can
   spend time on them.)



   - Plugins that are being released (or near completion)
      - Build System Integration
         - Maven



   - Scaffold


   - JSF


   - Angular



   - Database reverse engineering


   - Wizards


   - Eclipse connection profile integration



   - Java EE developer tooling & quick-start plugins


   - Jax RX / REST


   - JSF


   - CDI


   - etc..



   - Includes wizards/Forge menu integration into JBoss Tools



   - Forge 2 website, hopefully by March/April


-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131219/bc2cc230/attachment.html 

From fiorenzino at gmail.com  Thu Dec 19 11:42:25 2013
From: fiorenzino at gmail.com (JFlower)
Date: Thu, 19 Dec 2013 17:42:25 +0100
Subject: [forge-dev] Forge Roadmap Update for Jan 15th release and beyond
In-Reply-To: <CAEp_U4EeQxGawjzVP+Ke4P3v9nhVtdbTxmVSAQ759uwCtN5GEw@mail.gmail.com>
References: <CAEp_U4EeQxGawjzVP+Ke4P3v9nhVtdbTxmVSAQ759uwCtN5GEw@mail.gmail.com>
Message-ID: <CAC5yyzV=aJs-brRkd_=y0Z6sawsikHjt5L0Rp8r_oTBwrRF1VQ@mail.gmail.com>

Wow!!


2013/12/19 Lincoln Baxter, III <lincolnbaxter at gmail.com>

> Please feel free to add or comment if I've missed anything or if there's
> anything you'd like to discuss.
>
>
>    - Forge 2.0.0.FInal to be released Jan 15th
>
>
>
>    - (Does not include plugins - to be released separately as completed
>    as other projects/individuals can spend time working with us, or as we can
>    spend time on them.)
>
>
>
>    - Plugins that are being released (or near completion)
>       - Build System Integration
>          - Maven
>
>
>
>    - Scaffold
>
>
>    - JSF
>
>
>    - Angular
>
>
>
>    - Database reverse engineering
>
>
>    - Wizards
>
>
>    - Eclipse connection profile integration
>
>
>
>    - Java EE developer tooling & quick-start plugins
>
>
>    - Jax RX / REST
>
>
>    - JSF
>
>
>    - CDI
>
>
>    - etc..
>
>
>
>    - Includes wizards/Forge menu integration into JBoss Tools
>
>
>
>    - Forge 2 website, hopefully by March/April
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131219/1b99097d/attachment.html 

From ivan.st.ivanov at gmail.com  Thu Dec 19 11:46:54 2013
From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov)
Date: Thu, 19 Dec 2013 18:46:54 +0200
Subject: [forge-dev] Forge Roadmap Update for Jan 15th release and beyond
In-Reply-To: <CAC5yyzV=aJs-brRkd_=y0Z6sawsikHjt5L0Rp8r_oTBwrRF1VQ@mail.gmail.com>
References: <CAEp_U4EeQxGawjzVP+Ke4P3v9nhVtdbTxmVSAQ759uwCtN5GEw@mail.gmail.com>
	<CAC5yyzV=aJs-brRkd_=y0Z6sawsikHjt5L0Rp8r_oTBwrRF1VQ@mail.gmail.com>
Message-ID: <CACYLA9Hk-Gf8EhoqWjs+Sy4SdZVo70DVXQCNtMeWCduN-jdxNQ@mail.gmail.com>

Hey Forgers! :)

The git tools addon is nearly finished. I am giving it the final touches. I
think it will be ready before January 15th though I would appreciate some
early feedback from everybody. I am regularly pushing things to my github
repo:

https://github.com/ivannov/core/tree/FORGE-1128

Cheers,
Ivan


On Thu, Dec 19, 2013 at 6:42 PM, JFlower <fiorenzino at gmail.com> wrote:

> Wow!!
>
>
> 2013/12/19 Lincoln Baxter, III <lincolnbaxter at gmail.com>
>
>> Please feel free to add or comment if I've missed anything or if there's
>> anything you'd like to discuss.
>>
>>
>>    - Forge 2.0.0.FInal to be released Jan 15th
>>
>>
>>
>>    - (Does not include plugins - to be released separately as completed
>>    as other projects/individuals can spend time working with us, or as we can
>>    spend time on them.)
>>
>>
>>
>>    - Plugins that are being released (or near completion)
>>       - Build System Integration
>>          - Maven
>>
>>
>>
>>    - Scaffold
>>
>>
>>    - JSF
>>
>>
>>    - Angular
>>
>>
>>
>>    - Database reverse engineering
>>
>>
>>    - Wizards
>>
>>
>>    - Eclipse connection profile integration
>>
>>
>>
>>    - Java EE developer tooling & quick-start plugins
>>
>>
>>    - Jax RX / REST
>>
>>
>>    - JSF
>>
>>
>>    - CDI
>>
>>
>>    - etc..
>>
>>
>>
>>    - Includes wizards/Forge menu integration into JBoss Tools
>>
>>
>>
>>    - Forge 2 website, hopefully by March/April
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131219/29ffcf82/attachment-0001.html 

From ggastald at redhat.com  Thu Dec 19 17:46:54 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 19 Dec 2013 17:46:54 -0500 (EST)
Subject: [forge-dev] Forge Roadmap Update for Jan 15th release and beyond
In-Reply-To: <CACYLA9Hk-Gf8EhoqWjs+Sy4SdZVo70DVXQCNtMeWCduN-jdxNQ@mail.gmail.com>
References: <CAEp_U4EeQxGawjzVP+Ke4P3v9nhVtdbTxmVSAQ759uwCtN5GEw@mail.gmail.com>
	<CAC5yyzV=aJs-brRkd_=y0Z6sawsikHjt5L0Rp8r_oTBwrRF1VQ@mail.gmail.com>
	<CACYLA9Hk-Gf8EhoqWjs+Sy4SdZVo70DVXQCNtMeWCduN-jdxNQ@mail.gmail.com>
Message-ID: <C5193E7D-4820-4F52-9B25-56A7E42781F5@redhat.com>

Hey Ivan! 

Sounds great! But no rush, as we can distribute your Git addon in a different repository and merge to the core if that is really needed ( I'd prefer the former tbh).

Forge Ahead! 

George

> Em 19/12/2013, ?s 14:47, "Ivan St. Ivanov" <ivan.st.ivanov at gmail.com> escreveu:
> 
> Hey Forgers! :)
> 
> The git tools addon is nearly finished. I am giving it the final touches. I think it will be ready before January 15th though I would appreciate some early feedback from everybody. I am regularly pushing things to my github repo:
> 
> https://github.com/ivannov/core/tree/FORGE-1128
> 
> Cheers,
> Ivan
> 
> 
>> On Thu, Dec 19, 2013 at 6:42 PM, JFlower <fiorenzino at gmail.com> wrote:
>> Wow!!
>> 
>> 
>> 2013/12/19 Lincoln Baxter, III <lincolnbaxter at gmail.com>
>>> Please feel free to add or comment if I've missed anything or if there's anything you'd like to discuss.
>>> 
>>> Forge 2.0.0.FInal to be released Jan 15th
>>> 
>>> (Does not include plugins - to be released separately as completed as other projects/individuals can spend time working with us, or as we can spend time on them.) 
>>> 
>>> Plugins that are being released (or near completion)
>>> Build System Integration
>>> Maven
>>> 
>>> Scaffold
>>> JSF
>>> Angular
>>> 
>>> Database reverse engineering
>>> Wizards
>>> Eclipse connection profile integration
>>> 
>>> Java EE developer tooling & quick-start plugins
>>> Jax RX / REST
>>> JSF
>>> CDI
>>> etc..
>>> 
>>> Includes wizards/Forge menu integration into JBoss Tools
>>> 
>>> Forge 2 website, hopefully by March/April
>>> 
>>> -- 
>>> Lincoln Baxter, III
>>> http://ocpsoft.org
>>> "Simpler is better."
>>> 
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131219/340e860f/attachment.html 

From ggastald at redhat.com  Thu Dec 26 19:37:34 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 26 Dec 2013 19:37:34 -0500 (EST)
Subject: [forge-dev] JBoss Forge 2.0.0.Beta4 is available
Message-ID: <7FE0B2D6-A618-4B69-93B0-57FD8F050E68@redhat.com>

More info:
http://forge.jboss.org/news/2013/12/26/post-forge-2.html

Happy new year everyone!
George Gastaldi

From lincolnbaxter at gmail.com  Thu Dec 26 19:52:44 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Thu, 26 Dec 2013 19:52:44 -0500
Subject: [forge-dev] [forge-users] JBoss Forge 2.0.0.Beta4 is available
In-Reply-To: <7FE0B2D6-A618-4B69-93B0-57FD8F050E68@redhat.com>
References: <7FE0B2D6-A618-4B69-93B0-57FD8F050E68@redhat.com>
Message-ID: <CAEp_U4E5=wQJFYuHcbZqQY4X_-oK-jZNrfoOovZFLGaaZoppHA@mail.gmail.com>

Happy New Year! Good job everyone and job well done on this release! Best
2.0 branch release yet! We are very close to releasing .Final!


On Thu, Dec 26, 2013 at 7:37 PM, George Gastaldi <ggastald at redhat.com>wrote:

> More info:
> http://forge.jboss.org/news/2013/12/26/post-forge-2.html
>
> Happy new year everyone!
> George Gastaldi
> _______________________________________________
> forge-users mailing list
> forge-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-users
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131226/780f1996/attachment.html 

From jgreene at redhat.com  Fri Dec 27 08:03:57 2013
From: jgreene at redhat.com (Jason Greene)
Date: Fri, 27 Dec 2013 08:03:57 -0500 (EST)
Subject: [forge-dev] JBoss Forge 2.0.0.Beta4 is available
In-Reply-To: <7FE0B2D6-A618-4B69-93B0-57FD8F050E68@redhat.com>
References: <7FE0B2D6-A618-4B69-93B0-57FD8F050E68@redhat.com>
Message-ID: <53929522-9AA1-4236-8047-68F39F3F87DC@redhat.com>

Congrats!

Sent from my iPhone

> On Dec 26, 2013, at 6:37 PM, George Gastaldi <ggastald at redhat.com> wrote:
> 
> More info:
> http://forge.jboss.org/news/2013/12/26/post-forge-2.html
> 
> Happy new year everyone!
> George Gastaldi
> 

From vpereira at redhat.com  Mon Dec 30 17:32:12 2013
From: vpereira at redhat.com (Vineet Reynolds Pereira)
Date: Mon, 30 Dec 2013 17:32:12 -0500 (EST)
Subject: [forge-dev] Forge 2 - Starting troubles
In-Reply-To: <407020559.44009264.1388437097102.JavaMail.root@redhat.com>
Message-ID: <717871057.44014937.1388442732106.JavaMail.root@redhat.com>


Hey all,

    I managed to get a beginner (who shall be anonymous for now), to try out Forge 2. It turned out to be rather interesting, since he managed to build it from source, install JBossTools-Forge into Eclipse, before running into some issues. I think some of these would affect how we look at usability of Forge in several areas - the tooling in Eclipse, the web site etc.

    Some of the questions that were asked were:

    1. "Is there an overview or something of forge 1/2 ?"

    and later (in response to this: http://www.youtube.com/watch?v=Dpou-FWWatI):

    "not really, it tells me more about how powerful it is - but no overview, why I should do what, says I can use it from the command line but I did not spot how, ..."

    I think a beginner guide would help here, that would help users who're new to even Java EE.

    2. Later on, when using Forge in Eclipse, this feedback was offered:
    "I noticed on the 'Forge Run Command' dialog, the Tooltip did not really add much to what could be gained from the command name!
     ...
     possible it might be a good idea to have a variable sized text panel in the bottom half to give a more detailed explanation"
    
    I'm not sure if the Eclipse UI guidelines allow for that, but it's something to consider.

    3. Another interesting issue is that of the EE 6/7 POMs being installed into the project:

      * Selected 'JPA setup' version 2.1
      * Selected Wildfly Aplication Server
      * Specified: Java EE, forge-default
      * Modified HSQLDB to POSTGRES using java:jboss/datasource/ExamplDS as datasource, 
      * and now pom.xml has <artifactId>jboss-javaee-6.0</artifactId> and other changes

     The EE 7 APIs were expected to added here.

    I've also raised FORGE-1385 for Java 1.7 support, but that's fixed and should be out in the next release, so it is moot.

    Discuss!

Vineet

From ivan.st.ivanov at gmail.com  Tue Dec 31 12:32:49 2013
From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov)
Date: Tue, 31 Dec 2013 19:32:49 +0200
Subject: [forge-dev] The git-tools addon
Message-ID: <CACYLA9Ebg1dW=jTORyrJ336Ujw2RWXp-Xn6g1WTkOUuaDraeDQ@mail.gmail.com>

Hi everybody,

A few hours before 2013 is over, I am very happy to announce that the
git-tools plugin from Forge 1 is finally migrated to a Forge 2 addon.

I have transformed the missing functionality and the tests in Forge core
addon style: different projects for api, addon, impl (containing the UI
commands) and tests. The tests are passing both in Eclipse and in Maven. I
have added javadoc to the APIs, README.asciidoc file and some man commands.

I haven't yet issued a pull request for two reasons:

* I am not sure whether you will want git-tools in the core repository or
you may want it in another one
* I expect some feedback from your side on my work

You can access the addon code here:
https://github.com/ivannov/core/tree/FORGE-1128. Once you build it and
install it in your local maven repository (Java 7 and Maven 3.1 required),
you may install it by simply running (FORGE_HOME should be set to Forge 2):

forge --install git-tools

You can review the functionality in the README file:

https://github.com/ivannov/core/tree/FORGE-1128/git-tools

As I have promised, I will send my feedback about the development
experience in Forge 2. I will also give you some feedback on the command
line shell usage on Windows (and maybe add some JIRAs to Antonio's list).
And, Lincoln, I haven't forgot this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=368230.

At the end, I wish all of you and your families a very happy, healthy and
successful 2014!

Cheers,
Ivan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131231/d28f3173/attachment-0001.html 

From ggastald at redhat.com  Tue Dec 31 12:40:20 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Tue, 31 Dec 2013 12:40:20 -0500 (EST)
Subject: [forge-dev] The git-tools addon
In-Reply-To: <CACYLA9Ebg1dW=jTORyrJ336Ujw2RWXp-Xn6g1WTkOUuaDraeDQ@mail.gmail.com>
References: <CACYLA9Ebg1dW=jTORyrJ336Ujw2RWXp-Xn6g1WTkOUuaDraeDQ@mail.gmail.com>
Message-ID: <A23BD1C3-DF4F-4E57-BAC2-E26524E4CC41@redhat.com>

Hey Ivan!

We'll review your code asap. I think also we might create a "git-tools-forge-addon" repository in forge organization to distribute that. Wdyt?

May you and your family also have a happy new year.

Best Regards,

George

> Em 31/12/2013, ?s 15:33, "Ivan St. Ivanov" <ivan.st.ivanov at gmail.com> escreveu:
> 
> Hi everybody,
> 
> A few hours before 2013 is over, I am very happy to announce that the git-tools plugin from Forge 1 is finally migrated to a Forge 2 addon.
> 
> I have transformed the missing functionality and the tests in Forge core addon style: different projects for api, addon, impl (containing the UI commands) and tests. The tests are passing both in Eclipse and in Maven. I have added javadoc to the APIs, README.asciidoc file and some man commands.
> 
> I haven't yet issued a pull request for two reasons:
> 
> * I am not sure whether you will want git-tools in the core repository or you may want it in another one
> * I expect some feedback from your side on my work
> 
> You can access the addon code here: https://github.com/ivannov/core/tree/FORGE-1128. Once you build it and install it in your local maven repository (Java 7 and Maven 3.1 required), you may install it by simply running (FORGE_HOME should be set to Forge 2):
> 
> forge --install git-tools
> 
> You can review the functionality in the README file:
> 
> https://github.com/ivannov/core/tree/FORGE-1128/git-tools
> 
> As I have promised, I will send my feedback about the development experience in Forge 2. I will also give you some feedback on the command line shell usage on Windows (and maybe add some JIRAs to Antonio's list). And, Lincoln, I haven't forgot this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=368230. 
> 
> At the end, I wish all of you and your families a very happy, healthy and successful 2014!
> 
> Cheers,
> Ivan
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131231/5917eb73/attachment.html 

From lincolnbaxter at gmail.com  Tue Dec 31 17:15:24 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 31 Dec 2013 17:15:24 -0500
Subject: [forge-dev] Missing commands on shell (jpa-setup wizard)
Message-ID: <CAEp_U4GVX=nxNTMvvLwx9Pmbest+3MWSn7xHLYfOUhS4qUfzNQ@mail.gmail.com>

So I don't forget by the time we get back from new-years- The bug is in
ShellWizard.java:

https://issues.jboss.org/browse/FORGE-1407

   private CommandLineParser populate(ShellContext shellContext, String
line,

            final Map<String, InputComponent<?, ?>> inputs)

            throws Exception

   {

      inputs.putAll(getController().getInputs());

      CommandLineParser parser =
commandLineUtil.generateParser(getController(),
shellContext, inputs);

      CommandLine cmdLine = parser.parse(line, true);

      Map<String, InputComponent<?, ?>> populatedInputs =
commandLineUtil.populateUIInputs(cmdLine,
inputs);

      if (getController().isValid())

      {

         if (getController().canMoveToNextStep())

         {

            // The bug is here. we are immediately moving to the next step
and removing all inputs that are not populated.

            // this really needs to know if we have defaulted to next step
or actually moved there willingly

            // it should not remove old choices until a new choice has been
made

            getController().next().initialize();

            inputs.keySet().retainAll(populatedInputs.keySet());

            parser = populate(shellContext, line, inputs);

         }

      }

      return parser;

   }

-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131231/a5083ffb/attachment.html 

From lincolnbaxter at gmail.com  Tue Dec 31 17:15:42 2013
From: lincolnbaxter at gmail.com (Lincoln Baxter, III)
Date: Tue, 31 Dec 2013 17:15:42 -0500
Subject: [forge-dev] Missing commands on shell (jpa-setup wizard)
In-Reply-To: <CAEp_U4GVX=nxNTMvvLwx9Pmbest+3MWSn7xHLYfOUhS4qUfzNQ@mail.gmail.com>
References: <CAEp_U4GVX=nxNTMvvLwx9Pmbest+3MWSn7xHLYfOUhS4qUfzNQ@mail.gmail.com>
Message-ID: <CAEp_U4Ht=UTVgQzHeiGbzs9Yak5WHu7da8rwWA1zL4b7QLqdjA@mail.gmail.com>

Sorry, the subject should be "missing options"


On Tue, Dec 31, 2013 at 5:15 PM, Lincoln Baxter, III <
lincolnbaxter at gmail.com> wrote:

> So I don't forget by the time we get back from new-years- The bug is in
> ShellWizard.java:
>
> https://issues.jboss.org/browse/FORGE-1407
>
>    private CommandLineParser populate(ShellContext shellContext, String
> line,
>
>             final Map<String, InputComponent<?, ?>> inputs)
>
>             throws Exception
>
>    {
>
>       inputs.putAll(getController().getInputs());
>
>       CommandLineParser parser = commandLineUtil.generateParser(getController(),
> shellContext, inputs);
>
>       CommandLine cmdLine = parser.parse(line, true);
>
>       Map<String, InputComponent<?, ?>> populatedInputs = commandLineUtil.populateUIInputs(cmdLine,
> inputs);
>
>       if (getController().isValid())
>
>       {
>
>          if (getController().canMoveToNextStep())
>
>          {
>
>             // The bug is here. we are immediately moving to the next
> step and removing all inputs that are not populated.
>
>             // this really needs to know if we have defaulted to next
> step or actually moved there willingly
>
>             // it should not remove old choices until a new choice has
> been made
>
>             getController().next().initialize();
>
>             inputs.keySet().retainAll(populatedInputs.keySet());
>
>             parser = populate(shellContext, line, inputs);
>
>          }
>
>       }
>
>       return parser;
>
>    }
>
> --
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131231/62497a9e/attachment.html 

From ggastald at redhat.com  Tue Dec 31 18:00:10 2013
From: ggastald at redhat.com (George Gastaldi)
Date: Tue, 31 Dec 2013 18:00:10 -0500 (EST)
Subject: [forge-dev] Missing commands on shell (jpa-setup wizard)
In-Reply-To: <CAEp_U4GVX=nxNTMvvLwx9Pmbest+3MWSn7xHLYfOUhS4qUfzNQ@mail.gmail.com>
References: <CAEp_U4GVX=nxNTMvvLwx9Pmbest+3MWSn7xHLYfOUhS4qUfzNQ@mail.gmail.com>
Message-ID: <A98062F1-770A-44EE-9E84-D8C7B06680EA@redhat.com>

This looks like a duplicate of https://issues.jboss.org/browse/FORGE-1404

Maybe we should close FORGE-1404, given that FORGE-1407 has more information

> Em 31/12/2013, ?s 20:15, "Lincoln Baxter, III" <lincolnbaxter at gmail.com> escreveu:
> 
> So I don't forget by the time we get back from new-years- The bug is in ShellWizard.java:
> 
> https://issues.jboss.org/browse/FORGE-1407
>    private CommandLineParser populate(ShellContext shellContext, String line,
> 
>             final Map<String, InputComponent<?, ?>> inputs)
> 
>             throws Exception
> 
>    {
> 
>       inputs.putAll(getController().getInputs());
> 
>       CommandLineParser parser = commandLineUtil.generateParser(getController(), shellContext, inputs);
> 
>       CommandLine cmdLine = parser.parse(line, true);
> 
>       Map<String, InputComponent<?, ?>> populatedInputs = commandLineUtil.populateUIInputs(cmdLine, inputs);
> 
>       if (getController().isValid())
> 
>       {
> 
>          if (getController().canMoveToNextStep())
> 
>          {
> 
>             // The bug is here. we are immediately moving to the next step and removing all inputs that are not populated.
> 
>             // this really needs to know if we have defaulted to next step or actually moved there willingly
> 
>             // it should not remove old choices until a new choice has been made
> 
>             getController().next().initialize();
> 
>             inputs.keySet().retainAll(populatedInputs.keySet());
> 
>             parser = populate(shellContext, line, inputs);
> 
>          }
> 
>       }
> 
>       return parser;
> 
>    }
> 
> 
> -- 
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20131231/e3f3cb6d/attachment-0001.html