[JBoss JIRA] (WFLY-2680) java:comp/DefaultDataSource doesn't work in persistence.xml
by arjan tijms (JIRA)
arjan tijms created WFLY-2680:
---------------------------------
Summary: java:comp/DefaultDataSource doesn't work in persistence.xml
Key: WFLY-2680
URL: https://issues.jboss.org/browse/WFLY-2680
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: arjan tijms
Having a persistence.xml with the following content fails the deployment on WildFly 8 CR1:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
<persistence-unit name="testPU">
<jta-data-source>java:comp/DefaultDataSource</jta-data-source>
</persistence-unit>
</persistence>
{code}
It results in the following error:
{noformat}
13:51:40,367 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "dynamic-named-query.war")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"dynamic-named-query.war#testPU\".__FIRST_PHASE__ is missing [jboss.naming.context.java.module.dynamic-named-query.dynamic-named-query.DefaultDataSource]"]}
{noformat}
When I proposed the feature for the default data source over at the Java EE JIRA (https://java.net/jira/browse/JAVAEE_SPEC-4) I intended this to work. In the description I hinted that the standard JNDI name would be the standard alternative for {{java:jboss/datasources/ExampleDS}} on JBoss. The latter indeed does work in {{persistence.xml}} using WildFly 8 CR1.
Omitting the {{jta-data-source}} element altogether *does* work, which is great. However, I foresee a lot of users tripping over this in the future and just giving up the idea of using a default data source, especially since the error message is very cryptic for new developers.
In GlassFish 4 using {{java:comp/DefaultDataSource}} in {{persistence.xml}} does work.
See also WFLY-2027 and WFLY-2158
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level
by Markus Karnik (JIRA)
[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ]
Markus Karnik edited comment on WFLY-2533 at 12/22/13 8:18 AM:
---------------------------------------------------------------
I got an error "Message: JBAS014788: Unexpected attribute 'default-encoding' encountered" when try to configure "default-encoding" server-wide by setting:
{code:title=standalone.xml|borderStyle=solid}
<servlet-container name="default" default-buffer-cache="default" stack-trace-on-error="local-only" default-encoding="UTF-8">
{code}
Stacktrace
{noformat}
12:46:02,285 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.CR1.jar:8.0.0.CR1]
at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.CR1.jar:8.0.0.CR1]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.CR1.jar:8.0.0.CR1]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[346,137]
Message: JBAS014788: Unexpected attribute 'default-encoding' encountered
{noformat}
probably you missed adding ServletContainerDefinition.DEFAULT_ENCODING to undertow/src/main/java/org/wildfly/extension/undertow/UndertowSubsystemParser_1_0.java? Line 106. jboss-web.xml method works fine.
was (Author: markus.karnik):
I got an error "Message: JBAS014788: Unexpected attribute 'default-encoding' encountered" when try to configure "default-encoding" server-wide by setting:
{code:title=standalone.xml|borderStyle=solid}
<servlet-container name="default" default-buffer-cache="default" stack-trace-on-error="local-only" default-encoding="UTF-8">
{code}
Stacktrace
{noformat}
12:46:02,285 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.CR1.jar:8.0.0.CR1]
at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.CR1.jar:8.0.0.CR1]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.CR1.jar:8.0.0.CR1]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[346,137]
Message: JBAS014788: Unexpected attribute 'default-encoding' encountered
{noformat}
propably you missed adding ServletContainerDefinition.DEFAULT_ENCODING to undertow/src/main/java/org/wildfly/extension/undertow/UndertowSubsystemParser_1_0.java? Line 106! jboss-web.xml method works.
> Add ability to set default character encoding on a subsystem level
> ------------------------------------------------------------------
>
> Key: WFLY-2533
> URL: https://issues.jboss.org/browse/WFLY-2533
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.CR1
>
>
> Stuart: the charset one should be pretty simple, just an attribute on <servlet-container?
> Stuart: ideally we would also have it in jboss-web.xml as well
> Stuart: I should also add an option to use the connector encoding
> Stuart: as connectors have their own encoding set
> Stuart: that is used to decode the URL
> Stuart: we should have an option to use the connector encoding as the default encoding
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level
by Markus Karnik (JIRA)
[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ]
Markus Karnik commented on WFLY-2533:
-------------------------------------
I got an error "Message: JBAS014788: Unexpected attribute 'default-encoding' encountered" when try to configure "default-encoding" server-wide by setting:
{code:title=standalone.xml|borderStyle=solid}
<servlet-container name="default" default-buffer-cache="default" stack-trace-on-error="local-only" default-encoding="UTF-8">
{code}
Stacktrace
{noformat}
12:46:02,285 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.CR1.jar:8.0.0.CR1]
at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.CR1.jar:8.0.0.CR1]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.CR1.jar:8.0.0.CR1]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[346,137]
Message: JBAS014788: Unexpected attribute 'default-encoding' encountered
{noformat}
propably you missed adding ServletContainerDefinition.DEFAULT_ENCODING to undertow/src/main/java/org/wildfly/extension/undertow/UndertowSubsystemParser_1_0.java? Line 106! jboss-web.xml method works.
> Add ability to set default character encoding on a subsystem level
> ------------------------------------------------------------------
>
> Key: WFLY-2533
> URL: https://issues.jboss.org/browse/WFLY-2533
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.CR1
>
>
> Stuart: the charset one should be pretty simple, just an attribute on <servlet-container?
> Stuart: ideally we would also have it in jboss-web.xml as well
> Stuart: I should also add an option to use the connector encoding
> Stuart: as connectors have their own encoding set
> Stuart: that is used to decode the URL
> Stuart: we should have an option to use the connector encoding as the default encoding
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications
by Nico Schlebusch (JIRA)
[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ]
Nico Schlebusch commented on WFLY-334:
--------------------------------------
Good day,
I am on leave and will return to the office on Monday, 6 January 2014. For any urgent matters log a support ticket with support(a)nha.co.za or at telephone 0860142536.
Kind Regards
Nico Schlebusch
The e-mail and attachments are confidential and intended only for selected recipients. If you have received it in error, you may not in any way disclose or rely on the contents. You
may not keep, copy or distribute the e-mail. Should you receive it, immediately notify the sender of the error and delete the e-mail. Also note that this form of communication is
not secure, it can be intercepted, and may not necessarily be free of errors and viruses in spite of reasonable efforts to secure this medium.
> HA Singleton deployer for applications
> --------------------------------------
>
> Key: WFLY-334
> URL: https://issues.jboss.org/browse/WFLY-334
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering, Domain Management
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
> Labels: deployers, hasingleton
> Fix For: 8.0.0.Final
>
>
> A HASingleton deployer should be provided in standalone and domain mode.
> To be able to migrate such singleton applications from former AS versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (WFLY-490) Domain Management Role Based Access Control
by Felix Winistörfer (JIRA)
[ https://issues.jboss.org/browse/WFLY-490?page=com.atlassian.jira.plugin.s... ]
Felix Winistörfer commented on WFLY-490:
----------------------------------------
Not available till 06.01.2014.
Your mail may be (or may not be) read a little bit later.
Please contact NPE.
> Domain Management Role Based Access Control
> -------------------------------------------
>
> Key: WFLY-490
> URL: https://issues.jboss.org/browse/WFLY-490
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: Authorization
> Fix For: 8.0.0.Final
>
>
> Implement some coarse permissions for domain operations. Possibly allowing a break down for subsystem, profile, server, server-group - maybe read - write - execute.
> Also consider confidentiality in exchange e.g. Can read metrics over http but must use https to add new server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications
by Jochen Riedlinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ]
Jochen Riedlinger commented on WFLY-334:
----------------------------------------
Sehr geehrte Damen und Herren, von Montag, den 23.12.2013, bis einschließlich Freitag, den 10.01.2014, bin ich nicht im Hause. In dringenden Fällen wenden Sie sich bitte an Heiner Tittelbach (IT 271) oder Bernd Kirchgäßner (IT 221). Ihre Mail wird nicht automatisch weitergeleitet. Mit freundlichen Grüßen Jochen Riedlinger
> HA Singleton deployer for applications
> --------------------------------------
>
> Key: WFLY-334
> URL: https://issues.jboss.org/browse/WFLY-334
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering, Domain Management
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
> Labels: deployers, hasingleton
> Fix For: 8.0.0.Final
>
>
> A HASingleton deployer should be provided in standalone and domain mode.
> To be able to migrate such singleton applications from former AS versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (WFLY-11) Bundle path for Embedded server still not working properly
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-11?page=com.atlassian.jira.plugin.sy... ]
Jason Greene updated WFLY-11:
-----------------------------
Fix Version/s: 8.0.0.Final
> Bundle path for Embedded server still not working properly
> ----------------------------------------------------------
>
> Key: WFLY-11
> URL: https://issues.jboss.org/browse/WFLY-11
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Galder Zamarreño
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.CR1, 8.0.0.Final
>
>
> Error is:
> {code} io.escalante.test.artifact.ArtifactInstallTest: bundlesDir not a directory{code}
> The problem is that the check is done in an 'assert' block and that only happens when assertions have been enabled by the user :(
> The problem comes cos bundlesDir is set to "null/bundles", even if I have not set any bundlesDir.
> Seems like bundlesDir is pre-computed too early in EmbeddedContainerConfiguration where it expects a system property, but that might not be set, it might come from arquillian.xml. So better delay until EmbeddedServerFactory.create.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (WFLY-343) lower messaging's min-large-message-size value in standalone-full.xml
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-343?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-343:
------------------------------
Fix Version/s: (was: 8.0.0.CR1)
> lower messaging's min-large-message-size value in standalone-full.xml
> ---------------------------------------------------------------------
>
> Key: WFLY-343
> URL: https://issues.jboss.org/browse/WFLY-343
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 8.0.0.Final
>
>
> AS7's messaging subsystem defines 2 attributes:
> journal-file-size => 10MiB
> min-large-message-size => 100KiB
> However, for startup performance issue, the standalone-full.xml sets the journal-file-size at 1OOKiB. This leads to issues since it's the same value than the min-large-message-size.
> If we want to keep a low journal-file-size value in standalone-full.xml, the min-large-message-size must also bet set appropriately (eg 75KiB?)
> For production use, however, we should suggest to the users to remove the journal-file-size and min-large-message-size from standalone-full.xml to use the default values (resp. 10MiB & 100KiB)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months