[ebxmlms-develop] channels, classes, jndi etc.

[Ronald v. K. <rv...@ab...>]

While developing the small example with JNDI, some questions came to 
mind. What I was doing looked alot like implementing what can be done 
with session-beans in a j2ee server.

Without thinking of ejb's, the questions this raises for me are:

    * How dynamic should new classes (file/url/jms/....) be loaded.
          o  Should they be deployed expanded e.g. in a expanded
            deployed msh.war directory?
          o Is a restart acceptible?
    * Where and how should they be pre-configured (url, username,
      password, certificate etc).
    * Does each AppContext has it's own set of maximum of 3 'channel
      connectors'  (message, error, notify) or should the be shared
      between AppContexts?
    * Where is the dynamic configuration persisted (if at all?) in
      relation to the AppContext (JNDI?, Database?)
    * Should there be a limit in maximum connections to the receiving
      application? 
    * etc...

please comment..

Regards,

Ronald