4:27 a.m.
Hi all,
As we are almost done with the HelloWorlds, I think we can we start on the
Quickstart clients. As a reminder, the Quickstart will consist in a simple
Contact CRUD application with the possibility to send a Push Notification
to one of the listed contacts. Please refer to this
JIRA<https://issues.jboss.org/browse/AGPUSH-604> to
have more information.
The clients will have to communicate against secured REST endpoints. Joshua
and Pedro have started to work on that but nothing official is released
yet. I've tried out their
branch<https://github.com/pedroigor/jboss-wfk-quickstarts/tree/PLINK-3...
and
IMHO it's good enough to start using it for building our clients, the
restpoints won't change that much I believe.
And because I love you, I deployed on OpenShift a version of this secured
backend to ease the development of the clients !
If you browse to http://contacts-sblanc.rhcloud.com/ you will even see the
mobile web client. This deployed version contains also the Push Message
endpoint.
The branch of this deployed version can be found
here<https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push...
.
But let's take a look at the diffrent REST endpoints :
<https://gist.github.com/sebastienblanc/10966803#crud-operations>CRUD
operations
I won't detail them here, since there is already a doc for that :
https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.x-devel...
<https://gist.github.com/sebastienblanc/10966803#security>Security
*DISCLAIMER* : These might change
<https://gist.github.com/sebastienblanc/10966803#register>REGISTER<h...
a new
user<https://gist.github.com/sebastienblanc/10966803#restsecurityregis...
/rest/security/registration
- Request type: POST
- Request type: JSON
- Return type: JSON
- Request example:
curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
"Content-type: application/json" -X POST -d
'{"firstName":"Jaime","lastName":"Lannister","userName":"jaime.lannister@westerlands.com","password":"hearmeroar"}'
http://contacts-sblanc.rhcloud.com/rest/security/registration
*NOTE* : We should use the convention to use the *email* as userName
<https://gist.github.com/sebastienblanc/10966803#getlogin>GET/LOGIN<...
a user and log him
in<https://gist.github.com/sebastienblanc/10966803#restsecurityuserinf...
/rest/security/user/info
- Request type: GET
- Request type: JSON
- Auth : Basic Auth
- Return type: JSON
- Request example:
curl -v -b cookies.txt -c cookies.txt -u
"jaime.lannister@westerlands.com:hearmeroar" -H "Accept:
application/json" -H "Content-type: application/json" -X GET
http://contacts-sblanc.rhcloud.com/rest/security/user/info
<https://gist.github.com/sebastienblanc/10966803#logout>LOGOUT<https...
a user<https://gist.github.com/sebastienblanc/10966803#restsecurityuseri...
/rest/security/user/info
- Request type: POST
- Request type: JSON
- Return type: JSON
- Request example:
curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
"Content-type: application/json" -X POST
http://contacts-sblanc.rhcloud.com/rest/security/logout
<https://gist.github.com/sebastienblanc/10966803#push-rest-endpoint>Push
Rest Endpoint
I've added a new endpoint to push a message. In the deployed version, it's
hardcoded for now to send to the "quickstart" application created for the
https://quickstartsups-sblanc.rhcloud.com/ UPS instance, you will also have
to create the appropriate variants.
<https://gist.github.com/sebastienblanc/10966803#registration-with-the-ups...
with the UPS instance
I think the good flow would be to register with UPS once the login was
successfull. As *alias* the *email*should be passed
<https://gist.github.com/sebastienblanc/10966803#endpoint>Endpoint<h...
/rest/contacts/sendMessage
- Request type: POST
- Request type: JSON
- Return type: JSON
- Request example:
curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H
"Content-type: application/json" -X POST -d
'{"author":"Jaime","receiver":"john.snow@thenorth.com","message":"Winter
is coming !"}' http://contacts-sblanc.rhcloud.com/rest/contacts/sendMessage
So here we can see that we pass data like :
{
"author":"jaime.lannister@westerlands.com",
"receiver":"john.snow@thenorth.com",
"message":"Winter is coming !"
}
To keep it simple, the client should always pass a hardcoded value for the
message , we don't want (for now)to add any complexity to the clients by
adding an extra dialog to enter custom messages.
author and receiver should contain the emails as we used that for the alias in
UPS.
So, I hope all this will help to boostrap the client's work. Remarks,
questions ?
(the content of this email is available
here<https://gist.github.com/sebastienblanc/10966803>
)
Sebi
2:48 p.m.
If your idea is to be secure, please make sure to use HTTPS and enforce
users to be redirected. We did it in the past with HSTS on AG Security,
might not be hard to copy & paste.
Sebastien Blanc wrote:
And because I love you, I deployed on OpenShift a version of this
secured
backend to ease the development of the clients !
If you browse to http://contacts-sblanc.rhcloud.com/ you will even see the
mobile web client. This deployed version contains also the Push Message
endpoint.
--
abstractj
4:07 p.m.
Sure !
This is just a version to ease the client development.
I will ask PL team and Joshua their plans around HSTS and HTTPS.
In the mean time we can track all of this with
https://issues.jboss.org/browse/AGPUSH-596
Thx for the comment !
Sebi
On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
If your idea is to be secure, please make sure to use HTTPS and
enforce
users to be redirected. We did it in the past with HSTS on AG Security,
might not be hard to copy & paste.
Sebastien Blanc wrote:
> And because I love you, I deployed on OpenShift a version of this secured
> backend to ease the development of the clients !
>
> If you browse to http://contacts-sblanc.rhcloud.com/ you will even see
the
> mobile web client. This deployed version contains also the Push Message
> endpoint.
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
12:34 p.m.
To register I send "userName" and the login response "loginName"?
-- Passos
On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>wrote:
Sure !
This is just a version to ease the client development.
I will ask PL team and Joshua their plans around HSTS and HTTPS.
In the mean time we can track all of this with
https://issues.jboss.org/browse/AGPUSH-596
Thx for the comment !
Sebi
On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org>wrote:
> If your idea is to be secure, please make sure to use HTTPS and enforce
> users to be redirected. We did it in the past with HSTS on AG Security,
> might not be hard to copy & paste.
>
> Sebastien Blanc wrote:
> > And because I love you, I deployed on OpenShift a version of this
> secured
> > backend to ease the development of the clients !
> >
> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even see
> the
> > mobile web client. This deployed version contains also the Push Message
> > endpoint.
>
1:13 p.m.
Since we changed the use case for the Push part (now we broadcast) ,
passing a alias to UPS is not relevant anymore. For the login it's indeed
"loginName" to be passed in the auth header along with the password.
On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
To register I send "userName" and the login response
"loginName"?
-- Passos
On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>wrote:
> Sure !
> This is just a version to ease the client development.
> I will ask PL team and Joshua their plans around HSTS and HTTPS.
> In the mean time we can track all of this with
> https://issues.jboss.org/browse/AGPUSH-596
>
> Thx for the comment !
> Sebi
>
>
> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org>wrote:
>
>> If your idea is to be secure, please make sure to use HTTPS and enforce
>> users to be redirected. We did it in the past with HSTS on AG Security,
>> might not be hard to copy & paste.
>>
>> Sebastien Blanc wrote:
>> > And because I love you, I deployed on OpenShift a version of this
>> secured
>> > backend to ease the development of the clients !
>> >
>> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even
>> see the
>> > mobile web client. This deployed version contains also the Push Message
>> > endpoint.
>>
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
1:48 p.m.
Someone know that I am doing wrong?
Login
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-u "myuser:mypass" \
-X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
Update Contact
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-X PUT \
-d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
http://quickstarts-edewit.rhcloud.com/rest/contacts/7
— Passos
On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
Since we changed the use case for the Push part (now we broadcast) ,
passing a alias to UPS is not relevant anymore. For the login it's indeed
"loginName" to be passed in the auth header along with the password.
On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
> To register I send "userName" and the login response
"loginName"?
>
> -- Passos
>
>
>
> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
> wrote:
>
>> Sure !
>> This is just a version to ease the client development.
>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>> In the mean time we can track all of this with
>> https://issues.jboss.org/browse/AGPUSH-596
>>
>> Thx for the comment !
>> Sebi
>>
>>
>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org>
>> wrote:
>>
>>> If your idea is to be secure, please make sure to use HTTPS and enforce
>>> users to be redirected. We did it in the past with HSTS on AG Security,
>>> might not be hard to copy & paste.
>>>
>>> Sebastien Blanc wrote:
>>> > And because I love you, I deployed on OpenShift a version of this
>>> secured
>>> > backend to ease the development of the clients !
>>> >
>>> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even
>>> see the
>>> > mobile web client. This deployed version contains also the Push
>>> Message
>>> > endpoint.
>>>
>>
> _______________________________________________
> 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
2:39 a.m.
What is the issue you are having and what are you trying to do (issue just
with the update?) ?
On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me> wrote:
Someone know that I am doing wrong?
Login
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-u "myuser:mypass" \
-X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
Update Contact
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-X PUT \
-d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
http://quickstarts-edewit.rhcloud.com/rest/contacts/7
— Passos
On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
> Since we changed the use case for the Push part (now we broadcast) ,
> passing a alias to UPS is not relevant anymore. For the login it's indeed
> "loginName" to be passed in the auth header along with the password.
>
>
>
> On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
>
>> To register I send "userName" and the login response
"loginName"?
>>
>> -- Passos
>>
>>
>>
>> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
>> wrote:
>>
>>> Sure !
>>> This is just a version to ease the client development.
>>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>>> In the mean time we can track all of this with
>>> https://issues.jboss.org/browse/AGPUSH-596
>>>
>>> Thx for the comment !
>>> Sebi
>>>
>>>
>>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org>
>>> wrote:
>>>
>>>> If your idea is to be secure, please make sure to use HTTPS and enforce
>>>> users to be redirected. We did it in the past with HSTS on AG Security,
>>>> might not be hard to copy & paste.
>>>>
>>>> Sebastien Blanc wrote:
>>>> > And because I love you, I deployed on OpenShift a version of this
>>>> secured
>>>> > backend to ease the development of the clients !
>>>> >
>>>> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even
>>>> see the
>>>> > mobile web client. This deployed version contains also the Push
>>>> Message
>>>> > endpoint.
>>>>
>>>
>> _______________________________________________
>> 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
7:07 a.m.
Sorry,
Yes, I am try updating a contact and the server responded w/ status code 500
* Adding handle: conn: 0x7ff159003000
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7ff159003000) send_pipe: 1, recv_pipe: 0
* About to connect() to quickstarts-edewit.rhcloud.com port 80 (#0)
* Trying 50.16.176.239...
* Connected to quickstarts-edewit.rhcloud.com (50.16.176.239) port 80 (#0)
PUT /rest/contacts/7 HTTP/1.1
User-Agent: curl/7.30.0
Host: quickstarts-edewit.rhcloud.com
Cookie: JSESSIONID=zugucP2LNHLbCNNOwBrD3mx6.quickstarts-edewit.rhcloud.com
Accept: application/json
Content-type: application/json
Content-Length: 120
* upload completely sent off: 120 out of 120 bytes
< HTTP/1.1 500 Internal Server Error
< Date: Mon, 02 Jun 2014 12:04:59 GMT
< Content-Type: text/html;charset=ISO-8859-1
< Content-Length: 80
< Connection: close
<
* Closing connection 0
<html><head><title>Error</title></head><body>Internal
Server Error</body></html>
On Mon, Jun 2, 2014 at 4:39 AM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
What is the issue you are having and what are you trying to do (issue
just
with the update?) ?
On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me> wrote:
> Someone know that I am doing wrong?
> Login
>
> curl -v -b cookies.txt -c cookies.txt \
> -H "Accept: application/json" \
> -H "Content-type: application/json" \
> -u "myuser:mypass" \
> -X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
>
> Update Contact
>
> curl -v -b cookies.txt -c cookies.txt \
> -H "Accept: application/json" \
> -H "Content-type: application/json" \
> -X PUT \
> -d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
> http://quickstarts-edewit.rhcloud.com/rest/contacts/7
>
> — Passos
>
>
>
> On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
> wrote:
>
>> Since we changed the use case for the Push part (now we broadcast) ,
>> passing a alias to UPS is not relevant anymore. For the login it's indeed
>> "loginName" to be passed in the auth header along with the password.
>>
>>
>>
>> On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
>>
>>> To register I send "userName" and the login response
"loginName"?
>>>
>>> -- Passos
>>>
>>>
>>>
>>> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
>>> wrote:
>>>
>>>> Sure !
>>>> This is just a version to ease the client development.
>>>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>>>> In the mean time we can track all of this with
>>>> https://issues.jboss.org/browse/AGPUSH-596
>>>>
>>>> Thx for the comment !
>>>> Sebi
>>>>
>>>>
>>>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira
<bruno(a)abstractj.org>
>>>> wrote:
>>>>
>>>>> If your idea is to be secure, please make sure to use HTTPS and
>>>>> enforce
>>>>> users to be redirected. We did it in the past with HSTS on AG
>>>>> Security,
>>>>> might not be hard to copy & paste.
>>>>>
>>>>> Sebastien Blanc wrote:
>>>>> > And because I love you, I deployed on OpenShift a version of
this
>>>>> secured
>>>>> > backend to ease the development of the clients !
>>>>> >
>>>>> > If you browse to http://contacts-sblanc.rhcloud.com/ you will
even
>>>>> see the
>>>>> > mobile web client. This deployed version contains also the Push
>>>>> Message
>>>>> > endpoint.
>>>>>
>>>>
>>> _______________________________________________
>>> 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
7:10 a.m.
Your request look good but without having the application server log it's
hard to tell what is going on exactly. You could ask Erik to check the log
or deploy the backend locally.
On Mon, Jun 2, 2014 at 2:07 PM, Daniel Passos <daniel(a)passos.me> wrote:
Sorry,
Yes, I am try updating a contact and the server responded w/ status code
500
* Adding handle: conn: 0x7ff159003000
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7ff159003000) send_pipe: 1, recv_pipe: 0
* About to connect() to quickstarts-edewit.rhcloud.com port 80 (#0)
* Trying 50.16.176.239...
* Connected to quickstarts-edewit.rhcloud.com (50.16.176.239) port 80 (#0)
> PUT /rest/contacts/7 HTTP/1.1
> User-Agent: curl/7.30.0
> Host: quickstarts-edewit.rhcloud.com
> Cookie: JSESSIONID=zugucP2LNHLbCNNOwBrD3mx6.quickstarts-edewit.rhcloud.com
> Accept: application/json
> Content-type: application/json
> Content-Length: 120
>
* upload completely sent off: 120 out of 120 bytes
< HTTP/1.1 500 Internal Server Error
< Date: Mon, 02 Jun 2014 12:04:59 GMT
< Content-Type: text/html;charset=ISO-8859-1
< Content-Length: 80
< Connection: close
<
* Closing connection 0
<html><head><title>Error</title></head><body>Internal
Server Error</body></html>
On Mon, Jun 2, 2014 at 4:39 AM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
> What is the issue you are having and what are you trying to do (issue
> just with the update?) ?
>
>
>
> On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me> wrote:
>
>> Someone know that I am doing wrong?
>> Login
>>
>> curl -v -b cookies.txt -c cookies.txt \
>> -H "Accept: application/json" \
>> -H "Content-type: application/json" \
>> -u "myuser:mypass" \
>> -X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
>>
>> Update Contact
>>
>> curl -v -b cookies.txt -c cookies.txt \
>> -H "Accept: application/json" \
>> -H "Content-type: application/json" \
>> -X PUT \
>> -d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
>> http://quickstarts-edewit.rhcloud.com/rest/contacts/7
>>
>> — Passos
>>
>>
>>
>> On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
>> wrote:
>>
>>> Since we changed the use case for the Push part (now we broadcast) ,
>>> passing a alias to UPS is not relevant anymore. For the login it's
indeed
>>> "loginName" to be passed in the auth header along with the
password.
>>>
>>>
>>>
>>> On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me>
>>> wrote:
>>>
>>>> To register I send "userName" and the login response
"loginName"?
>>>>
>>>> -- Passos
>>>>
>>>>
>>>>
>>>> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc
<scm.blanc(a)gmail.com>
>>>> wrote:
>>>>
>>>>> Sure !
>>>>> This is just a version to ease the client development.
>>>>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>>>>> In the mean time we can track all of this with
>>>>> https://issues.jboss.org/browse/AGPUSH-596
>>>>>
>>>>> Thx for the comment !
>>>>> Sebi
>>>>>
>>>>>
>>>>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira
<bruno(a)abstractj.org>
>>>>> wrote:
>>>>>
>>>>>> If your idea is to be secure, please make sure to use HTTPS and
>>>>>> enforce
>>>>>> users to be redirected. We did it in the past with HSTS on AG
>>>>>> Security,
>>>>>> might not be hard to copy & paste.
>>>>>>
>>>>>> Sebastien Blanc wrote:
>>>>>> > And because I love you, I deployed on OpenShift a version of
this
>>>>>> secured
>>>>>> > backend to ease the development of the clients !
>>>>>> >
>>>>>> > If you browse to http://contacts-sblanc.rhcloud.com/ you
will
>>>>>> even see the
>>>>>> > mobile web client. This deployed version contains also the
Push
>>>>>> Message
>>>>>> > endpoint.
>>>>>>
>>>>>
>>>> _______________________________________________
>>>> 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
7:31 a.m.
Seems to be a NullPointer:
Caused by: java.lang.NullPointerException
at
org.jboss.quickstarts.wfk.contacts.customer.ContactRESTService.updateContact(ContactRESTService.java:192)
[classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[rt.jar:1.7.0_55]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.7.0_55]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_55]
at
org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
at
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:87)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.apache.deltaspike.security.impl.extension.DefaultSecurityStrategy.execute(DefaultSecurityStrategy.java:61)
[deltaspike-security-module-impl-0.5.jar:0.5]
at
org.apache.deltaspike.security.impl.extension.SecurityInterceptor.filterDeniedInvocations(SecurityInterceptor.java:44)
[deltaspike-security-module-impl-0.5.jar:0.5]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[rt.jar:1.7.0_55]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.7.0_55]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_55]
at
org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:103)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:81)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:105)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:77)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:68)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
[wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
[wildfly-jpa-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
at
org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:46)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
[wildfly-ee-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.ejb3.component.interceptors.NonPooledEJBComponentInstanceAssociatingInterceptor.processInvocation(NonPooledEJBComponentInstanceAssociatingInterceptor.java:59)
[wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273)
[wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1]
... 81 more
And that means the contact Id is null:
https://github.com/edewit/jboss-wfk-quickstarts/blob/push/contacts-mobile...
So your data should also contain the same id as the id in the url
-d
'{"firstName":"Davey","lastName":"Jones","phoneNumber":"1(212)555-3333","email":"davey.jones@locker.com","birthDate":"1996-08-07","id”:"7"}'
On 2 Jun,2014, at 14:10 , Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
Your request look good but without having the application server log
it's hard to tell what is going on exactly. You could ask Erik to check the log or
deploy the backend locally.
On Mon, Jun 2, 2014 at 2:07 PM, Daniel Passos <daniel(a)passos.me> wrote:
Sorry,
Yes, I am try updating a contact and the server responded w/ status code 500
* Adding handle: conn: 0x7ff159003000
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7ff159003000) send_pipe: 1, recv_pipe: 0
* About to connect() to quickstarts-edewit.rhcloud.com port 80 (#0)
* Trying 50.16.176.239...
* Connected to quickstarts-edewit.rhcloud.com (50.16.176.239) port 80 (#0)
> PUT /rest/contacts/7 HTTP/1.1
> User-Agent: curl/7.30.0
> Host: quickstarts-edewit.rhcloud.com
> Cookie: JSESSIONID=zugucP2LNHLbCNNOwBrD3mx6.quickstarts-edewit.rhcloud.com
> Accept: application/json
> Content-type: application/json
> Content-Length: 120
>
* upload completely sent off: 120 out of 120 bytes
< HTTP/1.1 500 Internal Server Error
< Date: Mon, 02 Jun 2014 12:04:59 GMT
< Content-Type: text/html;charset=ISO-8859-1
< Content-Length: 80
< Connection: close
<
* Closing connection 0
<html><head><title>Error</title></head><body>Internal
Server Error</body></html>
On Mon, Jun 2, 2014 at 4:39 AM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
What is the issue you are having and what are you trying to do (issue just with the
update?) ?
On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me> wrote:
Someone know that I am doing wrong?
Login
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-u "myuser:mypass" \
-X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
Update Contact
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-X PUT \
-d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
http://quickstarts-edewit.rhcloud.com/rest/contacts/7
— Passos
On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
Since we changed the use case for the Push part (now we broadcast) , passing a alias to
UPS is not relevant anymore. For the login it's indeed "loginName" to be
passed in the auth header along with the password.
On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
To register I send "userName" and the login response "loginName"?
-- Passos
On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
Sure !
This is just a version to ease the client development.
I will ask PL team and Joshua their plans around HSTS and HTTPS.
In the mean time we can track all of this with
https://issues.jboss.org/browse/AGPUSH-596
Thx for the comment !
Sebi
On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
If your idea is to be secure, please make sure to use HTTPS and enforce
users to be redirected. We did it in the past with HSTS on AG Security,
might not be hard to copy & paste.
Sebastien Blanc wrote:
> And because I love you, I deployed on OpenShift a version of this secured
> backend to ease the development of the clients !
>
> If you browse to http://contacts-sblanc.rhcloud.com/ you will even see the
> mobile web client. This deployed version contains also the Push Message
> endpoint.
_______________________________________________
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
9:05 a.m.
Would make sense to file a Jira to:
https://issues.jboss.org/browse/JBWFK ?
On 2014-06-02, Erik Jan de Wit wrote:
Seems to be a NullPointer:
Caused by: java.lang.NullPointerException
at
org.jboss.quickstarts.wfk.contacts.customer.ContactRESTService.updateContact(ContactRESTService.java:192)
[classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[rt.jar:1.7.0_55]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.7.0_55]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_55]
at
org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
at
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:87)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.apache.deltaspike.security.impl.extension.DefaultSecurityStrategy.execute(DefaultSecurityStrategy.java:61)
[deltaspike-security-module-impl-0.5.jar:0.5]
at
org.apache.deltaspike.security.impl.extension.SecurityInterceptor.filterDeniedInvocations(SecurityInterceptor.java:44)
[deltaspike-security-module-impl-0.5.jar:0.5]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[rt.jar:1.7.0_55]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.7.0_55]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_55]
at
org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:103)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:81)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:105)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:77)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:68)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
[wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
[wildfly-jpa-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
at
org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:46)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
[wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
[wildfly-ee-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at
org.jboss.as.ejb3.component.interceptors.NonPooledEJBComponentInstanceAssociatingInterceptor.processInvocation(NonPooledEJBComponentInstanceAssociatingInterceptor.java:59)
[wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273)
[wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1]
... 81 more
And that means the contact Id is null:
https://github.com/edewit/jboss-wfk-quickstarts/blob/push/contacts-mobile...
So your data should also contain the same id as the id in the url
-d
'{"firstName":"Davey","lastName":"Jones","phoneNumber":"1(212)555-3333","email":"davey.jones@locker.com","birthDate":"1996-08-07","id”:"7"}'
On 2 Jun,2014, at 14:10 , Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
> Your request look good but without having the application server log it's hard
to tell what is going on exactly. You could ask Erik to check the log or deploy the
backend locally.
>
>
>
> On Mon, Jun 2, 2014 at 2:07 PM, Daniel Passos <daniel(a)passos.me> wrote:
> Sorry,
>
> Yes, I am try updating a contact and the server responded w/ status code 500
>
>
> * Adding handle: conn: 0x7ff159003000
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0x7ff159003000) send_pipe: 1, recv_pipe: 0
> * About to connect() to quickstarts-edewit.rhcloud.com port 80 (#0)
> * Trying 50.16.176.239...
> * Connected to quickstarts-edewit.rhcloud.com (50.16.176.239) port 80 (#0)
> > PUT /rest/contacts/7 HTTP/1.1
> > User-Agent: curl/7.30.0
> > Host: quickstarts-edewit.rhcloud.com
> > Cookie: JSESSIONID=zugucP2LNHLbCNNOwBrD3mx6.quickstarts-edewit.rhcloud.com
> > Accept: application/json
> > Content-type: application/json
> > Content-Length: 120
> >
> * upload completely sent off: 120 out of 120 bytes
> < HTTP/1.1 500 Internal Server Error
> < Date: Mon, 02 Jun 2014 12:04:59 GMT
> < Content-Type: text/html;charset=ISO-8859-1
> < Content-Length: 80
> < Connection: close
> <
> * Closing connection 0
>
<html><head><title>Error</title></head><body>Internal
Server Error</body></html>
>
>
>
> On Mon, Jun 2, 2014 at 4:39 AM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
> What is the issue you are having and what are you trying to do (issue just with the
update?) ?
>
>
>
> On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me> wrote:
> Someone know that I am doing wrong?
>
> Login
>
> curl -v -b cookies.txt -c cookies.txt \
> -H "Accept: application/json" \
> -H "Content-type: application/json" \
> -u "myuser:mypass" \
> -X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
> Update Contact
>
> curl -v -b cookies.txt -c cookies.txt \
> -H "Accept: application/json" \
> -H "Content-type: application/json" \
> -X PUT \
> -d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
> http://quickstarts-edewit.rhcloud.com/rest/contacts/7
> — Passos
>
>
>
>
> On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
> Since we changed the use case for the Push part (now we broadcast) , passing a alias
to UPS is not relevant anymore. For the login it's indeed "loginName" to be
passed in the auth header along with the password.
>
>
>
> On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
> To register I send "userName" and the login response
"loginName"?
> -- Passos
>
>
>
> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
> Sure !
> This is just a version to ease the client development.
> I will ask PL team and Joshua their plans around HSTS and HTTPS.
> In the mean time we can track all of this with
https://issues.jboss.org/browse/AGPUSH-596
>
> Thx for the comment !
> Sebi
>
>
> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
> If your idea is to be secure, please make sure to use HTTPS and enforce
> users to be redirected. We did it in the past with HSTS on AG Security,
> might not be hard to copy & paste.
>
> Sebastien Blanc wrote:
> > And because I love you, I deployed on OpenShift a version of this secured
> > backend to ease the development of the clients !
> >
> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even see the
> > mobile web client. This deployed version contains also the Push Message
> > endpoint.
>
> _______________________________________________
> 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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
9:41 a.m.
Correct JIRA for WFK would be:
https://issues.jboss.org/browse/JBWFK2
However, I'd rather target upstream first:
https://issues.jboss.org/browse/JDF/component/12315845/
Karel
On Mon, 2 Jun 2014 11:05:45 -0300
Bruno Oliveira <bruno(a)abstractj.org> wrote:
Would make sense to file a Jira to:
https://issues.jboss.org/browse/JBWFK ?
On 2014-06-02, Erik Jan de Wit wrote:
> Seems to be a NullPointer:
>
> Caused by: java.lang.NullPointerException
> at
>
org.jboss.quickstarts.wfk.contacts.customer.ContactRESTService.updateContact(ContactRESTService.java:192)
> [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.7.0_55] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [rt.jar:1.7.0_55] at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.7.0_55] at java.lang.reflect.Method.invoke(Method.java:606)
> [rt.jar:1.7.0_55] at
>
org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> at
>
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
> at
>
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:87)
> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>
org.apache.deltaspike.security.impl.extension.DefaultSecurityStrategy.execute(DefaultSecurityStrategy.java:61)
> [deltaspike-security-module-impl-0.5.jar:0.5] at
>
org.apache.deltaspike.security.impl.extension.SecurityInterceptor.filterDeniedInvocations(SecurityInterceptor.java:44)
> [deltaspike-security-module-impl-0.5.jar:0.5] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.7.0_55] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [rt.jar:1.7.0_55] at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.7.0_55] at java.lang.reflect.Method.invoke(Method.java:606)
> [rt.jar:1.7.0_55] at
>
org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30)
> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:103)
> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:81)
> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
> org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:105)
> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:77)
> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:68)
> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80)
> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> at
>
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> [wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1] at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> [wildfly-jpa-8.1.0.CR1.jar:8.1.0.CR1] at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
> at
>
org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:46)
> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> [wildfly-ee-8.1.0.CR1.jar:8.1.0.CR1] at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at
>
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
>
org.jboss.as.ejb3.component.interceptors.NonPooledEJBComponentInstanceAssociatingInterceptor.processInvocation(NonPooledEJBComponentInstanceAssociatingInterceptor.java:59)
> [wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1] at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273)
> [wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1] ... 81 more
>
> And that means the contact Id is null:
>
>
https://github.com/edewit/jboss-wfk-quickstarts/blob/push/contacts-mobile...
>
> So your data should also contain the same id as the id in the url
>
> -d
>
'{"firstName":"Davey","lastName":"Jones","phoneNumber":"1(212)555-3333","email":"davey.jones@locker.com","birthDate":"1996-08-07","id”:"7"}'
>
>
> On 2 Jun,2014, at 14:10 , Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
>
> > Your request look good but without having the application server log it's
> > hard to tell what is going on exactly. You could ask Erik to check the
> > log or deploy the backend locally.
> >
> >
> >
> > On Mon, Jun 2, 2014 at 2:07 PM, Daniel Passos <daniel(a)passos.me> wrote:
> > Sorry,
> >
> > Yes, I am try updating a contact and the server responded w/ status code
> > 500
> >
> >
> > * Adding handle: conn: 0x7ff159003000
> > * Adding handle: send: 0
> > * Adding handle: recv: 0
> > * Curl_addHandleToPipeline: length: 1
> > * - Conn 0 (0x7ff159003000) send_pipe: 1, recv_pipe: 0
> > * About to connect() to quickstarts-edewit.rhcloud.com port 80 (#0)
> > * Trying 50.16.176.239...
> > * Connected to quickstarts-edewit.rhcloud.com (50.16.176.239) port 80 (#0)
> > > PUT /rest/contacts/7 HTTP/1.1
> > > User-Agent: curl/7.30.0
> > > Host: quickstarts-edewit.rhcloud.com
> > > Cookie:
> > > JSESSIONID=zugucP2LNHLbCNNOwBrD3mx6.quickstarts-edewit.rhcloud.com
> > > Accept: application/json Content-type: application/json
> > > Content-Length: 120
> > >
> > * upload completely sent off: 120 out of 120 bytes
> > < HTTP/1.1 500 Internal Server Error
> > < Date: Mon, 02 Jun 2014 12:04:59 GMT
> > < Content-Type: text/html;charset=ISO-8859-1
> > < Content-Length: 80
> > < Connection: close
> > <
> > * Closing connection 0
> >
<html><head><title>Error</title></head><body>Internal
Server
> > Error</body></html>
> >
> >
> > On Mon, Jun 2, 2014 at 4:39 AM, Sebastien Blanc <scm.blanc(a)gmail.com>
> > wrote: What is the issue you are having and what are you trying to do
> > (issue just with the update?) ?
> >
> >
> >
> > On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me> wrote:
> > Someone know that I am doing wrong?
> >
> > Login
> >
> > curl -v -b cookies.txt -c cookies.txt \
> > -H "Accept: application/json" \
> > -H "Content-type: application/json" \
> > -u "myuser:mypass" \
> > -X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
> > Update Contact
> >
> > curl -v -b cookies.txt -c cookies.txt \
> > -H "Accept: application/json" \
> > -H "Content-type: application/json" \
> > -X PUT \
> > -d
> >
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
> > "birthDate":"2001-03-24"}' \
> > http://quickstarts-edewit.rhcloud.com/rest/contacts/7 — Passos
> >
> >
> >
> >
> > On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
> > wrote: Since we changed the use case for the Push part (now we
> > broadcast) , passing a alias to UPS is not relevant anymore. For the
> > login it's indeed "loginName" to be passed in the auth header
along with
> > the password.
> >
> >
> >
> > On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
> > To register I send "userName" and the login response
"loginName"?
> > -- Passos
> >
> >
> >
> > On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
> > wrote: Sure !
> > This is just a version to ease the client development.
> > I will ask PL team and Joshua their plans around HSTS and HTTPS.
> > In the mean time we can track all of this with
> > https://issues.jboss.org/browse/AGPUSH-596
> >
> > Thx for the comment !
> > Sebi
> >
> >
> > On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org>
> > wrote: If your idea is to be secure, please make sure to use HTTPS and
> > enforce users to be redirected. We did it in the past with HSTS on AG
> > Security, might not be hard to copy & paste.
> >
> > Sebastien Blanc wrote:
> > > And because I love you, I deployed on OpenShift a version of this
> > > secured backend to ease the development of the clients !
> > >
> > > If you browse to http://contacts-sblanc.rhcloud.com/ you will even see
> > > the mobile web client. This deployed version contains also the Push
> > > Message endpoint.
> >
> > _______________________________________________
> > 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
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
9:43 a.m.
On 5 Jun 2014, at 15:41, Karel Piwko <kpiwko(a)redhat.com> wrote:
Correct JIRA for WFK would be:
https://issues.jboss.org/browse/JBWFK2
https://issues.jboss.org/browse/WFK2
However, I'd rather target upstream first:
https://issues.jboss.org/browse/JDF/component/12315845/
Karel
On Mon, 2 Jun 2014 11:05:45 -0300
Bruno Oliveira <bruno(a)abstractj.org> wrote:
> Would make sense to file a Jira to:
> https://issues.jboss.org/browse/JBWFK ?
>
> On 2014-06-02, Erik Jan de Wit wrote:
>> Seems to be a NullPointer:
>>
>> Caused by: java.lang.NullPointerException
>> at
>>
org.jboss.quickstarts.wfk.contacts.customer.ContactRESTService.updateContact(ContactRESTService.java:192)
>> [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> [rt.jar:1.7.0_55] at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> [rt.jar:1.7.0_55] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> [rt.jar:1.7.0_55] at java.lang.reflect.Method.invoke(Method.java:606)
>> [rt.jar:1.7.0_55] at
>>
org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
>> at
>>
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
>> at
>>
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:87)
>> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>>
org.apache.deltaspike.security.impl.extension.DefaultSecurityStrategy.execute(DefaultSecurityStrategy.java:61)
>> [deltaspike-security-module-impl-0.5.jar:0.5] at
>>
org.apache.deltaspike.security.impl.extension.SecurityInterceptor.filterDeniedInvocations(SecurityInterceptor.java:44)
>> [deltaspike-security-module-impl-0.5.jar:0.5] at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> [rt.jar:1.7.0_55] at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> [rt.jar:1.7.0_55] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> [rt.jar:1.7.0_55] at java.lang.reflect.Method.invoke(Method.java:606)
>> [rt.jar:1.7.0_55] at
>>
org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>>
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:103)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>>
org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:81)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>> org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:105)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>>
org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:77)
>> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>>
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:68)
>> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>>
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80)
>> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>>
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
>> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>>
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
>> at
>>
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
>> [wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1] at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
>> [wildfly-jpa-8.1.0.CR1.jar:8.1.0.CR1] at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
>> at
>>
org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:46)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at
>>
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
>> [wildfly-weld-8.1.0.CR1.jar:8.1.0.CR1] at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
>> [wildfly-ee-8.1.0.CR1.jar:8.1.0.CR1] at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
>> at
>>
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
>> at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>>
org.jboss.as.ejb3.component.interceptors.NonPooledEJBComponentInstanceAssociatingInterceptor.processInvocation(NonPooledEJBComponentInstanceAssociatingInterceptor.java:59)
>> [wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1] at
>> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
>> at
>> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273)
>> [wildfly-ejb3-8.1.0.CR1.jar:8.1.0.CR1] ... 81 more
>>
>> And that means the contact Id is null:
>>
>>
https://github.com/edewit/jboss-wfk-quickstarts/blob/push/contacts-mobile...
>>
>> So your data should also contain the same id as the id in the url
>>
>> -d
>>
'{"firstName":"Davey","lastName":"Jones","phoneNumber":"1(212)555-3333","email":"davey.jones@locker.com","birthDate":"1996-08-07","id”:"7"}'
>>
>>
>> On 2 Jun,2014, at 14:10 , Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
>>
>>> Your request look good but without having the application server log
it's
>>> hard to tell what is going on exactly. You could ask Erik to check the
>>> log or deploy the backend locally.
>>>
>>>
>>>
>>> On Mon, Jun 2, 2014 at 2:07 PM, Daniel Passos <daniel(a)passos.me>
wrote:
>>> Sorry,
>>>
>>> Yes, I am try updating a contact and the server responded w/ status code
>>> 500
>>>
>>>
>>> * Adding handle: conn: 0x7ff159003000
>>> * Adding handle: send: 0
>>> * Adding handle: recv: 0
>>> * Curl_addHandleToPipeline: length: 1
>>> * - Conn 0 (0x7ff159003000) send_pipe: 1, recv_pipe: 0
>>> * About to connect() to quickstarts-edewit.rhcloud.com port 80 (#0)
>>> * Trying 50.16.176.239...
>>> * Connected to quickstarts-edewit.rhcloud.com (50.16.176.239) port 80 (#0)
>>>> PUT /rest/contacts/7 HTTP/1.1
>>>> User-Agent: curl/7.30.0
>>>> Host: quickstarts-edewit.rhcloud.com
>>>> Cookie:
>>>> JSESSIONID=zugucP2LNHLbCNNOwBrD3mx6.quickstarts-edewit.rhcloud.com
>>>> Accept: application/json Content-type: application/json
>>>> Content-Length: 120
>>>>
>>> * upload completely sent off: 120 out of 120 bytes
>>> < HTTP/1.1 500 Internal Server Error
>>> < Date: Mon, 02 Jun 2014 12:04:59 GMT
>>> < Content-Type: text/html;charset=ISO-8859-1
>>> < Content-Length: 80
>>> < Connection: close
>>> <
>>> * Closing connection 0
>>>
<html><head><title>Error</title></head><body>Internal
Server
>>> Error</body></html>
>>>
>>>
>>> On Mon, Jun 2, 2014 at 4:39 AM, Sebastien Blanc <scm.blanc(a)gmail.com>
>>> wrote: What is the issue you are having and what are you trying to do
>>> (issue just with the update?) ?
>>>
>>>
>>>
>>> On Fri, May 30, 2014 at 8:48 PM, Daniel Passos <daniel(a)passos.me>
wrote:
>>> Someone know that I am doing wrong?
>>>
>>> Login
>>>
>>> curl -v -b cookies.txt -c cookies.txt \
>>> -H "Accept: application/json" \
>>> -H "Content-type: application/json" \
>>> -u "myuser:mypass" \
>>> -X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info
>>> Update Contact
>>>
>>> curl -v -b cookies.txt -c cookies.txt \
>>> -H "Accept: application/json" \
>>> -H "Content-type: application/json" \
>>> -X PUT \
>>> -d
>>>
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
>>> "birthDate":"2001-03-24"}' \
>>> http://quickstarts-edewit.rhcloud.com/rest/contacts/7 — Passos
>>>
>>>
>>>
>>>
>>> On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
>>> wrote: Since we changed the use case for the Push part (now we
>>> broadcast) , passing a alias to UPS is not relevant anymore. For the
>>> login it's indeed "loginName" to be passed in the auth header
along with
>>> the password.
>>>
>>>
>>>
>>> On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me>
wrote:
>>> To register I send "userName" and the login response
"loginName"?
>>> -- Passos
>>>
>>>
>>>
>>> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
>>> wrote: Sure !
>>> This is just a version to ease the client development.
>>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>>> In the mean time we can track all of this with
>>> https://issues.jboss.org/browse/AGPUSH-596
>>>
>>> Thx for the comment !
>>> Sebi
>>>
>>>
>>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org>
>>> wrote: If your idea is to be secure, please make sure to use HTTPS and
>>> enforce users to be redirected. We did it in the past with HSTS on AG
>>> Security, might not be hard to copy & paste.
>>>
>>> Sebastien Blanc wrote:
>>>> And because I love you, I deployed on OpenShift a version of this
>>>> secured backend to ease the development of the clients !
>>>>
>>>> If you browse to http://contacts-sblanc.rhcloud.com/ you will even see
>>>> the mobile web client. This deployed version contains also the Push
>>>> Message endpoint.
>>>
>>> _______________________________________________
>>> 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
>>
>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> _______________________________________________
> 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
3861
days inactive
3910
days old
12 comments
6 participants
participants (6)
-
Bruno Oliveira -
Daniel Passos -
Erik Jan de Wit -
Karel Piwko -
Pete Muir -
Sebastien Blanc