[JBoss JIRA] Created: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
by Ron Sigal (JIRA)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: 2.0.0 Alpha
In addition to the "http" transport, Remoting also has the http-based "servlet" transport. The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side. In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads. But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850 and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used. In principle, it's the appropriate transport to use when the server is running inside JBossAS. In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet. However, there have been a couple of problems. For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker"). However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBRULES-1023) Typing the parameter to be replace by DSL/DRL replacement
by christian bastin (JIRA)
Typing the parameter to be replace by DSL/DRL replacement
---------------------------------------------------------
Key: JBRULES-1023
URL: http://jira.jboss.com/jira/browse/JBRULES-1023
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: christian bastin
Assigned To: Mark Proctor
We have a very long DSL including more 150 différent lines (wich could be very similar). We have no posibility to be sure of the replacement operarted by the parsing. We often dicover problem that force us to move the order of the lines in the DSL. This is an simple example of what I think could be improved.
If you have a DSL
test {code} is {value}
this could replace this 2 rules in the DRL
rule "Rule-1"
when
test 10 is 10
then
> System.out.println("test 1 OK");
end
rule "Rule-1"
when
test 10 + 10 is 10
then
> System.out.println("test 1 OK");
end
I would like the ability to type the parameter of my DSL, for example with regular expression.
test {code|[0-9]+} is {value|[0-9]+}
so the only rule available for replacement should be the first rule ("Rule-1"). The other rule would not find a replacement and should be implemented in the DSL.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-3834) i18n of jmx-console
by Ryusuke Kajiyama (JIRA)
i18n of jmx-console
-------------------
Key: JBAS-3834
URL: http://jira.jboss.com/jira/browse/JBAS-3834
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.4.GA
Environment: Any operating system with multiple language such as MS932 (Japanese)
Reporter: Ryusuke Kajiyama
We found that there are difference in screen-displayed multibyte characters on using Internet Explorer and Firefox. When using MS932, with IE, characters are returned same as posted, however with Firefox, characters are url-escaped like %xx. Our guess is that html of jmx-console does not have charset and there are no functions to handle encoding request parameter.
It could be fixed if there were some filter action something like distinguish character set of posted data, and add <meta> tag into html or set Content-Type.
--
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
15 years, 7 months