[
https://jira.jboss.org/jira/browse/JBREM-1149?page=com.atlassian.jira.plu...
]
Ron Sigal closed JBREM-1149.
----------------------------
Resolution: Won't Fix
This request has, in effect, already been satisfied by the creation of the component jars.
For example, to use the socket transport, jboss-remoting.jar can be replaced by
jboss-remoting-core.jar and jboss-remoting-socket.jar, with the following sizes:
release: 2.2.3 2.5.1
===================================
jboss-remoting-core.jar: 290567 407565
jboss-remoting-socket.jar: 50692 68850
===================================
total: 341259 476415 bytes
For more information, see Chapter 4 of the Remoting Guide at
http://labs.jboss.com/jbossremoting/docs/index.html .
Do not include samples in the JAR
---------------------------------
Key: JBREM-1149
URL:
https://jira.jboss.org/jira/browse/JBREM-1149
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.1 (Flounder), 2.2.3
Environment: JBoss AS 5.1.0GA
Reporter: Ondrej Medek
Assignee: Ron Sigal
Priority: Minor
Fix For: 2.5.2 (Flounder), 2.2.3.SP1
We have a Java swing application using session beans. We have to distribute
jboss-remoting.jar (1,14MB) to our clients. I have found that when I delete samples from
the jboss-remoting.jar, it has only 0,86MB.
It saves some download time for our clients behind a thin line.
Please, remove the samples and all not-necessary code from the jboss-remoting.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira