> Hi Chathura: > > Chathura C. Ekanayake wrote: >> I think we should include the documents also in the zip distribution. >> And there should be a jar distribution as well, as we are targeting >> it to be used inside other Java programs. So IMHO the packaging >> structure and names can be as follows: >> >> wso2registry-1.0-alpha.war >> ================== >> >> Webapp with relevant jars and other resources to be deployed in >> servlet containers. >> This provides the web UI for human interaction and APP interface for >> interaction with other systems. > > +1 > >> wso2registry-1.0-alpha.jar >> ================= >> >> Registry library to be embedded and used inside Java programs. Once >> this is embedded, Java programs >> can interact with the Registry using the provided Java API. > > I think it's good to provide one jar that contains everything, but I > think it's also important that we ship an API jar (think JAXP) which > can be linked against by itself without regard for implementation: > > wso2registry-api-1.0-alpha.jar (or alternately s/api/client/) > > This contains the Registry interface, any common concrete classes, and > the ability to bootstrap particular implementations. I should be able > to just link against this jar and say: We could do this , however the issues is our maven module structure. If we look at Axiom there we can easily do that , but here we have both impl and implementation together so it is bit hard to create two jar from one module. Doable but withing this short time period very difficult to do that.\
-Deepal _______________________________________________ Registry-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
