On Thu, May 22, 2008 at 9:03 AM, Simon Nash <[EMAIL PROTECTED]> wrote:
> ant elder wrote: > >> On Wed, May 21, 2008 at 7:47 PM, Simon Nash <[EMAIL PROTECTED]> wrote: >> >> Scott Kurz wrote: >>> >>> That 'generate-sdo' only generates the Java types from the schema types, >>>> right? >>>> >>>> It's the WSDL2Java which maps portType operations t**o Java methods and >>>> (last I checked) our >>>> W2J is the only tool which knows how to do this with an SDO databinding. >>>> >>>> Are the Java Service Endpoint Interfaces generated from WSDL portTypes >>>> >>> when using an SDO databinding different from what JAX-WS would produce >>> when using a JAXB databinding? Or are the differences confined to the >>> Java code that's generated for the XSD types referenced in the WSDL? >>> If possible, it would be good if we could use standard tools to generate >>> the Java SEIs, and SDO-specific tools for the XSD to Java static SDO >>> translation. >>> >>> >> One extra thing an SCA specific tool does need to do is to add the >> org.osoa.sca.Remotable annotation to the SEI. Maybe that could be done >> with >> a simple post processor? >> >> ...ant >> >> According to the SCA Java spec, @WebService implies @Remotable > (see chapter 9 of JavaCAA), so this may not be an issue. > > For the benifit of those hunting for that its also in the errata for the 1.0 spec, item 12 at http://www.osoa.org/display/Main/Errata+for+Java+Annotations+and+APIs+V1.00 ...ant
