May 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2364) calendar support in drools

by Mark Proctor (JIRA)

calendar support in drools -------------------------- Key: JBRULES-2364 URL: https://jira.jboss.org/jira/browse/JBRULES-2364 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.1.0.M2 -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2240) True modify

by Geoffrey De Smet (JIRA)

True modify ----------- Key: JBRULES-2240 URL: https://jira.jboss.org/jira/browse/JBRULES-2240 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Mark Proctor Fix For: 5.1.0.M1 -- 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

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2525) Deprecate Exit Points and replace it by Channels

by Edson Tirelli (JIRA)

Deprecate Exit Points and replace it by Channels ------------------------------------------------ Key: JBRULES-2525 URL: https://jira.jboss.org/browse/JBRULES-2525 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.M1 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.CR1 Deprecate the APIs and the use of exit points and replace it by the concept of Channels. The idea is exactly the same, but we feel the name Channel better matches the concept it implements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7764) Update logo in ROOT.war

by Shelly McGowan (JIRA)

Update logo in ROOT.war ----------------------- Key: JBAS-7764 URL: https://jira.jboss.org/jira/browse/JBAS-7764 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Reporter: Shelly McGowan Fix For: JBossAS-6.0.0.M3 The JBoss logo needs to be changed to use the latest JBoss by Red Hat. -- 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

16 years, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBEE-16) Audit/Fix dependencies

by Jason T. Greene (JIRA)

Audit/Fix dependencies ---------------------- Key: JBEE-16 URL: https://jira.jboss.org/jira/browse/JBEE-16 Project: JBoss JavaEE APIs Issue Type: Task Components: Deployment API, EJB API, JACC API, JASPI API, JAXR API, JCA API, JMS API, Persistence API, Servlet API, Transaction API Reporter: Jason T. Greene Assignee: Shelly McGowan Fix For: 5.2.0.Beta2 Steve noticed that we have some broken dependencies. Every javaee API jar should only have dependencies on other API jars that are truly required: <dependency> <groupId>org.jboss.javaee</groupId> <artifactId>jboss-transaction-api</artifactId> <version>1.0.1.GA</version> <exclusions> <exclusion> <groupId>org.jboss.javaee</groupId> <artifactId>jboss-servlet-api</artifactId> </exclusion> <exclusion> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging-spi</artifactId> </exclusion> <exclusion> <groupId>org.jboss</groupId> <artifactId>jboss-common-core</artifactId> </exclusion> </exclusions> </dependency> -- 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

16 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-622) A maven plugin that tells us what new plugins are available

by Pete Muir (JIRA)

A maven plugin that tells us what new plugins are available ----------------------------------------------------------- Key: JBBUILD-622 URL: https://jira.jboss.org/browse/JBBUILD-622 Project: JBoss Build System Issue Type: Feature Request Reporter: Pete Muir Assignee: John Casey Maven best practice is to lock down all plugin versions (in a super-pom) so that your builds are reproducible. Therefore, to take advantage of maven plugin updates, a periodic review of plugin versions is needed. A tool to tell you what plugins have new versions available would make this much easier. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2098) ContainerNameMetaDataProcessor generates incorrect container name for EJB packaged in a jar which resides in a .sar

by jaikiran pai (JIRA)

ContainerNameMetaDataProcessor generates incorrect container name for EJB packaged in a jar which resides in a .sar ------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2098 URL: https://jira.jboss.org/browse/EJBTHREE-2098 Project: EJB 3.0 Issue Type: Bug Components: deployers Affects Versions: bom-eap5-0.1.0, EJB3_1 1.0.7 Reporter: jaikiran pai Assignee: jaikiran pai EJBTHREE-2047 introduced the ContainerNameMetaDataProcessor which is responsible for setting the container name in the JBossEnterpriseBeanMetaData. This processor generates the container name based on the deployment unit name and its top level unit name. Currently it checks whether the toplevel unit is an .ear file: private boolean isEar(DeploymentUnit unit) { return unit.getSimpleName().endsWith(".ear") || unit.getAttachment(JBossAppMetaData.class) != null; } In case of EJBs packaged in a .jar which resides in a .sar, this check returns false (as expected) and hence the container name doesn't take into account the top level deployment. This leads to a container name which is different from what the JavaEEComponentHelper.createObjectName() method generates. Note that in it's current state, for things to work properly, these two generated names (from different sources) should match. The ContainerNameMetaDataProcessor should hence be changed to take into account any type of top level unit instead of just .ear files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBJCA-313) Support annotation in generation code

by Jeff Zhang (JIRA)

Support annotation in generation code ------------------------------------- Key: JBJCA-313 URL: https://jira.jboss.org/jira/browse/JBJCA-313 Project: JBoss JCA Issue Type: Task Components: Code Generator Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Alpha12 -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-322) get wrong filename from url string

by Jeff Zhang (JIRA)

get wrong filename from url string ---------------------------------- Key: JBJCA-322 URL: https://jira.jboss.org/jira/browse/JBJCA-322 Project: JBoss JCA Issue Type: Bug Components: Deployer Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Alpha12 In the deployer and validator, we use the code to get the filename from url string, like: int lastIndex = urlFileName.lastIndexOf(File.separator); if (lastIndex != -1) urlFileName = urlFileName.substring(lastIndex + 1); urlFileName += ".log"; here is a bug. in the windows machine, File.separator) is "\", but the url.getPath is always return like "file://c/dir/filename", that we get wrong filename -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-329) make code generation about cii optional

by Jeff Zhang (JIRA)

make code generation about cii optional ---------------------------------------- Key: JBJCA-329 URL: https://jira.jboss.org/jira/browse/JBJCA-329 Project: JBoss JCA Issue Type: Task Components: Code Generator Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Alpha12 Use CCI [Y/N/Yes/No]: -- 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

16 years, 2 months

1
2
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 May 2010