February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2564) Allow genuine cross-origin resource sharing requests for domain management

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-2564?page=com.atlassian.jira.plugin.s... ] Heiko Braun edited comment on AS7-2564 at 2/26/13 5:12 AM: ----------------------------------------------------------- The console would make use of it too: We are thinking about hosting a version on openshift and pushing through the mozilla app store. In that case we require CORS to be enabled. was (Author: heiko.braun): The console would make use of it too: We are thinking about hosting a version on openshift and pushing throiugh the mozilla app store. In that case we require CORS to be enabled. > Allow genuine cross-origin resource sharing requests for domain management > -------------------------------------------------------------------------- > > Key: AS7-2564 > URL: https://issues.jboss.org/browse/AS7-2564 > Project: Application Server 7 > Issue Type: Task > Components: Console, Domain Management > Reporter: Darran Lofthouse > Labels: Console_Authentication > Fix For: Open To Community > > > There may be future scenarios where cross-origin requests could be supported such as custom web/admin applications deployed to different to a different server. > This issue is to implement both configuration for accepted requests and support for the OPTIONS method. -- 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-6239) Attribute read for uninstalled bundle breaks console

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/AS7-6239?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori edited comment on AS7-6239 at 2/26/13 5:10 AM: ----------------------------------------------------------------- Added as an attachment. Attached both web ui stacktrace and jboss-cli stacktrace. was (Author: jrantav): It's in the forum link. Added as an attachment also. > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: AS7-6239 > URL: https://issues.jboss.org/browse/AS7-6239 > Project: Application Server 7 > Issue Type: Bug > Components: Console, OSGi > Reporter: Thomas Diesler > Attachments: unread_bundle_stacktrace.txt, unread_bundle_stacktrace_cli.txt > > -- 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-2564) Allow genuine cross-origin resource sharing requests for domain management

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-2564?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-2564: ----------------------------- Component/s: Console The console would make use of it too: We are thinking about hosting a version on openshift and pushing throiugh the mozilla app store. In that case we require CORS to be enabled. > Allow genuine cross-origin resource sharing requests for domain management > -------------------------------------------------------------------------- > > Key: AS7-2564 > URL: https://issues.jboss.org/browse/AS7-2564 > Project: Application Server 7 > Issue Type: Task > Components: Console, Domain Management > Reporter: Darran Lofthouse > Labels: Console_Authentication > Fix For: Open To Community > > > There may be future scenarios where cross-origin requests could be supported such as custom web/admin applications deployed to different to a different server. > This issue is to implement both configuration for accepted requests and support for the OPTIONS method. -- 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-6239) Attribute read for uninstalled bundle breaks console

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/AS7-6239?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori updated AS7-6239: ----------------------------------- Attachment: unread_bundle_stacktrace_cli.txt > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: AS7-6239 > URL: https://issues.jboss.org/browse/AS7-6239 > Project: Application Server 7 > Issue Type: Bug > Components: Console, OSGi > Reporter: Thomas Diesler > Attachments: unread_bundle_stacktrace.txt, unread_bundle_stacktrace_cli.txt > > -- 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-6393) Update commons-codec version to 1.6

by Jan Roman (JIRA)

[ https://issues.jboss.org/browse/AS7-6393?page=com.atlassian.jira.plugin.s... ] Jan Roman commented on AS7-6393: -------------------------------- Hello Josef, I've just checked your pull request with latest master version of source code. Build has been successful and all tests have passed. I tried on these JDKs: java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-0ubuntu1~10.04.2) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) java version "1.7.0_02" Java(TM) SE Runtime Environment (build 1.7.0_02-b13) Java HotSpot(TM) 64-Bit Server VM (build 22.0-b10, mixed mode) Regards > Update commons-codec version to 1.6 > ----------------------------------- > > Key: AS7-6393 > URL: https://issues.jboss.org/browse/AS7-6393 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Apache HttpClient (4.2.1) library depends on commons-codec version 1.6, but we use only a version 1.4 now which is not fully compatible - e.g. changed behavior of the default constructor in Base64 class (chunked/not-chunked). > The problem is then in HttpClient's SPNEGO authentication. -- 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-6239) Attribute read for uninstalled bundle breaks console

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/AS7-6239?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori updated AS7-6239: ----------------------------------- Attachment: unread_bundle_stacktrace.txt > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: AS7-6239 > URL: https://issues.jboss.org/browse/AS7-6239 > Project: Application Server 7 > Issue Type: Bug > Components: Console, OSGi > Reporter: Thomas Diesler > Attachments: unread_bundle_stacktrace.txt > > -- 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-6239) Attribute read for uninstalled bundle breaks console

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/AS7-6239?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori commented on AS7-6239: ---------------------------------------- It's in the forum link. Added as an attachment also. > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: AS7-6239 > URL: https://issues.jboss.org/browse/AS7-6239 > Project: Application Server 7 > Issue Type: Bug > Components: Console, OSGi > Reporter: Thomas Diesler > Attachments: unread_bundle_stacktrace.txt > > -- 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-6565) single jdbc driver deployed inside ear takes name of ear

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] SBS JIRA Integration updated AS7-6565: -------------------------------------- Forum Reference: https://community.jboss.org/message/799490#799490 > single jdbc driver deployed inside ear takes name of ear > -------------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Feature Request > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > We need to always give service name for jdbdriver as > {code} > deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion > {code} > even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names. > Original description was: > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- 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-6565) single jdbc driver deployed inside ear takes name of ear

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] jaikiran pai reopened AS7-6565: ------------------------------- Re-opening this since this has caused deployment failures in latest master: https://community.jboss.org/thread/221726?tstart=0 http://lists.jboss.org/pipermail/jboss-as7-dev/2013-February/007625.html > single jdbc driver deployed inside ear takes name of ear > -------------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Feature Request > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > We need to always give service name for jdbdriver as > {code} > deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion > {code} > even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names. > Original description was: > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- 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] (JBWEB-227) Globally configure a Valve for the whole JBoss.

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/JBWEB-227?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere commented on JBWEB-227: ------------------------------------------- Note that there is an example of a global in https://github.com/jfclere/sample_valves > Globally configure a Valve for the whole JBoss. > ----------------------------------------------- > > Key: JBWEB-227 > URL: https://issues.jboss.org/browse/JBWEB-227 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: All > Reporter: Mo Zo > Assignee: Jean-Frederic Clere > Labels: as7, web > > Please provide a way to set and configure a Valve globally for all applications within a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR. > Now it is only possible to configure it per application. -- 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