[jboss-jira] [JBoss JIRA] Updated: (JBREM-542) change how remoting servlet finds servlet invoker

John Mazzitelli (JIRA) jira-events at jboss.com
Sat Jul 15 22:42:11 EDT 2006


     [ http://jira.jboss.com/jira/browse/JBREM-542?page=all ]

John Mazzitelli updated JBREM-542:
----------------------------------

    Attachment: JBREM-542-patch.txt
                ServerInvokerServlet.java

I've attached a patch (along with the full file) of ServerInvokerServlet where it accepts either locatorUrl or locatorName.  locatorUrl takes precedence.

This solves my problem of wanting to keep locatorName functionality but also allows you to specify the URL if you want.

Note that this introduces the JBoss and JMX dependency back in.  But I submit even the previous version still had those dependencies.  The servlet was always using JBoss logging so it still depended on JBoss before.  Also, ServerInvoker requires JMX which is always needed by the servlet, so it too depended in JMX before.

Please read the comment at the very bottom in the getMBeanServer() method - I explain a way that I think we can remove the JBoss MBeanServer dependency from this servlet (it requires having an abstract parent servlet class and just subclassing it with the JBoss-dependencies in that subclass.

> change how remoting servlet finds servlet invoker
> -------------------------------------------------
>
>                 Key: JBREM-542
>                 URL: http://jira.jboss.com/jira/browse/JBREM-542
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta2 (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Tom  Elrod
>             Fix For: 2.0.0.CR1 (Boon)
>
>         Attachments: JBREM-542-patch.txt, ServerInvokerServlet.java
>
>
> Currently the servlet deployed within servlet-invoker.war uses the servlet server invoker's JMX Object name (provide within the init-param of web.xml) to lookup the servlet server invoker to make calls upon.  This is limited in that requires JMX be available within the web container.  Althought this will probably be available in most J2EE app servers, might not be in other web container only deployments.  Need to remove this restriction.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list