April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-7818) RMIAdaptor replacement based on JSR160

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7818?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBAS-7818: -------------------------------------- The OSGi remote testsuite relies on the RMIAdaptor. Recent changes made <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-client</artifactId> <version>6.0.0.20100216-M2</version> unusable with jbossas/trunk. Could you please provide documentation on the intended migration path? * How should clients remotely connect to JMX in the future? * When is the existing access method intended to go out of service? I assume that access to the RMIAdaptor using the 6.0.0.20100216-M2 client libraries should continue to work for a while and that I am seeing a bug introduced by recent changes. > 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1217) Provide a Remoting context which can be retrieved statically

by David Lloyd (JIRA)

Provide a Remoting context which can be retrieved statically ------------------------------------------------------------ Key: JBREM-1217 URL: https://jira.jboss.org/jira/browse/JBREM-1217 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core, r3 core: api Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta3 The context should be usable for determining the current connection and/or endpoint during marshalling operations. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4383) Allow a different JSF implementation to be packaged in the WAR

by Stan Silvert (JIRA)

Allow a different JSF implementation to be packaged in the WAR -------------------------------------------------------------- Key: JBAS-4383 URL: http://jira.jboss.com/jira/browse/JBAS-4383 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JavaServerFaces Affects Versions: JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Stan Silvert Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-5.0.0.GA Prior to JEE5, most developers would bundle a JSF implementation such as MyFaces with the WAR. With AS 4.2 and 5.0, you should instead rely on the JSF implementation that ships with the container. However, for these legacy applications that rely on a particular implementation, we can disable the built-in JSF implementation as long as you stick with the default classloader settings. To disable the built-in JSF, you will add this to your web.xml: <context-param> <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name> <param-value>true</param-value> </context-param> -- 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

4
9
0 / 0

[JBoss JIRA] Created: (JBREM-1216) Connection should be accessible from Client

by David Lloyd (JIRA)

Connection should be accessible from Client ------------------------------------------- Key: JBREM-1216 URL: https://jira.jboss.org/jira/browse/JBREM-1216 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: api Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta3 In some cases (particularly, proxy serialization), it is desirable to get the Connection associated with a Client. It logically follows that all Clients must have Connections. Thus, a getter (getConnection) should be added to Client, and the methods which allow a Client which bypasses a Connection should be removed (these cases should be ported to use the "local:" protocol). -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREFLECT-114) NPE in JavassistAnnotatedInfo.getAnnotations() if there are no annotations

by Kabir Khan (JIRA)

NPE in JavassistAnnotatedInfo.getAnnotations() if there are no annotations -------------------------------------------------------------------------- Key: JBREFLECT-114 URL: https://jira.jboss.org/jira/browse/JBREFLECT-114 Project: JBoss Reflection Issue Type: Bug Affects Versions: JBossReflection.2.2.0-Alpha4 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossReflection.2.2.0-Alpha5 -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-115) JavassistInheritedAnnotationHolder incorrectly gets all annotations from super class regardless of if @Inherited or not

by Kabir Khan (JIRA)

JavassistInheritedAnnotationHolder incorrectly gets all annotations from super class regardless of if @Inherited or not ----------------------------------------------------------------------------------------------------------------------- Key: JBREFLECT-115 URL: https://jira.jboss.org/jira/browse/JBREFLECT-115 Project: JBoss Reflection Issue Type: Bug Affects Versions: JBossReflection.2.2.0-Alpha4 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossReflection.2.2.0-Alpha5 -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-784) NullPointerException in Dispatcher when doing toString

by Carlo de Wolf (JIRA)

NullPointerException in Dispatcher when doing toString ------------------------------------------------------ Key: JBAOP-784 URL: https://jira.jboss.org/jira/browse/JBAOP-784 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Carlo de Wolf java.lang.NullPointerException at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:117) at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:97) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy123.toString(Unknown Source) -- 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

15 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-771) Avoid transformation of classes that are already loaded but are not woven

by Flavia Rainone (JIRA)

Avoid transformation of classes that are already loaded but are not woven ------------------------------------------------------------------------- Key: JBAOP-771 URL: https://jira.jboss.org/jira/browse/JBAOP-771 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.9.GA This could bring some optimization, by avoiding useless work. -- 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

15 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (GPD-302) Generate Form Dialog is NOT auto-populated with controller variables or named transitions

by Nobody Cares (JIRA)

Generate Form Dialog is NOT auto-populated with controller variables or named transitions ----------------------------------------------------------------------------------------- Key: GPD-302 URL: https://jira.jboss.org/jira/browse/GPD-302 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM jPDL Designer 3.1.6 Environment: Eclipse 3.1.4 w/ packaged jBPM GPD (assuming 3.1.6) Reporter: Nobody Cares Assignee: Koen Aers Priority: Minor The launched dialog of a task's "Generate Form..." button is NOT automatically populated with the task's defined controller variables nor with buttons that correspond to the task's named transitions. This issue significantly hinders the usefulness of the GPD. -- 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

15 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAOP-776) jboss-50-install-jboss.xml does not install jboss-aop-deployers.jar

by Flavia Rainone (JIRA)

jboss-50-install-jboss.xml does not install jboss-aop-deployers.jar ------------------------------------------------------------------- Key: JBAOP-776 URL: https://jira.jboss.org/jira/browse/JBAOP-776 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.9.GA The jboss-aop-deployers.jar should be copied into the as lib directory during installation. -- 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

15 years, 7 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2010