We would like to tap into the built-in assembly/deployment features of the server api to help create custom plugins for our server.
So far, it looks to me like its best for us to define a totally new module type - a service module - which can be created from a template, assembled into an archive (with its own extension), and deployed to our j2ee server in the same manner as one would create, assemble, and deploy a j2eeApp or ejb module.
Does this sound reasonable? Any known caveats? I have a fairly good grasp of how to support a j2ee module/component, but now I want to actually tap into the side of the api that defines the actions and attach these to my new module node type. Any pointers in this area would be really helpful.
If you would like to report an abuse of our service, such as a spam message, please . Если Вы хотите пожаловаться на содержимое этой страницы, пожалуйста .
