Broadleaf Commerce Discussion Forums

Currently I am trying to get JSON of Product object from ProductController.

I wrote the method that return Product object.



When I request to /productDetail url from jquery ajax, I got these exception.



So, How can I get Product JSON including custom product.

Just a guess, it looks like you have 2 getter methods defined for property taxable (as seen in the stacktrace):


Try to add @JsonIgnore annotation on one of the getters like this:
JsonIgnore annotation tells Jackson-JSON marshaller to skip that getter.

Right! In Product, there is two getter methods for protected Character taxable; attribute in SkuImpl class.



I cannot add @JsonIgnore annotation to related getter method. Because, SkuImpl class is braodleaf's class. So, how can I configure @JsonIgnore in controller by dynamically.

Hmm ... looking into the exception once more:

If you're trying to get json data out of the com.yoma.product.PremiumProductImpl class, you could try to override the method in that class (PremiumProductImpl):

Thanks for replys.

Here are the my domain models.



I just only extends Product for my custom PremiumProduct. public Boolean getTaxable() method is in Sku.
Sku and Product are associated. So I think, I cannot override the getTaxable() from my PremiumProduct. So
is there any way to configure the runtime in controller.

Thanks

Well yes, you have few options:

1. Implement your own serializer and set it to deserialize that filed using your own serializer
In your PremiumProductImpl annotate the Sku field with:

And implement the CustomSkuSerializer:


However i think it would be an overkill in this situation.
I think that one of the two methods should be made private or transient in SkuImpl in BLC...

Our entities as they are are not meant to be serialized via XML or JSON. Instead, we have a 'wrapper' paradigm that is available in our out-of-the-box REST services. The tutorials section (http://docs.broadleafcommerce.org/curre ... rials.html) will be most relevant to your use case.

Also, it appears as though you are duplicating functionality that we already provide. Take a look at our approach to REST instead as this is already available. If you need additional functionality, you can always extend our endpoints and add your own.

Thanks for the replies. If you can provide a detailed illustration of the end to end 'wrapper' paradigm, it would really help us. I believe the core entities should be serializable to XML/JSON. The link to your illustration on how to extend a Product "http://docs.broadleafcommerce.org/current/Next-Steps.html#wiki-extending-product" is broken.