April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBAS-1193) EJB Timer DatabasePersistencePlugin issue

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1193?page=all ] Dimitris Andreadis reopened JBAS-1193: -------------------------------------- > EJB Timer DatabasePersistencePlugin issue > ----------------------------------------- > > Key: JBAS-1193 > URL: http://jira.jboss.com/jira/browse/JBAS-1193 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Thomas Diesler > Fix For: Closed issues from sourceforge > > > SourceForge Submitter: pyuill . > In 4.0.1 RC1 the > GeneralPurposeDatabasePersistencePlugin was changed > to use constants from the DatabasePersistencePlugin > interface for column names of the Timer table instead of > settable properties. One of the columns (INTERVAL) is a > reserved word in MySQL 4.1 > I can see three possible routes for the GPDPP: > 1) Reinstate the column name properties (perhaps > defaulting to the standard values). > 2) Respect the reserved word list in standardjbosscmp- > jdbc.xml (which can be easily expanded for particular a > DBMS). > 3) Change the INTERVAL column name. > Regards, > Peter Yuill -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1081) CreateTableDDL for EJBTimerService

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1081?page=all ] Dimitris Andreadis closed JBAS-1081. ------------------------------------ Resolution: Done > CreateTableDDL for EJBTimerService > ---------------------------------- > > Key: JBAS-1081 > URL: http://jira.jboss.com/jira/browse/JBAS-1081 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Thomas Diesler > Fix For: Closed issues from sourceforge > > > SourceForge Submitter: juanmartinez . > Hi. > > I don't if should report this as a bug, so feel free to delete this > report. > > I'm using Branch_4_0 with the PostgreSQL as the only datasource > (requirement). > > The EJBTimerService has the CreateTableDDL element defined as > > <attribute name="CreateTableDDL"> > create table TIMERS ( > TIMERID varchar(50) not null, > TARGETID varchar(50) not null, > INITIALDATE timestamp not null, > INTERVAL bigint, > INSTANCEPK other, > INFO other, > constraint timers_pk primary key (TIMERID) > ) > </attribute> > > which is a problem for PostgreSQL since the datatype "other" isn't > defined (INSTANCEPK and INFO). > > I'm hoping that another (standard) datatype could be used or > samples for the different database mappings could be provided. > > Let me know if I can provide more information. > Juan -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-1081) CreateTableDDL for EJBTimerService

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1081?page=all ] Dimitris Andreadis reopened JBAS-1081: -------------------------------------- Re-open to add proper component > CreateTableDDL for EJBTimerService > ---------------------------------- > > Key: JBAS-1081 > URL: http://jira.jboss.com/jira/browse/JBAS-1081 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Thomas Diesler > Fix For: Closed issues from sourceforge > > > SourceForge Submitter: juanmartinez . > Hi. > > I don't if should report this as a bug, so feel free to delete this > report. > > I'm using Branch_4_0 with the PostgreSQL as the only datasource > (requirement). > > The EJBTimerService has the CreateTableDDL element defined as > > <attribute name="CreateTableDDL"> > create table TIMERS ( > TIMERID varchar(50) not null, > TARGETID varchar(50) not null, > INITIALDATE timestamp not null, > INTERVAL bigint, > INSTANCEPK other, > INFO other, > constraint timers_pk primary key (TIMERID) > ) > </attribute> > > which is a problem for PostgreSQL since the datatype "other" isn't > defined (INSTANCEPK and INFO). > > I'm hoping that another (standard) datatype could be used or > samples for the different database mappings could be provided. > > Let me know if I can provide more information. > Juan -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1081) CreateTableDDL for EJBTimerService

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1081?page=all ] Dimitris Andreadis updated JBAS-1081: ------------------------------------- Component/s: Scheduling/Timers > CreateTableDDL for EJBTimerService > ---------------------------------- > > Key: JBAS-1081 > URL: http://jira.jboss.com/jira/browse/JBAS-1081 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Thomas Diesler > Fix For: Closed issues from sourceforge > > > SourceForge Submitter: juanmartinez . > Hi. > > I don't if should report this as a bug, so feel free to delete this > report. > > I'm using Branch_4_0 with the PostgreSQL as the only datasource > (requirement). > > The EJBTimerService has the CreateTableDDL element defined as > > <attribute name="CreateTableDDL"> > create table TIMERS ( > TIMERID varchar(50) not null, > TARGETID varchar(50) not null, > INITIALDATE timestamp not null, > INTERVAL bigint, > INSTANCEPK other, > INFO other, > constraint timers_pk primary key (TIMERID) > ) > </attribute> > > which is a problem for PostgreSQL since the datatype "other" isn't > defined (INSTANCEPK and INFO). > > I'm hoping that another (standard) datatype could be used or > samples for the different database mappings could be provided. > > Let me know if I can provide more information. > Juan -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4327) Embedded JBoss ignores custom classloader

