December 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7953) Incorrect parsing of jboss-service.xml

by Pavel Macik (JIRA)

Incorrect parsing of jboss-service.xml -------------------------------------- Key: JBAS-7953 URL: https://jira.jboss.org/jira/browse/JBAS-7953 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-5.1.0.GA Reporter: Pavel Macik Assignee: Dimitris Andreadis n the server/<config>/conf/jboss-service.xml file there is mbean's attributes configured as following: <server> <mbean ... name="jboss:service=Naming" ...> ... <attribute name="BindAddress"> <value-factory bean="ServiceBindingManager" method="getStringBinding"> <parameter>jboss:service=Naming</parameter> <parameter>Port</parameter> <parameter><null/></parameter> </value-factory> </attribute> ... </mbean> ... </server> This exact configuration is fine. But while I change element formatting as follows, the </null> parameter parsing fails. ... <attribute name="BindAddress"> <value-factory bean="ServiceBindingManager" method="getStringBinding"> <parameter>jboss:service=Naming</parameter> <parameter>Port</parameter> <parameter> <null/> </parameter> </value-factory> </attribute> ... It seems the parser that parses this file doesn't ignore white-spaces around the <null/> element and the mbean behaves in different way. -- 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: (JBMETA-323) @EJB annotation processors should take into account "lookup" attribute while creating metadata

by jaikiran pai (JIRA)

@EJB annotation processors should take into account "lookup" attribute while creating metadata ---------------------------------------------------------------------------------------------- Key: JBMETA-323 URL: https://issues.jboss.org/browse/JBMETA-323 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: common Affects Versions: jboss-metadata-common-2.0.0-alpha-22 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: jboss-metadata-common-2.0.0-alpha-23 @EJB introduces a new lookup attribute in Java EE6. The annotation processor in JBMETA should take this into account while creating metadata. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8728) Global naming context not removed on module undeploy

by Thomas Diesler (JIRA)

Global naming context not removed on module undeploy ---------------------------------------------------- Key: JBAS-8728 URL: https://issues.jboss.org/browse/JBAS-8728 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Redeploy of the same module fails with DuplicateServiceException -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBAS-8727) DeploymentModuleLoader not registered withj ClassifyingModuleLoader

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBAS-8727?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved JBAS-8727. ---------------------------------- Resolution: Done Done https://github.com/jbosgi/jboss-as/commit/8fbe81df5d27d5f1167c135bbfa825f... > DeploymentModuleLoader not registered withj ClassifyingModuleLoader > ------------------------------------------------------------------- > > Key: JBAS-8727 > URL: https://issues.jboss.org/browse/JBAS-8727 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > > The effect is that a deployed OSGi bundle cannot have a dependency on a deployed module any more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8727) DeploymentModuleLoader not registered withj ClassifyingModuleLoader

by Thomas Diesler (JIRA)

DeploymentModuleLoader not registered withj ClassifyingModuleLoader ------------------------------------------------------------------- Key: JBAS-8727 URL: https://issues.jboss.org/browse/JBAS-8727 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler The effect is that a deployed OSGi bundle cannot have a dependency on a deployed module any more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-319) hashCode and equals method definitions are ignored in Session beans

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/EJBTHREE-319?page=com.atlassian.jira.plug... ] Carlo de Wolf resolved EJBTHREE-319. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > hashCode and equals method definitions are ignored in Session beans > ------------------------------------------------------------------- > > Key: EJBTHREE-319 > URL: https://issues.jboss.org/browse/EJBTHREE-319 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC3 > Environment: Mac OS X 10.4, JBoss AP 4.0.3 > Reporter: Gregory Nolle > > An equals or hashCode method in a Session bean class is ignored for the final bean objects. There seems to be some internal implementation of these two methods and it cannot be overrided. > For example: > Test.java > ======== > public interface Test { } > TestBean.java > ============ > @Stateless > public class TestBean implements Test > { > public boolean equals(Object obj) { > return true; > } > public int hashCode() { > return 5; > } > } > Client code > ========== > InitialContext ctx = new InitialContext(); > Test test = (Test) ctx.lookup(Test.class.getName()); > if (!test.equals("anything")) > System.err.println("this is wrong"); > if (test.hashCode() != 5) > System.err.println("this is also wrong"); > Both of those error messages are printed, when in fact neither should be printed since the equals() method should always return true in this case, and the result of hashCode() should always be 5. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2216) Timerservice Table Creation is erroneously omitted if tables (TIMER, CALENDAR_TIMER, ...) exist in a foreign Database Schema (DB2 9.7)

by Robert Reimann (JIRA)

