September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-900) JBossTS 4.16.5.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-900: ------------------------------------- Summary: JBossTS 4.16.5.Final Key: JBJCA-900 URL: https://issues.jboss.org/browse/JBJCA-900 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2936) Importing decision table from Excel: Non Ascii chars should not be corrupted

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-2936: ------------------------------------------- @Jesper Would you mind making a 2 minute pull request for it? 1) Go to this url: https://github.com/droolsjbpm/drools/blob/master/drools-decisiontables/sr... 2) Click the button "edit" 3) Make the changes 4) Use a commit comment with this jira id in it. Better yet, but this will take longer: fork drools, fix it, compile and test it, write a unit test and send it as a pull request. > Importing decision table from Excel: Non Ascii chars should not be corrupted > ---------------------------------------------------------------------------- > > Key: JBRULES-2936 > URL: https://issues.jboss.org/browse/JBRULES-2936 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Fix For: 5.5.0.CR1 > > > see > http://stackoverflow.com/questions/5298748/guvnor-rules-encoding > Excel (like windows) probably has crappy encoding standardization (as in none at all), so I suspect that we 'll need to ask the excel document what encoding (or even what locale) it is and read the data in that encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2936) Importing decision table from Excel: Non Ascii chars should not be corrupted

by Jesper S. Møller (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug... ] Jesper S. Møller edited comment on JBRULES-2936 at 9/26/12 7:22 AM: -------------------------------------------------------------------- I've just checked the JXL forum / mailing list, and the current maintainer writes that nothing much is going on, the original author is no longer around, no releases are forthcoming, and lots of patches to apply. The bug has been known there for apprx. 4 years. There isn't a link to the repository, if one exists. Given that, I'd recommend adding the workaround code at the top (only with ISO-8859-1 in place of the Windows one) ############################## WorkbookSettings ws = new WorkbookSettings(); ws.setEncoding("ISO-8859-1"); // Workaround for bug in JXL regarding compressed Unicode format Workbook workbook = Workbook.getWorkbook( inStream , ws); ############################### Their forum's consensus is to switch to POI, which also has support for the newer Excel files (OOXML). Perhaps Drools should do the same? was (Author: jespersm): I've just checked the JXL forum / mailing list, and the current maintainer writes that nothing much is going on, the original author is no longer around, no releases are forthcoming, and lots of patches to apply. The bug has been known there for apprx. 4 years. There isn't a link to the repository, if one exists. Given that, I'd recommend adding the workaround code at the top (only with ISO-8859-1 in place of the Windows one) ############################## WorkbookSettings ws = new WorkbookSettings(); ws.setEncoding("ISO-8859-1"); // Workaround for bug in JXL regarding compressed Unicode format Workbook workbook = Workbook.getWorkbook( inStream , ws); ############################### Their forum's consensus is to switch POI, which also has support for the newer Excel files (OOXML). Perhaps Drools should do the same? > Importing decision table from Excel: Non Ascii chars should not be corrupted > ---------------------------------------------------------------------------- > > Key: JBRULES-2936 > URL: https://issues.jboss.org/browse/JBRULES-2936 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Fix For: 5.5.0.CR1 > > > see > http://stackoverflow.com/questions/5298748/guvnor-rules-encoding > Excel (like windows) probably has crappy encoding standardization (as in none at all), so I suspect that we 'll need to ask the excel document what encoding (or even what locale) it is and read the data in that encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2936) Importing decision table from Excel: Non Ascii chars should not be corrupted

