September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-748) check variable hibernatability before serializability

by Tom Baeyens (JIRA)

check variable hibernatability before serializability ----------------------------------------------------- Key: JBPM-748 URL: http://jira.jboss.com/jira/browse/JBPM-748 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.1.3, jBPM 3.2 alpha 1 when a variable is persisted, the order in which serializability and hibernatability is checked should be reversed. the new behaviour should be that first hibernatability is checked and only afterwards, serializability should be checked. see also: http://blogs.sourceallies.com/roller/page/joedeveloper?entry=jbpm_3_1_aut... -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-424) Cannot access the first message when starting the JMS subscriber

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-424?page=all ] Clebert Suconic closed JBMESSAGING-424. --------------------------------------- Resolution: Duplicate Issue This issue was fixed as a duplicate. However I double checked this by creating another testcase > Cannot access the first message when starting the JMS subscriber > ---------------------------------------------------------------- > > Key: JBMESSAGING-424 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-424 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Environment: JBoss jboss-4.0.4.GA & jboss-messaging-1.0.1.CR2 > Reporter: Seung Hyun > Assigned To: Clebert Suconic > Fix For: 1.0.1.CR5, 1.2.0.Alpha1 > > > Some messages are already published to the specific queue and the queue contains few messages. Starts the subscriber to receive the messages in the queue. It reads all the messages except the first message. Also, the first message is not accessible at all. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-336) BigDecimal is not handled properly

by Valerij Timofeev (JIRA)

BigDecimal is not handled properly ---------------------------------- Key: JBSEAM-336 URL: http://jira.jboss.com/jira/browse/JBSEAM-336 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.0.1 Environment: German or US locale, Windows XP Pro, myfaces 1.1.3, Oracle 9.2 or MySQL 4.1.9 Reporter: Valerij Timofeev Generating CRUD Seam applications results in some fields having Java type BigDecimal. It seems that this type is not handled properly. There are no error messages in the JBoss server.log (log4j javax.faces & org.jboss.seam priorities are DEBUG). Query returns no results. Debugging shows for example that findFirstPage() method is never called. Changing type e.g. to Double fixes the issue (see workarounds for details) : it becomes possible to step through the method. And query returns some results. Clicking on create link and then switching to find view (other bean than current) results in the following JSF error: Cannot set value for expression '#{somebeanEditor.instance.id}' to a new value of type java.lang.String Where ID is of type BigDecimal. -- 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

19 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-346) Full <ejb-jar> declaration in examples' ejb-jar.xml files

by Stephen Friedrich (JIRA)

Full <ejb-jar> declaration in examples' ejb-jar.xml files --------------------------------------------------------- Key: JBSEAM-346 URL: http://jira.jboss.com/jira/browse/JBSEAM-346 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 1.0.1 Reporter: Stephen Friedrich Currently ejb-jar.xml files in seam examples (1.0.1 GA) use just "<ejb-jar>". Would be nicer if they used a full, standard compliant declaration: {code} <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0"> {code} -- 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

19 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-327) Relax required=true in @Create and @Destroy methods

by Gavin King (JIRA)

Relax required=true in @Create and @Destroy methods --------------------------------------------------- Key: JBSEAM-327 URL: http://jira.jboss.com/jira/browse/JBSEAM-327 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.0.1 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 Might be convenient to relax required=true during lifecycle callbacks (but don't forget the EJB3 callbacks @PostCostruct/@PreDestroy/@PrePassivate/@PostActivate) -- 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

19 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-701) different interceptor stack for same method based on call via remote or local interface

by William DeCoste (JIRA)

different interceptor stack for same method based on call via remote or local interface --------------------------------------------------------------------------------------- Key: EJBTHREE-701 URL: http://jira.jboss.com/jira/browse/EJBTHREE-701 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC8 - FD Reporter: William DeCoste Assigned To: William DeCoste Priority: Optional -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-350) create specification for jbossws/jbosside plugin / integration

by Ole Matzura (JIRA)

create specification for jbossws/jbosside plugin / integration -------------------------------------------------------------- Key: JBIDE-350 URL: http://jira.jboss.com/jira/browse/JBIDE-350 Project: JBoss IDE Issue Type: Task Components: Webservices Plugin Reporter: Ole Matzura Assigned To: Ole Matzura Fix For: 2.0.0.Beta2 we need a spec that outlines how jbossws should be integrated into eclipse/jbosside -- 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

19 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-300) NAKACK.send() doesn't need to be synchronized

by Bela Ban (JIRA)

NAKACK.send() doesn't need to be synchronized --------------------------------------------- Key: JGRP-300 URL: http://jira.jboss.com/jira/browse/JGRP-300 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.4 NAKACK.send() currently calls passDown(evt) in a synchronized(sent_msgs) statement. However, this is not necessary (contrary to handleMessage() which needs to pass messages up in the order of sequence numbers) because messages can be sent un-ordered. The receivers will order the messages anyway, so if we sent 1,3,2,4 due to thread premption, the receivers will order them and deliver them as 1,2,3,4. BENEFIT: the less synchronization, the less probability of deadlocks -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-289) Make service container configurable wrt datasource and persistence manager config

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-289?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-289: ------------------------------------- We also need to make sure that when creating a PostOffice or any other component that requires sqlProperties the correct properties, in a core test, the correct properties are configured. Currently this is not the case. > Make service container configurable wrt datasource and persistence manager config > --------------------------------------------------------------------------------- > > Key: JBMESSAGING-289 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-289 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.CR5 > > > Must be made configurable so test suite can be run against different databases with different pm configs -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-619) PojoCache to support JDK5.0 Enum

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-619?page=comments#action_12343019 ] Ben Wang commented on JBCACHE-619: ---------------------------------- No, ejb3 entity cache doesn't use PojoCache. It uses the regular TreeCache, rather. So it should not be an issue there. > PojoCache to support JDK5.0 Enum > -------------------------------- > > Key: JBCACHE-619 > URL: http://jira.jboss.com/jira/browse/JBCACHE-619 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: PojoCache 2.1.0 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > In JDK5.0, Enum is Serializabe. We need to look into whether it is possible to intercept Enum operation as well. -- 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

19 years, 8 months

1
0
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 September 2006