February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6633) Complete support for OSGi JTA

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6633?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6633: -------------------------------- Description: R5 TCK compliance for JTA (was: R5 TCK compliance for JDBC ) > Complete support for OSGi JTA > ----------------------------- > > Key: AS7-6633 > URL: https://issues.jboss.org/browse/AS7-6633 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Transactions > Reporter: Thomas Diesler > > R5 TCK compliance for JTA -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6633) Complete support for OSGi JTA

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6633: ----------------------------------- Summary: Complete support for OSGi JTA Key: AS7-6633 URL: https://issues.jboss.org/browse/AS7-6633 Project: Application Server 7 Issue Type: Feature Request Components: JCA, OSGi Reporter: Thomas Diesler R5 TCK compliance for JDBC -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6632) Complete support for OSGi JDBC

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6632: ----------------------------------- Summary: Complete support for OSGi JDBC Key: AS7-6632 URL: https://issues.jboss.org/browse/AS7-6632 Project: Application Server 7 Issue Type: Feature Request Components: JMX, OSGi Reporter: Thomas Diesler R5 TCK compliance for JMX -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6632) Complete support for OSGi JDBC

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6632?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6632: -------------------------------- Component/s: JCA (was: JMX) > Complete support for OSGi JDBC > ------------------------------ > > Key: AS7-6632 > URL: https://issues.jboss.org/browse/AS7-6632 > Project: Application Server 7 > Issue Type: Feature Request > Components: JCA, OSGi > Reporter: Thomas Diesler > > R5 TCK compliance for JMX -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6632) Complete support for OSGi JDBC

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6632?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6632: -------------------------------- Description: R5 TCK compliance for JDBC (was: R5 TCK compliance for JMX ) > Complete support for OSGi JDBC > ------------------------------ > > Key: AS7-6632 > URL: https://issues.jboss.org/browse/AS7-6632 > Project: Application Server 7 > Issue Type: Feature Request > Components: JCA, OSGi > Reporter: Thomas Diesler > > R5 TCK compliance for JDBC -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6426) Jboss-cli crashes on Windows on backslash in history

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/AS7-6426?page=com.atlassian.jira.plugin.s... ] Ståle Pedersen commented on AS7-6426: ------------------------------------- yes, the latest fix for æsh was merged into as8 so thats the correct one. thanks for testing! > Jboss-cli crashes on Windows on backslash in history > ---------------------------------------------------- > > Key: AS7-6426 > URL: https://issues.jboss.org/browse/AS7-6426 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.2.0.Alpha1 > Environment: Windows 7, 64-bit > Reporter: Jarkko Rantavuori > Assignee: Alexey Loubyansky > > Note: seems to apply to latest snapshot only, not to 7.1.1. > If you use a backslash in commands (like you need to use on absolute path deployments on windows) and then press up button to go back to that command, jboss-cli crashes with > java.lang.NumberFormatException: For input string: "1B" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:492) > at java.lang.Integer.<init>(Integer.java:677) > at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120) > at java.io.FilterOutputStream.write(FilterOutputStream.java:125) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) > at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > at java.io.PrintWriter.flush(PrintWriter.java:320) > at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal.java:89) > at org.jboss.aesh.console.Console.drawLine(Console.java:923) > at org.jboss.aesh.console.Console.redrawLine(Console.java:902) > at org.jboss.aesh.console.Console.getHistoryElement(Console.java:673) > at org.jboss.aesh.console.Console.parseOperation(Console.java:476) > at org.jboss.aesh.console.Console.read(Console.java:377) > at org.jboss.aesh.console.Console.read(Console.java:331) > at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171) > at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1181) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > Press any key to continue . . . -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6630) Unable to change attributes of Mail session through cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6630?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6630: ---------------------------------------------- Tomaz Cerar <tcerar(a)redhat.com> made a comment on [bug 910282|https://bugzilla.redhat.com/show_bug.cgi?id=910282] Pull request to fix this was sent. > Unable to change attributes of Mail session through cli > ------------------------------------------------------- > > Key: AS7-6630 > URL: https://issues.jboss.org/browse/AS7-6630 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Mail > Affects Versions: 7.2.0.Alpha1, 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 7.3.0.Alpha1, 8.0.0.Alpha1 > > > Any attempt to change Mail session after it was created fails > Steps to Reproduce: In jboss-cli > 1. Create new session > /subsystem=mail/mail-session=mysession/:add(jndi-name="java:/musession") > result: > {"outcome" => "success"} > 2. Check created resource > /subsystem=mail/mail-session=mysession/:read-resource > result: > { > "outcome" => "success", > "result" => { > "custom" => undefined, > "debug" => false, > "from" => undefined, > "jndi-name" => "java:/mysession", > "server" => undefined > } > } > 3. Try to change some attribute (e.g. jndi) > /subsystem=mail/mail-session=mysession/:write-attribute(name=jndi-name,value="java:/mailsession") > result: > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: null", > "rolled-back" => true > } > > expected result: > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > Additional: > The debug attribute can be changed exactly once and only to true. Once it is turned on it cannot be changed again like the rest. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6630) Unable to change attributes of Mail session through cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6630?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6630: ---------------------------------------------- Tomaz Cerar <tcerar(a)redhat.com> changed the Status of [bug 910282|https://bugzilla.redhat.com/show_bug.cgi?id=910282] from NEW to ON_QA > Unable to change attributes of Mail session through cli > ------------------------------------------------------- > > Key: AS7-6630 > URL: https://issues.jboss.org/browse/AS7-6630 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Mail > Affects Versions: 7.2.0.Alpha1, 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 7.3.0.Alpha1, 8.0.0.Alpha1 > > > Any attempt to change Mail session after it was created fails > Steps to Reproduce: In jboss-cli > 1. Create new session > /subsystem=mail/mail-session=mysession/:add(jndi-name="java:/musession") > result: > {"outcome" => "success"} > 2. Check created resource > /subsystem=mail/mail-session=mysession/:read-resource > result: > { > "outcome" => "success", > "result" => { > "custom" => undefined, > "debug" => false, > "from" => undefined, > "jndi-name" => "java:/mysession", > "server" => undefined > } > } > 3. Try to change some attribute (e.g. jndi) > /subsystem=mail/mail-session=mysession/:write-attribute(name=jndi-name,value="java:/mailsession") > result: > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: null", > "rolled-back" => true > } > > expected result: > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > Additional: > The debug attribute can be changed exactly once and only to true. Once it is turned on it cannot be changed again like the rest. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6630) Unable to change attributes of Mail session through cli

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6630?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6630: ----------------------------- Bugzilla Update: (was: Perform) > Unable to change attributes of Mail session through cli > ------------------------------------------------------- > > Key: AS7-6630 > URL: https://issues.jboss.org/browse/AS7-6630 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Mail > Affects Versions: 7.2.0.Alpha1, 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 7.3.0.Alpha1, 8.0.0.Alpha1 > > > Any attempt to change Mail session after it was created fails > Steps to Reproduce: In jboss-cli > 1. Create new session > /subsystem=mail/mail-session=mysession/:add(jndi-name="java:/musession") > result: > {"outcome" => "success"} > 2. Check created resource > /subsystem=mail/mail-session=mysession/:read-resource > result: > { > "outcome" => "success", > "result" => { > "custom" => undefined, > "debug" => false, > "from" => undefined, > "jndi-name" => "java:/mysession", > "server" => undefined > } > } > 3. Try to change some attribute (e.g. jndi) > /subsystem=mail/mail-session=mysession/:write-attribute(name=jndi-name,value="java:/mailsession") > result: > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: null", > "rolled-back" => true > } > > expected result: > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > Additional: > The debug attribute can be changed exactly once and only to true. Once it is turned on it cannot be changed again like the rest. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6426) Jboss-cli crashes on Windows on backslash in history

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/AS7-6426?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori commented on AS7-6426: ---------------------------------------- wasn't able to reproduce on latest snapshot. Note: latest version I tested claims to be 8.0.0-Alpha1, so I don't know if there is separate for 7.x > Jboss-cli crashes on Windows on backslash in history > ---------------------------------------------------- > > Key: AS7-6426 > URL: https://issues.jboss.org/browse/AS7-6426 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.2.0.Alpha1 > Environment: Windows 7, 64-bit > Reporter: Jarkko Rantavuori > Assignee: Alexey Loubyansky > > Note: seems to apply to latest snapshot only, not to 7.1.1. > If you use a backslash in commands (like you need to use on absolute path deployments on windows) and then press up button to go back to that command, jboss-cli crashes with > java.lang.NumberFormatException: For input string: "1B" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:492) > at java.lang.Integer.<init>(Integer.java:677) > at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120) > at java.io.FilterOutputStream.write(FilterOutputStream.java:125) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) > at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > at java.io.PrintWriter.flush(PrintWriter.java:320) > at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal.java:89) > at org.jboss.aesh.console.Console.drawLine(Console.java:923) > at org.jboss.aesh.console.Console.redrawLine(Console.java:902) > at org.jboss.aesh.console.Console.getHistoryElement(Console.java:673) > at org.jboss.aesh.console.Console.parseOperation(Console.java:476) > at org.jboss.aesh.console.Console.read(Console.java:377) > at org.jboss.aesh.console.Console.read(Console.java:331) > at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171) > at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1181) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > Press any key to continue . . . -- 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, 4 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 February 2013