March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4219) Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs.

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-4219?page=com.atlassian.jira.plugin.s... ] Pavel Janousek moved JBPAPP-8487 to AS7-4219: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4219 (was: JBPAPP-8487) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.2.Final (was: EAP 6.0.0 ER 3_Beta1) Component/s: Web (was: Web) Security: (was: JBoss Internal) Docs QE Status: (was: NEW) > Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs. > ---------------------------------------------------------------------------------------- > > Key: AS7-4219 > URL: https://issues.jboss.org/browse/AS7-4219 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.2.Final > Reporter: Pavel Janousek > Assignee: Remy Maucherat > Priority: Blocker > > Invalid web.xml deployment descriptor like this: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" metadata-complete="false"> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > </web-app> > {code} > isn't rejected during deploying a such WAR application. > Uniqueness of <servlet-name> is requirement of Servlet deployment descriptor. -- 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-4190) add xa properties to xa-data-source add command

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-4190: -------------------------------------- Summary: add xa properties to xa-data-source add command Key: AS7-4190 URL: https://issues.jboss.org/browse/AS7-4190 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.2.Final The add command is based on the add operation exposed by the management model which doesn't accept xa properties, which means the added xa datasource is not in a fully initialized state to be enabled. With the recently added feature, default sub-commands of generic type commands can be overriden with custom handlers. So, from the users' perspective I think it'd be much more convenient to have add actually create a fully initialized datasource. -- 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
1
0 / 0

[JBoss JIRA] (AS7-4218) Additional optimisation for SASL / JAAS integration when non-JAAS realm used for authentication

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4218: ------------------------------------- Summary: Additional optimisation for SASL / JAAS integration when non-JAAS realm used for authentication Key: AS7-4218 URL: https://issues.jboss.org/browse/AS7-4218 Project: Application Server 7 Issue Type: Task Components: Domain Management, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.2.Final The JAAS based authentication and related caching makes an assumption that a username and password is available for the authentication process - where a user has already been authenticated using a SASL mechanisms this is most likely not the case e.g. Digest, Kerberos... To bridge this gap we create a fake username and password before the JAAS call - this task is to optimise that so that if a connection is held open the same generated username and password should be used so that any cached value can be used without triggering a JAAS auth for each call. -- 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-3901) jsr88 enterprise deployment URI processing does not take IP stack preference into account

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-3901: ---------------------------------------- Summary: jsr88 enterprise deployment URI processing does not take IP stack preference into account Key: AS7-3901 URL: https://issues.jboss.org/browse/AS7-3901 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.1.0.Final Reporter: Richard Achmatowicz Assignee: David Lloyd The test case org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase testDistributeWebApp is failing with the following exception when the testsuite is started with IPv6 addresses as follows: {noformat} ./integration-tests.sh clean install -Dnode0=::1 -Dnode1=::1 -DudpGroup=ff0e::1 -Dipv6 {noformat} The exception is: {noformat} <failure message="expected:<Completed> but was:<Failed>" type="java.lang.AssertionError">java.lang.AssertionError: expected:<Completed> but was:<Failed> at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:147) at org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase.testDistributeWebApp(EnterpriseDeploymentTestCase.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) </failure> <system-out> 10:39:34,387 INFO [org.jboss.as.ee.deployment.spi] (Thread-31) JBAS016100: Begin deploy: [target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7,parent=null,type=war,id=file:/tmp/deployment-web.war] Distribute failed on target: org.jboss.as.ee.deployment.spi.DeploymentManagerTarget@5b39626c: java.lang.RuntimeException: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:114) at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:47) at org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79) at org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.executeDeploymentPlan(DeploymentManagerTarget.java:203) at org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.deploy(DeploymentManagerTarget.java:126) at org.jboss.as.ee.deployment.spi.DeploymentWorker.run(DeploymentWorker.java:64) Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:168) at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:138) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:62) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:106) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:89) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:253) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:152) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:112) ... 5 more </system-out> {noformat} -- 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
6
0 / 0

[JBoss JIRA] (AS7-2245) Help text needed for topics

by Kevin Barfield (Created) (JIRA)

Help text needed for topics --------------------------- Key: AS7-2245 URL: https://issues.jboss.org/browse/AS7-2245 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Kevin Barfield Assignee: Heiko Braun There needs to be help text for each topic in the console - this help text should explain what the topic is, why it is important to the user, and maybe a link to the relevant docs section. This needs to be understandable by average people For example: Datasource Configurations Datasources are used to connect JBoss EAP to databases. This page allows admins to view existing datasources Admins can also create, modify, and delete datasources. Please see the datasource section of the documentation for more details about datasources <link>. -- 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-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, 3 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, 3 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, 3 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, 3 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, 3 months

2
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 March 2012