November 2014 - jboss-jira - Jboss List Archives

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

by shinzey shinzey (JIRA)

[ https://issues.jboss.org/browse/WFLY-4096?page=com.atlassian.jira.plugin.... ] shinzey shinzey commented on WFLY-4096: --------------------------------------- Here's the error message with hibernate.temp.use_jdbc_metadata_defaults set to false: {quote} 11:09:49,484 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "wildweb.war")]) - failure description: ("JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"wildweb.war#wwpu\".__FIRST_PHASE__ is missing [jboss.naming.context.java.app.wildweb.wildweb.test]"]) 11:09:49,562 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "wildweb.war" (runtime-name : "wildweb.war") 11:09:49,562 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.naming.context.java.app.wildweb.wildweb.test (missing) dependents: [service jboss.persistenceunit."wildweb.war#wwpu".__FIRST_PHASE__] JBAS014776: Newly corrected services: service jboss.deployment.unit."wildweb.war".beanmanager (no longer required) {quote} An interesting question is since GlassFish can make all of these work together, why can't WildFly? > 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)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-280) Recursive resolution breaks expression escaping

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-280?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-280: ------------------------------------ Summary: Recursive resolution breaks expression escaping (was: Escaped expressions are still expanded at runtime) > Recursive resolution breaks expression escaping > ----------------------------------------------- > > Key: WFCORE-280 > URL: https://issues.jboss.org/browse/WFCORE-280 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Priority: Minor > > In DMR expressions can be escaped with {{$$}}. Two passes are made in the [ExpressionResolverImpl|https://github.com/wildfly/wildfly/blob/master/con...]. The first pass changes {code}$${key}{code} to {code}${key}{code}. The second pass fully expands the expression. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-381) DefaultPropertyReplacer can't handle ${:} expression

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBMETA-381?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on JBMETA-381: ----------------------------------------- JBMETA-381 and DMR-14 are the same problem in separate codebases. > DefaultPropertyReplacer can't handle ${:} expression > ---------------------------------------------------- > > Key: JBMETA-381 > URL: https://issues.jboss.org/browse/JBMETA-381 > Project: JBoss Metadata > Issue Type: Bug > Components: common > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > If the string "${:}" is passed to default property replacer, it does not parse it as indicating File.pathSeparator; rather it treats it as the default delimiter. > ${:} resolves to an empty string. > a${:} resolves to a > ${:}a resolves to a -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-280) Escaped expressions are still expanded at runtime

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-280?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-2795 to WFCORE-280: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-280 (was: WFLY-2795) Component/s: Domain Management (was: Domain Management) > Escaped expressions are still expanded at runtime > ------------------------------------------------- > > Key: WFCORE-280 > URL: https://issues.jboss.org/browse/WFCORE-280 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Priority: Minor > > In DMR expressions can be escaped with {{$$}}. Two passes are made in the [ExpressionResolverImpl|https://github.com/wildfly/wildfly/blob/master/con...]. The first pass changes {code}$${key}{code} to {code}${key}{code}. The second pass fully expands the expression. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2795) Escaped expressions are still expanded at runtime

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2795?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-2795: -------------------------------------- Assignee: Brian Stansberry (was: James Perkins) > Escaped expressions are still expanded at runtime > ------------------------------------------------- > > Key: WFLY-2795 > URL: https://issues.jboss.org/browse/WFLY-2795 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Priority: Minor > > In DMR expressions can be escaped with {{$$}}. Two passes are made in the [ExpressionResolverImpl|https://github.com/wildfly/wildfly/blob/master/con...]. The first pass changes {code}$${key}{code} to {code}${key}{code}. The second pass fully expands the expression. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-382) Support recursive and nested expressions

by Brian Stansberry (JIRA)

Brian Stansberry created JBMETA-382: --------------------------------------- Summary: Support recursive and nested expressions Key: JBMETA-382 URL: https://issues.jboss.org/browse/JBMETA-382 Project: JBoss Metadata Issue Type: Feature Request Components: common Reporter: Brian Stansberry Assignee: Brian Stansberry For management configuration, WildFly and EAP support recursive expression resolution (where if ${x} resolves to ${y}, then ${y] is resolved) and will support nested expression resolution as well. The JBoss Metadata PropertyReplacer stuff should do the same so users get a consistent experience regardless of where they place an expression. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-276) whoami operation failed when rbac enabled but no roles assigned

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-276?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved WFCORE-276. ------------------------------------- Resolution: Won't Fix Marking as 'Won't Fix' as this failure is happening during the validation of a low level command, the recommended approach is to use a high level command. Within the CLI a high level command 'connection-info' already exists which amongst other things outputs the resulting role information from whoami so there is no benefit in adding another high level command to duplicate this. > whoami operation failed when rbac enabled but no roles assigned > --------------------------------------------------------------- > > Key: WFCORE-276 > URL: https://issues.jboss.org/browse/WFCORE-276 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > > Need to double check this is either the CLI making a call in addition to the whoami op and that call is failing or something being accessed by whoami is causing the failure. > Here is the failure for a user with no roles: - > {noformat} > [standalone@localhost:9990 /] [darranl@localhost bin]$ ./jboss-cli.sh -c --no-local-auth > Authenticating against security realm: ManagementRealm > Username: UserTwo > Password: > [standalone@localhost:9990 /] :whoami > { > "outcome" => "success", > "result" => {"identity" => { > "username" => "UserTwo", > "realm" => "ManagementRealm" > }} > } > [standalone@localhost:9990 /] :whoami(verbose=true) > Failed to get the list of the operation properties: "WFLYCTL0313: Unauthorized to execute operation 'read-operation-description' for resource '[]' -- "WFLYCTL0332: Permission denied"" > [standalone@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-275) Migrate some RBAC tests from WildFly full to core

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-275?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet commented on WFCORE-275: ------------------------------------------ AccessConstraintUtilizationTestCase -- non-core ApplicationTypeTestCase -- core -- create a variant using logging StandardRolesBasicTestCase -- core-ish -- replace war, figure out jmx, add extension to replace ds -- CliInterfaceStandardRolesBasicTestCase -- core -- HttpInterfaceStandardRolesBasicTestCase -- core -- NativeInterfaceStandardRolesBasicTestCase -- core -- Jmx2ndInterfaceStandardRolesBasicTestCase ??? -- JmxInterfaceStandardRolesBasicTestCase ??? DeploymentScannerTestCase -- core; replace sar IncludeAllRoleTestCase -- core JmxNonSensitiveTestCase -- with jmx JmxSensitiveTestCase -- with jmx LdapRoleMappingG2UTestCase -- core LdapRoleMappingU2GTestCase -- core PermissionsCoverageTestCase -- core and full ReadResourceDescriptionVsActualOperationTestCase -- core, but meh RejectingCombinationPolicyTestCase -- core RoleMappingRuntimeReconfigurationTestCase -- core RolesIntegrityCheckingTestCase -- core ValidateAddressOrOperationTestCase -- core; replace DS VaultExpressionSensitivityTestCase -- core; replace DS > Migrate some RBAC tests from WildFly full to core > ------------------------------------------------- > > Key: WFCORE-275 > URL: https://issues.jboss.org/browse/WFCORE-275 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > All RBAC integration testing is currently done in the WILDFLY project whereas the code is in WFCORE. Migrate some tests which are not related to the RBAC usage in WILDFLY to WFCORE. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-279) Upgrade to JBoss Remoting after 4.0.5.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-279: --------------------------------------- Summary: Upgrade to JBoss Remoting after 4.0.5.Final Key: WFCORE-279 URL: https://issues.jboss.org/browse/WFCORE-279 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: Darran Lofthouse Assignee: David Lloyd Fix For: 1.0.0.Alpha14 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3285) Domain directory properties only work on specific operating systems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3285?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3285: ----------------------------------------------- Jason T. Greene <jason.greene(a)redhat.com> changed the Status of [bug 1091198|https://bugzilla.redhat.com/show_bug.cgi?id=1091198] from POST to MODIFIED > Domain directory properties only work on specific operating systems > ------------------------------------------------------------------- > > Key: WFLY-3285 > URL: https://issues.jboss.org/browse/WFLY-3285 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.1.0.CR1 > Reporter: Dennis Reed > Assignee: Tomaz Cerar > > domain.sh only parses -Djboss.domain.base.dir, -Djboss.domain.log.dir, and -Djboss.domain.config.dir (used to set -Dlogging.configuration and -Dorg.jboss.boot.log.file) on Linux, Solaris, and OS X. > It does not attempt to parse these (and therefore does not set the logging properties correctly) on any other OS, including AIX. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 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 November 2014