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

[John Mazzitelli (JIRA)]

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

John Mazzitelli reopened JBREM-542:
-----------------------------------

             
Tom - can I ask that this be re-opened and the "old" way of specifying locatorName re-introduced.  You can leave this new way (locatorUrl) also supported, but I would also like to use the locatorName and NOT the locator URL.

Here's why I need it back in.

Suppose I'm writing a server app that I distribute to my customers.  I pre-package a JBossAS server and I bundle this war in it.  I ship it to my customers that they unzip and run.  If you force me to configure this servlet with the locator URL, my customers will be forced to go into this web.xml and modify it so it matches their hostname in the URL (they would need to change "localhost" to their hostname or IP) - same with the port.  That or I need to write an "installer" script that auto-modifies this web.xml.  But no matter what, if the customer ever changes the hostname or IP of the box, they will be forced to change the web.xml (they would first have to KNOW to do this and remember to do it).

The original way you had it, the web.xml didn't have to change - the JMX ObjectName was always the same.  I just took the stock web.xml that came out of the Remoting build and it works across any machine - whether or not the port was on 8080 or the bind address was localhost.

Before you say, "ah... but you'd still have the jboss-service.xml <mbean> for the Connector that you'd have to change with that information" - In my use case, I don't have a <mbean> that directly installs a Connector.  I have my own custom bootstrap <mbean> that installs my Connector in a custom way.  It does this by reading a configuration file that my customers will have full control over (all the configuration will be here, just not this connector stuff).  It is THIS configuration file that the customer will specify things like what the hostname or port number will be - I don't want the customer to have to modify any jboss-service.xml or web.xml file, I only want them touching this custom config file.

> 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)
>
>
> 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