--
You received this message because you are subscribed to the Google Groups "Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
@GET @ApiOperation(value = "Returns xxx", notes = "Notes", response = TestClassInEjb.class)
@Path("/test")
public void test(TestClass tc){}
TestClass being in web module, and TestClassEjb in EJB module.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggersocket+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
That's okay, but I actually asked about Java package of the model.Can you possibly produce a sample project to show the issue? I could probably find the solution based on that.
On Tue, Mar 11, 2014 at 2:19 PM, Jussi Juvonen <juss...@gmail.com> wrote:
For testing purposes I just created a model class to each module, for testing I did this (also tried wise-versa just in case):@GET @ApiOperation(value = "Returns xxx", notes = "Notes", response = TestClassInEjb.class)
@Path("/test")
public void test(TestClass tc){}
TestClass being in web module, and TestClassEjb in EJB module.
I use RestEasy (that bundles with Wildfly 8).-J
tiistai, 11. maaliskuuta 2014 12.41.37 UTC+2 Ron R kirjoitti:
When moving them between the projects, did you also move their packages?Also, which JAX-RS implementation do you use?
On Tue, Mar 11, 2014 at 12:31 PM, Jussi Juvonen <juss...@gmail.com> wrote:
Hi and thanks for the great project,Having an issue with @ApiModelProperty, when my models are defined within EJB module (My project setup is equivalent to https://github.com/wildfly/quickstart/tree/master/ejb-in-ear). If I move the model class into Web module, stuff defined in the annotation show up fine in the API definitions. Any idea how get the annotations working from model classes within EJB module? Or any good suggestions for a work around (excluding the moving of models to web module)?BR,-Jussi
--
You received this message because you are subscribed to the Google Groups "Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggersocket+unsubscri...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
"models":{"TestClass":{"id":"TestClass","description":"Model in web","properties":{"i":{"type":"integer","format":"int32","description":"testting"}}},"EjbModel":{"id":"EjbModel","properties":{"i":{"type":"integer","format":"int32"}}}}}
So from the EjbModel the descriptions are missing.
-J
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
If you put an ejb in the ejb module with a method that returns an instance of "model.EjbModel" and calls the method from the web module, you will produce a ClassCastException since the class of the returned object (from the dependency in the ear) and the expected class (from the "compile" dependency in the war) will come from different places.
I.e. with this solution you cant put any ejb:s in the ejb module...
Is it possible to reopen the bug on GitHub?
any updates? I am still facing the same problem.
--
You received this message because you are subscribed to the Google Groups "Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.