by Jesper S. Møller (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug... ] Jesper S. Møller commented on JBRULES-2936: ------------------------------------------- I've just checked the JXL forum / mailing list, and the current maintainer writes that nothing much is going on, the original author is no longer around, no releases are forthcoming, and lots of patches to apply. The bug has been known there for apprx. 4 years. There isn't a link to the repository, if one exists. Given that, I'd recommend adding the workaround code at the top (only with ISO-8859-1 in place of the Windows one) ############################## WorkbookSettings ws = new WorkbookSettings(); ws.setEncoding("ISO-8859-1"); // Workaround for bug in JXL regarding compressed Unicode format Workbook workbook = Workbook.getWorkbook( inStream , ws); ############################### Their forum's consensus is to switch POI, which also has support for the newer Excel files (OOXML). Perhaps Drools should do the same? > Importing decision table from Excel: Non Ascii chars should not be corrupted > ---------------------------------------------------------------------------- > > Key: JBRULES-2936 > URL: https://issues.jboss.org/browse/JBRULES-2936 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Fix For: 5.5.0.CR1 > > > see > http://stackoverflow.com/questions/5298748/guvnor-rules-encoding > Excel (like windows) probably has crappy encoding standardization (as in none at all), so I suspect that we 'll need to ask the excel document what encoding (or even what locale) it is and read the data in that encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2269) Virtual Service Manager

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2269?page=com.atlassian.jira.plug... ] Michael Anstis updated JBRULES-2269: ------------------------------------ Fix Version/s: 5.5.0.CR1 (was: 5.5.0.Beta1) > Virtual Service Manager > ----------------------- > > Key: JBRULES-2269 > URL: https://issues.jboss.org/browse/JBRULES-2269 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 5.5.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2936) Importing decision table from Excel: Non Ascii chars should not be corrupted

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug... ] Michael Anstis updated JBRULES-2936: ------------------------------------ Fix Version/s: 5.5.0.CR1 (was: 5.5.0.Beta1) > Importing decision table from Excel: Non Ascii chars should not be corrupted > ---------------------------------------------------------------------------- > > Key: JBRULES-2936 > URL: https://issues.jboss.org/browse/JBRULES-2936 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Fix For: 5.5.0.CR1 > > > see > http://stackoverflow.com/questions/5298748/guvnor-rules-encoding > Excel (like windows) probably has crappy encoding standardization (as in none at all), so I suspect that we 'll need to ask the excel document what encoding (or even what locale) it is and read the data in that encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5639) Run OSGi CT with AS7

by David Bosschaert (JIRA)

[ https://issues.jboss.org/browse/AS7-5639?page=com.atlassian.jira.plugin.s... ] David Bosschaert moved JBOSGI-499 to AS7-5639: ---------------------------------------------- Project: Application Server 7 (was: JBoss OSGi) Key: AS7-5639 (was: JBOSGI-499) Workflow: GIT Pull Request workflow (was: jira) Component/s: OSGi (was: Core Framework) Security: (was: Public) Fix Version/s: (was: Approved / Unscheduled) > Run OSGi CT with AS7 > -------------------- > > Key: AS7-5639 > URL: https://issues.jboss.org/browse/AS7-5639 > Project: Application Server 7 > Issue Type: Task > Components: OSGi > Reporter: David Bosschaert > Assignee: David Bosschaert > > The OSGi CT is currently run with the JBoss OSGi framework standalone. It should also be possible to run the CT with the AS7 integration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5090) CLI --version does not show version

by Dennis Reed (JIRA)

Dennis Reed created AS7-5090: -------------------------------- Summary: CLI --version does not show version Key: AS7-5090 URL: https://issues.jboss.org/browse/AS7-5090 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.2.Final (EAP) Reporter: Dennis Reed Assignee: Alexey Loubyansky "jboss-cli.sh --connect --version" does not actually show the version: JBoss AS release: <connect to the controller and re-run the version command to see the release info> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8014) Complete Site and Documentation for AS6 EJB

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 EJB ------------------------------------------- Key: JBAS-8014 URL: https://jira.jboss.org/jira/browse/JBAS-8014 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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

13 years, 9 months

4
6
0 / 0

[JBoss JIRA] (AS7-5284) Can't navigate to datasource statistics resources

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5284: ------------------------------------- Summary: Can't navigate to datasource statistics resources Key: AS7-5284 URL: https://issues.jboss.org/browse/AS7-5284 Project: Application Server 7 Issue Type: Bug Components: CLI, Domain Management, JCA Reporter: Brian Stansberry Assignee: Brian Stansberry [standalone@localhost:9999 /] cd subsystem=datasources/data-source=ExampleDS/statistics=pool JBAS014808: Child resource '"statistics" => "pool"' not found Same for the statistics=jdbc resource. The JMX mbean exposing the datasource resource is broken for this as well. Interestingly, navigating to the parent, and then doing :read-resource(include-runtime=true, recursive=true) shows the resource information. The CLI GUI must work this way, as it shows the resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
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 2012