September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-847) CodeGenerator Maven configuration misconfigures src/build paths, sets incorrect java version.

by Murray Todd Williams (JIRA)

Murray Todd Williams created JBJCA-847: ------------------------------------------ Summary: CodeGenerator Maven configuration misconfigures src/build paths, sets incorrect java version. Key: JBJCA-847 URL: https://issues.jboss.org/browse/JBJCA-847 Project: IronJacamar Issue Type: Bug Components: Code Generator Affects Versions: 1.1.0.Beta1 Reporter: Murray Todd Williams Assignee: Jesper Pedersen If one uses the CodeGenerator (via command line or Eclipse plugin) with the option to export to Maven, the resulting code (a) cannot be imported into an Eclipse Maven project, (b) cannot run a test via "mvn test" and (c) generates Eclipse code errors because the source/target are set to Java 1.5 but the @Override annotation is not allowed for Interface overrides in Java 1.5. (I've lumped these all into one JIRA ticket report because I think it can all be resolved with some tweaks to the pom.xml generation.) -- 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

11 years, 9 months

4
18
0 / 0

[JBoss JIRA] (AS7-5553) Web Console's profile help popup is confusing

by Ramesh Reddy (JIRA)

Ramesh Reddy created AS7-5553: --------------------------------- Summary: Web Console's profile help popup is confusing Key: AS7-5553 URL: https://issues.jboss.org/browse/AS7-5553 Project: Application Server 7 Issue Type: Enhancement Components: Console Affects Versions: 7.1.1.Final Reporter: Ramesh Reddy Assignee: Heiko Braun Currently in the "profile" panels, when the "help" link clicked it shows a pop-up panel, in it it has descriptions of all the fields that are on that page. It shows the dmr attribute name and it's description. However, the dmr attributes names are some times cryptic and long and not human friendly and does not show any relation to "display name" by which all the fields are shown on the page. For a user they really need to know the mapping between the dmr attribute name and display name to make sense of the descriptions. My suggestion is replace the dmr attribute name with display name; or have both on the pop-up screen. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5193) OSGi console allows to start/stop the system bundle

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5193: ----------------------------------- Summary: OSGi console allows to start/stop the system bundle Key: AS7-5193 URL: https://issues.jboss.org/browse/AS7-5193 Project: Application Server 7 Issue Type: Bug Components: Console, OSGi Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.2.0.CR1 Start/Stop on the system bundle are invalid operations -- 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

11 years, 9 months

3
6
0 / 0

[JBoss JIRA] (AS7-5120) Improve jboss maven plugin to allow to start server as embedded

by Charles Moulliard (JIRA)

Charles Moulliard created AS7-5120: -------------------------------------- Summary: Improve jboss maven plugin to allow to start server as embedded Key: AS7-5120 URL: https://issues.jboss.org/browse/AS7-5120 Project: Application Server 7 Issue Type: Feature Request Reporter: Charles Moulliard The existing jboss maven plugin allows to deploy a WAR/EAR project in a JBOSS instance installed on the machine but does not allow to start JBOSS within maven process as we can do with Glassfish or OPS4J PaxExam - https://github.com/ops4j/org.ops4j.pax.exam2/blob/exam3-milestones/contai.... So this could be interesting to improve existing maven plugin to support embedded mode -- 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

11 years, 9 months

3
8
0 / 0

[JBoss JIRA] (AS7-5550) servlet filter mapping empty string not working

by Cheng Fang (JIRA)

Cheng Fang created AS7-5550: ------------------------------- Summary: servlet filter mapping empty string not working Key: AS7-5550 URL: https://issues.jboss.org/browse/AS7-5550 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.2.0.Alpha1 Reporter: Cheng Fang Assignee: Remy Maucherat the special url pattern "" (empty string) works in servlet mapping, but not in servlet filter mapping. {quote} 12.2 Specification of Mappings ... The empty string ("") is a special URL pattern that exactly maps to the application's context root, i.e., requests of the form http://host:port/<context- root>/. {quote} The @WebFilter(urlPatterns={""}) is not triggered at request time. -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5551) LoginModule needs a TCCL setup/restore wrapper

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-5551: ---------------------------------- Summary: LoginModule needs a TCCL setup/restore wrapper Key: AS7-5551 URL: https://issues.jboss.org/browse/AS7-5551 Project: Application Server 7 Issue Type: Feature Request Components: Security Reporter: Anil Saldhana Assignee: Stefan Guilhen security subsystem has a ModuleClassLoader locator that combines module cl + tccl for the JDK jaas setup. Jason's comment: The TCCL is set to the *last* module. But yeah the problem is that its set once for the whole login stack. I think to correct this picketbox needs to wrap every login module with a TCCL setup/restore wrapper. -- 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

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8791) log4j-appender seems not working in jboss-logging (AS6 final)

by Gregoire Botquin (JIRA)

