September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2684) Copy-paste bug in Activator

by Antoine Toulme (JIRA)

Copy-paste bug in Activator --------------------------- Key: JBRULES-2684 URL: https://jira.jboss.org/browse/JBRULES-2684 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow) Affects Versions: 5.2.0.M1 Reporter: Antoine Toulme Assignee: Mark Proctor Fix For: FUTURE Attachments: activator.patch The Activator of drools-flow-core contains a double assignment to a registered service. The patch attached fixes the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8037) Optimize AS build process

by Jesper Pedersen (JIRA)

Optimize AS build process ------------------------- Key: JBAS-8037 URL: https://jira.jboss.org/browse/JBAS-8037 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Affects Versions: 6.0.0.M3 Reporter: Jesper Pedersen Assignee: Paul Gier Priority: Critical The AS build process it taking way too long when there are no changes made. Do: svn co https://.... cd trunk ./build.sh Then without changing anything do ./build.sh again - result: [INFO] Total time: 5 minutes 29 seconds [INFO] Finished at: Thu May 20 05:10:56 EDT 2010 [INFO] Final Memory: 193M/452M The Nexus repo seems to be checked too frequently - but I'll let you create sub-tasks for those issues -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8378) QuerySyntaxException : Entity not mapped when code is migrated from jboss-4.2.3 to jboss-5.1.0.GA

by Raghavan TV (JIRA)

QuerySyntaxException : Entity not mapped when code is migrated from jboss-4.2.3 to jboss-5.1.0.GA ------------------------------------------------------------------------------------------------- Key: JBAS-8378 URL: https://jira.jboss.org/browse/JBAS-8378 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Hibernate service Affects Versions: JBossAS-5.1.0.GA Environment: jboss-5.1.0.GA, jdk-1.6.0_05, oracle 10g, hibernate that is bundled with jboss-5.1.0.GA Reporter: Raghavan TV Assignee: Steve Ebersole Priority: Critical We encountered this error during the migration of our j2ee app from jboss-4.2.3 to jboss-5.1.0.GA. To narrow down the issue, created a unit code to reproduce the same problem. Stack Trace --------------- 21:02:27,059 ERROR [STDERR] org.hibernate.hql.ast.QuerySyntaxException: SsoUser is not mapped [select ssou from SsoUser ssou] at org.hibernate.hql.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:181) at org.hibernate.hql.ast.tree.FromElementFactory.addFromElement(FromElementFactory.java:110) at org.hibernate.hql.ast.tree.FromClause.addFromElement(FromClause.java:93) at org.hibernate.hql.ast.HqlSqlWalker.createFromElement(HqlSqlWalker.java:277) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3056) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2945) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:251) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:134) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1650) at com.mycomp.mydomain.testhibernateprj.TestDAO.getSsoUserById(TestDAO.java:25) at com.tcs.telecom.tib.testhibernateprj.servlets.SampleServlet.processRequest(SampleServlet.java:40) at com.mycomp.mydomain.testhibernateprj.servlets.SampleServlet.doGet(SampleServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2157) no-interface view should be type-compatible with the bean type

by jaikiran pai (JIRA)

no-interface view should be type-compatible with the bean type -------------------------------------------------------------- Key: EJBTHREE-2157 URL: https://jira.jboss.org/browse/EJBTHREE-2157 Project: EJB 3.0 Issue Type: Bug Components: nointerface Affects Versions: depchain-1.0.0-alpha-2 Reporter: jaikiran pai Assignee: jaikiran pai Consider this: class Base { ... } @Stateless @LocalBean class Bean extends Base implements Blah {.. } This bean exposes a no-interface view. When a client accesses this no-interface view reference: Object nointerfaceView = ctx.lookup("Bean/no-interface"); The returned instead should be castable to Base, Blah and Bean. Currently it's only castable to the bean class type (i.e. Bean) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2680) Business Rule - Guided Editor- missing "

by Alex Porras (JIRA)

Business Rule - Guided Editor- missing " ---------------------------------------- Key: JBRULES-2680 URL: https://jira.jboss.org/browse/JBRULES-2680 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.0.FINAL Reporter: Alex Porras Assignee: Mark Proctor When adding a new business rule using the guided editor, the expression editor is not providing the following options in the drop down: - greater than - less than - greater than or equal to - less than or equal to -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWEB-179) Inconsistant Version Number and Documentation in multiple files

by Gordon Zheng (JIRA)

Inconsistant Version Number and Documentation in multiple files --------------------------------------------------------------- Key: JBWEB-179 URL: https://jira.jboss.org/browse/JBWEB-179 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossWeb-2.1.9.GA Environment: This issue affect all OS Reporter: Gordon Zheng Assignee: Remy Maucherat Multiple files listed the wrong version number for the jboss-web modules build.properties.default list the module version as 2.1.4 SNAPSHOT build.xml & dist.xml list the module version as 2.1.0 SNAPSHOT from 2008 This information leads to confusing logging information inside the JBoss Boot log. The Boot log currently identifying the jboss web version as 2.1.4-SNAPSHOT when the version is 2.1.9-GA. The Boot log information is pulled from the java\org\apache\catalina\util\ServerInfo.Properties files which in turn reference the build.properties.default file. Other files might be affected, but those are the one I have found so far. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2160) ejbCreate method not called on MDBs

by Carlo de Wolf (JIRA)

ejbCreate method not called on MDBs ----------------------------------- Key: EJBTHREE-2160 URL: https://jira.jboss.org/browse/EJBTHREE-2160 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: depchain-1.0.0 An MDB can optionally have a public ejbCreate method which functions as a post-construct life-cycle callback. EJB 3.0 5.6.3: the class or any super-class may implement the ejbCreate method -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
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 2010