July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3690) split xts-enviroment's URL attribute in 4 different attribute

by Stefano Maestri (JIRA)

Stefano Maestri created WFLY-3690: ------------------------------------- Summary: split xts-enviroment's URL attribute in 4 different attribute Key: WFLY-3690 URL: https://issues.jboss.org/browse/WFLY-3690 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: Transactions Reporter: Stefano Maestri Assignee: Stefano Maestri Currently we have the following configuration element: <xts-environment url="http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService"/> we need to split url in 4 different attribute: * protocol * host * port * path -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-783) LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-783?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-783: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1051057|https://bugzilla.redhat.com/show_bug.cgi?id=1051057] from NEW to CLOSED > LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components > -------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-783 > URL: https://issues.jboss.org/browse/SECURITY-783 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Peter Skopek > Priority: Minor > Attachments: SECURITY-783.patch > > > The LdapExtLoginModule requires that the vault string used for the bindCredentials not include the '${' prefix and '}' suffix. This is different than other places in the standalone.xml file where the ${ and } are required. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3664) Exceptions during download of webstart libraries

by Markus Schwarz (JIRA)

[ https://issues.jboss.org/browse/WFLY-3664?page=com.atlassian.jira.plugin.... ] Markus Schwarz commented on WFLY-3664: -------------------------------------- Have you tested it multiple times with clearing the webstart cache in between, because sometimes I also didn't get an exception. Have you tested it locally or remote (Ok, for me, in both cases error had been thrown)? What does this exception mean, because the webstart application is running as normal. Do I have to care about those exceptions? > Exceptions during download of webstart libraries > ------------------------------------------------ > > Key: WFLY-3664 > URL: https://issues.jboss.org/browse/WFLY-3664 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: Windows 7 (64bit), Windows Server 2012 R2 (64bit) > Reporter: Markus Schwarz > Assignee: Stuart Douglas > Priority: Minor > Attachments: demo-src.zip, server.log > > > I have a webstart application using the JnlpDownloadServlet. If the client cache is empty, launching the JNLP will download the libraries. The webstart application works as expected, but in the server logs there are many errors regarding download of the libraries. > Just to mention: Not always the same libraries are listed with erros in the logs files. Sometimes I even got now exceptions. > For my tests I used Wildfly 8.1.0.FINAL as well as a nightly build from 24. of July without any further changes of the configuration files (https://ci.jboss.org/hudson/job/WildFly-latest-master/). > I tested it under Windows 7 and Windows Server 2012 R2. The demo contains an older JnlpDownloadServlet, but I tested it also with the one coming with JDK 7u65. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3674) In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-3674?page=com.atlassian.jira.plugin.... ] Sande Gilda commented on WFLY-3674: ----------------------------------- Thanks Scott. I'm watching it now. > In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3674 > URL: https://issues.jboss.org/browse/WFLY-3674 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > > For compatibility with earlier JBoss application server versions (5.0/6.0), add an extension that allows the persistence context to last until the referencing persistence context is closed. > For example, in a session method that has no active JTA transaction, entities returned, will not cleared from the persistence context, until the session method completes. This extension is only introduced to allow compatibility with older application server versions. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3674) In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3674?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-3674: ------------------------------- Description: For compatibility with earlier JBoss application server versions (5.0/6.0), add an extension that allows the persistence context to last until the referencing persistence context is closed. For example, in a session method that has no active JTA transaction, entities returned, will not cleared from the persistence context, until the session method completes. This extension is only introduced to allow compatibility with older application server versions. > In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3674 > URL: https://issues.jboss.org/browse/WFLY-3674 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > > For compatibility with earlier JBoss application server versions (5.0/6.0), add an extension that allows the persistence context to last until the referencing persistence context is closed. > For example, in a session method that has no active JTA transaction, entities returned, will not cleared from the persistence context, until the session method completes. This extension is only introduced to allow compatibility with older application server versions. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3674) In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3674?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-3674: ------------------------------------ Adding "jboss.as.jpa.deferdetach" persistence unit hint that may be set to true to enable WFLY-3674 extension. {quote} <property name="jboss.as.jpa.deferdetach" value="true" /> {quote} > In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3674 > URL: https://issues.jboss.org/browse/WFLY-3674 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > > For compatibility with earlier JBoss application server versions (5.0/6.0), add an extension that allows the persistence context to last until the referencing persistence context is closed. > For example, in a session method that has no active JTA transaction, entities returned, will not cleared from the persistence context, until the session method completes. This extension is only introduced to allow compatibility with older application server versions. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3664) Exceptions during download of webstart libraries

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3664?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3664: -------------------------------------- I just tested this out and I don't see any exceptions. The error message looks odd, like something is killing the underlying connection. > Exceptions during download of webstart libraries > ------------------------------------------------ > > Key: WFLY-3664 > URL: https://issues.jboss.org/browse/WFLY-3664 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: Windows 7 (64bit), Windows Server 2012 R2 (64bit) > Reporter: Markus Schwarz > Assignee: Stuart Douglas > Priority: Minor > Attachments: demo-src.zip, server.log > > > I have a webstart application using the JnlpDownloadServlet. If the client cache is empty, launching the JNLP will download the libraries. The webstart application works as expected, but in the server logs there are many errors regarding download of the libraries. > Just to mention: Not always the same libraries are listed with erros in the logs files. Sometimes I even got now exceptions. > For my tests I used Wildfly 8.1.0.FINAL as well as a nightly build from 24. of July without any further changes of the configuration files (https://ci.jboss.org/hudson/job/WildFly-latest-master/). > I tested it under Windows 7 and Windows Server 2012 R2. The demo contains an older JnlpDownloadServlet, but I tested it also with the one coming with JDK 7u65. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3644) Infinispan supports backups for Invalidation Cache while wildfly integration does not

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-3644?page=com.atlassian.jira.plugin.... ] Paul Ferraro resolved WFLY-3644. -------------------------------- Resolution: Rejected Closing this. Please post your questions about RELAY2 to the jgroups forum or user lists. > Infinispan supports backups for Invalidation Cache while wildfly integration does not > ------------------------------------------------------------------------------------- > > Key: WFLY-3644 > URL: https://issues.jboss.org/browse/WFLY-3644 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.1.0.Final > Environment: Linux > Reporter: Tarek Hammoud > Assignee: Paul Ferraro > > It seems that the integration with infinispan 6.x removes the ability of RELAY support for invalidation caches. > The jboss-as-infinispan_2_0.xsd allows backups to be specified only for shared-state-cache while the actual infinispan xsd has no such limitation. We can not leverage that capability. Infinispan will only fire updates to other sites if the backups are defined which make sense. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3679) Port jboss-as-infinispan_1_5.xsd schema from EAP to WildFly

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-3679?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-3679: ------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Port jboss-as-infinispan_1_5.xsd schema from EAP to WildFly > ----------------------------------------------------------- > > Key: WFLY-3679 > URL: https://issues.jboss.org/browse/WFLY-3679 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 9.0.0.CR1 > > > In addition to this the remaining infinispan schemas differ due to changes in the default values - these should be synchronized accordingly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-34) Move jboss-invocation & jboss-classwriter to full repo

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-34: --------------------------------- Summary: Move jboss-invocation & jboss-classwriter to full repo Key: WFCORE-34 URL: https://issues.jboss.org/browse/WFCORE-34 Project: WildFly Core Issue Type: Task Security Level: Public (Everyone can see) Components: Modules Reporter: Tomaz Cerar Assignee: Stuart Douglas We discussed this and idea was to get rid of deps if not absolutely needed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014