July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-45) complete JBoss50Creator

by Alexey Loubyansky (JIRA)

complete JBoss50Creator ----------------------- Key: JBMETA-45 URL: http://jira.jboss.com/jira/browse/JBMETA-45 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: 1.0.0.CR1 Following JBMETA-20, JBoss50Creator was introduced which is supposed to parse EJB3 spec and JBoss-specific annotations and produce a merged metadata view in the form of JBoss50MetaData. -- 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

16 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMETA-20) Include JBoss extensions to EJB3

by Kabir Khan (JIRA)

Include JBoss extensions to EJB3 -------------------------------- Key: JBMETA-20 URL: http://jira.jboss.com/jira/browse/JBMETA-20 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Alexey Loubyansky Fix For: 1.0.0.Beta8 @Service and @Consumer are not picked up. I added testEJBExtensions to AnnotationEjb3UnitTestCase. The corresponding assertMyServiceBean() and assertMyService() methods will need tweaking to check for the real metadata. -- 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

16 years, 2 months

5
9
0 / 0

[JBoss JIRA] Updated: (JBAS-2750) Create integration tests using JBossCache and JBoss TM

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2750?page=all ] Brian Stansberry updated JBAS-2750: ----------------------------------- Fix Version/s: Backlog (was: JBossAS-5.0.0.CR2) This should really be done in the JBC testsuite. > Create integration tests using JBossCache and JBoss TM > ------------------------------------------------------ > > Key: JBAS-2750 > URL: http://jira.jboss.com/jira/browse/JBAS-2750 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: Backlog > > > Need to add integration tests that confirm that JBossCache works properly with JBoss TM as its transaction manager. The standalone cache unit tests use DummyTransactionManager, as use of JBoss TM requires the app server. Beginning with 4.0.4, the AS web-tier state replication tests also no longer use JBoss TM. > See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76306 for an example of the kind of thing such tests should find. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1799) Create additional integration tests for JBossCache

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1799?page=all ] Brian Stansberry updated JBAS-1799: ----------------------------------- Fix Version/s: Backlog (was: JBossAS-5.0.0.CR2) Moving to backlog. The existent AS testsuite thoroughly exercises the API. Further improvement should be done in the JBC itself by ensuring there are tests that exercise the AS call patterns using the AS configs. > Create additional integration tests for JBossCache > -------------------------------------------------- > > Key: JBAS-1799 > URL: http://jira.jboss.com/jira/browse/JBAS-1799 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Backlog > > Original Estimate: 1 week > Remaining Estimate: 1 week > > When JBossCache module is supplied through the thirdparty jar, we will need additioanl integration testing under current AS to make sure the API is compliant. > Pieces that I can think of are: > 1. Core system classes > 2. JBossAop. This one can be more volatile. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1647) Incorrect reporting by verifier of unmatchable pattern with connective OR

by Michael Neale (JIRA)

Incorrect reporting by verifier of unmatchable pattern with connective OR ------------------------------------------------------------------------- Key: JBRULES-1647 URL: http://jira.jboss.com/jira/browse/JBRULES-1647 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Verifier Affects Versions: 5.0.0-M1 Reporter: Michael Neale Assigned To: Toni Rikkola Fix For: 5.0.0-M1 rule "Gold Discount High Priority" dialect "mvel" when customer : Customer( status > "30" && < "50" ) order : OrderHeader( customer == customer , orderPriority == "3" || == "4" ) then order.setOrderDiscount( 6.0 ); end Generates this error: Restriction LiteralRestriction from rule [Gold Discount High Priority] value '== 4' and LiteralRestriction from rule [Gold Discount High Priority] value '== 3'are in conflict. Because of this, pattern that contains them can never be satisfied. when a connective (like || ==) is used, this should not be treated as a conjunction of extra literal restrictions. -- 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

16 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1341) Analytics fails on Inner Class Enums

by Steve Shabino (JIRA)

Analytics fails on Inner Class Enums ------------------------------------ Key: JBRULES-1341 URL: http://jira.jboss.com/jira/browse/JBRULES-1341 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0 Reporter: Steve Shabino Drools Analytics fails when flattening a condition with an inner-class enum like this: vs : WorkerStatus(type != WorkerStatus.Type.ON_JOB) NPE in PackageDescrFlattener when executing method: private void flatten(QualifiedIdentifierRestrictionDescr descr, AnalyticsComponent parent, int orderNumber) on line: restriction.setVariableId(variable.getId()); Running in the debugger proves that variable == null. One can reproduce this error by running analytics on the "dispatch" example in contrib/benchmarks -- 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

16 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-264) Remove the old schema binding initializer from the kernel project

by Adrian Brock (JIRA)

Remove the old schema binding initializer from the kernel project ----------------------------------------------------------------- Key: JBMICROCONT-264 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-264 Project: JBoss MicroContainer Issue Type: Sub-task Components: Deployment Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMC.2.0.0.CR1 This can't be removed until aop-mc-int no longer depends upon it. Once that has been updated to jaxb, the initializer can be moved to the spring-int 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBAS-1313) RepositorySelector should be integrated into JBoss Server

by Amit Bhayani (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1313?page=all ] Amit Bhayani updated JBAS-1313: ------------------------------- Attachment: log4j-rs-withTimerTask.zip > RepositorySelector should be integrated into JBoss Server > --------------------------------------------------------- > > Key: JBAS-1313 > URL: http://jira.jboss.com/jira/browse/JBAS-1313 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-5.0.1.CR1 > > Attachments: log4-rs.zip, log4j-rs-withTimerTask.zip, log4j-test.sar, TestingLog4j.zip > > > Often, an application will want to have its own log4j configuration and have all log messages generated go to an application-specific log file. Solutions to this problem are documented on this wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=Logging > The log4j RepositorySelector provides a clean solution to this problem without any special classloader settings. However, at the present time, a developer must create his own version of a RepositorySelector and make sure his application initializes it properly. > This can be difficult to accomplish because the RepositorySelector feature is not well known and takes time to understand. It can also be difficult to make sure that the RepositorySelector is initialized before the application makes ANY call to Logger.getLogger(). > We can instead, provide a RepositorySelector implementation as part of the JBoss Application server. If a deployer finds a log4j.xml file in the /META-INF direcotry (or /WEB-INF for WARs) it would add an entry into the RepositorySelector for that application. Then, logging from that application would use the custom log4j configuration. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-1313) RepositorySelector should be integrated into JBoss Server

by Amit Bhayani (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1313?page=comments#action_12420034 ] Amit Bhayani commented on JBAS-1313: ------------------------------------ Attached log4j-rs-withTimerTask.zip is a modified version of Log4jRepositorySelector where the deployed log4j.xml/log4j.properties files are continuously monitored for any modification and if modifications are found the log file is re created with new configuration. > RepositorySelector should be integrated into JBoss Server > --------------------------------------------------------- > > Key: JBAS-1313 > URL: http://jira.jboss.com/jira/browse/JBAS-1313 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-5.0.1.CR1 > > Attachments: log4-rs.zip, log4j-rs-withTimerTask.zip, log4j-test.sar, TestingLog4j.zip > > > Often, an application will want to have its own log4j configuration and have all log messages generated go to an application-specific log file. Solutions to this problem are documented on this wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=Logging > The log4j RepositorySelector provides a clean solution to this problem without any special classloader settings. However, at the present time, a developer must create his own version of a RepositorySelector and make sure his application initializes it properly. > This can be difficult to accomplish because the RepositorySelector feature is not well known and takes time to understand. It can also be difficult to make sure that the RepositorySelector is initialized before the application makes ANY call to Logger.getLogger(). > We can instead, provide a RepositorySelector implementation as part of the JBoss Application server. If a deployer finds a log4j.xml file in the /META-INF direcotry (or /WEB-INF for WARs) it would add an entry into the RepositorySelector for that application. Then, logging from that application would use the custom log4j configuration. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1668) Smooks Data Loader

by Mark Proctor (JIRA)

Smooks Data Loader ------------------ Key: JBRULES-1668 URL: http://jira.jboss.com/jira/browse/JBRULES-1668 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 5.0.0.M2 Create a project to allow smooks to insert filtered data into the session, making sure smooks is aware of internal drools models. -- 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

16 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008