January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18372) Remote EAP server with mgmt profile - Publishing to server shows 0 % until done

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18372?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18372. --------------------------------- Resolution: Done fixed versions > Remote EAP server with mgmt profile - Publishing to server shows 0 % until done > ------------------------------------------------------------------------------- > > Key: JBIDE-18372 > URL: https://issues.jboss.org/browse/JBIDE-18372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha1, 4.2.1.Final > > > When I publish a very big project to a remote server and it's taking minutes, the status bar still keeps saying 0 % is complete. > I got this issue with a remote EAP 6.3 with management profile. Not sure about file operations profile. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18372) Remote EAP server with mgmt profile - Publishing to server shows 0 % until done

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18372?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18372: -------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.3.x) > Remote EAP server with mgmt profile - Publishing to server shows 0 % until done > ------------------------------------------------------------------------------- > > Key: JBIDE-18372 > URL: https://issues.jboss.org/browse/JBIDE-18372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > When I publish a very big project to a remote server and it's taking minutes, the status bar still keeps saying 0 % is complete. > I got this issue with a remote EAP 6.3 with management profile. Not sure about file operations profile. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3089) x509 Authentication to OpenShift

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3089?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3089: ----------------------------------- [~mmusaji]Our focus here is on v3. Any changes to v2 functionality require negotiation/coordination across multiple teams. > x509 Authentication to OpenShift > -------------------------------- > > Key: JBDS-3089 > URL: https://issues.jboss.org/browse/JBDS-3089 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Eric Rich > Assignee: Max Rydahl Andersen > Labels: authentication, ssl > Fix For: 8.0.x > > > Currently customers are asking for RHC to support x509 Authentication with the broker service (https://bugzilla.redhat.com/show_bug.cgi?id=1089703). The same is being asked of JBDS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19015) JPA Hibernate validator cannot work with the annotation @ElementCollection

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19015?page=com.atlassian.jira.plugi... ] Matous Jobanek updated JBIDE-19015: ----------------------------------- Attachment: ui-ejb-minimized.zip > JPA Hibernate validator cannot work with the annotation @ElementCollection > -------------------------------------------------------------------------- > > Key: JBIDE-19015 > URL: https://issues.jboss.org/browse/JBIDE-19015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: JBDS 8.0.1.GA > Reporter: Matous Jobanek > Attachments: ui-ejb-minimized.zip > > > The JPA Hibernate cannot work with variables annotated with the annotation @ElementCollection. When this annotation is used and for example the annotation @ManyToOne is used as well, the JBDS shows errors at places where they shouldn't be. > Follow my instructions to reproduce this issue: > 1. Download attached reproducer ui-ejb-minimized.zip > 2. Extract it > 3. Import the project into JBDS as an existing maven project > 4. Look at the errors. There are two errors for this project: > {noformat} > Target entity is not defined Person.java /ui-ejb-minimized/src/main/java/org/jboss/seam/example/ui line 25 JPA Problem > The given name of the entity "org.jboss.seam.example.ui.Country" is empty Country.java /ui-ejb-minimized/src/main/java/org/jboss/seam/example/ui line 9 JPA Problem > {noformat} > Both of them are unnecessary because both the target entity and the name of the entity are optional. > 5. Comment the variable: > {code} > @ElementCollection > private List<String> notes = new ArrayList<String>(); > {code} > 6. Save the class Person > 7. Click on Project -> Clean > Then all the errors will disappear. > 8. uncomment the variable with the annotation back > 9. Save the class Person > 10. Click on Project -> Clean > The two errors are back > The attached reproducer is minimized Seam project ui-ejb of the example ui. https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/ui > This Seam example is more complicated and the number of the wrong errors shown in JBDS is much bigger. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19015) JPA Hibernate validator cannot work with the annotation @ElementCollection

by Matous Jobanek (JIRA)

Matous Jobanek created JBIDE-19015: -------------------------------------- Summary: JPA Hibernate validator cannot work with the annotation @ElementCollection Key: JBIDE-19015 URL: https://issues.jboss.org/browse/JBIDE-19015 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Environment: JBDS 8.0.1.GA Reporter: Matous Jobanek The JPA Hibernate cannot work with variables annotated with the annotation @ElementCollection. When this annotation is used and for example the annotation @ManyToOne is used as well, the JBDS shows errors at places where they shouldn't be. Follow my instructions to reproduce this issue: 1. Download attached reproducer ui-ejb-minimized.zip 2. Extract it 3. Import the project into JBDS as an existing maven project 4. Look at the errors. There are two errors for this project: {noformat} Target entity is not defined Person.java /ui-ejb-minimized/src/main/java/org/jboss/seam/example/ui line 25 JPA Problem The given name of the entity "org.jboss.seam.example.ui.Country" is empty Country.java /ui-ejb-minimized/src/main/java/org/jboss/seam/example/ui line 9 JPA Problem {noformat} Both of them are unnecessary because both the target entity and the name of the entity are optional. 5. Comment the variable: {code} @ElementCollection private List<String> notes = new ArrayList<String>(); {code} 6. Save the class Person 7. Click on Project -> Clean Then all the errors will disappear. 8. uncomment the variable with the annotation back 9. Save the class Person 10. Click on Project -> Clean The two errors are back The attached reproducer is minimized Seam project ui-ejb of the example ui. https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/ui This Seam example is more complicated and the number of the wrong errors shown in JBDS is much bigger. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3089) x509 Authentication to OpenShift

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3089?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-3089: -------------------------------------- [~maxandersen] [~burrsutter] to confirm but discussions for OSE v2 and OSE v3 are on going. They can confirm but if customer will use OSE v3 then this feature will more than likely be implemented for that. OSE v2 support will need product management decision but unlikely to be done for V2. [~burrsutter] agree? > x509 Authentication to OpenShift > -------------------------------- > > Key: JBDS-3089 > URL: https://issues.jboss.org/browse/JBDS-3089 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Eric Rich > Assignee: Max Rydahl Andersen > Labels: authentication, ssl > Fix For: 8.0.x > > > Currently customers are asking for RHC to support x509 Authentication with the broker service (https://bugzilla.redhat.com/show_bug.cgi?id=1089703). The same is being asked of JBDS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3089) x509 Authentication to OpenShift

