January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2574) setter declared in a superclass prevents SAR deployments from being deployed

by Radim Hanus (Created) (JIRA)

setter declared in a superclass prevents SAR deployments from being deployed ---------------------------------------------------------------------------- Key: AS7-2574 URL: https://issues.jboss.org/browse/AS7-2574 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.2.Final Reporter: Radim Hanus java.lang.IllegalStateException: No such set method for property 'xxx' found on class XXX is thrown when the property setter is not declared in bean class but superclass -- 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, 3 months

8
9
0 / 0

[JBoss JIRA] (AS7-3214) RESTEasy: Resource with resource method with more than one parameter that is not annotated isn't rejected, nor warning generated

by Pavel Janousek (Moved) (JIRA)

[ https://issues.jboss.org/browse/AS7-3214?page=com.atlassian.jira.plugin.s... ] Pavel Janousek moved JBPAPP-7874 to AS7-3214: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3214 (was: JBPAPP-7874) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.0.CR1b (was: EAP 6.0.0 DR 9) Component/s: REST (was: RESTEasy) Security: (was: JBoss Internal) Docs QE Status: (was: NEW) > RESTEasy: Resource with resource method with more than one parameter that is not annotated isn't rejected, nor warning generated > -------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-3214 > URL: https://issues.jboss.org/browse/AS7-3214 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Weinan Li > > Section 3.3.2.1. of JAX-RS 1.1. specs says: > <cite> > 3.3.2.1 Entity Parameters > The value of a non-annotated parameter, called the entity parameter, is mapped from the request entity body. Conversion between an entity body and a Java type is the responsibility of an entity provider, see section 4.2. > Resource methods MUST NOT have more than one parameter that is not annotated with one of the above-listed annotations. > </cite> > If Reource contains methos that isn't conformed with second paragraph,actual behavior is only saying "404 - not found" when someone do access to a such "endpoint". I think we should provide better handling of this situation - I prefer rejecting of a such resource during deploying the JAX-RS application, but at least some warning could be generated at this situation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3213) RESTEasy: Actual implementation doesn't met 3.3.1 requirement (Visibility) of JAX-RS 1.1. specs

by Pavel Janousek (Moved) (JIRA)

[ https://issues.jboss.org/browse/AS7-3213?page=com.atlassian.jira.plugin.s... ] Pavel Janousek moved JBPAPP-7872 to AS7-3213: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3213 (was: JBPAPP-7872) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.0.CR1b (was: EAP 6.0.0 DR 9) Component/s: REST (was: RESTEasy) Security: (was: JBoss Internal) Docs QE Status: (was: NEW) > RESTEasy: Actual implementation doesn't met 3.3.1 requirement (Visibility) of JAX-RS 1.1. specs > ----------------------------------------------------------------------------------------------- > > Key: AS7-3213 > URL: https://issues.jboss.org/browse/AS7-3213 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Weinan Li > Priority: Blocker > > Section 3.3.1 of JAX-RS 1.1. standard: > <cite> > 3.3.1 Visibility > Only public methods may be exposed as resource methods. An implementation +SHOULD warn+ users if a non-public method carries a method designator or @Path annotation. > </cite> > isn't met at all. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1417) Provide Arquillian clustering example for domain server

by Karel Piwko (JIRA)

Provide Arquillian clustering example for domain server ------------------------------------------------------- Key: AS7-1417 URL: https://issues.jboss.org/browse/AS7-1417 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.0.0.CR1 Reporter: Karel Piwko Assignee: Andrew Rubinger Create an example which is using a domain controller and starts two domains on a single machine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-3204) Fail to deploy war with reference to more than one virtual-host

by Luis Barreiro (Created) (JIRA)

Fail to deploy war with reference to more than one virtual-host --------------------------------------------------------------- Key: AS7-3204 URL: https://issues.jboss.org/browse/AS7-3204 Project: Application Server 7 Issue Type: Bug Components: Web Reporter: Luis Barreiro Assignee: Jean-Frederic Clere When deploying a war with the following jboss-web.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 5.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd"> <jboss-web> <virtual-host>virtual.host</virtual-host> <virtual-host>virtual.alias</virtual-host> </jboss-web> one gets the exception MSC00001: Failed to start service jboss.deployment.unit."jbossweb-virtual-host.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbossweb-virtual-host.war".PARSE: Failed to process phase PARSE of deployment "jbossweb-virtual-host.war" [...] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse "/content/jbossweb-virtual-host.war/WEB-INF/jboss-web.xml" at [5,5] at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:68) [...] that is, at least, misleading, because the XML is well formatted and is valid. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3196) ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described

by Kamal Suriyakumar (Created) (JIRA)

ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described ------------------------------------------------------------------------------------------------------- Key: AS7-3196 URL: https://issues.jboss.org/browse/AS7-3196 Project: Application Server 7 Issue Type: Clarification Components: Server Affects Versions: 7.1.0.Final, Open To Community Environment: Jboss as7 server Reporter: Kamal Suriyakumar Assignee: Jason Greene Priority: Blocker Fix For: Open To Community ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:153) at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106) at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget(AOPConstructorJoinpoint.java:282) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:103) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70) at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:66) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) 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.install(AbstractController.java:774) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:319) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:297) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76) at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:91) at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:161) at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:138) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:722) Failed to boot JBoss: java.lang.IllegalStateException: Incompletely deployed: DEPLOYMENTS IN ERROR: Deployment "AttachmentStore" is in error due to: java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File] -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-3211) If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation

by Scott Marlow (Created) (JIRA)

If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation ----------------------------------------------------------------------------------------------- Key: AS7-3211 URL: https://issues.jboss.org/browse/AS7-3211 Project: Application Server 7 Issue Type: Task Reporter: Scott Marlow Priority: Minor Fix For: 7.2.0.Alpha1 For Queries, handoff the EntityManager to a Query object wrapper and have the Query object finalizer close the EntityManager. Make sure that we respect JPA 2.0 section 3.8.6 (detach objects returned from Query object). 1. Methods that return a Query, will hand off the EM to the Query object wrapper. 2. Other methods will close the EM at the end of the EM method invocation. When making this change, make sure that performance doesn't degrade. The cost of this change, will be that each (transaction scoped non-tx) EM invocation will create a new persistence context, but we can eliminate the NonTxEmCloser which has its own overhead. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1484) Validate Apache Tomcat SingleSignonValve

by Anil Saldhana (JIRA)

Validate Apache Tomcat SingleSignonValve ---------------------------------------- Key: AS7-1484 URL: https://issues.jboss.org/browse/AS7-1484 Project: Application Server 7 Issue Type: Task Components: Web Reporter: Anil Saldhana Assignee: Marcus Moyses We need to validate the Apache SSO Valve in AS7. We need a wiki article that describes the setup for the valve. Please see the end of http://community.jboss.org/wiki/JBossAS7SecurityDomainModel to do valve configuration in jboss-web.xml of the web archive. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
8
0 / 0

[JBoss JIRA] (AS7-3208) Improve CLI output of "help" command in Windows cmd box

by Wolfgang Knauf (Created) (JIRA)

Improve CLI output of "help" command in Windows cmd box ------------------------------------------------------- Key: AS7-3208 URL: https://issues.jboss.org/browse/AS7-3208 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.CR1 Environment: Any Windows version Reporter: Wolfgang Knauf Assignee: Alexey Loubyansky Priority: Minor Attachments: clihelp.PNG Attached is a screenshot of the output of the CLI command "help" in a standard windows command window. It is very hard to read, as a dosbox by default has a width of 80 chars. Any change to improve the line wrapping? -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3209) Make platform-mbean module conform to ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Make platform-mbean module conform to ANDIAMO-2 ----------------------------------------------- Key: AS7-3209 URL: https://issues.jboss.org/browse/AS7-3209 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Final Make use of the Logger and Messages classes that are already there. -- 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, 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 January 2012