[ https://jira.jboss.org/jira/browse/JBREM-505?page=com.atlassian.jira.plug... ]
David Lloyd closed JBREM-505.
-----------------------------
Resolution: Duplicate Issue
Duplicates JBAS-3151.
> convert jndi to use remoting for transport
> ------------------------------------------
>
> Key: JBREM-505
> URL: https://jira.jboss.org/jira/browse/JBREM-505
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: general
> Affects Versions: External_issues
> Reporter: Tom Elrod
>
> Need to convert jndi to use remoting as transport. Ties in with JBREM-424.
--
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
update jbossws to include 2.0.0 in component-info.xml
-----------------------------------------------------
Key: JBREM-566
URL: http://jira.jboss.com/jira/browse/JBREM-566
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: general
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: External_issues
Have already e-mailed ws team. Need this to be updated in repository or won't be able to update build-thirdpary.xml within jbossas.
--
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
[ https://jira.jboss.org/jira/browse/JBREM-407?page=com.atlassian.jira.plug... ]
David Lloyd closed JBREM-407.
-----------------------------
Resolution: Out of Date
Assignee: (was: Tom Elrod)
> deploying servlet-invoker.war within JBossAS
> --------------------------------------------
>
> Key: JBREM-407
> URL: https://jira.jboss.org/jira/browse/JBREM-407
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: general
> Affects Versions: External_issues
> Reporter: Tom Elrod
> Fix For: External_issues
>
>
> remoting has a servlet-invoker.war that needs to be deployed within JBossAS if is going to have a remoting transport that uses a servlet for the transport (i.e. ejb3 configured to use servlet transport).
> Need to determine if should be included by default within JBossAS distribution, and if so, how to get it there (because jboss-remoting.jar is a file kept in repository that is downloaded, but servlet-invoker.war is not and am not sure if can be).
--
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
[ https://jira.jboss.org/jira/browse/JBREM-322?page=com.atlassian.jira.plug... ]
David Lloyd closed JBREM-322.
-----------------------------
Resolution: Out of Date
Assignee: (was: Tom Elrod)
> disconnect error with servlet and http transport (when using ejb3)
> ------------------------------------------------------------------
>
> Key: JBREM-322
> URL: https://jira.jboss.org/jira/browse/JBREM-322
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: transport
> Affects Versions: 1.4.0 final
> Reporter: Tom Elrod
> Fix For: External_issues
>
>
> When doing an ejb3 remove using the servlet and http transport, get an error.
--
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
Update ejb3 project for use of 2.0.0 of remoting
------------------------------------------------
Key: JBREM-567
URL: http://jira.jboss.com/jira/browse/JBREM-567
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: general
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: External_issues
Need to make sure 'xmbean-dd="org/jboss/remoting/transport/Connector.xml" is removed from all the service descriptors, as Connector is now a standard mbean and not an xmbean.
--
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
integration testing for 2.0.0 release
-------------------------------------
Key: JBREM-565
URL: http://jira.jboss.com/jira/browse/JBREM-565
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: general
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.GA (Boon)
Need to do some integration testing with new 2.0.0.CR1 of remoting with JBossAS 4 & 5 to make sure everything is working correctly.
--
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
[ https://jira.jboss.org/jira/browse/JBAS-7818?page=com.atlassian.jira.plug... ]
Scott Marlow commented on JBAS-7818:
------------------------------------
I took a few thread dumps during the ten minute (initial pause) during as boot. http://pastebin.com/jyjVA7pv
> RMIAdaptor replacement based on JSR160
> --------------------------------------
>
> Key: JBAS-7818
> URL: https://jira.jboss.org/jira/browse/JBAS-7818
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMX
> Reporter: Scott M Stark
> Assignee: Scott Marlow
> Fix For: JBossAS-6.0.0.M3
>
>
> A replacement for the proprietary RMIAdaptor is needed that supports authentication, authorization and SSL.
--
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