True. I probably messed up the copy-paste from the original source since I was updating it while reading this tutorial (the annotations for ignoring certain elements when serializing JSon are not mentioned here), and ended up deleting the original @JsonIgnoreProperties("show").
I know it's a complex project and hard to put all details in the tutorial, but this one is hardly debuggable (AS 7 throws a ClassNotFoundException and meaningless serialization output) and it should be highlighted somewhere for newbies like me. But yeah, this is a showcase project, maybe I'm asking a lot :)
By the way, isn't there a standardized solution that will not involve library-specific annotations? Because this seriously cripples the re-usability of the model. What if XML was the serialization target? What if I have methods that will also iterate through an Entity's members and call them recursively?
I think I will try and develop my custom authentication method/interceptor since I kinda need to assess feasibility sooner than later with this whole framework (I'm composing a spec for a possible client). I have updated my dependencies to use RESTEasy 3 and am currently setting up a user/pass JBoss security domain, so I can benefit from its OAuth2 implementations (apparently production-safe unlike RESTEasy's OAuth 1 take) and eventually reuse the domain for non-rest authentication . I might be reinventing the rock, but I guess it's fine so I understand the trade-offs of custom auth, and benefit from the bleeding edge authentication technologies such as SSO.
Settings
TBorba
True. I probably messed up the copy-paste from the original source since I was updating it while reading this tutorial (the annotations for ignoring certain elements when serializing JSon are not mentioned here), and ended up deleting the original @JsonIgnoreProperties("show").
I know it's a complex project and hard to put all details in the tutorial, but this one is hardly debuggable (AS 7 throws a ClassNotFoundException and meaningless serialization output) and it should be highlighted somewhere for newbies like me. But yeah, this is a showcase project, maybe I'm asking a lot :)
By the way, isn't there a standardized solution that will not involve library-specific annotations? Because this seriously cripples the re-usability of the model. What if XML was the serialization target? What if I have methods that will also iterate through an Entity's members and call them recursively?
I think I will try and develop my custom authentication method/interceptor since I kinda need to assess feasibility sooner than later with this whole framework (I'm composing a spec for a possible client). I have updated my dependencies to use RESTEasy 3 and am currently setting up a user/pass JBoss security domain, so I can benefit from its OAuth2 implementations (apparently production-safe unlike RESTEasy's OAuth 1 take) and eventually reuse the domain for non-rest authentication . I might be reinventing the rock, but I guess it's fine so I understand the trade-offs of custom auth, and benefit from the bleeding edge authentication technologies such as SSO.
5:25 a.m., Tuesday June 4
Moderate this comment by email
Email address: tborba@outsoft.pt | IP address: 84.91.197.21
Reply to this email with “Delete”, “Approve”, or “Spam”, or moderate from the Disqus moderation panel.