[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp-comment] a few questions
Answers intertwined with <rt> Timo Tetzlaf <Timo.Tetzlaf@met To: "'wsrp-comment@lists.oasis-open.org'" ris.de> <wsrp-comment@lists.oasis-open.org> cc: 11/12/2002 06:41 Subject: [wsrp-comment] a few questions AM Hi, Again, I have some questions regard to WSIA - WSRP Core Specification v0.8. 1.) In section 11.7, Handle Type, you describe that Handle extends String. But String is 'final' and so it is impossible to extend from it. I am correct or do I understand something wrong ? <rt> String is a final class in Java. In the document world, string is a simple type with various facets. The length restriction of Handles would be setting one of these facets. Our current WSDL does not use this form because it breaks the JAX-RPC tooling due to the issue you raise about String being a final class. The Axis tooling accepted the definition (Handle became a class that had a string member), but ignored the additional restriction. I don't remember if .Net did any better in handling the refined definition. </rt> 2.) Is there any reference implementation available, that I can use for my degree dissertation ? Any sourcecoude I an use (have not be compileable) is helpfully to see how it will work. <rt> There are implementations that member companies have in house and a stated intent by IBM to contribute source to an Apache project early next year. </rt> 3.) Does my assumption is right, if I think that the Producer-Service (which support getServiceDescription(), getEntityDescripton() and so on) is a kind of Manager who manage all Entities in one scope ? <rt> yes ... and that scope is either the Consumer's registration (when registration is supported) or the Producer (when registration is not supported). </rt> So I have to announce all Entity which shall be visible on getServiceDescription() ? <rt> The Producer announces all available entities given the supplied registration and userContext. </rt> 4.) In regard to my degree dissertation, I want to implement a small example WSRP-Service using the existing specification. Which existing frameworks can I use, to simplify this ? Till now I am using APACHE-AXIS (for web service), and want to use Cocoon or JSF (for transforming XML in any other markup I want to use in my entity) and EJB for persistence. <rt> Using Axis for the web service interface that then provides a container for entities using particular support classes (Cocoon, JSF and EJB being good examples) is a very reasonable approach. If you wish to avoid the container, you could also write the Producer to offer only a single entity type. If you wish to avoid writing the persistence, you could use the options for pushing persistent information to the Consumer. </rt> Thanks, Timo Tetzlaf
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC