March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HIBERNATE-172) Hibernate generates no needed update statement

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/HIBERNATE-172?page=com.atlassian.jira.pl... ] nimo stephan updated HIBERNATE-172: ----------------------------------- Description: I have an orderinary entity with this property: {code:java} @Entity @DynamicUpdate public class User { @Convert(converter = TaskConverter.class) private Map<Task, Type> tasks; .. } {code} where the `Task` is an Enum-class and the `Type` is another Enum-class. The converter converts the tasks to a string and back. All works, however, Hibernate generates an additional update statement for the `tasks` when I create a new `User`-Instance or update other entity properties of the `User`-instance: {code:java} // this update statement is always created altough "tasks" was not changed update User set tasks=? where id_user=? {code} The above update statement always follows after another update statement of the same entity. For example: {code:java} // here I only change the name property and an update is triggered update User set name=? where id_user=? // but then hibernate also creates this update statement even if I did not change tasks update User set tasks=? where id_user=? {code} It behaves as if `tasks` would be an @ElementCollection where the tasks is always recreated on create or update of its parent entity `User`. However, I annotated it with `@Convert`. Hibernate should not generate an update statement if `tasks` is left unchanged. was: I have an orderinary entity with this property: {code:java} @Entity @DynamicUpdate public class User { @Convert(converter = TaskConverter.class) private Map<Task, Type> tasks; .. } {code} where the `Task` is an Enum-class and the `Type` is another Enum-class. The converter converts the tasks to a string and back. All works, however, Hibernate generates an additional update statement for the `tasks` when I create a new `User`-Instance or update other entity properties of the `User`-instance: {code:java} // this update statement is always created altough "tasks" was not changed update User set tasks=? where id_user=? {code} It behaves as if `tasks` would be an @ElementCollection where the tasks is always recreated on create or update of its parent entity `User`. However, I annotated it with `@Convert`. Hibernate should not generate an update statement if `tasks` is left unchanged. > Hibernate generates no needed update statement > ---------------------------------------------- > > Key: HIBERNATE-172 > URL: https://issues.redhat.com/browse/HIBERNATE-172 > Project: Hibernate Integration > Issue Type: Bug > Reporter: nimo stephan > Assignee: Steve Ebersole > Priority: Major > > I have an orderinary entity with this property: > {code:java} > @Entity > @DynamicUpdate > public class User { > > @Convert(converter = TaskConverter.class) > private Map<Task, Type> tasks; > > .. > } > {code} > where the `Task` is an Enum-class and the `Type` is another Enum-class. The converter converts the tasks to a string and back. All works, however, Hibernate generates an additional update statement for the `tasks` when I create a new `User`-Instance or update other entity properties of the `User`-instance: > > {code:java} > // this update statement is always created altough "tasks" was not changed > update User set tasks=? where id_user=? > {code} > The above update statement always follows after another update statement of the same entity. For example: > {code:java} > // here I only change the name property and an update is triggered > update User set name=? where id_user=? > // but then hibernate also creates this update statement even if I did not change tasks > update User set tasks=? where id_user=? > {code} > It behaves as if `tasks` would be an @ElementCollection where the tasks is always recreated on create or update of its parent entity `User`. However, I annotated it with `@Convert`. > Hibernate should not generate an update statement if `tasks` is left unchanged. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-172) Hibernate generates no needed update statement

by nimo stephan (Jira)

nimo stephan created HIBERNATE-172: -------------------------------------- Summary: Hibernate generates no needed update statement Key: HIBERNATE-172 URL: https://issues.redhat.com/browse/HIBERNATE-172 Project: Hibernate Integration Issue Type: Bug Reporter: nimo stephan Assignee: Steve Ebersole I have an orderinary entity with this property: {code:java} @Entity @DynamicUpdate public class User { @Convert(converter = TaskConverter.class) private Map<Task, Type> tasks; .. } {code} where the `Task` is an Enum-class and the `Type` is another Enum-class. The converter converts the tasks to a string and back. All works, however, Hibernate generates an additional update statement for the `tasks` when I create a new `User`-Instance or update other entity properties of the `User`-instance: {code:java} // this update statement is always created altough "tasks" was not changed update User set tasks=? where id_user=? {code} It behaves as if `tasks` would be an @ElementCollection where the tasks is always recreated on create or update of its parent entity `User`. However, I annotated it with `@Convert`. Hibernate should not generate an update statement if `tasks` is left unchanged. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4896) Support iteration over filtered cli query

by Georg Tsakumagos (Jira)

