6:06 p.m.
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
9:56 a.m.
My sense is that you're trying to perform a CORS request and probably
your REST service is not configured to support CORS.
Here is an example to configure it [1]
[1]:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/src/m...
On Sat, 2013-12-14 at 12:06 -0500, Burr Sutter 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:11 a.m.
On Mon, Dec 16, 2013 at 9:56 AM, Apostolos Emmanouilidis <
aemmanou(a)redhat.com> wrote:
My sense is that you're trying to perform a CORS request and
probably
your REST service is not configured to support CORS.
CORS should not be an issue for a hybrid/cordova app and even then, the
POST should not even occurs if there was a CORS issue.
Here is an example to configure it [1]
[1]:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/src/m...
On Sat, 2013-12-14 at 12:06 -0500, Burr Sutter 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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
1:01 p.m.
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@test.com","name":"newTest"}'
http://agmobile-html5.rhcloud.com/rest/forge/members
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.
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 ?
On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
2:23 p.m.
without even looking, that is what i was thinking the culprit is.
On Dec 16, 2013, at 7:01 AM, Sebastien Blanc <scm.blanc(a)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@test.com","name":"newTest"}'
http://agmobile-html5.rhcloud.com/rest/forge/members
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.
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 ?
On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
7:52 p.m.
Adding Vineet as he has spent time on the Forge REST scaffolding.
On Dec 16, 2013, at 7:01 AM, Sebastien Blanc <scm.blanc(a)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@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/burr...
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")
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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
8:23 p.m.
On Dec 16, 2013, at 1:52 PM, Burr Sutter <bsutter(a)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(a)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@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/burr...
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")
>
> 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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
9:06 p.m.
----- Original Message -----
From: "Lucas Holmquist" <lholmqui(a)redhat.com>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Cc: "Vineet Reynolds Pereira" <vpereira(a)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(a)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(a)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@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/burr...
> 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(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
9:29 p.m.
That seems to do the trick - now, where do we apply the fix? :-)
On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira <vpereira(a)redhat.com> wrote:
----- Original Message -----
> From: "Lucas Holmquist" <lholmqui(a)redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
> Cc: "Vineet Reynolds Pereira" <vpereira(a)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(a)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(a)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@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/burr...
>> 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(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:25 p.m.
Adding forge-dev.
----- Original Message -----
From: "Burr Sutter" <bsutter(a)redhat.com>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)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(a)redhat.com >
wrote:
----- Original Message -----
From: "Lucas Holmquist" < lholmqui(a)redhat.com >
To: "AeroGear Developer Mailing List" < aerogear-dev(a)lists.jboss.org >
Cc: "Vineet Reynolds Pereira" < vpereira(a)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(a)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(a)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@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/burr...
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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:27 p.m.
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(a)redhat.com>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Cc: "forge-dev List" <forge-dev(a)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(a)redhat.com>
> To: "AeroGear Developer Mailing List"
<aerogear-dev(a)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(a)redhat.com
> >
> wrote:
>
>
>
>
>
>
> ----- Original Message -----
>
>
> From: "Lucas Holmquist" < lholmqui(a)redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev(a)lists.jboss.org
>
> Cc: "Vineet Reynolds Pereira" < vpereira(a)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(a)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(a)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@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/burr...
> 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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
11:41 p.m.
New subject: [forge-dev] Aerogear.js for CRUD
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(a)redhat.com> wrote:
Adding forge-dev.
----- Original Message -----
> From: "Burr Sutter" <bsutter(a)redhat.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev(a)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(a)redhat.com >
> wrote:
>
>
>
>
>
>
> ----- Original Message -----
>
>
> From: "Lucas Holmquist" < lholmqui(a)redhat.com >
> To: "AeroGear Developer Mailing List" < aerogear-dev(a)lists.jboss.org
>
> Cc: "Vineet Reynolds Pereira" < vpereira(a)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(a)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(a)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@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/burr...
> 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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
4:47 p.m.
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(a)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.
4:54 p.m.
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(a)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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
9:57 a.m.
On Wed, Dec 18, 2013 at 4:54 PM, Burr Sutter <bsutter(a)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(a)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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
3774
days inactive
3779
days old
14 comments
6 participants
participants (6)
-
Apostolos Emmanouilidis -
Burr Sutter -
Karel Piwko -
Lucas Holmquist -
Sebastien Blanc -
Vineet Reynolds Pereira