April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4875) Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6)

by Dimitris Andreadis (JIRA)

Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6) -------------------------------------------------------- Key: JBAS-4875 URL: http://jira.jboss.com/jira/browse/JBAS-4875 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JB5-Transaction Manager Reporter: Dimitris Andreadis Assigned To: Mark Little Fix For: JBossAS-4.2.3.GA -- 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

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-280) Move defaults from AbstractKernelDeployer to AbstractKernelDeployment

by Ales Justin (JIRA)

Move defaults from AbstractKernelDeployer to AbstractKernelDeployment --------------------------------------------------------------------- Key: JBMICROCONT-280 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-280 Project: JBoss MicroContainer Issue Type: Task Components: Kernel Affects Versions: JBossMC-2.0.0.Beta12 Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossMC.2.0.0.CR1 We originally had all the deployment defaults in AbstractKernelDeployer::deploybean(), but other defaults have been added in the AbstractKernelDeployment::getBeans(). The AbstractKernelDeployment is the correct place for this code, so we should look at moving all the logic that is AbstractKernelDeployer::deployBean() into there. Especially since the AbstractKernelDeployer is not always used, e.g. the BeanMetaDeployer in the deployers project. -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1538) Support for rf/rfm files in ant build script

by Param S (JIRA)

Support for rf/rfm files in ant build script -------------------------------------------- Key: JBRULES-1538 URL: http://jira.jboss.com/jira/browse/JBRULES-1538 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 4.0.4 Environment: Windows XP, drools version 4.0.4, IBM RAD, Websphere Reporter: Param S Assigned To: Mark Proctor Fix For: 4.0.4 Hello, I am using Rule flow in Drools and I need help in writing an ant script to create a package which includes .drl as well as the .rfm too.. If you have any sample script which clearly shows how to do it or can point me to correct resource where in can find one then please respond back asap. Thanks 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

17 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5360) MBeanServerLocator.locate always returns the first item in the map instead of a lookup

by Narayanan Raghavan (JIRA)

MBeanServerLocator.locate always returns the first item in the map instead of a lookup -------------------------------------------------------------------------------------- Key: JBAS-5360 URL: http://jira.jboss.com/jira/browse/JBAS-5360 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Reporter: Narayanan Raghavan Fix For: JBossAS-4.2.1.GA The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. Affected archive/ file: soap.esb services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean mbeanServer = MBeanServerLocator.locate(); The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use MBeanServerLocator.locateJboss(); Thanks! -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1247) Implement WS integration API

by Heiko Braun (JIRA)

Implement WS integration API ---------------------------- Key: EJBTHREE-1247 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1247 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 5.0.0.Beta4 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: AS 5.0.0.CR1 -- 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

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1754) RoleModule documentation has duplicate code in identity chapter

by Chris Laprun (JIRA)

RoleModule documentation has duplicate code in identity chapter --------------------------------------------------------------- Key: JBPORTAL-1754 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1754 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun Assigned To: Boleslaw Dawidowicz -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1935) wrong confirmation when creating a user in identity management portlet

by Prabhat Jha (JIRA)

wrong confirmation when creating a user in identity management portlet ---------------------------------------------------------------------- Key: JBPORTAL-1935 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1935 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.4 Final Reporter: Prabhat Jha Assigned To: Boleslaw Dawidowicz Fix For: 2.6.5 Final When using LDAPExtUserModuleImpl, creation of user through identity management portal fails but portlet displays the message as "user created". 14:32:33,216 ERROR [IdentityUserManagementServiceImpl] Error when creating user java.lang.UnsupportedOperationException: User management is not supported in this implementation of UserModule at org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl.createUser(LDAPExtUserModuleImpl.java:100) at org.jboss.portal.core.identity.services.impl.IdentityUserManagementServiceImpl.createUser(IdentityUserManagementServiceImpl.java:187) at org.jboss.portal.core.identity.services.workflow.impl.RegistrationServiceImpl.registerUser(RegistrationServiceImpl.java:163) -- 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

17 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1170) Partial state transfer fails when multiple regions present

by Brian Stansberry (JIRA)

Partial state transfer fails when multiple regions present ---------------------------------------------------------- Key: JBCACHE-1170 URL: http://jira.jboss.com/jira/browse/JBCACHE-1170 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Brian Stansberry Assigned To: Manik Surtani The partial state transfer mechanism is getting confused about the Fqn of the region being transferred. Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase. Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state: 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call. Using region /JSESSION/localhost/http-field 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped". Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal. Two problems: 1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly. 2) Need to ensure that the right Fqn gets written. In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything. If not, just cleaning up the ThreadLocal should work. -- 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

17 years, 8 months

2
11
0 / 0

[JBoss JIRA] Created: (JBMDR-21) Create a meta annotation for ignorable instance annotations

by Adrian Brock (JIRA)

Create a meta annotation for ignorable instance annotations ----------------------------------------------------------- Key: JBMDR-21 URL: http://jira.jboss.com/jira/browse/JBMDR-21 Project: JBoss MetaData Repository Issue Type: Task Components: MetaData Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMDR-2.0.0.CR1 When AOP asks whether there are instance annotations it does this to decide whether an instance proxy is required. In some cases, e.g. the @JMX annotation, the instance annotation does not require an instance proxy instead we are just reusing the point cut language to invoke "advices" during deployment. To better handle this case, we should be able to meta annotate an annotation as not requiring an instance proxy, e.g. something like: @org.jboss.metadata.spi.annotation.InstanceAnnotation(false) public @interface JMX { ... } then we can tell aop whether an instance proxy is required. -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1934) errors on console during profile update

by Prabhat Jha (JIRA)

errors on console during profile update --------------------------------------- Key: JBPORTAL-1934 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1934 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: Identity-1.0 Reporter: Prabhat Jha Assigned To: Boleslaw Dawidowicz This is with identity-1.0.2 but I dont see this version for identity module. There are errors in server log/console during profile update. First/Last names are not mapped in portlet-config.xml, should not it be mapped because I would think this is a common use case?? when I try to update a user profile after loggin as user, I see exception in server log: 13:23:08,500 ERROR [IdentityUserBean] updateProfile failed org.jboss.portal.identity.IdentityException: Cannot resolve property: portal.user.homepage at org.jboss.portal.identity.DelegatingUserProfileModuleImpl.setProperty(DelegatingUserProfileModuleImpl.java:143) at sun.reflect.GeneratedMethodAccessor434.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor. ............. Caused by: java.lang.NullPointerException at org.jboss.portal.identity.ldap.LDAPUserProfileModuleImpl.setProperty(LDAPUserProfileModuleImpl.java:190) at org.jboss.portal.identity.DelegatingUserProfileModuleImpl.setProperty(DelegatingUserProfileModuleImpl.java:129) I think identity module should gracefully handle this. -- 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

17 years, 8 months

3
2
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 2008