Georg Tsakumagos created WFCORE-4896: ---------------------------------------- Summary: Support iteration over filtered cli query Key: WFCORE-4896 URL: https://issues.redhat.com/browse/WFCORE-4896 Project: WildFly Core Issue Type: Enhancement Components: CLI, Management Reporter: Georg Tsakumagos Assignee: Jean Francois Denise It would be usefull to iterate over filtered queries in cli. I need to spare the only alowed level of if expression for the control foll inside the loop. I like to update all profiles containing elytron subsystem and to spare out all inherited profiles which include the base profiles. {code:java|title=CLI query example} for profile in /profile=*:query(select=[name], where=[includes=undefined]) echo $profile done {code} {code:JSON|title=actual result} {"address" => [("profile" => "default")],"outcome" => "success","result" => {"name" => "default"}} {"address" => [("profile" => "ha")],"outcome" => "success","result" => {"name" => "ha"}} {"address" => [("profile" => "full")],"outcome" => "success","result" => {"name" => "full"}} {"address" => [("profile" => "full-ha")],"outcome" => "success","result" => {"name" => "full-ha"}} {"address" => [("profile" => "load-balancer")],"outcome" => "success","result" => {"name" => "load-balancer"}} {code} {code:java|title=desired result} default full full-ha gfi ha load-balancer {code} Maybe it would be a solution to extend the operation extend read-children-names by an property where to apply a filter. {code:JSON|title=extend read-children-names} for profile in /:read-children-names(child-type=profile,where=[includes=undefined]) echo $profile done {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13309) [GSS](7.3.z) Upgrade weld from 3.1.2.Final-redhat-00001 to 3.1.4.Final-redhat-00001

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13309?page=com.atlassian.jira.plugi... ] Ingo Weiss moved JBEAP-19129 to WFLY-13309: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13309 (was: JBEAP-19129) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CDI / Weld (was: CDI / Weld) Affects Version/s: 19.0.0.Final (was: 7.2.4.GA) Fix Version/s: 20.0.0.Beta1 (was: 7.3.1.GA) > [GSS](7.3.z) Upgrade weld from 3.1.2.Final-redhat-00001 to 3.1.4.Final-redhat-00001 > ----------------------------------------------------------------------------------- > > Key: WFLY-13309 > URL: https://issues.redhat.com/browse/WFLY-13309 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Affects Versions: 19.0.0.Final > Reporter: Ingo Weiss > Assignee: Roberto Oliveira > Priority: Critical > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Tag: https://github.com/weld/core/tree/3.1.4.Final > Diff: https://github.com/weld/core/compare/3.1.2.Final..3.1.4.Final > Commit: https://github.com/weld/core/commit/369c0c7e1c42f3522b3fee41d67e4caee7bd8446 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13309) Upgrade weld from 3.1.3.Final to 3.1.4.Final

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13309?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-13309: ------------------------------ Summary: Upgrade weld from 3.1.3.Final to 3.1.4.Final (was: [GSS](7.3.z) Upgrade weld from 3.1.2.Final-redhat-00001 to 3.1.4.Final-redhat-00001) > Upgrade weld from 3.1.3.Final to 3.1.4.Final > -------------------------------------------- > > Key: WFLY-13309 > URL: https://issues.redhat.com/browse/WFLY-13309 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Affects Versions: 19.0.0.Final > Reporter: Ingo Weiss > Assignee: Roberto Oliveira > Priority: Critical > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Tag: https://github.com/weld/core/tree/3.1.4.Final > Diff: https://github.com/weld/core/compare/3.1.2.Final..3.1.4.Final > Commit: https://github.com/weld/core/commit/369c0c7e1c42f3522b3fee41d67e4caee7bd8446 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13309) Upgrade weld from 3.1.3.Final to 3.1.4.Final

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13309?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-13309: ------------------------------ Description: (was: Tag: https://github.com/weld/core/tree/3.1.4.Final Diff: https://github.com/weld/core/compare/3.1.2.Final..3.1.4.Final Commit: https://github.com/weld/core/commit/369c0c7e1c42f3522b3fee41d67e4caee7bd8446) > Upgrade weld from 3.1.3.Final to 3.1.4.Final > -------------------------------------------- > > Key: WFLY-13309 > URL: https://issues.redhat.com/browse/WFLY-13309 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Affects Versions: 19.0.0.Final > Reporter: Ingo Weiss > Assignee: Roberto Oliveira > Priority: Critical > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1105) install maistra job fails for 1.12.6 operator version

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1105: ------------------------------------ Summary: install maistra job fails for 1.12.6 operator version Key: SWSQE-1105 URL: https://issues.redhat.com/browse/SWSQE-1105 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Filip Brychta KIALI_OPERATOR_TAG 1.12.6 is passed directly to OPERATOR_VERSION_LABEL which is looking for 1.12.6 branch which does not exists. It must be v1.12 branch. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10715) TransactionSubsystemTestCase does not test for invalid XML in some cases

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/WFLY-10715?page=com.atlassian.jira.plugi... ] Mayank Kunwar reassigned WFLY-10715: ------------------------------------ Assignee: Mayank Kunwar (was: Thomas Jenkinson) > TransactionSubsystemTestCase does not test for invalid XML in some cases > ------------------------------------------------------------------------ > > Key: WFLY-10715 > URL: https://issues.redhat.com/browse/WFLY-10715 > Project: WildFly > Issue Type: Task > Components: Test Suite, Transactions > Reporter: Thomas Jenkinson > Assignee: Mayank Kunwar > Priority: Major > > 7.0.0+ introduces the following attributes not found in 6.4.0: [use-journal-store, statistics-enabled, journal-store-enable-async-io]. The test xml should be updated to include these and transformers added where missing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11767) Remove unused dependencies from org.jboss.as.connector

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-11767?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-11767: ------------------------------------- [~yersan] I think both dependencies has been removed from or.jboss.as.connector as i have checked. Thanks, Parul > Remove unused dependencies from org.jboss.as.connector > ------------------------------------------------------ > > Key: WFLY-11767 > URL: https://issues.redhat.com/browse/WFLY-11767 > Project: WildFly > Issue Type: Sub-task > Components: Class Loading > Reporter: Yeray Borges Santana > Assignee: Parul Sharma > Priority: Major > > The analysis shows these dependencies are not used by this module: > * org.jboss.jts > * org.glassfish.javax.el -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13308) BOMs is a separate component

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-13308: -------------------------------------- Summary: BOMs is a separate component Key: WFLY-13308 URL: https://issues.redhat.com/browse/WFLY-13308 Project: WildFly Issue Type: Bug Components: Build System Environment: Patched Galleon to obey dependency management (issue forthcoming) Reporter: Eduardo Martins Assignee: Eduardo Martins Fix For: 19.0.0.Beta1, 19.0.0.Final {{wildfly-jms-client-bom}} is defined as having version {{${project.version}}}, but the main codebase does not produce this artifact. https://github.com/jbossas/jboss-eap7/blob/CD14/pom.xml#L819 It is produced at https://github.com/wildfly/boms/blob/master/client/jms-client/pom.xml#L40 If Galleon were to obey dependency management this leads to: {noformat} [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:2.0.1.Alpha1-SNAPSHOT:generate-feature-specs (feature-spec-build) on project wildfly-galleon-pack: Failed to resolve artifact org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT as a dependency of eap-cd-servlet@maven(org.jboss.universe:product-universe):current#7.2.0.CD14-redhat-SNAPSHOT (persisted as org.jboss.eap:wildfly-jms-client-bom:7.2.0.CD14-redhat-SNAPSHOT::pom): Couldn't resolve artifact: Failure to find org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:2.0.1.Alpha1-SNAPSHOT:generate-feature-specs (feature-spec-build) on project wildfly-galleon-pack: Failed to resolve artifact org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT as a dependency of eap-cd-servlet@maven(org.jboss.universe:product-universe):current#7.2.0.CD14-redhat-SNAPSHOT (persisted as org.jboss.eap:wildfly-jms-client-bom:7.2.0.CD14-redhat-SNAPSHOT::pom) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.maven.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:39) at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:122) at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:50) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to resolve artifact org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT as a dependency of eap-cd-servlet@maven(org.jboss.universe:product-universe):current#7.2.0.CD14-redhat-SNAPSHOT (persisted as org.jboss.eap:wildfly-jms-client-bom:7.2.0.CD14-redhat-SNAPSHOT::pom) at org.wildfly.galleon.maven.WfFeatureSpecBuildMojo.processFeaturePackDep(WfFeatureSpecBuildMojo.java:564) at org.wildfly.galleon.maven.WfFeatureSpecBuildMojo.processFeaturePackDeps(WfFeatureSpecBuildMojo.java:511) at org.wildfly.galleon.maven.WfFeatureSpecBuildMojo.doExecute(WfFeatureSpecBuildMojo.java:235) at org.wildfly.galleon.maven.WfFeatureSpecBuildMojo.execute(WfFeatureSpecBuildMojo.java:191) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 27 more Caused by: org.apache.maven.plugin.MojoExecutionException: Couldn't resolve artifact: Failure to find org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced at org.wildfly.galleon.maven.WfFeatureSpecBuildMojo.findArtifact(WfFeatureSpecBuildMojo.java:716) at org.wildfly.galleon.maven.WfFeatureSpecBuildMojo.processFeaturePackDep(WfFeatureSpecBuildMojo.java:562) ... 32 more Caused by: org.apache.maven.shared.artifact.resolve.ArtifactResolverException: Failure to find org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced at org.apache.maven.shared.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact(Maven31ArtifactResolver.java:116) at org.apache.maven.shared.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact(Maven31ArtifactResolver.java:80) at org.apache.maven.shared.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:73) at org.wildfly.galleon.maven.WfFeatureSpecBuildMojo.findArtifact(WfFeatureSpecBuildMojo.java:713) ... 33 more Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to find org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) at org.apache.maven.shared.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact(Maven31ArtifactResolver.java:108) ... 36 more Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find org.jboss.eap:wildfly-jms-client-bom:pom:7.2.0.CD14-redhat-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:231) at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:183) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421) ... 40 more {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2020