by Ken Evensen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3089?page=com.atlassian.jira.plugin.... ] Ken Evensen commented on JBDS-3089: ----------------------------------- The customer uses x509 authentication (PKCS12 certificates) almost exclusively. In order to use JBDS with their OpenShift installation, this is a necessity. When OSE 3.x is deployed at the customer, once again they will be using x509 authentication. I would imagine JBDS will still be the go to IDE for developing JBoss EAP apps in OSE 3.x. Therefore this feature will still be required in the future. > x509 Authentication to OpenShift > -------------------------------- > > Key: JBDS-3089 > URL: https://issues.jboss.org/browse/JBDS-3089 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Eric Rich > Assignee: Max Rydahl Andersen > Labels: authentication, ssl > Fix For: 8.0.x > > > Currently customers are asking for RHC to support x509 Authentication with the broker service (https://bugzilla.redhat.com/show_bug.cgi?id=1089703). The same is being asked of JBDS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19014) JAX-RS Web Services in Project Explorer does not show properly inherited metadata (abstract class)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19014?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19014: ---------------------------------- Summary: JAX-RS Web Services in Project Explorer does not show properly inherited metadata (abstract class) (was: JAX-RS Web Services in Project Explorer does not show properly inherited metadata from abstract class) > JAX-RS Web Services in Project Explorer does not show properly inherited metadata (abstract class) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19014 > URL: https://issues.jboss.org/browse/JBIDE-19014 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.1.Final > Reporter: Marián Labuda > Labels: jax-rs > Fix For: 4.3.x > > > I am having abstract class and it's descendant with following code. > {code:title=AbstractResource.java} > @Path("/resource") > public abstract class AbstractResource { > @GET > public abstract void getSomeObject(); > } > {code} > {code:title=SpecificResource.java} > public class SpecificResource extends AbstractResource { > @GET > @Path("specific-object") > @Override > public void getSomeObject() { > // some code > } > } > {code} > Implementation of getSomeObject along with its path is used for evaluation of HTTP GET request, but in JAX-RS Web Services Explorer is shown only matching URL from abstract class _/resource_ instead of _/resource/specific-object_. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16145) All wizards: Consider replacing "*"-decoration for for fields that require input

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16145?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16145: ------------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > All wizards: Consider replacing "*"-decoration for for fields that require input > -------------------------------------------------------------------------------- > > Key: JBIDE-16145 > URL: https://issues.jboss.org/browse/JBIDE-16145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.3.x > > Attachments: OpenShift_newapp.png, required-field.png > > > In New OpenShift Application wizard, the following have * (asterisk) at the beginning: > * use existing application check box > * name field > * type field > This should be the (i) icon (blue i in a circle) like in Window>Install New Software wizard. > There maybe more in the wizard but I haven't got past the first page. > !OpenShift_newapp.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18954) JAX-RS Web Services in Project Explorer does not show properly inherited metadata (interface)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18954?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18954: ---------------------------------- Summary: JAX-RS Web Services in Project Explorer does not show properly inherited metadata (interface) (was: JAX-RS Web Services in Project Explorer does not show properly inherited metadata) > JAX-RS Web Services in Project Explorer does not show properly inherited metadata (interface) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18954 > URL: https://issues.jboss.org/browse/JBIDE-18954 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.1.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.x > > > I have an interface with annotated JAX-RS methods (HTTP method type, path, consumes...) CarResourceInterface and implementation of this interface CarResourceImpl. Inheriting all metadata related to one method should affect processing of this JAX-RS web services - new values from Impl should be used and probably it would be good to show it also in JAX-RS Web Services node in Project Explorer view. Currently there are shown only interface JAX-RS web services and any change in Impl is ignored in this view. > There are chunk of codes for interface and implementation. At first I was having only interface and it's web service has been shown in JAX-RS Web Services. Then I have added implementation and overrode interface but still in JAX-RS Web Services the interface is shown. > {code:title=CarResource.java} > @Path("car") > public interface CarResource { > > @GET > @Path("/{id:[0-9][0-9]*}") > @Produces({ "application/xml", "application/json" }) > public Response findById(@PathParam("id") final Long id); > } > {code} > {code:title=CarResourceImpl.java} > public class CarResourceImpl implements CarResource { > @GET > @Path("/{carid:a[0-9]*}") > @Produces({ "text", "application/json" }) > public Response findById(@PathParam("carid") final Long id) { > //TODO: retrieve the car > return null; > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015