November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-869) Session created if it doesn't exist even if authentication does not occur.

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-869: ----------------------------------------- Summary: Session created if it doesn't exist even if authentication does not occur. Key: SECURITY-869 URL: https://issues.jboss.org/browse/SECURITY-869 Project: PicketBox Issue Type: Bug Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_3_5.Final -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4096) Datasource Defined in web.xml Does Not Work with JPA Entity Manager

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-4096?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-4096: ------------------------------------ I know about the CDI issue. There are other issues as well. The persistence unit has to be started, very early in deployment (before any application classes are loaded so that entity class rewriting works), but the CDI beanmanager will not be ready until very late. Same is true for datasources created in the deployment (@DataSourceDefinition). Can we start the CDI beanmanager earlier? I was told no, as the application classloader is expected to be used. Can we start application defined datasources early? I was told no on that as well. This all came up on the as7 or wildfly development email list before. Regarding the hibernate.temp.use_jdbc_metadata_defaults property, did you get any further in Hibernate with that (if you looked at the deployment exception call stack?) > Datasource Defined in web.xml Does Not Work with JPA Entity Manager > ------------------------------------------------------------------- > > Key: WFLY-4096 > URL: https://issues.jboss.org/browse/WFLY-4096 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate, Web (JBoss Web) > Affects Versions: 8.1.0.Final > Environment: Windows 7 > Java 8u25 > WildFly 8.1.0.Final > Reporter: shinzey shinzey > Assignee: Scott Marlow > Priority: Critical > Labels: datasource, deployment, jpa, persistence.xml, persistenceUnit > > The datasource defined in web.xml: > {quote} > <data-source> > <name>java:/datasources/test</name> > <class-name>org.apache.derby.jdbc.ClientDataSource</class-name> > <database-name>test</database-name> > <url>jdbc:derby://localhost:1527/test</url> > <user>test</user> > <password>test</password> > </data-source> > {quote} > The persistence unit: > {quote} > <persistence-unit name="wtpu" transaction-type="JTA"> > <jta-data-source>java:/datasources/test</jta-data-source> > </persistence-unit> > {quote} > The deployment error: > {quote} > 17:57:10,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "WebTest.war" (runtime-name: "WebTest.war") > 17:57:11,078 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for wtpu > 17:57:11,172 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "WebTest.war")]) - failure description: ("JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"WebTest.war#wtpu\".__FIRST_PHASE__ is missing [jboss.naming.context.java.datasources.test]"]) > 17:57:11,187 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "WebTest.war" (runtime-name : "WebTest.war") > 17:57:11,187 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.naming.context.java.datasources.test (missing) dependents: [service jboss.persistenceunit."WebTest.war#wtpu".__FIRST_PHASE__] > {quote} > If I remove the persistence unit, the datasource can be successfully bound: > {quote} > 17:55:47,851 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/datasources/test] > {quote} > The same code works as expected in GlassFish 4.1, and the @DataSourceDefinition annotation has the same issue. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-273) ServerInventory#reconnectServer should take auto-start into account

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-458 to WFCORE-273: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-273 (was: WFLY-458) Component/s: Domain Management (was: Domain Management) Fix Version/s: 1.0.0.CR1 (was: 9.0.0.Beta1) > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFCORE-273 > URL: https://issues.jboss.org/browse/WFCORE-273 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > Fix For: 1.0.0.CR1 > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-272) Provide a "default" role for management users with no other role specified

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-272?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1895 to WFCORE-272: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-272 (was: WFLY-1895) Component/s: Domain Management Security (was: Domain Management) (was: Security) Fix Version/s: 1.0.0.CR1 (was: 9.0.0.Beta1) > Provide a "default" role for management users with no other role specified > -------------------------------------------------------------------------- > > Key: WFCORE-272 > URL: https://issues.jboss.org/browse/WFCORE-272 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Jakub Cechacek > Assignee: Emanuel Muckenhuber > Labels: rbac-filed-by-qa > Fix For: 1.0.0.CR1 > > > Currently it seems that when using RBAC provider users with no defined role are unable to read domain model at all. Consequently logging into Admin Console leads to 500 error page. Similar errors in CLI. > In relation to this, it should be considered what is the expected behavior of unsecured management interface. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4112) Update Wildfly JDF Stacks (BOM) for 8.2.0.Final

