February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2329) Web Console: Breadcrumbs in the console to give people context of where they are in UI

by Jim Tyrrell (Created) (JIRA)

Web Console: Breadcrumbs in the console to give people context of where they are in UI -------------------------------------------------------------------------------------- Key: AS7-2329 URL: https://issues.jboss.org/browse/AS7-2329 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell It would be nice to see context of where you are in the UI. -- 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

14 years, 4 months

4
4
0 / 0

[JBoss JIRA] (AS7-2370) Web Console: Datasources do not have the "Edit" Button

by Jim Tyrrell (Created) (JIRA)

Web Console: Datasources do not have the "Edit" Button ------------------------------------------------------ Key: AS7-2370 URL: https://issues.jboss.org/browse/AS7-2370 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Attachments: Screen shot 2011-10-26 at 2.36.39 PM.png The Datasources tab in the console, does not continue the practice of an edit button for making changes to the configuration. See the screen shot for a lack of a screen shot. -- 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

14 years, 4 months

6
7
0 / 0

[JBoss JIRA] (AS7-2645) Test Connection when creating a Data Source, see screen shot

by Jim Tyrrell (Created) (JIRA)

Test Connection when creating a Data Source, see screen shot ------------------------------------------------------------ Key: AS7-2645 URL: https://issues.jboss.org/browse/AS7-2645 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Attachments: Screenshot-3.png When I am creating a data source, and put in the URL, I should have the ability to check make sure the data source URL is valid. Waiting until I have to save it off to test it is a pain, if I fat finger the URL I have about 10 more things to do, to correct it. -- 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

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (JBRULES-3401) mvel mis-parses opening comment delimiter

by Wolfgang Laun (JIRA)

Wolfgang Laun created JBRULES-3401: -------------------------------------- Summary: mvel mis-parses opening comment delimiter Key: JBRULES-3401 URL: https://issues.jboss.org/browse/JBRULES-3401 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.4.0.Beta2 Reporter: Wolfgang Laun Assignee: Mark Proctor rule x dialect "mvel" when then System.out.println( "/*" ); end Unable to Analyse Expression System.out.println( "/*" ); /: [Error: Malformed expression] [Near : {... System.out.println( "/*" ); ....}] ^ [Line: 39, Column: 0] : [Rule name='x'] -- 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

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] (JBRULES-3399) MVEL comment token /* // in java string literal in consequence causes parse error.

by Benjamin Bennett (JIRA)

Benjamin Bennett created JBRULES-3399: ----------------------------------------- Summary: MVEL comment token /* // in java string literal in consequence causes parse error. Key: JBRULES-3399 URL: https://issues.jboss.org/browse/JBRULES-3399 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.4.0.Beta2, 5.3.0.CR1 Environment: Linux x64, sun jdk 1.6 Reporter: Benjamin Bennett Assignee: Mark Proctor Priority: Minor Having a /* // comment using the mvel dialect in java string literal in the consequence causes [Error: Malformed expression] to be thrown. Looking at the lexar, all comments inside of a string cause a parse error. Similar to JBRULES-2518 but that is fixed in the current version. I wrote a test case for JBRULES-2518 merge request submitted. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9028) JARs with OSGi metadata cannot be used by EE

by David Lloyd (JIRA)

JARs with OSGi metadata cannot be used by EE -------------------------------------------- Key: JBAS-9028 URL: https://issues.jboss.org/browse/JBAS-9028 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Critical Fix For: 7.0.0.Beta3 If a JAR such as a JDBC driver or other service provider (like MSC ServiceActivation) is deployed, and that JAR happens to have OSGi metadata on it, the deployment is invisible to, or incompatible with, most of the other deployers which actually enable these services, usually on behalf of one or more subsystems. We need OSGi JARs to coexist on at least some level. A first step might be to have OSGi's modularization process use the same attachment set so that modules and resource roots can reliably be found in the DU attachments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
10
0 / 0

[JBoss JIRA] (AS7-3287) Admin console: deploying a datasource should trigger 'server reload is required'

by Jan Martiska (JIRA)

Jan Martiska created AS7-3287: --------------------------------- Summary: Admin console: deploying a datasource should trigger 'server reload is required' Key: AS7-3287 URL: https://issues.jboss.org/browse/AS7-3287 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Deploying a datasource should trigger 'server reload is required' message and require a server reload. It is necessary for example for the datasource to appear in the JNDI naming list. Editing an existing datasource triggers this, but creation does not. -- 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

14 years, 4 months

5
10
0 / 0

[JBoss JIRA] Created: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs

by Aslak Knutsen (JIRA)

Create a uber-jar for the JBoss JavaEE APIs ------------------------------------------- Key: JBEE-73 URL: https://issues.jboss.org/browse/JBEE-73 Project: JBoss JavaEE APIs Issue Type: Feature Request Components: javaee_6.0_spec Affects Versions: 1.0.0.Final-javaee_6.0 Reporter: Aslak Knutsen Assignee: Shelly McGowan My Windows users are having problems.. Windows has a limitation on how long the ClassPath can be, when you start to include libraries like, jbossas-client(249 deps) and jboss-javaee-6.0 (x) windows refuse to execute the java process. http://community.jboss.org/message/586381#586381 Would it be possible to release a uber-jar v. of the jboss-javaee-6.0 pom? Basically merge it into one artifact. Most users don't care about the individual specs, they use EE. And as long as the pom is there as well, they have both options. <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0-all</artifactId> <-- using a different artifact id is probably easier to setup --> <version>1.0.0.Final</version> <type>jar</type> <-- a single jar --> </dependency> http://maven.apache.org/plugins/maven-shade-plugin/ ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

8
10
0 / 0

[JBoss JIRA] (JBEE-96) Configure each spec to be an OSGi bundle

by Paul Gier (Created) (JIRA)

Configure each spec to be an OSGi bundle ---------------------------------------- Key: JBEE-96 URL: https://issues.jboss.org/browse/JBEE-96 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Components: general Reporter: Paul Gier Assignee: Paul Gier Fix For: JavaEE 6 Spec APIs 1.0.0 All the specs builds should be configured to produce a jar that is a valid OSGi bundle. -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] (AS7-2801) Certificate to principal mapping

by Yves Peter (Created) (JIRA)

Certificate to principal mapping -------------------------------- Key: AS7-2801 URL: https://issues.jboss.org/browse/AS7-2801 Project: Application Server 7 Issue Type: Feature Request Components: Security, Web Affects Versions: 7.1.0.Beta1 Reporter: Yves Peter Assignee: Anil Saldhana In JBoss 7 it is no longer possible to configure how a certificate is mapped to a principal using client-cert authentication. The dynamic code was removed in JBoss 7 in the JBossWebRealm and is now hard coded to use the SubjectDNMapping: http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... Also the JBossWebRealm does only consider role- but no principal-mapping modules. We use this for authentication of users against an ldap server where the dn of the user doesn't match the dn in the ldap server. Also it's useful for display purpose in an application. An example and some further information is in the linked user form thread. -- 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

14 years, 4 months

6
6
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 2012