November 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2151) cdi-new-interceptor doesn't generate an @AroundInvoke on the method

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2151?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-2151: ---------------------------------------- Assignee: Antonio Goncalves > cdi-new-interceptor doesn't generate an @AroundInvoke on the method > ------------------------------------------------------------------- > > Key: FORGE-2151 > URL: https://issues.jboss.org/browse/FORGE-2151 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.12.2.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > The {{cdi-new-interceptor}} generates the following method : > {code} > private Object intercept(InvocationContext ic) throws Exception > { > try > { > return ic.proceed(); > } > finally > { > } > } > {code} > It misses an {{@AroundInvoke}} > {code} > @AroundInvoke > private Object intercept(InvocationContext ic) throws Exception > { > try > { > return ic.proceed(); > } > finally > { > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2151) cdi-new-interceptor doesn't generate an @AroundInvoke on the method

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2151: ---------------------------------------- Summary: cdi-new-interceptor doesn't generate an @AroundInvoke on the method Key: FORGE-2151 URL: https://issues.jboss.org/browse/FORGE-2151 Project: Forge Issue Type: Bug Components: Java EE Affects Versions: 2.12.2.Final Reporter: Antonio Goncalves Fix For: 2.x Future The {{cdi-new-interceptor}} generates the following method : {code} private Object intercept(InvocationContext ic) throws Exception { try { return ic.proceed(); } finally { } } {code} It misses an {{@AroundInvoke}} {code} @AroundInvoke private Object intercept(InvocationContext ic) throws Exception { try { return ic.proceed(); } finally { } } {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1530) Command constraint-setup creates a Bean Validation 1.1 descriptor

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1530?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1530: ------------------------------------- Parent Issue: FORGE-1926 (was: FORGE-1491) > Command constraint-setup creates a Bean Validation 1.1 descriptor > ----------------------------------------------------------------- > > Key: FORGE-1530 > URL: https://issues.jboss.org/browse/FORGE-1530 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When executing the {{constraint-setup}} command, it generates a Bean Validation 1.1 descriptor instead of a 1.0 (which is Java EE 6) : > {code} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd"/> > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1852) Parameter --beanValidationVersion missing in constraint-setup

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1852?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1852: ------------------------------------- Parent: FORGE-1926 Issue Type: Sub-task (was: Feature Request) > Parameter --beanValidationVersion missing in constraint-setup > ------------------------------------------------------------- > > Key: FORGE-1852 > URL: https://issues.jboss.org/browse/FORGE-1852 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Most {{setup}} commands have a version parameter to choose which version you want to use : > {code} > cdi-setup --cdiVersion > ejb-setup --ejbVersion > faces-setup --facesVersion > jms-setup --jmsVersion > jpa-setup --jpaVersion > rest-setup --jaxrsVersion > websocket-setup --webSocketVersion > {code} > At the moment, the only Java EE component that misses this parameter is Bean Validation. The {{constraint-setup}} command has the following parameters : > {code} > [test]$ constraint-setup TAB > --providers --providedScope > {code} > A parameter {{beanValidationVersion}} parameter should be added. The values would be 1.0 or 1.1. That will have an impact on the XSD of the generated {{validation.xml}} file and the dependencies in the {{pom.xml}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2150) jpa-new-field should generate constructor with not null attributes

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2150: ---------------------------------------- Summary: jpa-new-field should generate constructor with not null attributes Key: FORGE-2150 URL: https://issues.jboss.org/browse/FORGE-2150 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.12.2.Final Reporter: Antonio Goncalves Fix For: 2.x Future When a field is not nullable (either with {{@Column(nullable=false)}} or with a {{@NotNull}} constraint) it would be helpful to generate a constructor with all the needed not null values (and a default constructor). For example, here, I generate an {{Address}} entity with not null {{street1}} and {{city}}. It would be good to generate a default constructor + another one with these two needed attributes : {code} @Entity public class Address implements Serializable { @Column(length = 50, nullable = false) @Size(min = 5, max = 50) @NotNull private String street1; @Column(length = 50, nullable = false) @Size(min = 2, max = 50) @NotNull private String city; public Address() { } public Address(String street1, String city) { this.street1 = street1; this.city = city; } {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2149) validation.xml doesn't have the version="1.1" in the xml

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2149?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2149: ------------------------------------- Fix Version/s: 2.x Future > validation.xml doesn't have the version="1.1" in the xml > --------------------------------------------------------- > > Key: FORGE-2149 > URL: https://issues.jboss.org/browse/FORGE-2149 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.12.2.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When Bean Validation is setup, here is the generated {{META-INF/validation.xml}} file: > {code} > <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd"/> > {code} > It misses the {{version}} attribute and should be : > {code} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd" version="1.1"/> > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2149) validation.xml doesn't have the version="1.1" in the xml

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2149?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2149: ------------------------------------- Description: When Bean Validation is setup, here is the generated {{META-INF/validation.xml}} file: {code} <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd"/> {code} It misses the {{version}} attribute and should be : {code} <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd" version="1.1"/> {code} was: When Bean Validation is setup, here is the generated {{META-INF/validation.xml}} file: {code} <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd"/> {code} It misses the {{version}} attribute and should be : {code} <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd" version="1.1"/> {code} > validation.xml doesn't have the version="1.1" in the xml > --------------------------------------------------------- > > Key: FORGE-2149 > URL: https://issues.jboss.org/browse/FORGE-2149 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.12.2.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When Bean Validation is setup, here is the generated {{META-INF/validation.xml}} file: > {code} > <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd"/> > {code} > It misses the {{version}} attribute and should be : > {code} > <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd" version="1.1"/> > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2149) validation.xml doesn't have the version="1.1" in the xml

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2149: ---------------------------------------- Summary: validation.xml doesn't have the version="1.1" in the xml Key: FORGE-2149 URL: https://issues.jboss.org/browse/FORGE-2149 Project: Forge Issue Type: Bug Components: Java EE Affects Versions: 2.12.2.Final Reporter: Antonio Goncalves When Bean Validation is setup, here is the generated {{META-INF/validation.xml}} file: {code} <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd"/> {code} It misses the {{version}} attribute and should be : {code} <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd" version="1.1"/> {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-176) Forge Arquillian add-on to include JAX-RS impl

by Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-176?page=com.atlassian.jira.... ] Arun Gupta commented on FORGEPLUGINS-176: ----------------------------------------- Also add appropriate JAXB dependencies. For example, following are required for WildFly: <dependency> <groupId>org.jboss.resteasy</groupId> <artifactId>resteasy-client</artifactId> <version>3.0.5.Final</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.resteasy</groupId> <artifactId>resteasy-jaxb-provider</artifactId> <version>3.0.5.Final</version> <scope>test</scope> </dependency> > Forge Arquillian add-on to include JAX-RS impl > ---------------------------------------------- > > Key: FORGEPLUGINS-176 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-176 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Components: Arquillian Plugin > Reporter: Arun Gupta > > Forge Arquillian add-on (https://github.com/forge/addon-arquillian.git) should include container specific JAX-RS impl in test scope. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-176) Forge Arquillian add-on to include JAX-RS impl

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-176?page=com.atlassian.jira.... ] George Gastaldi updated FORGEPLUGINS-176: ----------------------------------------- Component/s: Arquillian Plugin > Forge Arquillian add-on to include JAX-RS impl > ---------------------------------------------- > > Key: FORGEPLUGINS-176 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-176 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Components: Arquillian Plugin > Reporter: Arun Gupta > > Forge Arquillian add-on (https://github.com/forge/addon-arquillian.git) should include container specific JAX-RS impl in test scope. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2014