[JBoss JIRA] (JBIDE-12637) Hibernate Tools generates @SequenceGenerator with not unique name
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12637?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-12637:
------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.x)
Story Points: 8
> Hibernate Tools generates @SequenceGenerator with not unique name
> -----------------------------------------------------------------
>
> Key: JBIDE-12637
> URL: https://issues.jboss.org/browse/JBIDE-12637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Nicolas Bihan
> Assignee: Koen Aers
> Priority: Critical
> Labels: SequenceGenerator, hibenate, hibernate-tools, jpa
> Fix For: 4.4.0.Alpha3
>
>
> When generating entities with EJB3 annotations with a strategy set to "sequence", Hibernate tools generates POJOs with non unique javax.persistence.SequenceGenerator name "generator". But according to the Java documentation :
> bq. String name (Required) A unique generator name that can be referenced by one or more classes to be the generator for primary key values.
> See [javadoc|http://docs.oracle.com/javaee/5/api/javax/persistence/SequenceGen...]
> Exemple of generated code with 4.0.0 Alpha1:
> {code}
> @SequenceGenerator(name = "generator", sequenceName = "S_CLIENT")
> @Id
> @GeneratedValue(strategy = SEQUENCE, generator = "generator")
> @Column(name = "CLIENT_ID", unique = true, nullable = false, precision = 22, scale = 0)
> public long getClientId() {
> return this.clientId;
> }
> {code}
> [Source code|https://github.com/hibernate/hibernate-tools/blob/master/src/java/or...] can be seen here.
> So looks like the //TODO comment is right and it should generate a unique name atribute. sequencename+"generator" would be a good name.
> It would even be better if we could define this name in reveng.xml or/and in a DelegatingReverseEngineeringStrategy class.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21302:
--------------------------------
Sprint: devex #0 January 2016, devex #1 February 2016, devex #2 February 2016, devex #115 May 2016 (was: devex #0 January 2016, devex #1 February 2016, devex #2 February 2016)
> Removing user from credentials framework while not authenticated to secure storage should not work
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21302
> URL: https://issues.jboss.org/browse/JBIDE-21302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> Removing credentials (which are stored in secure storage) using
> CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21302:
--------------------------------
Story Points: 2
> Removing user from credentials framework while not authenticated to secure storage should not work
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21302
> URL: https://issues.jboss.org/browse/JBIDE-21302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> Removing credentials (which are stored in secure storage) using
> CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months