[jboss-jira] [JBoss JIRA] Closed: (JBREM-819) Consider removing dependency on jboss-commons

[David Lloyd (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-819?page=all ]

David Lloyd closed JBREM-819.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Won't Fix

Won't fix in the 2.x series.  Remoting 3 does not depend on JBoss commons though.

> Consider removing dependency on jboss-commons
> ---------------------------------------------
>
>                 Key: JBREM-819
>                 URL: http://jira.jboss.com/jira/browse/JBREM-819
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Trustin Lee
>
> From Greg Hinkle of the JBoss Operations Network group:  
> "... not only are the including tons of crap in the garbage pale called commons, but they dictate tons of library dependencies and serialization versions. For a group like ours that has to be able to simultaneously connect to every version of jboss released in the last 3 years it is not a good situation. We end up having to create a separate class loader per connection.
> "Now with remoting, we're actually using it as a core infrastructure piece. That means its in parent classloaders to these connection classloaders. As long as commons is in that required list we can't use remoting this way. We're going to have to do some serious classloader restructuring to be able to support our needs."

-- 
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