March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6796) Fix & re-enable ignored security tests

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-6796: -------------------------------- Summary: Fix & re-enable ignored security tests Key: AS7-6796 URL: https://issues.jboss.org/browse/AS7-6796 Project: Application Server 7 Issue Type: Task Components: Security Affects Versions: 8.0.0.Alpha1 Environment: AS8 with undertow Reporter: Tomaz Cerar Assignee: Darran Lofthouse Fix For: 8.0.0.Alpha1 AS8 with undertow fails few security tests. This issue is here just for tracking what they are so they can be fixed -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2166) Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-2166?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-2166: ---------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 899644|https://bugzilla.redhat.com/show_bug.cgi?id=899644] Merge to 4.x branch - https://source.jboss.org/changelog/JBossWS?cs=17417 > Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea > ---------------------------------------------------------------------------- > > Key: AS7-2166 > URL: https://issues.jboss.org/browse/AS7-2166 > Project: Application Server 7 > Issue Type: Sub-task > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Labels: eap6_prd_req > Fix For: 7.1.2.Final (EAP) > > > James Perkins: > {quote} > At one point there was a JIRA for OpenJDK 6, in fact I think a couple. The issue with OpenJDK 6 is in the build we use some JavaScript and OpenJDK 6 doesn't come with a JavaScript engine. I tried a couple things to get Rhino working with it as that's what the Sun JDK uses, but I think it needs to implement an SPI to get it to work. I didn't look into it much beyond that. > JDK 7 is a different issue. It's a bug in the annotation processing API which the JBoss Logging Tooling uses. I just refreshed my OpenJDK 7 update source and it looks like the bug is fixed in there. It's fixed in IcedTea as well. There could be the JavaScript issue here as well I can't actually remember, but I thought I had some successful builds with custom JDK's I compiled. > I did just try with IcedTea 7 and got some other errors. I'm building the latest upstream of OpenJDK 7 now and we'll see if it works. I'll let you know either way. > Let me know if you have any more questions on this. I did dig into a while ago a little. > {quote} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6691) SingletonService.getValue() throws NPE if not started

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6691?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6691: ---------------------------------------------- Jitka Kudrnacova <jkudrnac(a)redhat.com> made a comment on [bug 911065|https://bugzilla.redhat.com/show_bug.cgi?id=911065] Verified during 6.1.0.ER3 testing cycle. > SingletonService.getValue() throws NPE if not started > ----------------------------------------------------- > > Key: AS7-6691 > URL: https://issues.jboss.org/browse/AS7-6691 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.3.Final (EAP) > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha1 > > > It should instead throw an ISE. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6691) SingletonService.getValue() throws NPE if not started

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6691?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6691: ---------------------------------------------- Jitka Kudrnacova <jkudrnac(a)redhat.com> changed the Status of [bug 911065|https://bugzilla.redhat.com/show_bug.cgi?id=911065] from ON_QA to VERIFIED > SingletonService.getValue() throws NPE if not started > ----------------------------------------------------- > > Key: AS7-6691 > URL: https://issues.jboss.org/browse/AS7-6691 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.3.Final (EAP) > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha1 > > > It should instead throw an ISE. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6795) IronJacamar 1.0.16.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-6795: ------------------------------------ Summary: IronJacamar 1.0.16.Final Key: AS7-6795 URL: https://issues.jboss.org/browse/AS7-6795 Project: Application Server 7 Issue Type: Component Upgrade Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 8.0.0.Alpha1 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-90) Incremental Build fails if KieModule POM is invalid

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-90?page=com.atlassian.jira.plugin.... ] Mario Fusco reassigned DROOLS-90: --------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Incremental Build fails if KieModule POM is invalid > --------------------------------------------------- > > Key: DROOLS-90 > URL: https://issues.jboss.org/browse/DROOLS-90 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michael Anstis > Assignee: Mario Fusco > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6794) SQLServerXADataSource IntegratedSecurity not working when adding XA JNDI datasource

by Vedran Mikulcic (JIRA)

Vedran Mikulcic created AS7-6794: ------------------------------------ Summary: SQLServerXADataSource IntegratedSecurity not working when adding XA JNDI datasource Key: AS7-6794 URL: https://issues.jboss.org/browse/AS7-6794 Project: Application Server 7 Issue Type: Feature Request Components: Server Affects Versions: 7.1.1.Final Environment: Windows Reporter: Vedran Mikulcic Assignee: Jason Greene When setting the IntegratedSecurity in the XA datasource on JBoss to true, Microsoft's JDBC driver doesn't resolve the 'true' setting to boolean value but throws an error: {code} java.lang.NoSuchMethodException: com.microsoft.sqlserver.jdbc.SQLServerXADataSource.setIntegratedSecurity(java.lang.String) {code} This is only the issue when using the XA datasource, non XA datasources work normally. Steps to reproduce: 1. In the JBoss AS configuration\standalone\standalone.xml add a new xa-datasource to JNDI: {code} <xa-datasource jta="true" jndi-name="java:jboss/datasources/jndiName" pool-name="poolName" enabled="true" use-java-context="true" use-ccm="true">  <xa-datasource-property name="IntegratedSecurity"> true </xa-datasource-property> <xa-datasource-property name="ServerName"> localhost </xa-datasource-property> <xa-datasource-property name="DatabaseName"> MyDbName </xa-datasource-property> <xa-datasource-property name="SelectMethod"> cursor </xa-datasource-property> <xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class> <driver>sqljdbc</driver> <xa-pool> <is-same-rm-override>false</is-same-rm-override> </xa-pool> <validation> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker"/> </validation> </xa-datasource> {code} 2. Restart JBoss AS 3. Try to execute a query using the configured JNDI connection: {code} InitialContext ic = new InitialContext(); DataSource ds = (DataSource) ic.lookup("java:jboss/datasources/jndiName"); Connection conn = null; try { conn = ds.getConnection(); // try to execute something CallableStatement stmt = conn.prepareCall("{? = call some_stored_procedure()}"); stmt.execute(); } finally { if (conn != null) conn.close(); } {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1017) IronJacamar 1.0.16.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1017?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1017. ------------------------------------ Resolution: Done > IronJacamar 1.0.16.Final > ------------------------ > > Key: JBJCA-1017 > URL: https://issues.jboss.org/browse/JBJCA-1017 > Project: IronJacamar > Issue Type: Release > Components: Build > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.16.Final > > > Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1017) IronJacamar 1.0.16.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1017: -------------------------------------- Summary: IronJacamar 1.0.16.Final Key: JBJCA-1017 URL: https://issues.jboss.org/browse/JBJCA-1017 Project: IronJacamar Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.16.Final Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6791) Provide a way to add a description for a deployment

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6791?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6791: ----------------------------- Assignee: Brian Stansberry (was: Alexey Loubyansky) > Provide a way to add a description for a deployment > --------------------------------------------------- > > Key: AS7-6791 > URL: https://issues.jboss.org/browse/AS7-6791 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Sven Plath > Assignee: Brian Stansberry > Priority: Minor > > h2.Summary > It would be nice to have a feature that allows to add an *optional description* to a deployment when using the console or the web interface to deploy it. > h2.Current Situation > Currently, it is possible to deploy applications using: > {code} > deploy C:\path\to\application.jar --name=... --runtime-name=... > {code} > The _runtime-name_ is used for dependency resolution. When for example we have an application *app_A-1.0.0.jar* and deploy it using the following command_ > {code} > deploy C:\path\to\application.jar --name=app_A.jar --runtime-name=app_A-1.jar > {code} > we loose the version information of that application. > * We could write the version into the _name_ argument, however it could lead to multiple deployments of the same application when the old one is not removed before updating. > * We could add the version information into the _runtime-name_ argument, but that would be problematic when updating applications to a newer version. We would have to change the deployment-descriptor. > h2.Request > When deploying applications, we could provide an additional argument, called *description*. It would allow us to do the following: > {code} > deploy C:\path\to\application-1.0.0.jar --name=application-1.jar --description="Application v1.0.0" > {code} > When doing _/deployment=application-1.jar:read-resource_, it would result in the following output: > {code} > { > "outcome" => "success", > "result" => { > "content" => [{"hash" => bytes { > 0x10, 0xd6, 0x20, 0x46, 0x74, 0xcc, 0xe5, 0x39, > 0x7d, 0xef, 0x2e, 0xe3, 0x26, 0x45, 0x28, 0xad, > 0xa5, 0xde, 0xdd, 0x80 > }}], > "enabled" => true, > "name" => "application-1.jar", > "persistent" => true, > "runtime-name" => "application-1.jar", > "description" => "Application v1.0.0", > "subdeployment" => undefined, > "subsystem" => undefined > } > } > {code} > This description information should be kept when replacing that particular deployment, so when doing: > {code} > deploy C:\path\to\application-1.0.0.jar --name=application-1.jar --force > {code} > it should replace the existing application, but without deleting the description information. That should be removed when doing: > {code} > /deployment=application-1.jar:remove > {code} > When explicitly adding the _description_ argument to the _deploy_ command, the description has to be replaced by the new one. -- 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, 3 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 March 2013