July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2533) Update Eclipse Compiler dependency

by Fabian Lange (JIRA)

Update Eclipse Compiler dependency ---------------------------------- Key: JBRULES-2533 URL: https://jira.jboss.org/browse/JBRULES-2533 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.1.0.M2 Reporter: Fabian Lange Assignee: Mark Proctor drools-compiler pom includes a reference to eclipse JDT. in 5.0.1 this was a 4 MB core_whatever.jar Because I wanted to improve compiler performance I tried out a never eclipse compiler package. Finding it was not very easy, because eclipse seems to change group and artifact ids every day. I found a module which only contains the compiler part from eclipse 3.5.1, which works in all my tests ok. Another nice benefit was that the size of my war shrunk by 3 Megabytes, as this module is only 1.7 megs. It even helped for performance of compilation process by the way. Not that this is a main bottleneck, but we have files that take seconds to compile. My tests on my windows box with java 6 gave 5-10% improvement using the 3.5.1 jdt compiler. Here the part for the pom: {code} <dependency> <groupId>org.eclipse.jdt.core.compiler</groupId> <artifactId>ecj</artifactId> <version>3.5.1</version> </dependency> {code} -- 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

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2866) Support for Metadata in Decision Tables

by Jason Mihalick (JIRA)

Support for Metadata in Decision Tables --------------------------------------- Key: JBRULES-2866 URL: https://issues.jboss.org/browse/JBRULES-2866 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.1.1.FINAL Environment: All Reporter: Jason Mihalick Assignee: Mark Proctor Fix For: FUTURE Please add support for Metadata annotations in decision tables. Discussion thread here: http://drools-java-rules-engine.46999.n3.nabble.com/Need-help-with-Decisi... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (AS7-884) Support masking of password using Base64 for both domain model definitions of users and properties file definition of users.

by Darran Lofthouse (JIRA)

Support masking of password using Base64 for both domain model definitions of users and properties file definition of users. ---------------------------------------------------------------------------------------------------------------------------- Key: AS7-884 URL: https://issues.jboss.org/browse/AS7-884 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-8470) SocketBinding.createMulticastSocket() not safe across platforms

by Brian Stansberry (JIRA)

SocketBinding.createMulticastSocket() not safe across platforms --------------------------------------------------------------- Key: JBAS-8470 URL: https://jira.jboss.org/browse/JBAS-8470 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.M2 The usage of java.net.MulticastSocket is one of the areas where the JDK does a poor job of abstracting away the underlying OS. Patterns of MulticastSocket construction that work well on BSD-based OSs don't work on Windows and vice versa. SocketBinding.createMulticastSocket() should adapt the code used in JGroups for dealing with this. -- 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

12 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (AS7-1219) Add jboss-dmr documentation to the Admin Guide

by Brian Stansberry (JIRA)

Add jboss-dmr documentation to the Admin Guide ---------------------------------------------- Key: AS7-1219 URL: https://issues.jboss.org/browse/AS7-1219 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Basic documentation on DMR: 1) Purpose 2) Source location and maven coordinates 3) Description of the 2 public classes, ModelNode and ModelType, link to 1.0.0.Final code for each on github 4) Some simple examples 5) Fully document the string format, so people know how to read DMR output and how to write DMR input 6) Links to 5) above in the CLI docs, both in a place that describes how to read output and in a place that describes the format for parameter values in low-level operation requests -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
13
0 / 0

[JBoss JIRA] Created: (AS7-1221) HTTP management API section in the Admin Guide

by Brian Stansberry (JIRA)

HTTP management API section in the Admin Guide ---------------------------------------------- Key: AS7-1221 URL: https://issues.jboss.org/browse/AS7-1221 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry We need a technical guide to the HTTP management API. The "Management clients" section gives a basic overview. But it should reference a separate section that documents the usage of GET and POST, the URL patterns, the JSON representation of DMR etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (AS7-1298) JBoss AS 7 doesn't appear to support container-managed security via web.xml and jboss-web.xml

by Craig Ringer (JIRA)