log4j-appender seems not working in jboss-logging (AS6 final) ------------------------------------------------------------- Key: JBAS-8791 URL: https://issues.jboss.org/browse/JBAS-8791 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: 6.0.0.Final Reporter: Gregoire Botquin Assignee: David Lloyd We are using some custom logger based on log4j appenders. I made a jboss-logging.xml configuration but it seems that my log4j-appender doesn't log anything. I'm working in AS6 final version. I made an example with a standard log4j appender (neither working). The category "com.sample" should be managed by the log4jappender. Every second the bean should write something, but nothing happens, the log file is not even created. I tried with other log4j loggers/ custom loggers and no success. When activating CONSOLE handler the logs are correctly written in console, but when only using the log4j-appender nothing happens after server started. The configuration file seems correct (?), but can't unfortunately check it against a documentation yet. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- <logging xmlns="urn:jboss:logging:6.0" xmlns:b="urn:jboss:bean-deployer:2.0">     <periodic-rotating-file-handler file-name="${jboss.server.log.dir}/server.log" name="FILE" autoflush="true" append="true" suffix=".yyyy-MM-dd">  <error-manager> <only-once/> </error-manager> <formatter>    <pattern-formatter pattern="%d %-5p [%c] (%t) %s%E%n"/> </formatter> </periodic-rotating-file-handler>    <console-handler name="CONSOLE" autoflush="true" target="System.out"> <error-manager> <only-once/> </error-manager> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] %s%E%n"/> </formatter> </console-handler> <log4j-appender name="Log4jAppender" class="org.apache.log4j.DailyRollingFileAppender"> <error-manager> <only-once/> </error-manager> <level name="DEBUG"/> <properties>  <property name="file">${jboss.server.log.dir}/log4j.log</property> <property name="append">true</property> <property name="datePattern">'.'yyyy-MM-dd</property> </properties> <formatter> <pattern-formatter pattern="%d %-5p [%c] %m%n"/> </formatter> </log4j-appender> <logger category="com.sample"> <level name="DEBUG"/> <handlers> <handler-ref name="Log4jAppender"/> </handlers> </logger>    <root-logger>  <level name="${jboss.server.log.threshold:INFO}"/> <handlers> <handler-ref name="Log4jAppender"/>  </handlers> </root-logger> </logging> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- package com.sample; import javax.ejb.Schedule; import javax.ejb.Stateless; import org.apache.log4j.Logger; //@Singleton @Stateless public class TestBean { public static final Logger LOG = Logger.getLogger(TestBean.class); public TestBean(){ System.out.println("TestBean is instantiated and should write someting in the log file"); LOG.info("This is information log"); } @Schedule(second="*/1", minute="*",hour="*", persistent=false) public void writeSomething(){ System.out.println("This should write something in the log file at scheduled times"); LOG.info("This is scheduled information log"); } } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

9
17
0 / 0

[JBoss JIRA] (JBRULES-3621) Declared types : Constructor with more than 255 parameters

by JP Chemali (JIRA)

JP Chemali created JBRULES-3621: ----------------------------------- Summary: Declared types : Constructor with more than 255 parameters Key: JBRULES-3621 URL: https://issues.jboss.org/browse/JBRULES-3621 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.4.0.Final Reporter: JP Chemali Assignee: Mark Proctor When declaring a class type in a drools file declare MyType i1:int i2:int ... i256:int end The generated bean contains a constructor with ALL fields parameters, which when they exceed 255, cause an unrecoverable ClassFormatError Possible solutions: - Check this limit to skip the constructor generation in org.drools.factmodel.DefaultBeanClassBuilder.generateConstructors() - Maybe an explicit annotation to disable the behavior for those who don't need it? -- 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

11 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-917) Provide the ability to :reload() through the console

by Heiko Braun (JIRA)

Provide the ability to :reload() through the console ---------------------------------------------------- Key: AS7-917 URL: https://issues.jboss.org/browse/AS7-917 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun 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

11 years, 9 months

1
3
0 / 0

[JBoss JIRA] (JGRP-1515) GossipRouter tests: port conflicts as every instance uses 12001 by default

by Bela Ban (JIRA)

Bela Ban created JGRP-1515: ------------------------------ Summary: GossipRouter tests: port conflicts as every instance uses 12001 by default Key: JGRP-1515 URL: https://issues.jboss.org/browse/JGRP-1515 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.2 We have 4 tests involving GossipRouter. They use either tunnel.xml or tcpgossip.xml, which have GR running at 12001. When 2 or more of those tests run in parallel, we get a lot of SKIPPED tests, due to the fact the a GR cannot be started as its port is already taken (in setup()). SOLUTION: instead of using tunnel.xml and tcpgossip.xml, create a stack *programmatically*, using a port for GR that's retrieved via the ResourceManager. This also has the advantage that the GR tests don't rely on config files, which might get changed. -- 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

11 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012