[JBoss JIRA] (ELY-34) Create a JAAS based security realm.
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-34:
-----------------------------------
Summary: Create a JAAS based security realm.
Key: ELY-34
URL: https://issues.jboss.org/browse/ELY-34
Project: WildFly Elytron
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Realms
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.0.0.Beta1
Legacy integration is always going to be a concern so should verify that we can delegate to JAAS if required.
_Delegating to JAAS is always going to simplify the password types supported so this is more of an ensure we can integrate with JAAS rather than ensure we can fully integrate with JAAS._
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3638) Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3638?page=com.atlassian.jira.plugin.... ]
Brian Stansberry edited comment on WFLY-3638 at 7/31/14 11:55 AM:
------------------------------------------------------------------
One last background comment... this test has a bunch of stuff related to letting arquillian provide a modular environment (actually starting a full server process), and then a full mock model controller etc is run inside that environment. My assumption is all that stuff about providing the environment remains in ParseAndMarshalModelsTestCase and the static utility methods will "just work", same as they do now. We don't allow an arquillian dependency in core, so we can't move any of that stuff into the utility.
was (Author: brian.stansberry):
One last background comment... this test has a bunch of stuff related to letting arquillian provide a modular environment (actually starting a full server process), and then a full mock model controller etc is run inside that environment. My assumption is all that stuff remains in ParseAndMarshalModelsTestCase and the static utility methods will "just work", same as they do now. We don't allow an arquillian dependency in core, so we can't move any of that stuff into the utility.
> Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3638
> URL: https://issues.jboss.org/browse/WFLY-3638
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Fix For: 9.0.0.Beta1
>
>
> ServerRootResourceDefinition constructor and CoreManagementResourceDefinition static methods have been deprecated.
> Replace their use with the new methods with the BootErrorCollector parameter.
> This can be done with core 1.0.0.Alpha4.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3638) Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3638?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3638:
----------------------------------------
One last background comment... this test has a bunch of stuff related to letting arquillian provide a modular environment (actually starting a full server process), and then a full mock model controller etc is run inside that environment. My assumption is all that stuff remains in ParseAndMarshalModelsTestCase and the static utility methods will "just work", same as they do now. We don't allow an arquillian dependency in core, so we can't move any of that stuff into the utility.
> Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3638
> URL: https://issues.jboss.org/browse/WFLY-3638
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Fix For: 9.0.0.Beta1
>
>
> ServerRootResourceDefinition constructor and CoreManagementResourceDefinition static methods have been deprecated.
> Replace their use with the new methods with the BootErrorCollector parameter.
> This can be done with core 1.0.0.Alpha4.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3638) Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3638?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3638:
----------------------------------------
The standaloneXmlTest, domainXmlTest and hostXmlTest methods can all be made static and provided by a utility class in wildfly-core/testsuite-core/shared. So lets add that, @Ignore this test, replace the current methods with those names with methods that throw UnsupportedOperationException, rip out all the code those current methods call, and then when we integrate the wildfly-core version with the new utility, replace the unsupported methods with calls to the utility and un-@Ignore the test.
> Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3638
> URL: https://issues.jboss.org/browse/WFLY-3638
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Fix For: 9.0.0.Beta1
>
>
> ServerRootResourceDefinition constructor and CoreManagementResourceDefinition static methods have been deprecated.
> Replace their use with the new methods with the BootErrorCollector parameter.
> This can be done with core 1.0.0.Alpha4.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3638) Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3638?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3638:
----------------------------------------
I believe this is all about ParseAndMarshalModelsTestCase.
I'm finding another conflict in this class with some other changes I'm making in core.
So instead of just changing this signature, we need to change this class so it does not rely on so many wildfly-core internals. Expose something simple in wildfly-core/testsuite-core/shared that tests like this can simply call.
> Remove use of deprecated methods from CoreManagementResourceDefinition and ServerRootResourceDefinition
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3638
> URL: https://issues.jboss.org/browse/WFLY-3638
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Fix For: 9.0.0.Beta1
>
>
> ServerRootResourceDefinition constructor and CoreManagementResourceDefinition static methods have been deprecated.
> Replace their use with the new methods with the BootErrorCollector parameter.
> This can be done with core 1.0.0.Alpha4.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3698) Could not inject persistence unit into CDI managed bean
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-3698?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-3698:
------------------------------------
probably would be better to ask questions like this on the wildfly forums. Anyway, I would enable TRACE logging for JPA to get more insight on why the persistence unit wasn't found. [Read this link for help in getting that going |https://docs.jboss.org/author/display/WFLY9/JPA+Reference+Guide#JPAReferenceGuide-Troubleshooting]
Also try the WildFly 9 nightly build, in case that helps (https://community.jboss.org/thread/224262).
> Could not inject persistence unit into CDI managed bean
> -------------------------------------------------------
>
> Key: WFLY-3698
> URL: https://issues.jboss.org/browse/WFLY-3698
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 8.1.0.Final
> Environment: Windows 8.1 64 bits, Notebook Lenovo Z570 Intel Core i7 (2nd Gen) 2670QM / 2.2 GHz , 8GB RAM, using Eclipse Luna to develop
> Reporter: Oscar Calderon
> Assignee: Stuart Douglas
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> I have a project running Spring 4 & JSF 2.1 using Primefaces 5 and Hibernate JPA 2.0. I use Wildfly 8.1 and configured a datasource pointing to an Oracle 10 database. The Wildfly datasource works fine (i've tested using plain JDBC) but when i try to create a LocalContainerEntityManagerFactoryBean through Spring i set the property persistenceUnitName to specify the name of my PU and then injecting in my DAOs using @PersistenceContext(unitName="myPersUnit").
> Using JBoss AS 7.1.1 Final works fine and even i don't need to specify persistenceUnitName and it creates as "default" and injects it to my DAOs without specifying name, but with JBoss 8.1 Final it doesn't work. With the same configuration, it shows me the next error:
> Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named persUnit in deployment
> But, when i remove the @PersistenceContext annotation from my property in my DAO, strangely it initializes the persistenceUnit as i can see in server log:
> 08:19:57,144 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-13) HHH000204: Processing PersistenceUnitInfo [
> name: persUnit
> ...]
> But when i try to inject it, it doesn't
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3698) Could not inject persistence unit into CDI managed bean
by Oscar Calderon (JIRA)
[ https://issues.jboss.org/browse/WFLY-3698?page=com.atlassian.jira.plugin.... ]
Oscar Calderon updated WFLY-3698:
---------------------------------
Description:
I have a project running Spring 4 & JSF 2.1 using Primefaces 5 and Hibernate JPA 2.0. I use Wildfly 8.1 and configured a datasource pointing to an Oracle 10 database. The Wildfly datasource works fine (i've tested using plain JDBC) but when i try to create a LocalContainerEntityManagerFactoryBean through Spring i set the property persistenceUnitName to specify the name of my PU and then injecting in my DAOs using @PersistenceContext(unitName="myPersUnit").
Using JBoss AS 7.1.1 Final works fine and even i don't need to specify persistenceUnitName and it creates as "default" and injects it to my DAOs without specifying name, but with JBoss 8.1 Final it doesn't work. With the same configuration, it shows me the next error:
Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named persUnit in deployment
But, when i remove the @PersistenceContext annotation from my property in my DAO, strangely it initializes the persistenceUnit as i can see in server log:
08:19:57,144 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-13) HHH000204: Processing PersistenceUnitInfo [
name: persUnit
...]
But when i try to inject it, it doesn't
was:
I have a project running Spring 4 & JSF 2.1 using Primefaces 5. I use Wildfly 8.1 and configured a datasource pointing to an Oracle 10 database. The Wildfly datasource works fine (i've tested using plain JDBC) but when i try to create a LocalContainerEntityManagerFactoryBean through Spring i set the property persistenceUnitName to specify the name of my PU and then injecting in my DAOs using @PersistenceContext(unitName="myPersUnit").
Using JBoss AS 7.1.1 Final works fine and even i don't need to specify persistenceUnitName and it creates as "default" and injects it to my DAOs without specifying name, but with JBoss 8.1 Final it doesn't work. With the same configuration, it shows me the next error:
Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named persUnit in deployment
But, when i remove the @PersistenceContext annotation from my property in my DAO, strangely it initializes the persistenceUnit as i can see in server log:
08:19:57,144 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-13) HHH000204: Processing PersistenceUnitInfo [
name: persUnit
...]
But when i try to inject it, it doesn't
> Could not inject persistence unit into CDI managed bean
> -------------------------------------------------------
>
> Key: WFLY-3698
> URL: https://issues.jboss.org/browse/WFLY-3698
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 8.1.0.Final
> Environment: Windows 8.1 64 bits, Notebook Lenovo Z570 Intel Core i7 (2nd Gen) 2670QM / 2.2 GHz , 8GB RAM, using Eclipse Luna to develop
> Reporter: Oscar Calderon
> Assignee: Stuart Douglas
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> I have a project running Spring 4 & JSF 2.1 using Primefaces 5 and Hibernate JPA 2.0. I use Wildfly 8.1 and configured a datasource pointing to an Oracle 10 database. The Wildfly datasource works fine (i've tested using plain JDBC) but when i try to create a LocalContainerEntityManagerFactoryBean through Spring i set the property persistenceUnitName to specify the name of my PU and then injecting in my DAOs using @PersistenceContext(unitName="myPersUnit").
> Using JBoss AS 7.1.1 Final works fine and even i don't need to specify persistenceUnitName and it creates as "default" and injects it to my DAOs without specifying name, but with JBoss 8.1 Final it doesn't work. With the same configuration, it shows me the next error:
> Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named persUnit in deployment
> But, when i remove the @PersistenceContext annotation from my property in my DAO, strangely it initializes the persistenceUnit as i can see in server log:
> 08:19:57,144 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-13) HHH000204: Processing PersistenceUnitInfo [
> name: persUnit
> ...]
> But when i try to inject it, it doesn't
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3698) Could not inject persistence unit into CDI managed bean
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3698?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3698:
------------------------------
Fix Version/s: (was: 8.1.0.Final)
(was: 8.2.0.CR1)
> Could not inject persistence unit into CDI managed bean
> -------------------------------------------------------
>
> Key: WFLY-3698
> URL: https://issues.jboss.org/browse/WFLY-3698
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: CDI / Weld
> Affects Versions: 8.1.0.Final
> Environment: Windows 8.1 64 bits, Notebook Lenovo Z570 Intel Core i7 (2nd Gen) 2670QM / 2.2 GHz , 8GB RAM, using Eclipse Luna to develop
> Reporter: Oscar Calderon
> Assignee: Stuart Douglas
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> I have a project running Spring 4 & JSF 2.1 using Primefaces 5. I use Wildfly 8.1 and configured a datasource pointing to an Oracle 10 database. The Wildfly datasource works fine (i've tested using plain JDBC) but when i try to create a LocalContainerEntityManagerFactoryBean through Spring i set the property persistenceUnitName to specify the name of my PU and then injecting in my DAOs using @PersistenceContext(unitName="myPersUnit").
> Using JBoss AS 7.1.1 Final works fine and even i don't need to specify persistenceUnitName and it creates as "default" and injects it to my DAOs without specifying name, but with JBoss 8.1 Final it doesn't work. With the same configuration, it shows me the next error:
> Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named persUnit in deployment
> But, when i remove the @PersistenceContext annotation from my property in my DAO, strangely it initializes the persistenceUnit as i can see in server log:
> 08:19:57,144 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-13) HHH000204: Processing PersistenceUnitInfo [
> name: persUnit
> ...]
> But when i try to inject it, it doesn't
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3698) Could not inject persistence unit into CDI managed bean
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3698?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3698:
------------------------------
Component/s: JPA / Hibernate
> Could not inject persistence unit into CDI managed bean
> -------------------------------------------------------
>
> Key: WFLY-3698
> URL: https://issues.jboss.org/browse/WFLY-3698
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 8.1.0.Final
> Environment: Windows 8.1 64 bits, Notebook Lenovo Z570 Intel Core i7 (2nd Gen) 2670QM / 2.2 GHz , 8GB RAM, using Eclipse Luna to develop
> Reporter: Oscar Calderon
> Assignee: Stuart Douglas
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> I have a project running Spring 4 & JSF 2.1 using Primefaces 5. I use Wildfly 8.1 and configured a datasource pointing to an Oracle 10 database. The Wildfly datasource works fine (i've tested using plain JDBC) but when i try to create a LocalContainerEntityManagerFactoryBean through Spring i set the property persistenceUnitName to specify the name of my PU and then injecting in my DAOs using @PersistenceContext(unitName="myPersUnit").
> Using JBoss AS 7.1.1 Final works fine and even i don't need to specify persistenceUnitName and it creates as "default" and injects it to my DAOs without specifying name, but with JBoss 8.1 Final it doesn't work. With the same configuration, it shows me the next error:
> Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named persUnit in deployment
> But, when i remove the @PersistenceContext annotation from my property in my DAO, strangely it initializes the persistenceUnit as i can see in server log:
> 08:19:57,144 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-13) HHH000204: Processing PersistenceUnitInfo [
> name: persUnit
> ...]
> But when i try to inject it, it doesn't
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3698) Could not inject persistence unit into CDI managed bean
by Oscar Calderon (JIRA)
Oscar Calderon created WFLY-3698:
------------------------------------
Summary: Could not inject persistence unit into CDI managed bean
Key: WFLY-3698
URL: https://issues.jboss.org/browse/WFLY-3698
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: CDI / Weld
Affects Versions: 8.1.0.Final
Environment: Windows 8.1 64 bits, Notebook Lenovo Z570 Intel Core i7 (2nd Gen) 2670QM / 2.2 GHz , 8GB RAM, using Eclipse Luna to develop
Reporter: Oscar Calderon
Assignee: Stuart Douglas
Fix For: 8.2.0.CR1, 8.1.0.Final
I have a project running Spring 4 & JSF 2.1 using Primefaces 5. I use Wildfly 8.1 and configured a datasource pointing to an Oracle 10 database. The Wildfly datasource works fine (i've tested using plain JDBC) but when i try to create a LocalContainerEntityManagerFactoryBean through Spring i set the property persistenceUnitName to specify the name of my PU and then injecting in my DAOs using @PersistenceContext(unitName="myPersUnit").
Using JBoss AS 7.1.1 Final works fine and even i don't need to specify persistenceUnitName and it creates as "default" and injects it to my DAOs without specifying name, but with JBoss 8.1 Final it doesn't work. With the same configuration, it shows me the next error:
Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named persUnit in deployment
But, when i remove the @PersistenceContext annotation from my property in my DAO, strangely it initializes the persistenceUnit as i can see in server log:
08:19:57,144 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-13) HHH000204: Processing PersistenceUnitInfo [
name: persUnit
...]
But when i try to inject it, it doesn't
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months