[JBoss JIRA] (JBIDE-13581) Generate DTO with @Xml annotations from given POJO for the XML/JSON Mediatypes
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13581?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-13581:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Generate DTO with @Xml annotations from given POJO for the XML/JSON Mediatypes
> ------------------------------------------------------------------------------
>
> Key: JBIDE-13581
> URL: https://issues.jboss.org/browse/JBIDE-13581
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.6.x
>
>
> use-case is:
> - if a user does not want to expose directly its entities, he needs to provide some DTOs with @javax.xml.bind.annotation.XmlRootElement annotation (so that the JAX-RS runtime can unmarshall/marshall the request and response bodies).
> These DTOs coding could be automated by a wizard which would let the user select the POJO fields and choose his prefered annotation style (field vs method) and output package
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-18565) Default generated entity is invalid
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18565?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18565:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Default generated entity is invalid
> -----------------------------------
>
> Key: JBIDE-18565
> URL: https://issues.jboss.org/browse/JBIDE-18565
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate, upstream
> Reporter: Arun Gupta
> Assignee: Koen Aers
> Fix For: 4.6.x
>
>
> Code for a default generated JPA entity looks like:
> package org.svcc;
> import java.io.Serializable;
> import javax.persistence.*;
> /**
> * Entity implementation class for Entity: Student
> *
> */
> @Entity
> public class Student implements Serializable {
>
> private static final long serialVersionUID = 1L;
> public Student() {
> super();
> }
>
> }
> This is an invalid entity because each JPA entity must have a primary key.
> For a simpler OOTB experience, generate a default primary key.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-18352) Include a working JAX-WS configurator in the m2e catalog
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18352?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18352:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Include a working JAX-WS configurator in the m2e catalog
> --------------------------------------------------------
>
> Key: JBIDE-18352
> URL: https://issues.jboss.org/browse/JBIDE-18352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Fred Bricon
> Fix For: 4.6.x
>
>
> there are compilation/build errors when importing projects using the jaxws maven plugin (see javaee7-samples case on JBDS-2847), because the project is not properly configured during the import. Generated code from the project's WSDL would be missing.
> The known work-around is to invoke maven from command-line to have the code generated.
> Having a fine-tuned, working m2e configurator (ie, tuned for incremental builds and not triggering a full interface generation when some unrelated file is edited) would fix the problem.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22335) NullPointerException in JaxrsMarkerResolutionGenerator.findJaxrsElement
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22335?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22335:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NullPointerException in JaxrsMarkerResolutionGenerator.findJaxrsElement
> -----------------------------------------------------------------------
>
> Key: JBIDE-22335
> URL: https://issues.jboss.org/browse/JBIDE-22335
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.ws.jaxrs.ui.quickfix.JaxrsMarkerResolutionGenerator.findJaxrsElement(JaxrsMarkerResolutionGenerator.java:246)
> at org.jboss.tools.ws.jaxrs.ui.quickfix.JaxrsMarkerResolutionGenerator.generateMissingAttributesCompletionProposal(JaxrsMarkerResolutionGenerator.java:163)
> at org.jboss.tools.ws.jaxrs.ui.quickfix.JaxrsMarkerResolutionGenerator.getCorrections(JaxrsMarkerResolutionGenerator.java:126)
> at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor$SafeCorrectionCollector.safeRun(JavaCorrectionProcessor.java:378)
> at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor$SafeCorrectionProcessorAccess.run(JavaCorrectionProcessor.java:339)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor$SafeCorrectionProcessorAccess.process(JavaCorrectionProcessor.java:335)
> at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor.collectCorrections(JavaCorrectionProcessor.java:468)
> at org.eclipse.jdt.internal.ui.text.java.hover.ProblemHover$ProblemInfo.getJavaAnnotationFixes(ProblemHover.java:225)
> at org.eclipse.jdt.internal.ui.text.java.hover.ProblemHover$ProblemInfo.getCompletionProposals(ProblemHover.java:199)
> at org.eclipse.jdt.internal.ui.text.java.hover.AbstractAnnotationHover$AnnotationInformationControl.deferredCreateContent(AbstractAnnotationHover.java:285)
> at org.eclipse.jdt.internal.ui.text.java.hover.AbstractAnnotationHover$AnnotationInformationControl.setInput(AbstractAnnotationHover.java:186)
> at org.eclipse.jface.text.AbstractInformationControlManager.internalShowInformationControl(AbstractInformationControlManager.java:1181)
> at org.eclipse.jface.text.AbstractInformationControlManager.presentInformation(AbstractInformationControlManager.java:1150)
> at org.eclipse.jface.text.AbstractHoverInformationControlManager.presentInformation(AbstractHoverInformationControlManager.java:902)
> at org.eclipse.jface.text.TextViewerHoverManager.doPresentInformation(TextViewerHoverManager.java:243)
> at org.eclipse.jface.text.TextViewerHoverManager$5.run(TextViewerHoverManager.java:233)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
> {noformat}
> Bundles:
> | org.eclipse.core.commands | 3.7.0.v20150422-0725 | 3.7.0.v20150422-0725 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 |
> Operating Systems:
> | Linux | 4.2.0 | 4.2.0 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571f286ce4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22862) Example "." found when searching for a Camel quickstart
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22862?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22862:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Example "." found when searching for a Camel quickstart
> -------------------------------------------------------
>
> Key: JBIDE-22862
> URL: https://issues.jboss.org/browse/JBIDE-22862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.4.1.AM1
> Environment: JBoss Fuse Tools must be installed
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.6.x
>
>
> When the JBoss Fuse tools are installes, the Camel examples are available in JBoss Central. If you search for Camel, An example named "." is returned. It fails to import.
> See !http://content.screencast.com/users/fbricon/folders/Jing/media/36fb717a-1cd8-4c6a-8c25-b74d46c4c6be/00000447.png|width=700!
> That example should not be returned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-24503) Properties: Events are hardly useable
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24503?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24503:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Properties: Events are hardly useable
> -------------------------------------
>
> Key: JBIDE-24503
> URL: https://issues.jboss.org/browse/JBIDE-24503
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.6.x
>
> Attachments: events-entries.png, image-2017-05-23-22-58-58-587.png
>
>
> steps:
> # EXEC: create some new application (via template or image) so that you have a build and image pulling happening
> # EXEC: select project in OpenShift Explorer and open up "Properties". In "Properties" select "Events" tab. In event entries, select some item (ex. some "Pulling" in "Reason" column), inspect the details that are displayed for it
> Result:
> !events-entries.png!
> Many entries like "Pulling", "Failed Sync", "BackOff" etc. that have larger "Message" and "Source" are hardly useable.
> * If the "Message" is very long, you have to enlarge the "Value" column a lot to be able to read the message.
> * If the "Source" is multi-line, you'll only see the opening "{", the rest is simply not displayed.
> Workaround:
> open web console where the logs are nicely displayed
> !image-2017-05-23-22-58-58-587.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25225) OSIO login: error when the login window is closed by the user
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25225?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25225:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> OSIO login: error when the login window is closed by the user
> -------------------------------------------------------------
>
> Key: JBIDE-25225
> URL: https://issues.jboss.org/browse/JBIDE-25225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Martin Malina
> Fix For: 4.6.x
>
> Attachments: osio-error.png
>
>
> I tested the OSIO login feature and it works pretty well. But one thing should be fixed I think. When you click the icon and the login browser window is opened and then you change your mind and click Close on the window, you're given an error:
> Error login to cluster OpenShift.io
> !osio-error.png!
> I think in the case of the user closing the window there shouldn't be an error like this.
> I understand that we do need some form of indication if the username is correct (so the webpage accepts it), but the login in devstudio fails somehow. In this case it is correct to display an error.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23666) Update quickstarts on Central Home Page
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23666:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Update quickstarts on Central Home Page
> ---------------------------------------
>
> Key: JBIDE-23666
> URL: https://issues.jboss.org/browse/JBIDE-23666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.3.AM1
> Environment: Red Hat JBoss Developer Studio
> Version: 10.3.0.AM1
> Build id: AM1-v20161225-1238-B6761
> Build date: 20161225-1238
> Reporter: Josef Kopriva
> Assignee: Fred Bricon
> Fix For: 4.6.x
>
>
> Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur:
> {code:java}
> Description Resource Path Location Type
> Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem
> No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem
> {code}
> For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22917) HIDDEN below VpvDefaultTemplate.create (thrown in CoreDocumentImpl.createAttribute)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22917?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22917:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> HIDDEN below VpvDefaultTemplate.create (thrown in CoreDocumentImpl.createAttribute)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22917
> URL: https://issues.jboss.org/browse/JBIDE-22917
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> HIDDEN: HIDDEN
> at org.apache.xerces.dom.CoreDocumentImpl.createAttribute(null:-1)
> at org.apache.xerces.dom.ElementImpl.setAttribute(null:-1)
> at org.jboss.tools.vpe.preview.core.template.VpvDefaultTemplate.create(VpvDefaultTemplate.java:39)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:86)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.convertNode(VpvDomBuilder.java:123)
> at org.jboss.tools.vpe.preview.core.transform.VpvDomBuilder.buildVisualModel(VpvDomBuilder.java:49)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getVisualModel(VpvController.java:145)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:62)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | org.apache.xerces | 2.9.0.v201101211617 | 2.9.0.v201101211617 |
> | org.jboss.tools.vpe.preview.core | 3.8.0.Final-v20160609-2229-B3 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | Linux | 4.6.3.fc24 | 4.6.3.fc24 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5783a919e4b07f3dc2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-20492) Allow configuring FreeMarker (per project)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20492?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20492:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Allow configuring FreeMarker (per project)
> ------------------------------------------
>
> Key: JBIDE-20492
> URL: https://issues.jboss.org/browse/JBIDE-20492
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.6.x
>
>
> Some configuration settings affect parsing, and more such settings may appear in the future. A simple yet quite flexible and future-proof way of allowing configuring per project is adding a multi-line text input with label "Configuration settings (Java properites format)" under Project properties / FreeMarker, where the user can enter arbitrary text, then parse that with {{java.util.Properties}} and pass it to {{Configuration.setSettings(Properties)}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months