[JBoss JIRA] (JBIDE-16713) Application wizard: Deploying shared (e.g. SVN) project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16713?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16713:
-------------------------------------
Summary: Application wizard: Deploying shared (e.g. SVN) project (was: OpenShift Wizard: Deploying shared (e.g. SVN) project)
> Application wizard: Deploying shared (e.g. SVN) project
> -------------------------------------------------------
>
> Key: JBIDE-16713
> URL: https://issues.jboss.org/browse/JBIDE-16713
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Labels: application_wizard
> Fix For: 4.2.x
>
>
> It is not possible to deploy SVN project yet. In new application wizard on the second wizard page is possibility to choose (hit the Browse... button) project, but in browsing dialog is note, that only non-shared or git project are possible to import.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18068) JAX-RS Explorer doesn't have "expand" icon
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18068?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-18068.
-----------------------------------
Verified with JBDS 8.0.0 CR1-v20140831-0335-B201
> JAX-RS Explorer doesn't have "expand" icon
> ------------------------------------------
>
> Key: JBIDE-18068
> URL: https://issues.jboss.org/browse/JBIDE-18068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.CR1
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
> Attachments: JBIDE-18068.ogv
>
>
> After a JAX-RS resource is created in a fresh project, the JAX-RS Explorer doesn't seem to be updated because the "expand" icon hasn't been appeared so it looks like the explorer doesn't contain any items. However, the explorer works properly and can be even expanded.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16720) Server Adapter: Allow easier access to openshift operations from jboss servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16720:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> Server Adapter: Allow easier access to openshift operations from jboss servers
> ------------------------------------------------------------------------------
>
> Key: JBIDE-16720
> URL: https://issues.jboss.org/browse/JBIDE-16720
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.1.Final
> Reporter: Mark Drilling
> Labels: server_adapter
> Fix For: 4.3.x
>
>
> We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case.
> Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push.
> Currently, we connect to an OpenShift DV instance like this:
> 1) Deploy DV cartridge via OpenShift web console.
> 2) Port forward from command line using rhc port-forward
> 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective
> The issues we observed:
> 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo.
> 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list.
> Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16720) Server Adapter: Allow easier access to openshift operations from jboss servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16720:
-------------------------------------
Labels: server_adapter (was: )
> Server Adapter: Allow easier access to openshift operations from jboss servers
> ------------------------------------------------------------------------------
>
> Key: JBIDE-16720
> URL: https://issues.jboss.org/browse/JBIDE-16720
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.1.Final
> Reporter: Mark Drilling
> Labels: server_adapter
> Fix For: 4.3.x
>
>
> We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case.
> Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push.
> Currently, we connect to an OpenShift DV instance like this:
> 1) Deploy DV cartridge via OpenShift web console.
> 2) Port forward from command line using rhc port-forward
> 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective
> The issues we observed:
> 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo.
> 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list.
> Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15881) Annotated field with QueryParam missing in URL Endpoint template
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15881?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-15881.
-----------------------------------
Verified with JBDS 8.0.0 CR1-v20140831-0335-B201
> Annotated field with QueryParam missing in URL Endpoint template
> ----------------------------------------------------------------
>
> Key: JBIDE-15881
> URL: https://issues.jboss.org/browse/JBIDE-15881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
>
> Take the following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @QueryParam("foo1")
> private String foo2;
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> return new BookResource();
> }
> }
> {code}
> and
> {code}
> @Produces({ MediaType.APPLICATION_XML, "application/json" })
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> ASSERT: the URL Template for the Endpoint should be something like
> {code}
> /products/{productType}/{id}?foo1={String}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16444) Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16444?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16444:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16444
> URL: https://issues.jboss.org/browse/JBIDE-16444
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.x
>
> Attachments: accept-certificate.png
>
>
> In JBIDE-14768 we introduced a dialog that allows users to accept/refuse untrusted SSL certificates.
> !accept-certificate.png!
> The authorization is currently stored for the current Eclipse session. We should store those authorizations in the Eclipse preferences and add a preferences page which shows these and allows users to revoke the given authorizations.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18181) Errors when hibernate.cfg.xml not at classpath root
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18181?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-18181:
------------------------------
Labels: respin-a (was: )
> Errors when hibernate.cfg.xml not at classpath root
> ---------------------------------------------------
>
> Key: JBIDE-18181
> URL: https://issues.jboss.org/browse/JBIDE-18181
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599, Hibernate 4.1.12
> Reporter: Luke Maurer
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> If a project keeps its hibernate.cfg.xml anywhere besides the root of the classpath, Hibernate Tools will not recognize it. In the Hibernate Configurations tree, expanding either Session Factory or Database gives an error ending in “/hibernate.cfg.xml not found”. (The Configuration subtree appears to work.)
> As a workaround, if I go into the directory holding WEB-INF/classes (i.e. where compiled Java bytecode goes) and symlink hibernate.cfg.xml there, it seems to work.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months