by Christian Bauer (JIRA)

Embedded JBoss ignores custom classloader ----------------------------------------- Key: JBAS-4327 URL: http://jira.jboss.com/jira/browse/JBAS-4327 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Christian Bauer CVS from Tuesday: Ejb3AnnotationHandler.java, line 278: protected void populateBaseInfo() throws Exception { String ejbName = null; ejbClass = di.getClassLoader().loadClass(className); This uses the classloader of the DeploymentUnit,which is not the classloader I've been setting with Bootstrap.getInstance().setLoader(myClassLoader). Looks like there is a bug in the classloader handling that binds Embedded JBoss to Thread.... getContextClassLoader(). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4326) Overwriting an existing passwordFile with FilePassword can corrupt the file

by Thorsten Gast (JIRA)

Overwriting an existing passwordFile with FilePassword can corrupt the file --------------------------------------------------------------------------- Key: JBAS-4326 URL: http://jira.jboss.com/jira/browse/JBAS-4326 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.3 SP1 Environment: Windows XP, JDK 5 Reporter: Thorsten Gast Assigned To: Scott M Stark When you create a passwordFile with org.jboss.security.plugins.FilePassword which generates a 16 bytes long encoded password and afterwards overwrite this file with a shorter password, the second eight bytes of the former password are still in the file. When now decode tries to decrypt the password from the passwordFile it reads 16 bytes instead of the correct eight bytes and throws a BadPaddingException. Sure, the workaround to delete the file prior to generation is eligible, but wouldn't it be nicer to have it done automatically. And if it's only for all the newbies, which don't have to debug into that. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-702) Typo org.drools.RuleBaseConfiguration,101: drools.iassertBehaviour

by Juergen none (JIRA)

Typo org.drools.RuleBaseConfiguration,101: drools.iassertBehaviour ------------------------------------------------------------------ Key: JBRULES-702 URL: http://jira.jboss.com/jira/browse/JBRULES-702 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.1-m1 Reporter: Juergen none Assigned To: Mark Proctor Priority: Trivial Typo in org.drools.RuleBaseConfiguration.java, line 101: drools.iassertBehaviour 3.1-M1 -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-460) Please allow ftp downloads to "resume"

by hoogenbj (JIRA)

Please allow ftp downloads to "resume" -------------------------------------- Key: JBRULES-460 URL: http://jira.jboss.com/jira/browse/JBRULES-460 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Any Reporter: hoogenbj Assigned To: Mark Proctor Priority: Minor Hi Guys In my part of the world (South Africa) we still get dropped connections and here a 128kbps connection counts as broadband. It is extremely &*^&^$%#$ annoying if I lose a connection while trying to download a 23MB file (JBoss Rules 3.0.4 binary with deps) and I have to start from the beginning because your ftp server does not allow "resume". (I've already made 3 attempts today) PLEASE PLEASE PLEASE change it. Other parts of JBoss do allow it so why not you? I'm not sure why you disallow it. Maybe you think that people multiplexing a download over multiple connections (with DAP) put too much load on the server? Think about it: you are actually increasing the load by not allowing it, because someone like me have to make multiple attempts at downloading something before succeeding. If I have to try 3 times and come close to succeeding the first two times, it is effectively the same as three people downloading the same software. Allow resume and I'll succeed sooner and go away sooner. Again, PUHHLEASSEEE! Regards Johan Hoogenboezem -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-658) Unable to invoke global variable Service from an embedded Function()

by James DePaul (JIRA)

Unable to invoke global variable Service from an embedded Function() -------------------------------------------------------------------- Key: JBRULES-658 URL: http://jira.jboss.com/jira/browse/JBRULES-658 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Environment: Windows Reporter: James DePaul Assigned To: Mark Proctor Priority: Minor Trying to invoke a service referenced in a global variable works when invoked from the <consequence> block, but NOT from the function imbeded in the Rule definition - see code sample below: rule "Shipper Match" salience 90 when shipperGI : GateIn ( customerId == "NISSAN", primaryShipperId == "YELLOW" ) then myService.sendNotification(shipperGI, Constants.SHIPPER_MATCH); // <-- This WORKS // notifyPartNer(shipperGI, COnstants.SHIPPER_MATCH); <-- This DOES NOT work! end // Match found - notify customer function void notifyPartner(GateIn _event, String _action ) { System.out.println("Invoking Service for action = " + _action ); //myService.sendNotification(_event, _action); } -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-469) function name overloading

by Mark Proctor (JIRA)

function name overloading ------------------------- Key: JBRULES-469 URL: http://jira.jboss.com/jira/browse/JBRULES-469 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Reporter: Mark Proctor Assigned To: Mark Proctor Currently the function resolver is limited with regards to overloading and you can only use the same function name once in a package. We need to have more correct overloading and ofcourse handle multiple versions of the same function name in a package. -- 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, 3 months

2
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 April 2007