[JBoss JIRA] (JBIDE-18710) Invalid generated code in JAX-RS Endpoint
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18710?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18710:
----------------------------------
Labels: jax-rs (was: )
> Invalid generated code in JAX-RS Endpoint
> -----------------------------------------
>
> Key: JBIDE-18710
> URL: https://issues.jboss.org/browse/JBIDE-18710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.2.1.Final
>
>
> The generated code in the 'create' method contains something like this:
> {code}
> return Response.created(
> UriBuilder.fromResource(Session.class)
> .path(String.valueOf(session.getId())).build()).build();
> {code}
> but the {{Session.class}} should be {{SessionEndpoint.class}} since it must be the resource class annotated with {{@Path}}
> Also, after discussion with [~maxandersen], here the plan to fix this issue:
> - if the {{create}} method generation is selected and the target entity is selected and contains a 'getId()' method, then generate the following method body:
> {code}
> //TODO: process the given pojo
> // here we use Pojo#getId(), assuming it provides the end-user with the identifier to retrieve the created Pojo resource
> Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build())
> .build();
> {code}
> - if the {{create}} method generation is selected and the target entity is selected and *does not contain* a 'getId()' method, then generate the following method body:
> {code}
> //TODO: process the given pojo
> // you may want to do something like this
> // return Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build();
> // assuming that Pojo#getId() or a similar method would provide the end-user with the identifier to retrieve the created Pojo resource
> Response.created(null).build();
> {code}
> If no target entity is provided, there is no way to generate the method skeletons.
> The goal if this change is to make sure we generate code that compiles (that was not the case if the target entity class did not have a {{getId()}} method) and that returns a sensitive Response object (hence, we don't return {{null}}).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18808) JAX-RS Resource wizard: Resource methods are created even though there is no Target entity specified anymore
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18808?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18808:
----------------------------------
Labels: jax-rs (was: )
> JAX-RS Resource wizard: Resource methods are created even though there is no Target entity specified anymore
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18808
> URL: https://issues.jboss.org/browse/JBIDE-18808
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Alpha1
>
>
> If I start typing name of Target entity in the JAX-RS Resource wizard, then checkboxes for creating resource methods (findById, listAll...) are allowed to be changed (checked/unchecked). But after completely removing of Target entity (leaving the field blank) the checkboxes are stilled in state checked/unchecked as they were changed while having filled Entity, but this changes are propagated next. That cause generating resource class with those methods even though there was no Entity specified and it leaves blank space in those generated methods causing syntax error.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18812:
----------------------------------
Labels: jax-rs jax-ws (was: jax-rs, jax-ws)
> Unable to build Web Services
> ----------------------------
>
> Key: JBIDE-18812
> URL: https://issues.jboss.org/browse/JBIDE-18812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: jax-rs, jax-ws
> Fix For: 4.3.0.Alpha1
>
>
> When running a {{mvn clean verify}} on MacOSX, I get the following errors:
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> [INFO] Scanning for projects...
> [WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
> [WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-server (${jbosstools-server-site}): No connector available to access repository jbosstools-server (${jbosstools-server-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
> [ERROR] Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86} -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 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:483)
> 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)
> Caused by: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
> at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.fixSWT(ProjectorResolutionStrategy.java:155)
> at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:95)
> at org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:166)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:103)
> at org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies(P2DependencyResolver.java:352)
> at org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies(P2DependencyResolver.java:325)
> at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:107)
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> ... 11 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18812:
----------------------------------
Labels: jax-rs, jax-ws (was: )
> Unable to build Web Services
> ----------------------------
>
> Key: JBIDE-18812
> URL: https://issues.jboss.org/browse/JBIDE-18812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: jax-rs,, jax-ws
> Fix For: 4.3.0.Alpha1
>
>
> When running a {{mvn clean verify}} on MacOSX, I get the following errors:
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> [INFO] Scanning for projects...
> [WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
> [WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-server (${jbosstools-server-site}): No connector available to access repository jbosstools-server (${jbosstools-server-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
> [ERROR] Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86} -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 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:483)
> 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)
> Caused by: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
> at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.fixSWT(ProjectorResolutionStrategy.java:155)
> at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:95)
> at org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:166)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:103)
> at org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies(P2DependencyResolver.java:352)
> at org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies(P2DependencyResolver.java:325)
> at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:107)
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> ... 11 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18823) Invalid generated code in JAX-RS Endpoint
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18823?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18823:
----------------------------------
Labels: jax-rs (was: )
> Invalid generated code in JAX-RS Endpoint
> -----------------------------------------
>
> Key: JBIDE-18823
> URL: https://issues.jboss.org/browse/JBIDE-18823
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Alpha1
>
>
> The generated code in the 'create' method contains something like this:
> {code}
> return Response.created(
> UriBuilder.fromResource(Session.class)
> .path(String.valueOf(session.getId())).build()).build();
> {code}
> but the {{Session.class}} should be {{SessionEndpoint.class}} since it must be the resource class annotated with {{@Path}}
> Also, after discussion with [~maxandersen], here the plan to fix this issue:
> - if the {{create}} method generation is selected and the target entity is selected and contains a 'getId()' method, then generate the following method body:
> {code}
> //TODO: process the given pojo
> // here we use Pojo#getId(), assuming it provides the end-user with the identifier to retrieve the created Pojo resource
> Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build())
> .build();
> {code}
> - if the {{create}} method generation is selected and the target entity is selected and *does not contain* a 'getId()' method, then generate the following method body:
> {code}
> //TODO: process the given pojo
> // you may want to do something like this
> // return Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build();
> // assuming that Pojo#getId() or a similar method would provide the end-user with the identifier to retrieve the created Pojo resource
> Response.created(null).build();
> {code}
> If no target entity is provided, there is no way to generate the method skeletons.
> The goal if this change is to make sure we generate code that compiles (that was not the case if the target entity class did not have a {{getId()}} method) and that returns a sensitive Response object (hence, we don't return {{null}}).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months