[JBoss JIRA] (JBIDE-13003) No support for inheritance in JAX-RS API scan
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13003?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-13003:
----------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.x)
> No support for inheritance in JAX-RS API scan
> ---------------------------------------------
>
> Key: JBIDE-13003
> URL: https://issues.jboss.org/browse/JBIDE-13003
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Alpha2
> Reporter: Ron Ratovsky
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Alpha1
>
>
> Assume:
> class BaseRest {
> @POST
> public Response save(Object o) {
> ....
> }
> }
> @Path("/url")
> class RealRest extends BaseRest {}
> The JAX-RS tools won't add a "POST /url" entry to the JAX-RS calls overview.
> While not tested (due to another bug) - they may also apply to definitions of @PathParam's in the parent class.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17877) Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17877?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-17877.
-----------------------------------
Resolution: Won't Fix
[~dgolovin],
thanks for the reply. There is no exception at the JAX-RS tooling level when processing the code sample, and there's an endpoint for the Java method in the Project explorer, as expected.
So, I'm closing this issue.
> Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17877
> URL: https://issues.jboss.org/browse/JBIDE-17877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
>
> Exception below was fixed by checking instance of target obect before casting to IType see JBIDE-17716 and skipping the rest of the code.
> Do we need to do something extra in this case?
> {code}
> org.jboss.tools.common
> Error
> Mon Jun 30 12:28:44 CEST 2014
> org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> org.jboss.tools.common.validation.JBTValidationException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> Caused by: java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:79)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.getReturnType(JdtUtils.java:1143)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1067)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:1037)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.recordAST(CompilationUnitsRepository.java:112)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.getAST(CompilationUnitsRepository.java:76)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:413)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16219) Errors about Hibernate console configuration, with no easy way to resolve
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16219?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-16219:
-------------------------------------------
Assignee: Max Rydahl Andersen
> Errors about Hibernate console configuration, with no easy way to resolve
> -------------------------------------------------------------------------
>
> Key: JBIDE-16219
> URL: https://issues.jboss.org/browse/JBIDE-16219
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Environment: JBDS 7.0.1.GA
> Reporter: Pete Muir
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.CR1
>
> Attachments: kitchensink-angularjs-bad.zip, kitchensink-angularjs-good.zip
>
>
> In my case, this appears to be caused by existing dot-files (which were created by a previous version of JBDS, on Maven Import...). Removing those files and reimporting fixes the problem.
> I haven't tested whether newer dot-files will cause the problem, or not.
> Attached are two projects, one which shows the problem, and one that doesn't (clean dot-files generated).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months