[JBoss JIRA] Created: (JBREM-579) transporter does not handle reflection conversion for primitive types
by Tom Elrod (JIRA)
transporter does not handle reflection conversion for primitive types
---------------------------------------------------------------------
Key: JBREM-579
URL: http://jira.jboss.com/jira/browse/JBREM-579
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: transporter
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.GA (Boon)
When the TransporterHandler receives an invocation request and uses reflection to make the call on the target object, it does not take into account primitive types for the signature type. So need to explicitly check for primitive types in method signature and do manual conversion of type provided by reflection to the real primitive class type. For example, reflection will say that int type argument is 'int' and needs to be converted to Integer.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
18 years, 8 months
[JBoss JIRA] Created: (JBREM-564) Default client socket factory configured by a system property
by Roland R?z (JIRA)
Default client socket factory configured by a system property
-------------------------------------------------------------
Key: JBREM-564
URL: http://jira.jboss.com/jira/browse/JBREM-564
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Roland R?z
Assigned To: Tom Elrod
To activate an ssl socket factory for the jobs remoting on the in a JBoss standalone client, the default socket factory of a VM can be configured by a java.security configuration activated with the java.security.properties=.../java.security System Property.
Providing always such a configuration file is complicated. A simpler solution is a system property providing the name of the socket factory class:
Here a possible implementation:
Class org.jboss.remoting.security.SSLSocketBuilder:
public SocketFactory createSSLSocketFactory() throws IOException,
NoSuchAlgorithmException, KeyStoreException, CertificateException,
KeyManagementException {
SocketFactory sf = null;
if (useSSLSocketFactory) {
String defaultFactoryName = System
.getProperty("jboss.remoting.defaultSocketFactory");
if (defaultFactoryName != null) {
try {
Class sfClass = Thread.currentThread()
.getContextClassLoader().loadClass(
defaultFactoryName);
Method m = sfClass.getMethod("getDefault", null);
if (m == null) {
throw new RuntimeException(
"Could not create the socket factory "
+ defaultFactoryName
+ " because the class "
+ sfClass
+ " doesn't provide the getDefault method.");
}
sf = (SocketFactory) m.invoke(null, null);
} catch (Exception ex) {
throw new RuntimeException(
"Could not create the socket factory "
+ defaultFactoryName, ex);
}
}
if (sf == null) {
sf = SSLSocketFactory.getDefault();
}
} else {
sf = createCustomSocketFactory();
}
return sf;
}
--
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
18 years, 8 months
[JBoss JIRA] Created: (JBREM-556) versioning tests failing
by Tom Elrod (JIRA)
versioning tests failing
------------------------
Key: JBREM-556
URL: http://jira.jboss.com/jira/browse/JBREM-556
Project: JBoss Remoting
Issue Type: Bug
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)
Broke some backwards compatibility with previous remoting versions (1.4.x).
Run versioning tests via ant target 'tests.versioning.quick'
In particular, failures are:
HTTP:
beta2 client => rc1 server
java.lang.NoClassDefFoundError: org/jboss/remoting/transport/http/WebServerError
Multiplex:
All failed (even rc1 client => rc1 server)
RMI:
beta2 client => rc1 server & rc1 client => beta2 server
Caused by: java.io.InvalidClassException: org.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory; local class incompatible: stream classdesc serialVersionUID = -7491556589517716155, local class serialVersionUID = -3039839695840773968
--
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
18 years, 8 months