JAX-RS : initial WADL support
|
View:
New views
10 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
 |
RE: JAX-RS : initial WADL support
by Sadhana Jain
::
Rate this Message:
Hi Sergey,
Thanks for the WADL generation support in CXF JAX-RS implementation. I tried it and it looks good. I was wondering why the WADL is generated within <String>...</String> elements? Is there a way to not get these and get only the valid WADL? Thanks, Sadhana Sadhana Jain Sr. Software Engineer Rovi Corporation 795 Folsom St, Suite 200 San Francisco, CA 94107 Direct: 415.247.5023 | Mobile: 925.212.6495 sadhana.jain@... rovicorp.com Rovi. The new name for Macrovision. -----Original Message----- From: Sergey Beryozkin [mailto:sberyozk@...] Sent: Wednesday, July 08, 2009 9:23 AM To: users@... Subject: JAX-RS : initial WADL support Hi CXF JAX-RS now supports the auto-generation of WADL for JAX-RS endpoints (trunk, 2.2.3-SNAPSHOT). The whole tree/graph will be described in a generated instance. Note that JAX-RS subresources are supposed to be late-resolved, so I'd recommend using annotated interfaces for subresources and an enableStaticResolution=true property. At the moment I've decided to stay away from from supporting WADl for those subresources whicg are resolved late - will be very easy to support if really needed. Schemas will be generated for JAXB-annotated types. I'd appreciate if users could experiment a bit with the latest SNAPSHOTS and provide the feedback and help us to improve whatever we have in time for 2.2.3. I don't think WADL support in 2.2.3 will be perfect but we'll try our best to polish it in 2.3. I also do believe there's a practical advantage in us eventually supporting WSDL2 in some form (meaning the typed server code generation at least which is something we can't do with WADL, as well as supporting those users who are working with proxy-based client api) but I can't confirm at this stage when exactly we will do WSDL2. WADL instances for RESTful endpoints are available from {base endpoint address}/services, in addition to SOAP endpoints if any. Note that you can override the location at which listings are provided (in case you'd like '/services' be available to your resources) using 'service-list-path' parameter, ex : 'service-list-path' = '/listings' So please give it a try and let us know what you think thanks, Sergey |
|
|
Re: JAX-RS : initial WADL support
by Gabo Manuel
::
Rate this Message:
Hi Sergey,
A few things: 1. I have both XmlRootElement and XmlType annotations in my object. I added namespace to both of them. By 2.2.4, I'll remove them both. Currently still using the 2.2.3 release. 2. The wadl generated has xmlns:tns and xmlns:prefix1 defined as "http://domains.some", with tns being used in the grammars, while prefix1 is being used in the resources. Although, it would still evaluate the same, I think it would be better to remove the duplicate and just use the same namespace definition for both grammar and resource, right? Thanks Gabo Sergey Beryozkin wrote: > Hi Gabo > > I've just got it fixed. WADLgenerator will now introspect package-info.java > in cases when @XmlRootElement has only a local name set and if the namespace > is available then the resulting WADL will correctly link to a generated > schema element.... > > thanks for raising this issue > Sergey > > > Sergey Beryozkin wrote: > >> Hi Gabo >> >> MyObject has @XmlRootElement with only a local name specified. Does >> package-info.java has a namespace specified too, in addition to the local >> name ? >> >> cheers, Sergey >> >> >> Gabo Manuel wrote: >> >>> Hi Sergey, >>> >>> I am a bit confused. How do I supply the namespace needed? I thought the >>> package-info.java would be enough. >>> >>> Yes, for now I would be limiting the consume to just text/xml. The >>> initial intent was to take advantage of CXF's handling between xml and >>> json. But for now, we would be sticking to text/xml. >>> >>> Gabo >>> >>> Sergey Beryozkin wrote: >>> >>>> Hi Gabo >>>> >>>> thanks... >>>> The reason you only see the '<representation/>' for my MyObject is that >>>> there's no namespace available , so even though the <grammars/> section >>>> has >>>> the schema embedded there's no way to link to it from the >>>> <representation/>. >>>> May be I should have some XML comment generated which will advise to >>>> check >>>> the schema (with no namespace) ? >>>> >>>> You might also want to update Consumes("*/*") to require a more specific >>>> media type. >>>> >>>> >>>> >>>>> I haven't tried it lately without the providers, but are primitives now >>>>> supported out of the box? >>>>> >>>>> >>>> They are but only for text/plain. I'll add a task to wrap them in some >>>> tag >>>> like <response> for xml media types >>>> >>>> >>>> >>>>> Also, is there somewhere to look to be able to use the tool that >>>>> creates >>>>> an http-centric client-code from the wadl? >>>>> >>>>> >>>> No, I haven't started working on the code gen tool yet....But it's on >>>> the >>>> map >>>> >>>> cheers, Sergey >>>> >>>> >>>> >>>> Gabo Manuel wrote: >>>> >>>> >>>>> Hi Sergey, >>>>> >>>>> Sorry for the late response. I may have misrepresented the method, it >>>>> should be as follows: >>>>> >>>>> @WebService(name="MyObjectService") >>>>> @SOAPBinding(use=Use.LITERAL, style=Style.RPC) >>>>> @Consumes("*/*") >>>>> @Produces("text/xml") >>>>> @Path("/MyObjects") >>>>> public interface MyObjectService{ >>>>> @GET >>>>> @Path("/") >>>>> @WebMethod >>>>> @WebResult(name="myObjectInstance") >>>>> public MyObject getMyObject( >>>>> @QueryParam("uniqueIDField") >>>>> @WebParam(name="uniqueIDField") >>>>> long uniqueIDField) >>>>> ; >>>>> >>>>> @PUT >>>>> @Path("/") >>>>> @WebMethod >>>>> @WebResult(name="uniqueIDField") >>>>> public long insertMyObject( >>>>> @WebParam(name="myObjectInstance") >>>>> MyObject myObjectInstance, >>>>> @QueryParam("reason") >>>>> @WebParam(name="reason") >>>>> String reason >>>>> ) >>>>> ; >>>>> } >>>>> >>>>> @WebService(endpointInterface="some.domain.MyObjectService", >>>>> serviceName="MyObjectService", portName="MyObjectServicePort") >>>>> public class MyObjectServiceImpl implements MyObjectService{ >>>>> public MyObject getMyObject(long uniqueIDField) throws >>>>> SolegyContingencyException{ >>>>> return new MyObject(); >>>>> } >>>>> public long insertMyObject(MyObject myObjectInstance, String >>>>> reason) >>>>> throws SolegyContingencyException{ >>>>> return 1; >>>>> } >>>>> } >>>>> >>>>> @XmlType(name="MyObject") >>>>> @XmlAccessorType(XmlAccessType.PROPERTY) >>>>> @XmlRootElement(name="MyObject") >>>>> public class MyObject { >>>>> private long uniqueIDField; >>>>> @GET >>>>> @Path("/uniqueIDField") >>>>> public long getUniqueIDField() { >>>>> return uniqueIDField; >>>>> } >>>>> public void setUniqueIDField(long uniqueIDField) { >>>>> this.uniqueIDField = uniqueIDField; >>>>> } >>>>> } >>>>> >>>>> The wadl section i get is something as follows: >>>>> >>>>> <method name="GET"> >>>>> <request> >>>>> >>>>> </request> >>>>> <response> >>>>> <representation mediaType="text/xml"/> >>>>> </response> >>>>> </method> >>>>> <method name="PUT"> >>>>> <request> >>>>> <representation/> >>>>> >>>>> </request> >>>>> <response> >>>>> <!-- Primitive type : xs:long --><representation >>>>> mediaType="text/xml"/> >>>>> </response> >>>>> </method> >>>>> >>>>> And yes, I did specify text/xml. I also have providers included to wrap >>>>> the response in tags. I had to add the providers because at the time >>>>> (2.0), primitives were not supported. I haven't tried it lately without >>>>> the providers, but are primitives now supported out of the box? >>>>> >>>>> Also, is there somewhere to look to be able to use the tool that >>>>> creates >>>>> an http-centric client-code from the wadl? >>>>> >>>>> Thanks! >>>>> >>>>> Gabo. >>>>> >>>>> Sergey Beryozkin wrote: >>>>> >>>>> >>>>>> Hi Gabo >>>>>> >>>>>> It is an 'Object' so a WSDL generator has no idea what else to say, >>>>>> apart >>>>>> from <representation/>. If you add "Consumes' with some values then >>>>>> you'll >>>>>> get a bit more specific tag... >>>>>> >>>>>> >>>>>> However, there appears to be a bug : >>>>>> >>>>>> <response><!-- Primitive type : xs:long >>>>>> --><representation >>>>>> mediaType="text/xml"/></response></method></resource> >>>>>> >>>>>> or do you have Produces('text/xml') on the class itself ? Can you >>>>>> please >>>>>> send me a class sample so that I can fix it ? >>>>>> >>>>>> cheers, Sergey >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> No virus found in this incoming message. >>>> Checked by AVG - www.avg.com >>>> Version: 8.5.409 / Virus Database: 270.13.62/2315 - Release Date: >>>> 08/20/09 06:05:00 >>>> >>>> >>>> >>> >> > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.409 / Virus Database: 270.13.65/2323 - Release Date: 08/24/09 06:05:00 > > |
|
|
Re: JAX-RS : initial WADL support
by Gabo Manuel
::
Rate this Message:
Hi Sadhana,
Any chance that an out interceptor is enclosing the result? I think the generation of wadl is still treated as a regular transaction so all in and out interceptor chains apply. Gabo Sadhana Jain wrote: > Hi Sergey, > > Thanks for the WADL generation support in CXF JAX-RS implementation. > I tried it and it looks good. I was wondering why the WADL is generated within <String>...</String> elements? Is there a way to not get these and get only the valid WADL? > > Thanks, > Sadhana > > Sadhana Jain > Sr. Software Engineer > > > Rovi Corporation > 795 Folsom St, Suite 200 > San Francisco, CA 94107 > Direct: 415.247.5023 | Mobile: 925.212.6495 > sadhana.jain@... > rovicorp.com > > > Rovi. The new name for Macrovision. > > > -----Original Message----- > From: Sergey Beryozkin [mailto:sberyozk@...] > Sent: Wednesday, July 08, 2009 9:23 AM > To: users@... > Subject: JAX-RS : initial WADL support > > Hi > > CXF JAX-RS now supports the auto-generation of WADL for JAX-RS endpoints (trunk, 2.2.3-SNAPSHOT). > The whole tree/graph will be described in a generated instance. Note that JAX-RS subresources are supposed to be late-resolved, so I'd recommend using annotated interfaces for subresources and an enableStaticResolution=true property. At the moment I've decided to stay away from from supporting WADl for those subresources whicg are resolved late - will be very easy to support if really needed. Schemas will be generated for JAXB-annotated types. > > I'd appreciate if users could experiment a bit with the latest SNAPSHOTS and provide the feedback and help us to improve whatever we have in time for 2.2.3. I don't think WADL support in 2.2.3 will be perfect but we'll try our best to polish it in 2.3. > I also do believe there's a practical advantage in us eventually supporting WSDL2 in some form (meaning the typed server code generation at least which is something we can't do with WADL, as well as supporting those users who are working with proxy-based client api) but I can't confirm at this stage when exactly we will do WSDL2. > > WADL instances for RESTful endpoints are available from {base endpoint address}/services, in addition to SOAP endpoints if any. > Note that you can override the location at which listings are provided (in case you'd like '/services' be available to your resources) using 'service-list-path' parameter, ex : > 'service-list-path' = '/listings' > > So please give it a try and let us know what you think > > thanks, Sergey > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.409 / Virus Database: 270.13.66/2325 - Release Date: 08/25/09 06:08:00 > > |
|
|
Re: JAX-RS : initial WADL support
by Sergey Beryozkin
::
Rate this Message:
Hi
I missed this query, sorry. Just yesterday, I saw a generated WADL embedded in <String/>, in a specific DOSGi case (when no OSGI HttpService was used). Otherwise it's properly presented as XML.... Sadhana, can you help me please in reproducing this issue ? Are you using (D)OSGI by any chance ? If not then how exactly your application has been set up ? thanks, Sergey
|
|
|
Re: JAX-RS : initial WADL support
by Sergey Beryozkin
::
Rate this Message:
Hi Gabo
Agreed about 1. About 2 : the schema is generated by JAXB so WADLGenerator is not controlling the prefixes on the schema itself. 'tns' is typically used by convention. I can't use 'tns' on the top-level wadl:application though because it won't work in cases when multiple schemas have been generated, and it will be a bit confusing in cases when WADL instances are not using default namespaces, because 'tns' would actually link to some other non-WADL namespace. WADL processors should have no problems in processing 'prefix1'/prefix2', etc, 'tns' won't be even visible to them.... cheers, Sergey
|
|
|
Re: JAX-RS : initial WADL support
by Gabo Manuel
::
Rate this Message:
Hi Sergey,
Just want to confirm. It would not be a problem even if they use different prefix as long as it evaluates the same, ryt? Gabo Sergey Beryozkin wrote: > Hi Gabo > > Agreed about 1. > About 2 : the schema is generated by JAXB so WADLGenerator is not > controlling the prefixes on the schema itself. 'tns' is typically used by > convention. I can't use 'tns' on the top-level wadl:application though > because it won't work in cases when multiple schemas have been generated, > and it will be a bit confusing in cases when WADL instances are not using > default namespaces, because 'tns' would actually link to some other non-WADL > namespace. > WADL processors should have no problems in processing 'prefix1'/prefix2', > etc, 'tns' won't be even visible to them.... > > cheers, Sergey > > > Gabo Manuel wrote: > >> Hi Sergey, >> >> A few things: >> >> 1. I have both XmlRootElement and XmlType annotations in my object. I >> added namespace to both of them. By 2.2.4, I'll remove them both. >> Currently still using the 2.2.3 release. >> >> 2. The wadl generated has xmlns:tns and xmlns:prefix1 defined as >> "http://domains.some", with tns being used in the grammars, while >> prefix1 is being used in the resources. Although, it would still >> evaluate the same, I think it would be better to remove the duplicate >> and just use the same namespace definition for both grammar and >> resource, right? >> >> Thanks >> >> Gabo >> >> Sergey Beryozkin wrote: >> >>> Hi Gabo >>> >>> I've just got it fixed. WADLgenerator will now introspect >>> package-info.java >>> in cases when @XmlRootElement has only a local name set and if the >>> namespace >>> is available then the resulting WADL will correctly link to a generated >>> schema element.... >>> >>> thanks for raising this issue >>> Sergey >>> >>> >>> Sergey Beryozkin wrote: >>> >>> >>>> Hi Gabo >>>> >>>> MyObject has @XmlRootElement with only a local name specified. Does >>>> package-info.java has a namespace specified too, in addition to the >>>> local >>>> name ? >>>> >>>> cheers, Sergey >>>> >>>> >>>> Gabo Manuel wrote: >>>> >>>> >>>>> Hi Sergey, >>>>> >>>>> I am a bit confused. How do I supply the namespace needed? I thought >>>>> the >>>>> package-info.java would be enough. >>>>> >>>>> Yes, for now I would be limiting the consume to just text/xml. The >>>>> initial intent was to take advantage of CXF's handling between xml and >>>>> json. But for now, we would be sticking to text/xml. >>>>> >>>>> Gabo >>>>> >>>>> Sergey Beryozkin wrote: >>>>> >>>>> >>>>>> Hi Gabo >>>>>> >>>>>> thanks... >>>>>> The reason you only see the '<representation/>' for my MyObject is >>>>>> that >>>>>> there's no namespace available , so even though the <grammars/> >>>>>> section >>>>>> has >>>>>> the schema embedded there's no way to link to it from the >>>>>> <representation/>. >>>>>> May be I should have some XML comment generated which will advise to >>>>>> check >>>>>> the schema (with no namespace) ? >>>>>> >>>>>> You might also want to update Consumes("*/*") to require a more >>>>>> specific >>>>>> media type. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> I haven't tried it lately without the providers, but are primitives >>>>>>> now >>>>>>> supported out of the box? >>>>>>> >>>>>>> >>>>>>> >>>>>> They are but only for text/plain. I'll add a task to wrap them in some >>>>>> tag >>>>>> like <response> for xml media types >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Also, is there somewhere to look to be able to use the tool that >>>>>>> creates >>>>>>> an http-centric client-code from the wadl? >>>>>>> >>>>>>> >>>>>>> >>>>>> No, I haven't started working on the code gen tool yet....But it's on >>>>>> the >>>>>> map >>>>>> >>>>>> cheers, Sergey >>>>>> >>>>>> >>>>>> >>>>>> Gabo Manuel wrote: >>>>>> >>>>>> >>>>>> >>>>>>> Hi Sergey, >>>>>>> >>>>>>> Sorry for the late response. I may have misrepresented the method, it >>>>>>> should be as follows: >>>>>>> >>>>>>> @WebService(name="MyObjectService") >>>>>>> @SOAPBinding(use=Use.LITERAL, style=Style.RPC) >>>>>>> @Consumes("*/*") >>>>>>> @Produces("text/xml") >>>>>>> @Path("/MyObjects") >>>>>>> public interface MyObjectService{ >>>>>>> @GET >>>>>>> @Path("/") >>>>>>> @WebMethod >>>>>>> @WebResult(name="myObjectInstance") >>>>>>> public MyObject getMyObject( >>>>>>> @QueryParam("uniqueIDField") >>>>>>> @WebParam(name="uniqueIDField") >>>>>>> long uniqueIDField) >>>>>>> ; >>>>>>> >>>>>>> @PUT >>>>>>> @Path("/") >>>>>>> @WebMethod >>>>>>> @WebResult(name="uniqueIDField") >>>>>>> public long insertMyObject( >>>>>>> @WebParam(name="myObjectInstance") >>>>>>> MyObject myObjectInstance, >>>>>>> @QueryParam("reason") >>>>>>> @WebParam(name="reason") >>>>>>> String reason >>>>>>> ) >>>>>>> ; >>>>>>> } >>>>>>> >>>>>>> @WebService(endpointInterface="some.domain.MyObjectService", >>>>>>> serviceName="MyObjectService", portName="MyObjectServicePort") >>>>>>> public class MyObjectServiceImpl implements MyObjectService{ >>>>>>> public MyObject getMyObject(long uniqueIDField) throws >>>>>>> SolegyContingencyException{ >>>>>>> return new MyObject(); >>>>>>> } >>>>>>> public long insertMyObject(MyObject myObjectInstance, String >>>>>>> reason) >>>>>>> throws SolegyContingencyException{ >>>>>>> return 1; >>>>>>> } >>>>>>> } >>>>>>> >>>>>>> @XmlType(name="MyObject") >>>>>>> @XmlAccessorType(XmlAccessType.PROPERTY) >>>>>>> @XmlRootElement(name="MyObject") >>>>>>> public class MyObject { >>>>>>> private long uniqueIDField; >>>>>>> @GET >>>>>>> @Path("/uniqueIDField") >>>>>>> public long getUniqueIDField() { >>>>>>> return uniqueIDField; >>>>>>> } >>>>>>> public void setUniqueIDField(long uniqueIDField) { >>>>>>> this.uniqueIDField = uniqueIDField; >>>>>>> } >>>>>>> } >>>>>>> >>>>>>> The wadl section i get is something as follows: >>>>>>> >>>>>>> <method name="GET"> >>>>>>> <request> >>>>>>> >>>>>>> </request> >>>>>>> <response> >>>>>>> <representation mediaType="text/xml"/> >>>>>>> </response> >>>>>>> </method> >>>>>>> <method name="PUT"> >>>>>>> <request> >>>>>>> <representation/> >>>>>>> >>>>>>> </request> >>>>>>> <response> >>>>>>> <!-- Primitive type : xs:long --><representation >>>>>>> mediaType="text/xml"/> >>>>>>> </response> >>>>>>> </method> >>>>>>> >>>>>>> And yes, I did specify text/xml. I also have providers included to >>>>>>> wrap >>>>>>> the response in tags. I had to add the providers because at the time >>>>>>> (2.0), primitives were not supported. I haven't tried it lately >>>>>>> without >>>>>>> the providers, but are primitives now supported out of the box? >>>>>>> >>>>>>> Also, is there somewhere to look to be able to use the tool that >>>>>>> creates >>>>>>> an http-centric client-code from the wadl? >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> Gabo. >>>>>>> >>>>>>> Sergey Beryozkin wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Hi Gabo >>>>>>>> >>>>>>>> It is an 'Object' so a WSDL generator has no idea what else to say, >>>>>>>> apart >>>>>>>> from <representation/>. If you add "Consumes' with some values then >>>>>>>> you'll >>>>>>>> get a bit more specific tag... >>>>>>>> >>>>>>>> >>>>>>>> However, there appears to be a bug : >>>>>>>> >>>>>>>> <response><!-- Primitive type : xs:long >>>>>>>> --><representation >>>>>>>> mediaType="text/xml"/></response></method></resource> >>>>>>>> >>>>>>>> or do you have Produces('text/xml') on the class itself ? Can you >>>>>>>> please >>>>>>>> send me a class sample so that I can fix it ? >>>>>>>> >>>>>>>> cheers, Sergey >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> >>>>>> >>>>>> No virus found in this incoming message. >>>>>> Checked by AVG - www.avg.com >>>>>> Version: 8.5.409 / Virus Database: 270.13.62/2315 - Release Date: >>>>>> 08/20/09 06:05:00 >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> No virus found in this incoming message. >>> Checked by AVG - www.avg.com >>> Version: 8.5.409 / Virus Database: 270.13.65/2323 - Release Date: >>> 08/24/09 06:05:00 >>> >>> >>> >> > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.339 / Virus Database: 270.13.67/2326 - Release Date: 08/25/09 18:07:00 > > |
|
|
RE: JAX-RS : initial WADL support
by Sadhana Jain
::
Rate this Message:
Hi Sergey/Gabo, Thanks for the replies. Our application is using our own MessageBodyWriter (that uses XStream provider instead of JAXB) and it seems that is putting the <String> around the WADL xml. I will try to fix this in our MessageBodyWriter and hopefully will solve the issue. Your replies were helpful in debugging the issue so thanks a lot again. -Sadhana -----Original Message----- From: Sergey Beryozkin [mailto:sergey.beryozkin@...] Sent: Wednesday, August 26, 2009 3:38 AM To: users@... Subject: Re: JAX-RS : initial WADL support Hi I missed this query, sorry. Just yesterday, I saw a generated WADL embedded in <String/>, in a specific DOSGi case (when no OSGI HttpService was used). Otherwise it's properly presented as XML.... Sadhana, can you help me please in reproducing this issue ? Are you using (D)OSGI by any chance ? If not then how exactly your application has been set up ? thanks, Sergey Gabo Manuel wrote: > > Hi Sadhana, > > Any chance that an out interceptor is enclosing the result? I think the > generation of wadl is still treated as a regular transaction so all in > and out interceptor chains apply. > > Gabo > > Sadhana Jain wrote: >> Hi Sergey, >> >> Thanks for the WADL generation support in CXF JAX-RS implementation. >> I tried it and it looks good. I was wondering why the WADL is generated >> within <String>...</String> elements? Is there a way to not get these and >> get only the valid WADL? >> >> Thanks, >> Sadhana >> >> Sadhana Jain >> Sr. Software Engineer >> >> >> Rovi Corporation >> 795 Folsom St, Suite 200 >> San Francisco, CA 94107 >> Direct: 415.247.5023 | Mobile: 925.212.6495 >> sadhana.jain@... >> rovicorp.com >> >> >> Rovi. The new name for Macrovision. >> >> >> -----Original Message----- >> From: Sergey Beryozkin [mailto:sberyozk@...] >> Sent: Wednesday, July 08, 2009 9:23 AM >> To: users@... >> Subject: JAX-RS : initial WADL support >> >> Hi >> >> CXF JAX-RS now supports the auto-generation of WADL for JAX-RS endpoints >> (trunk, 2.2.3-SNAPSHOT). >> The whole tree/graph will be described in a generated instance. Note that >> JAX-RS subresources are supposed to be late-resolved, so I'd recommend >> using annotated interfaces for subresources and an >> enableStaticResolution=true property. At the moment I've decided to stay >> away from from supporting WADl for those subresources whicg are resolved >> late - will be very easy to support if really needed. Schemas will be >> generated for JAXB-annotated types. >> >> I'd appreciate if users could experiment a bit with the latest SNAPSHOTS >> and provide the feedback and help us to improve whatever we have in time >> for 2.2.3. I don't think WADL support in 2.2.3 will be perfect but we'll >> try our best to polish it in 2.3. >> I also do believe there's a practical advantage in us eventually >> supporting WSDL2 in some form (meaning the typed server code generation >> at least which is something we can't do with WADL, as well as supporting >> those users who are working with proxy-based client api) but I can't >> confirm at this stage when exactly we will do WSDL2. >> >> WADL instances for RESTful endpoints are available from {base endpoint >> address}/services, in addition to SOAP endpoints if any. >> Note that you can override the location at which listings are provided >> (in case you'd like '/services' be available to your resources) using >> 'service-list-path' parameter, ex : >> 'service-list-path' = '/listings' >> >> So please give it a try and let us know what you think >> >> thanks, Sergey >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.409 / Virus Database: 270.13.66/2325 - Release Date: >> 08/25/09 06:08:00 >> >> > > -- View this message in context: http://www.nabble.com/JAX-RS-%3A-initial-WADL-support-tp24394736p25150356.html Sent from the cxf-user mailing list archive at Nabble.com. |
|
|
RE: JAX-RS : initial WADL support
by Sergey Beryozkin
::
Rate this Message:
Hi Sadhana
Ok, it's actually a bug in CXF then. Custom MessageBodyWriter should not be invoked after WADL has been generated - I'll fix it thanks, Sergey
|
|
|
Re: JAX-RS : initial WADL support
by Sergey Beryozkin
::
Rate this Message:
Hi Gabo -
should not be, we don't have a processor yet but I'm presuming that a schemas cache will be created after a <grammars/> section has been processed, with schemas keyed by namespaces, so eventually other prefixes like 'prefix1' will be bound to corresponding schemas. cheers, Sergey
|
|
|
RE: JAX-RS : initial WADL support
by Sergey Beryozkin
::
Rate this Message:
Hi Sadhana
I've got it fixed. I've also introduced a property called 'ignore.response.writers' (JAXRSUtils.IGNORE_RESPONSE_WRITERS) which custom RequestHandler or ResponseHandler filters may want to use to avoid their Response entities being handled by writers and being directly written to the stream... Another option is to write to HttpServletResponse but I thought having this property would simplify things a bit when needed cheers, Sergey
|
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
