[ openjms-Bugs-737037 ] http transport ignores servlet path

Bugs item #737037, was opened at 2003-05-13 23:09
Message generated for change (Comment added) made by tanderson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=737037&group_id=54559

Category: transport
>Group: v0.7.5
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: John Evans (lgas)
>Assigned to: Tim Anderson (tanderson)
Summary: http transport ignores servlet path

Initial Comment:
I was trying to use the http_jms.xml config example, but 
with a few changes, specifically like so:

  <HttpConfiguration host="www.jpevans.com"
                     port="8282"
                     clientPingInterval="20"
                     jndiServlet="/openjms-
0.7.5/OpenJMSJndi"
                     adminServlet="/openjms-
0.7.5/OpenJMSServer" />

And it seems to have been ignoring my adminServlet 
setting, and trying to 
access "/openjms/OpenJMSServer" instead.  It looks 
like perhaps this is hardcoded in the code.

I am able to workaround this by symlinking the openjms-
0.7.5 directory as openjms... but it would be nice if it 
paid attention to those settings....



----------------------------------------------------------------------

>Comment By: Tim Anderson (tanderson)
Date: 2003-08-23 11:46

Message:
Logged In: YES 
user_id=557161

Fixed in CVS. 

Connection factories are now bound in JNDI with the fully 
qualified URL of the OpenJMS server servlet. The path to
the servlet is specified by the new 'serverServlet' attribute of 
<HttpConfiguration/>:

  <HttpConfiguration host="localhost"
         port="80"
         serverServlet="/openjms/OpenJMSServer"
         jndiServlet="/openjms/OpenJMSJndi"
         adminServlet="/openjms/OpenJMSServer" />

The fix will be available in the 0.7.6 release

----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)
Date: 2003-05-14 07:58

Message:
Logged In: YES 
user_id=557161

The problem is that despite the configuration option, 
the URLs are hardcoded.

To fix it:
. the configured URLs need to be added to the 
environment properties bound with the 
ConnectionFactory in JNDI. 
. the client needs to be modified to use the bound 
properties. 
 Currently it expects the org.exolab.jms.http.server.url 
property to be the web server address, minus the servlet 
path

At the very least, the following need to be modified:
src/main/org/exolab/jms/client/http/HttpJmsServerStu
b.java
src/main/org/exolab/jms/client/http/HttpJmsSessionSt
ub
src/main/org/exolab/jms/administration/http/HttpJms
AdminConnection.java
src/main/org/exolab/jms/server/http/HttpJmsServer.jav
a


----------------------------------------------------------------------

Comment By: John Evans (lgas)
Date: 2003-05-13 23:14

Message:
Logged In: YES 
user_id=137603

I just updated the e-mail address that my sourceforge e-mail 
goes to, but it said it make take up to 24 hours.  In case you 
need to contact me, my current e-mail is john-/[email protected]

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=737037&group_id=54559