July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-827) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-827?page=com.atlassian.jira.plugin.s... ] Scott Marlow resolved WFLY-827. ------------------------------- Resolution: Duplicate Issue The fix for WFLY-69 is merged for WildFly (will be in 9.0.0.Beta1). That fix replaces the NPE with an ISE. > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: WFLY-827 > URL: https://issues.jboss.org/browse/WFLY-827 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Brand Neu > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-827) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-827?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-827: ------------------------------ Fix Version/s: 9.0.0.Beta1 > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: WFLY-827 > URL: https://issues.jboss.org/browse/WFLY-827 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Brand Neu > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-565) Retrieve the rule that caused a RuleRuntimeEvent

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-565: ------------------------------------- Summary: Retrieve the rule that caused a RuleRuntimeEvent Key: DROOLS-565 URL: https://issues.jboss.org/browse/DROOLS-565 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 6.1.0.CR2, 6.0.1.Final, 6.0.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Minor Fix For: 6.2.0.Beta1 In 5.x, rule runtime events used to expose the propagation context, which is now (rightfully) hidden. However, it is still useful to access the rule which caused the event if any -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-21) Changes made to ExtensionRegistry by operations are not reverted if the operation rolls back

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-21: -------------------------------------- Summary: Changes made to ExtensionRegistry by operations are not reverted if the operation rolls back Key: WFCORE-21 URL: https://issues.jboss.org/browse/WFCORE-21 Project: WildFly Core Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry ExtensionRegistry maintains state that OSHs modify during Stage.MODEL. But ExtensionRegistry doesn't (and can't, readily) support the copy-on-write/publish-on-commit behavior that is ideal in Stage.MODEL, so those state changes need to be reverted by the OSH if the operation rolls back. Affects ExtensionAddHandler, ExtensionRemoveHandler, ApplyMissingDomainModelResourcesHandler and ApplyExtensionsHandler. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3580) EJB/remoting configuration does not propagate the certificate as credentials for authentication if mutual auth SSL was used for the connection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3580?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3580: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=953200, https://bugzilla.redhat.com/show_bug.cgi?id=1123505 (was: https://bugzilla.redhat.com/show_bug.cgi?id=953200) > EJB/remoting configuration does not propagate the certificate as credentials for authentication if mutual auth SSL was used for the connection > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3580 > URL: https://issues.jboss.org/browse/WFLY-3580 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, EJB > Reporter: Derek Horton > Assignee: Darran Lofthouse > > EJB/remoting configuration does not propagate the certificate as credentials for authentication if mutual auth SSL was used for the connection. This makes it impossible to get the certificate for use in a custom login module. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-564) NPE when using globals as query element inputs

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-564: ------------------------------------- Summary: NPE when using globals as query element inputs Key: DROOLS-564 URL: https://issues.jboss.org/browse/DROOLS-564 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.1.0.CR2, 5.6.0.Final Reporter: Davide Sottara Assignee: Davide Sottara Priority: Minor Fix For: 6.2.0.Beta1 Globals cannot be used as actual (input) parameters in queries without throwing a NPE -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

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

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3664?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3664: ------------------------------ Affects Version/s: 8.1.0.Final (was: 8.2.0.CR1) > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-28) Define Permissions Checks for org.wildfly.security.auth.provider.SecuritySystem

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-28: ----------------------------------- Summary: Define Permissions Checks for org.wildfly.security.auth.provider.SecuritySystem Key: ELY-28 URL: https://issues.jboss.org/browse/ELY-28 Project: WildFly Elytron Issue Type: Sub-task Security Level: Public (Everyone can see) Components: API / SPI Reporter: Darran Lofthouse Fix For: 1.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-27) Permissions Checks

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-27: ----------------------------------- Summary: Permissions Checks Key: ELY-27 URL: https://issues.jboss.org/browse/ELY-27 Project: WildFly Elytron Issue Type: Task Security Level: Public (Everyone can see) Components: API / SPI Reporter: Darran Lofthouse Fix For: 1.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-301) When custom error pages are used in web.xml wrong status codes are returned

by Troy Longo (JIRA)

[ https://issues.jboss.org/browse/JBWEB-301?page=com.atlassian.jira.plugin.... ] Troy Longo edited comment on JBWEB-301 at 7/25/14 2:25 PM: ----------------------------------------------------------- This is reproducible in Jboss EAP 6.2.4 also was (Author: tclongo): This reproducible in Jboss EAP 6.2.4 also > When custom error pages are used in web.xml wrong status codes are returned > --------------------------------------------------------------------------- > > Key: JBWEB-301 > URL: https://issues.jboss.org/browse/JBWEB-301 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-7.2.1.GA > Environment: JBoss EAP 6.1.1 > Red Hat Linux 6.1 > CamelServlet 2.13.0 > Reporter: Troy Longo > Assignee: Remy Maucherat > > I have the following code in my ServletFilter > if(request instanceof HttpServletRequest) > { > isHttpRequest = true; > > if(!(((HttpServletRequest)request).getMethod().equals("POST"))) > { > ((HttpServletResponse)response).sendError(HttpServletResponse.SC_METHOD_NOT_ALLOWED); > return; > } > } > When I send a GET request, everything works fine and I am receive a response with a 405 status code. However when I send a PUT or DELETE, I receive a 403 and 501 status code respectively. I have debugged through my code and verified that I am hitting the same line above in my code. What I noticed is that this code was working nicely until I added some custom error pages into my web.xml. My web xml error page definitions are as follows. Removing these custom error pages from the web.xml cause the code to work as expected. >  -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 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