Timerservice Table Creation is erroneously omitted if tables (TIMER, CALENDAR_TIMER, ...) exist in a foreign Database Schema (DB2 9.7) -------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2216 URL: https://issues.jboss.org/browse/EJBTHREE-2216 Project: EJB 3.0 Issue Type: Bug Components: timerservice-mk2 Environment: JBossAS 6.0.0.CR1, DB2 9.7 Reporter: Robert Reimann Changing DefaultDS to a DB2 Database which hosts multiple JBossAS instances in different schemas leads to deplomyent errors due to missing EJB3 Timerservice tables. The search for existing EJB3 Timerservice tables (TIMER, TIMEOUT_METHOD, CALENDAR_TIMER, TIMEOUTMETHOD_METHODPARAMS) is not restricted to the current schema. In case of existing tables within a foreign schema (which is different from the current user/schema) the required tables are not created for the current schema even though they are not available. In the example below tables are found within the unrelated USER01 schema even thought the current user/schema for DefaultDS is USER02: 16:37:46,188 DEBUG [Configuration] resolving reference to class: org.jboss.ejb3.timerservice.mk2.persistence.TimeoutMethod 16:37:46,188 DEBUG [Configuration] resolving reference to class: org.jboss.ejb3.timerservice.mk2.persistence.TimerEntity 16:37:46,188 DEBUG [Configuration] resolving reference to class: org.jboss.ejb3.timerservice.mk2.persistence.TimeoutMethod 16:37:46,631 INFO [TableMetadata] table found: USER01.TIMEOUTMETHOD_METHODPARAMS 16:37:46,632 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id] 16:37:46,632 INFO [TableMetadata] foreign keys: [fkf294c964b7de2d8a] 16:37:46,632 INFO [TableMetadata] indexes: [] 16:37:46,774 INFO [TableMetadata] table found: USER01.CALENDAR_TIMER ... 16:38:38,670 DEBUG [JDBCExceptionReporter] could not execute query [select timerentit0_.id as id0_, timerentit0_.info as info0_, timerentit0_.initialDate as initialD3_0_, timerentit0_.nextDate as nextDate0_, timerentit0_.previousRun as previous5_0_, timerentit0_.repeatInterval as repeatIn6_0_, timerentit0_.timedObjectId as timedObj7_0_, timerentit0_.timerState as timerState0_, timerentit0_1_.autoTimer as autoTimer2_, timerentit0_1_.scheduleExprDayOfMonth as schedule2_2_, timerentit0_1_.scheduleExprDayOfWeek as schedule3_2_, timerentit0_1_.scheduleExprEndDate as schedule4_2_, timerentit0_1_.scheduleExprHour as schedule5_2_, timerentit0_1_.scheduleExprMinute as schedule6_2_, timerentit0_1_.scheduleExprMonth as schedule7_2_, timerentit0_1_.scheduleExprSecond as schedule8_2_, timerentit0_1_.scheduleExprStartDate as schedule9_2_, timerentit0_1_.scheduleExprTimezone as schedul10_2_, timerentit0_1_.scheduleExprYear as schedul11_2_, timerentit0_1_.timeoutMethod_id as timeout13_2_, case when timerentit0_1_.id is not null then 1 when timerentit0_.id is not null then 0 end as clazz_ from timer timerentit0_ left outer join calendar_timer timerentit0_1_ on timerentit0_.id=timerentit0_1_.id where timerentit0_.timedObjectId=? and (timerentit0_.timerState not in (? , ?))]: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=USER02.TIMER, DRIVER=3.61.75 There has been a comparable issue in the EJBTimerService: https://issues.jboss.org/browse/JBAS-4042 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
1
0 / 0

[JBoss JIRA] Moved: (JBAS-8724) Facelets xhtml "hot reload" doesn't work if the application directory is out of "deploy" directory

by Fernando Nasser (JIRA)

[ https://issues.jboss.org/browse/JBAS-8724?page=com.atlassian.jira.plugin.... ] Fernando Nasser moved JBPAPP-3406 to JBAS-8724: ----------------------------------------------- Project: JBoss Application Server (was: JBoss Enterprise Application Platform) Key: JBAS-8724 (was: JBPAPP-3406) Affects Version/s: (was: EAP 5.0.0) Component/s: Deployers (was: System) Fix Version/s: TBD (was: TBD EAP 5) > Facelets xhtml "hot reload" doesn't work if the application directory is out of "deploy" directory > -------------------------------------------------------------------------------------------------- > > Key: JBAS-8724 > URL: https://issues.jboss.org/browse/JBAS-8724 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Salvatore Insalaco > Fix For: TBD > > > In JBoss EAP 5 the facelets hot-xhtml-deploy has been fixed (if you modify a facelets xhtml file it reloads automatically), and it works if the exploded war/ear is inside the deploy directory. > Unfortunately it doesn't work if the exploded war/ear is deployed externally from the deploy directory, using JMX (like JetBrains IntelliJ Idea IDE does). > It worked in JBoss EAP 4.3. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBADMCON-157) JBoss-5.1.0.GA Admin console

by Betty Schwartz (JIRA)

JBoss-5.1.0.GA Admin console ----------------------------- Key: JBADMCON-157 URL: https://jira.jboss.org/browse/JBADMCON-157 Project: JBoss Admin Console Issue Type: Feature Request Components: General Console Environment: Windows XP, JBoss-5.1.0.GA Admin console, ESB 4.8 Reporter: Betty Schwartz Priority: Optional I am wondering when the next release of the community version of JBoss-5.1.0.GA will happen; I just spent several hours finding and implementing the changes required to fix the issue described at http://community.jboss.org/thread/145880.pdf and first reported almost a year ago. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBADMCON-158) JBoss-5.1.0.GA Admin console

by Betty Schwartz (JIRA)

JBoss-5.1.0.GA Admin console ----------------------------- Key: JBADMCON-158 URL: https://jira.jboss.org/browse/JBADMCON-158 Project: JBoss Admin Console Issue Type: Feature Request Components: General Console Environment: Windows XP, JBoss-5.1.0.GA Admin console, ESB 4.8 Reporter: Betty Schwartz Priority: Optional I am wondering when the next release of the community version of JBoss-5.1.0.GA will happen; I just spent several hours finding and implementing the changes required to fix the issue described at http://community.jboss.org/thread/145880.pdf and first reported almost a year ago. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 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 December 2010