May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6383) Entities using Extended PersistentContext are not managed

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-6383?page=com.atlassian.jira.plugin.... ] Yeray Santana Borges updated WFLY-6383: --------------------------------------- Attachment: WFLY-6383.zip Added a maven project with the example files > Entities using Extended PersistentContext are not managed > --------------------------------------------------------- > > Key: WFLY-6383 > URL: https://issues.jboss.org/browse/WFLY-6383 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Environment: WildFLy 10.0.0.Final > Mac > Reporter: Rakesh K. Cherukuri > Labels: Extended, JPA, Persistence, PersistenceContext > Attachments: AtInjectedStatefulEjbClient.java, CdiStatefulEmployeeBean.java, StatefulEjb.java, StatefulEjbClient.java, WFLY-6383.zip > > > Entities using Extended PersistentContext are not managed in a Stateful bean. > Attached are the bean class and the client servlet class -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6383) Entities using Extended PersistentContext are not managed

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-6383?page=com.atlassian.jira.plugin.... ] Yeray Santana Borges commented on WFLY-6383: -------------------------------------------- Hi [~rakcheru] Can you see any error trace in the server log? I have been playing a little with your files and both options works fine in WildFLy 10.0.0.Final (Mac Os, Oracle JDK 1.8), at least using H2 in memory data base, but I think that the database type is not relevant in this issue. > Entities using Extended PersistentContext are not managed > --------------------------------------------------------- > > Key: WFLY-6383 > URL: https://issues.jboss.org/browse/WFLY-6383 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Environment: WildFLy 10.0.0.Final > Mac > Reporter: Rakesh K. Cherukuri > Labels: Extended, JPA, Persistence, PersistenceContext > Attachments: AtInjectedStatefulEjbClient.java, CdiStatefulEmployeeBean.java, StatefulEjb.java, StatefulEjbClient.java > > > Entities using Extended PersistentContext are not managed in a Stateful bean. > Attached are the bean class and the client servlet class -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-69) Enable the patch command

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-69?page=com.atlassian.jira.plugin.... ] James Perkins closed JBASMP-69. ------------------------------- Resolution: Won't Do New features are only going into the [WildFly Maven Plugin|https://issues.jboss.org/browse/WFMP]. > Enable the patch command > ------------------------ > > Key: JBASMP-69 > URL: https://issues.jboss.org/browse/JBASMP-69 > Project: JBoss AS Maven Plugins > Issue Type: Feature Request > Affects Versions: 7.5.Final > Reporter: Shaun Appleton > > A new patching mechanism was introduced for EAP. This involves the new cli command: patch > This is a request to extend the maven plugin to be able to run the patch command as some customers would like to use this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-32) Overriding the deployment name overrides the web-context

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-32?page=com.atlassian.jira.plugin.... ] James Perkins closed JBASMP-32. ------------------------------- Resolution: Won't Do > Overriding the deployment name overrides the web-context > -------------------------------------------------------- > > Key: JBASMP-32 > URL: https://issues.jboss.org/browse/JBASMP-32 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Reporter: James Perkins > > http://stackoverflow.com/questions/14241493/jboss-7-deployment-issues-wit... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-107) jboss-logging-tools don't include the license file

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-107?page=com.atlassian.jira.plugi... ] James Perkins commented on LOGTOOL-107: --------------------------------------- The attached PR adds a {{LICENSE.txt}} file to the {{META-INF}} directory in both the source and binary JAR's. {code} jperkins@localhost ~/projects/jboss/logging/jboss-logging-tools (LOGTOOL-107) $ jar tf annotations/target/jboss-logging-annotations-2.1.0.Alpha1-SNAPSHOT-sources.jar META-INF/MANIFEST.MF META-INF/ org/ org/jboss/ org/jboss/logging/ org/jboss/logging/annotations/ org/jboss/logging/annotations/ConstructType.java org/jboss/logging/annotations/Cause.java org/jboss/logging/annotations/Once.java org/jboss/logging/annotations/Transform.java org/jboss/logging/annotations/Suppressed.java org/jboss/logging/annotations/Fields.java org/jboss/logging/annotations/Property.java META-INF/INDEX.LIST org/jboss/logging/annotations/FormatWith.java org/jboss/logging/annotations/LogMessage.java org/jboss/logging/annotations/LoggingClass.java org/jboss/logging/annotations/MessageBundle.java org/jboss/logging/annotations/Param.java org/jboss/logging/annotations/ValidIdRanges.java org/jboss/logging/annotations/Field.java org/jboss/logging/annotations/Properties.java org/jboss/logging/annotations/Signature.java org/jboss/logging/annotations/Message.java org/jboss/logging/annotations/Pos.java org/jboss/logging/annotations/ValidIdRange.java org/jboss/logging/annotations/MessageLogger.java META-INF/LICENSE.txt {code} If this doesn't look correct just let me know. > jboss-logging-tools don't include the license file > -------------------------------------------------- > > Key: LOGTOOL-107 > URL: https://issues.jboss.org/browse/LOGTOOL-107 > Project: Log Tool > Issue Type: Bug > Reporter: gil cattaneo > Assignee: James Perkins > > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging... > thanks > regards -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6620) Remove typo from BAControler interface and its implementations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6620?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-6620: ------------------------------------- Can you add a note as to when this is required for, e.g. a link to a SHA from Narayana > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: WFLY-6620 > URL: https://issues.jboss.org/browse/WFLY-6620 > Project: WildFly > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-556) Wrapper HTTP and SASL Mechanism factories to automatically set the server name.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-556: ------------------------------------ Summary: Wrapper HTTP and SASL Mechanism factories to automatically set the server name. Key: ELY-556 URL: https://issues.jboss.org/browse/ELY-556 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP, SASL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta6 For SASL this will be the server name passed in to the factory, for HTTP this should be derived from the Host header in the request. HTTP mechanisms will need to be double checked as this can only happen after the request is received from the client i.e. Basic authentication will need to wait until the request is received before the mechanism realms can be identified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-107) jboss-logging-tools don't include the license file