JBoss AS 7 doesn't appear to support container-managed security via web.xml and jboss-web.xml --------------------------------------------------------------------------------------------- Key: AS7-1298 URL: https://issues.jboss.org/browse/AS7-1298 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.0.0.Final, 7.1.0.Alpha1 Environment: n/a Reporter: Craig Ringer There's no documentation for container-managed security in JBoss AS 7, and the schema for the main jboss config files and jboss-web.xml don't suggest any configuration mechanisms for JAAS realms, principal-to-user/group mappings, etc. This is a significant limitation for apps porting from Glassfish 3, which expect to be able to access the current security principal from JNDI or inject it, and expect to be able to declare container-controlled access to particular URLs and different HTTP methods in web.xml. Documenting this limitation in AS 7.0.0 would be a big improvement and would save porting time and hassle. Implementing support in a future version would, of course, be ideal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (JGRP-1322) Discovery protocol based on mod-cluster

by alex soto (JIRA)

Discovery protocol based on mod-cluster --------------------------------------- Key: JGRP-1322 URL: https://issues.jboss.org/browse/JGRP-1322 Project: JGroups Issue Type: Feature Request Reporter: alex soto Assignee: Bela Ban It would be nice to have a discovery protocol that can use mod-cluster as the source of the node information. Mod-cluster already knows the list of participating nodes and provides this information in a well known format, so it could be simple to implement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-8955) Injection of a WebServiceContext in an Interceptor fails when deployed.

by Peer Bech Hansen (JIRA)

Injection of a WebServiceContext in an Interceptor fails when deployed. ----------------------------------------------------------------------- Key: JBAS-8955 URL: https://issues.jboss.org/browse/JBAS-8955 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: Windows 7 US, JDK 1.6.22 Reporter: Peer Bech Hansen Assignee: Carlo de Wolf Fix For: 6.0.0.Final http://community.jboss.org/message/589104 public class WebserviceLogInterceptor { @Resource private WebServiceContext wsc; @AroundInvoke public Object logCall(InvocationContext context) throws Exception { try { return context.proceed(); } catch (Exception e) { throw e; } } } org.jboss.deployers.spi.DeploymentException: Error deploying Project-1.0-SNAPSHOT.jar: Exception while processing container metadata for EJB: DemoService in unit: Project-1.0-SNAPSHOT.jar at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:196) at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:99) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.Exception: Exception while processing container metadata for EJB: DemoService in unit: Project-1.0-SNAPSHOT.jar at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:549) at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189) ... 29 more Caused by: java.lang.ArrayStoreException: org.jboss.injection.WebServiceContextPropertyInjector at java.util.AbstractCollection.toArray(AbstractCollection.java:171) at org.jboss.ejb3.interceptor.InterceptorInjector.(InterceptorInjector.java:42) at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:610) at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:418) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:527) ... 30 more 18:01:38,527 WARN Re: Bug: injecting WebServiceContext at AroundInvoke Failed to process changes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2853) ResourceFactory.newClassPathResource(drlPath) behaves differently on different platforms (linux, windows): it parses the file with different encodings

by Geoffrey De Smet (JIRA)

ResourceFactory.newClassPathResource(drlPath) behaves differently on different platforms (linux, windows): it parses the file with different encodings ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-2853 URL: https://issues.jboss.org/browse/JBRULES-2853 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Critical This really sucks for non English people :) English people write in pure ASCII, so they don't suffer from this problem. French, Dutch etc mix in Latin-1 chars. Russian, Chinese use something else. The root problem: There are 2 ways to create an InputStream: - with encoding = GOOD, use encoding "UTF-8" and there are no problems. - without encoding: use the default platform encoding = BAD -- Linux: UTF-8, Windows in Belgium: Latin-1, Windows in China: Chinese-1, Windows in Sweden: Latin-2, ... -- Java's InputStream should have just defaulted it on UTF-8 Proposition 1: Overloaded method which has an extra String encoding: - ResourceFactory.newClassPathResource(drlPath, encoding) - similar tactic as InputStream Proposition 2: Keep it simple. We decide what a DRL file is. Just like an XML file says to hell with the specified encoding, so can we. Note: All XML files default to UTF-8 encoding, and you can overwrite it in a header in the XML file itself (= self-describing): no need to mess around in the java code. Same principle: All DRL files are default UTF-8 encoding. Optionally we can define an encoding header later. I strongly prefer proposition 2. The world has got enough encoding problems. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
15
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011