by Cody Lerum (JIRA)

Cody Lerum created WFLY-4112: -------------------------------- Summary: Update Wildfly JDF Stacks (BOM) for 8.2.0.Final Key: WFLY-4112 URL: https://issues.jboss.org/browse/WFLY-4112 Project: WildFly Issue Type: Feature Request Affects Versions: 8.1.0.Final Reporter: Cody Lerum Assignee: Tomaz Cerar Fix For: 8.1.0.Final The JDF stacks haven't been updated for Wildfly 8.1.0.Final This creates an issue for users wishing to keep the provided impl versions in sync with their project for debugging purposes. For example org.wildfly.bom:jboss-javaee-7.0-with-hibernate:8.0.0.Final specifes hibernate-search version 4.5.0.Final while Wildfly 8.1.0.Final bundles 4.5.1.Final -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4112) Update Wildfly JDF Stacks (BOM) for 8.2.0.Final

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-4112?page=com.atlassian.jira.plugin.... ] Cody Lerum updated WFLY-4112: ----------------------------- Fix Version/s: (was: 8.1.0.Final) Affects Version/s: 8.2.0.Final (was: 8.1.0.Final) Description: The JDF stacks haven't been updated for Wildfly 8.2.0.Final This creates an issue for users wishing to keep the provided impl versions in sync with their project for debugging purposes. was: The JDF stacks haven't been updated for Wildfly 8.1.0.Final This creates an issue for users wishing to keep the provided impl versions in sync with their project for debugging purposes. For example org.wildfly.bom:jboss-javaee-7.0-with-hibernate:8.0.0.Final specifes hibernate-search version 4.5.0.Final while Wildfly 8.1.0.Final bundles 4.5.1.Final > Update Wildfly JDF Stacks (BOM) for 8.2.0.Final > ----------------------------------------------- > > Key: WFLY-4112 > URL: https://issues.jboss.org/browse/WFLY-4112 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 8.2.0.Final > Reporter: Cody Lerum > Assignee: Tomaz Cerar > > The JDF stacks haven't been updated for Wildfly 8.2.0.Final > This creates an issue for users wishing to keep the provided impl versions in sync with their project for debugging purposes. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-650. -------------------------------- Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/4aeaa9fc179ac8ccf0b2b80520493... > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-210) IO error during deployment scanning triggers undeployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-210?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-210: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1159709|https://bugzilla.redhat.com/show_bug.cgi?id=1159709] from POST to MODIFIED > IO error during deployment scanning triggers undeployment > --------------------------------------------------------- > > Key: WFCORE-210 > URL: https://issues.jboss.org/browse/WFCORE-210 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha10 > Reporter: James Livingston > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Alpha14 > > > If an IO error such as reaching the file descriptor limit occurs during deployment scanning, the scanner continues with an empty deployment list causing it to undeploy applications. > This occurs because FileSystemDeploymentService.scanDirectory() treats File.listFiles() returning null as an empty list rather than an error. http://docs.oracle.com/javase/7/docs/api/java/io/File.html#listFiles%28%29 notes that it returns an empty array if the directory is empty, and null if it is not a directory or an IO error occurs. > It should instead respond to a null return value by aborting the scanner run, with a log message, and not proceed to undeploy applications. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-650: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-451) Filter Apache CXF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-451?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-451: ---------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1166502|https://bugzilla.redhat.com/show_bug.cgi?id=1166502] from POST to MODIFIED > Filter Apache CXF > ----------------- > > Key: WFLY-451 > URL: https://issues.jboss.org/browse/WFLY-451 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 8.0.0.Alpha1 > > > Detect Apache CXF libraries in user deployment and *if* the webservices subsystem is actually being triggered for the deployment, either log a major warning or make the deployment fail. This would basically prevent later issues with users trying to deploy not properly packaged applications (e.g. the same war embedding CXF they were using on Tomcat) and making them aware of what they need to do. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2014