12:49 p.m.
add sslservlet procotol
-----------------------
Key: JBREM-539
URL: http://jira.jboss.com/jira/browse/JBREM-539
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: transport
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Need to add sslservlet as there is no way to currently have a ssl deployed servlet invoker
without this distinction. This will require use of HTTPSClientInvoker on the client
side.
Would also be nice to do a check internally to make sure that servlet is available and log
an error if is not (maybe within start() method), since is only way to really know if
servlet deployed within web container properly.
--
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
10:04 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-539) add sslservlet procotol
[ http://jira.jboss.com/jira/browse/JBREM-539?page=comments#action_12339632 ]
Tom Elrod commented on JBREM-539:
----------------------------------
Test case: there is no automated test case, but manual tests can be run be following
readme.txt in src/tests/org/jboss/test/remoting/transport/servlet/readme.txt
add sslservlet procotol
-----------------------
Key: JBREM-539
URL: http://jira.jboss.com/jira/browse/JBREM-539
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Need to add sslservlet as there is no way to currently have a ssl deployed servlet
invoker without this distinction. This will require use of HTTPSClientInvoker on the
client side.
Would also be nice to do a check internally to make sure that servlet is available and
log an error if is not (maybe within start() method), since is only way to really know if
servlet deployed within web container properly.
--
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
10:49 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-539) add sslservlet procotol
[ http://jira.jboss.com/jira/browse/JBREM-539?page=comments#action_12339637 ]
Tom Elrod commented on JBREM-539:
----------------------------------
Example of servlet-invoker.war/WEB-INF/web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<!-- The the JBossRemoting server invoker servlet web.xml descriptor
$Id: web.xml,v 1.1 2005/06/16 21:12:48 telrod Exp $
-->
<web-app>
<servlet>
<servlet-name>ServerInvokerServlet</servlet-name>
<description>The ServerInvokerServlet receives requests via HTTP
protocol from within a web container and passes it onto the
ServletServerInvoker for processing.
</description>
<servlet-class>org.jboss.remoting.transport.servlet.web.ServerInvokerServlet</servlet-class>
<init-param>
<param-name>locatorUrl</param-name>
<param-value>sslservlet://localhost:8443/servlet-invoker/ServerInvokerServlet</param-value>
<description>The servlet server invoker locator url</description>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>ServerInvokerServlet</servlet-name>
<url-pattern>/ServerInvokerServlet/*</url-pattern>
</servlet-mapping>
</web-app>
Example of service xml:
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:service=Connector,transport=SSLServlet"
display-name="Servlet transport Connector">
<attribute name="InvokerLocator">
sslservlet://localhost:8443/servlet-invoker/ServerInvokerServlet
</attribute>
<attribute name="Configuration">
<config>
<handlers>
<handler
subsystem="test">org.jboss.test.remoting.transport.web.WebInvocationHandler</handler>
</handlers>
</config>
</attribute>
</mbean>
</server>
add sslservlet procotol
-----------------------
Key: JBREM-539
URL: http://jira.jboss.com/jira/browse/JBREM-539
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Need to add sslservlet as there is no way to currently have a ssl deployed servlet
invoker without this distinction. This will require use of HTTPSClientInvoker on the
client side.
Would also be nice to do a check internally to make sure that servlet is available and
log an error if is not (maybe within start() method), since is only way to really know if
servlet deployed within web container properly.
--
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
11:55 p.m.
New subject: [JBoss JIRA] Resolved: (JBREM-539) add sslservlet procotol
[ http://jira.jboss.com/jira/browse/JBREM-539?page=all ]
Tom Elrod resolved JBREM-539.
------------------------------
Resolution: Done
add sslservlet procotol
-----------------------
Key: JBREM-539
URL: http://jira.jboss.com/jira/browse/JBREM-539
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Need to add sslservlet as there is no way to currently have a ssl deployed servlet
invoker without this distinction. This will require use of HTTPSClientInvoker on the
client side.
Would also be nice to do a check internally to make sure that servlet is available and
log an error if is not (maybe within start() method), since is only way to really know if
servlet deployed within web container properly.
--
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
4:31 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-539) add sslservlet procotol
[ http://jira.jboss.com/jira/browse/JBREM-539?page=all ]
David Lloyd closed JBREM-539.
-----------------------------
add sslservlet procotol
-----------------------
Key: JBREM-539
URL: http://jira.jboss.com/jira/browse/JBREM-539
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Need to add sslservlet as there is no way to currently have a ssl deployed servlet
invoker without this distinction. This will require use of HTTPSClientInvoker on the
client side.
Would also be nice to do a check internally to make sure that servlet is available and
log an error if is not (maybe within start() method), since is only way to really know if
servlet deployed within web container properly.
--
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
6581
days inactive
7022
days old
4 comments
2 participants
participants (2)
-
David Lloyd (JIRA) -
Tom Elrod (JIRA)