by gil cattaneo (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-107?page=com.atlassian.jira.plugi... ] gil cattaneo edited comment on LOGTOOL-107 at 5/31/16 12:40 PM: ---------------------------------------------------------------- Sorry, but dont undarstand your first question. Fedora packaging guideline say "All program binaries and program libraries included in Fedora packages must be built from the source code that is included in the source package" https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelin... Regards was (Author: puntogil): Sorry, but dont undarstand your first question. Fedora packaging guideline say "All program binaries and program libraries included in Fedora packages must be built from the source code that is included in the source" https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelin... Regards > jboss-logging-tools don't include the license file > -------------------------------------------------- > > Key: LOGTOOL-107 > URL: https://issues.jboss.org/browse/LOGTOOL-107 > Project: Log Tool > Issue Type: Bug > Reporter: gil cattaneo > Assignee: James Perkins > > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging... > thanks > regards -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-107) jboss-logging-tools don't include the license file

by gil cattaneo (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-107?page=com.atlassian.jira.plugi... ] gil cattaneo commented on LOGTOOL-107: -------------------------------------- Sorry, but dont undarstand your first question. Fedora packaging guideline say "All program binaries and program libraries included in Fedora packages must be built from the source code that is included in the source" https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelin... Regards > jboss-logging-tools don't include the license file > -------------------------------------------------- > > Key: LOGTOOL-107 > URL: https://issues.jboss.org/browse/LOGTOOL-107 > Project: Log Tool > Issue Type: Bug > Reporter: gil cattaneo > Assignee: James Perkins > > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging... > thanks > regards -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-108) Add README with some basic getting started documentation

by James Perkins (JIRA)

James Perkins created LOGTOOL-108: ------------------------------------- Summary: Add README with some basic getting started documentation Key: LOGTOOL-108 URL: https://issues.jboss.org/browse/LOGTOOL-108 Project: Log Tool Issue Type: Task Reporter: James Perkins There should be a README with some basic getting started tips/how to's. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016