May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-403) Refactoring of MessageDispatcher, RpcDispatcher, RequestCorrelator and GroupRequest

by Bela Ban (JIRA)

Refactoring of MessageDispatcher, RpcDispatcher, RequestCorrelator and GroupRequest ----------------------------------------------------------------------------------- Key: JGRP-403 URL: http://jira.jboss.com/jira/browse/JGRP-403 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 We may be able to trash GroupRequest and RequestCorrelator, this functionality can be provided by MessageDispatcher -- 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

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-1056) RpcDispatcher: reduce number of callXXX() methods

by Bela Ban (JIRA)

RpcDispatcher: reduce number of callXXX() methods ------------------------------------------------- Key: JGRP-1056 URL: https://jira.jboss.org/jira/browse/JGRP-1056 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Instead, create methods callRemoteMethod(Collection<Address> dests, MethodCall call) and callRemoteMethod(Address dest, MethodCall call); MethodCall then contains all necessary details for invoking the clustered call, e.g. - method name, types of parameters and actual argument (already exists, and is marshalled) - mode (GET_FIRST, GET_ALL etc) - timeout - Flags (e.g. OOB, DONT_BUNDLE) - boolean use_anycasts - RspFilter -- 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

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Resolved: (JGRP-193) RpcDispatcher.callRemoteMethod(s) should add "throws Exception" to signature

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-193?page=com.atlassian.jira.plugin.s... ] Bela Ban resolved JGRP-193. --------------------------- Resolution: Done Actually, IMO throwing a runtime exception is fine > RpcDispatcher.callRemoteMethod(s) should add "throws Exception" to signature > ---------------------------------------------------------------------------- > > Key: JGRP-193 > URL: https://issues.jboss.org/browse/JGRP-193 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9, 2.2.9.1, 2.3, 2.4, 2.5, 3.x > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.0 > > > This will requirec code changes to callers of these methods, so this will make it not API compatible with previous versions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-880) Specializing bean in bundled archive doesn't work

by Nicklas Karlsson (JIRA)

Specializing bean in bundled archive doesn't work ------------------------------------------------- Key: AS7-880 URL: https://issues.jboss.org/browse/AS7-880 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.0.Beta3 Reporter: Nicklas Karlsson Assignee: Stuart Douglas Attachments: test.zip @Specializing a bean by extending it directly from a bundled CDI-archive gives a Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class fi.affecto.test.MyApplicationBundles] with qualifiers [@Any @Default] at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:545) at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:124) at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:202) at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:372) at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) ... 4 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-870) add command that would print version and env info

by Alexey Loubyansky (JIRA)

add command that would print version and env info ------------------------------------------------- Key: AS7-870 URL: https://issues.jboss.org/browse/AS7-870 Project: Application Server 7 Issue Type: Sub-task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.CR1 Instead of echoing the env info from the script, there could be a separate command that would print the relevant info. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-871) limit logging in non-interactive mode

by Alexey Loubyansky (JIRA)

limit logging in non-interactive mode ------------------------------------- Key: AS7-871 URL: https://issues.jboss.org/browse/AS7-871 Project: Application Server 7 Issue Type: Sub-task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.CR1 In non-interactive mode, i.e. when command, commands or file is specified as the argument to jboss-admin.[sh|bat], the logs should include only the output of the commands specified for execution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-81) Release Final versions of APIs for inclusion in AS 7.0.0.Final

by Shelly McGowan (JIRA)

Release Final versions of APIs for inclusion in AS 7.0.0.Final -------------------------------------------------------------- Key: JBEE-81 URL: https://issues.jboss.org/browse/JBEE-81 Project: JBoss JavaEE APIs Issue Type: Release Components: JaxRS, JCA API Reporter: Shelly McGowan Assignee: Shelly McGowan org.jboss.spec.javax.faces.jboss-jsf-api_2.0_spec: 1.0.0.Beta2 org.jboss.spec.javax.resource.jboss-connector-api_1.6_spec: 1.0.0.Beta1 org.jboss.spec.javax.ws.rs.jboss-jaxrs-api_1.1_spec: 1.0.0.Beta1 org.jboss.spec.javax.xml.ws.jboss-jaxws-api_2.2_spec: 2.0.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-681) Upgrade maven-release-plugin 2.0 -> 2.1

by Lukáš Fryč (JIRA)

Upgrade maven-release-plugin 2.0 -> 2.1 --------------------------------------- Key: JBBUILD-681 URL: https://issues.jboss.org/browse/JBBUILD-681 Project: JBoss Build System Issue Type: Enhancement Components: JBoss Parent POM Affects Versions: JBoss Parent POM - 6-beta-2 Reporter: Lukáš Fryč Assignee: Paul Gier maven-release-plugin adds some nice to have features like pushChanges=false in its 2.1 version http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
1
0 / 0

[JBoss JIRA] Deleted: (HIBERNATE-126) [HHH-2389] Optimistic lock does not throw exception

by Ricardo Martinelli Oliveira (JIRA)

[ https://issues.jboss.org/browse/HIBERNATE-126?page=com.atlassian.jira.plu... ] Ricardo Martinelli Oliveira deleted HIBERNATE-126: -------------------------------------------------- > [HHH-2389] Optimistic lock does not throw exception > --------------------------------------------------- > > Key: HIBERNATE-126 > URL: https://issues.jboss.org/browse/HIBERNATE-126 > Project: Hibernate Integration > Issue Type: Bug > Reporter: Ricardo Martinelli Oliveira > Assignee: Steve Ebersole > Priority: Minor > > Customer created a test case where he found a bug in a situation where must be thrown OptmisticLockException, but it didn't throw. I attached a Test Case where it describes the problem in method checkAttachedChangedVersion_CASO_REAL(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (HIBERNATE-126) [HHH-2389] Optimistic lock does not throw exception

by Ricardo Martinelli Oliveira (JIRA)

[HHH-2389] Optimistic lock does not throw exception --------------------------------------------------- Key: HIBERNATE-126 URL: https://issues.jboss.org/browse/HIBERNATE-126 Project: Hibernate Integration Issue Type: Bug Reporter: Ricardo Martinelli Oliveira Assignee: Steve Ebersole Priority: Minor Customer created a test case where he found a bug in a situation where must be thrown OptmisticLockException, but it didn't throw. I attached a Test Case where it describes the problem in method checkAttachedChangedVersion_CASO_REAL(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011