From: Chad B. (JIRA) <ji...@an...> - 2005-02-17 01:19:09
|
[ http://thecla.homeftp.net:8380/jira/browse/SPRING-34?page=history ] Chad Brandon closed SPRING-34: ------------------------------ Resolution: Fixed Applied...great job Peter (you respected the coding style and everything..I appreciate that :)). Please check it out, and make sure everything is there. > Spring Remoting > --------------- > > Key: SPRING-34 > URL: http://thecla.homeftp.net:8380/jira/browse/SPRING-34 > Project: Spring Cartridge > Type: New Feature > Reporter: Peter Friese > Assignee: Chad Brandon > Priority: Minor > Attachments: SpringMetafacadeModel.xml.zip, remoting.patch > > > Add remoting to the Spring cartridge so that services can be exported using httpinvoker, rmi, burlap or hessian. > Suggestion: > Add a tagged value "@andromda.spring.remoting.type" with values [none, httpinvoker, rmi, hessian, burlap] that can be used to specify the type of remote communication explicitly for each service. This way you can export some services and leave other unexported. > Add a namespace property "defaultServiceRemotingType" that makes it possible to define a default remoting type (makes life easier if you want to export all but a few services) > Add three namespace properties defaultServiceRemotePort, defaultServiceRemoteContext, defaultServiceRemoteServer that allow for configuring where the remote service is running. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://thecla.homeftp.net:8380/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |