[Design of JBoss/Tomcat Integration] - Deployers conflict
by deruelle_jean
Hi,
We are currently building a sip servlets (JSR 289) implementation that aims to be able to run both on top of Tomcat and Jboss. (available at https://sip-servlets.dev.java.net/)
Unfortunately for us, the specs mandates that compliant containers should be able to deploy sip servlets bundled as a sar archive (.sar extension, same as jboss service archive extension). A valid sar file should contain a sip.xml in its WEB-INF directory.
This requirement made me look into Jboss AS 4.2.2.GA code and I found that the current SARDeployer will accept any file with .sar extension (in its accepts method, actually through the SubDeployerSupport accepts method). However if the sar file deployed doesn't contain a META-INF/jboss-service.xml it will fail to deploy.
This prevents us to provide our custom Tomcat Deployer to deploy sip servlet archive file (sar file with a sip.xml)
We have a proposition to correct the situation so that we can use Jboss as a sip servlets converged container :
Provide an accepts method in SARDeployer that enforce checks to see if the sar file contains a META-INF/jboss-service.xml. If not the method would return false and won't accept the deployment, leaving it for our sip servlets deployer to process and accept since it will contain a sip.xml.
We might have missed something. if not, do you think that would be possible ? If so should I open an issue in JIRA or something ?
Thx.
Best regards
Jean Deruelle
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122551#4122551
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122551
18 years, 2 months
[Design of JBoss jBPM] - how crucial are exception handlers ?
by tom.baeyens@jboss.com
i'm in doubt about the importance of exception handlers in the PVM. i want your opinion on whether they should go in the PVM.
exception handlers are only to catch java exceptions that occur in user code (delegation classes). The purpose of exception handlers is to create global catch clauses that handle certain exceptions for multiple invocations of user code. This way, the try-catch doesn't have to be programmed into each user-code-class individually.
users could create abstract base classes to include the handling of exceptions and handle it that way. but that would not give the flexibility of the parent lookup of exception handlers. (i'm in doubt if that is needed)
also, if we do it on the level of the pvm, exception handlers don't make a distinction between process language code and real user code in case of jPDL. the node behaviour implementation is considered a delegation class and hence guarded with the exception handler. but for the exceptions that are thrown, the pvm doesn't know if it comes from the process language implementation or from real user code.
an alternative could be interceptors. i have in jPDL a mechanism for installing an interceptor for user code. i could do something like that in the PVM as well. that could be an alternative way to enable exception handling functionality to clients of the pvm. the question there would be: what levels would we support interceptors: in jpdl now, it is a static member field, so it's only on the level of the complete engine. But we could also support it on process definition, delegation or even on execution instance level.
those are my thought pieces that don't come to conclusion. your thoughts are appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122520#4122520
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122520
18 years, 2 months