On Wed, May 28, 2008 at 10:48 AM, Afkham Azeez <[EMAIL PROTECTED]> wrote:
> Once you configure the services using WSAS, using the create service > archive feature, you can get a self contained AAR file, which has the new > configuration, which can be dropped into another server. However, if you > have associated keystores etc. with the service, you will have to make sure > that those are in the other server as well. > When creating service archive, can't we put it in to the .aar and set the relative path correctly in the RampartConfig ? Another problem is the password callback classes, we will have to ship them too with the .aar file and set the correct class in the Rampart Config. thanks, nandana > > Azeez > > Samisa Abeysinghe wrote: > >> Our current WSAS is based on the assumption that people will run it and >> use that to deploy and configure services. >> As an example, it is amazingly easy to deploy a service and secure it >> using some security scenario. >> >> However, what it I want to deploy and configure couple of services, >> re-pack it and provide that as a package for someone else to run? Assume >> that this someone else know nothing about Java. >> I think that is a reasonable use case, WDYT? >> >> Samisa... >> >> > > _______________________________________________ > Wsas-java-dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev >
_______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
