[JBoss JIRA] (JBIDE-15402) Doubled warnings Multiple JAX-RS Activators
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15402?page=com.atlassian.jira.plugi... ]
Radoslav Rábara updated JBIDE-15402:
------------------------------------
Steps to Reproduce:
STEP: Create Dynamic Web Project with JAX-RS support
STEP: Create JAX-RS Activator, for example:
{code:title=Activator1.java|borderStyle=solid}
import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;
@ApplicationPath("/test")
public class Activator1 extends Application {
}
{code}
STEP: Create another JAX-RS Activator
ASSERT: There are 2 warnings: Multiple JAX-RS Activators are defined for the project. (for both files)
FAIL: There are 4 warnings. (two same warnings for both files)
was:
STEP: Create Dynamic Web Project with JAX-RS support
STEP: Create JAX-RS Activator, for example:
{code:title=Activator1.java|borderStyle=solid}
import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;
@ApplicationPath("/test")
public class Activator1 extends Application {
}
{code}
STEP: Create another JAX-RS Activator
ASSERT: There are 2 warnings: Multiple JAX-RS ACtivators are defined for the project. (for both files)
FAIL: There are 4 warnings. (two same warnings for both files)
> Doubled warnings Multiple JAX-RS Activators
> -------------------------------------------
>
> Key: JBIDE-15402
> URL: https://issues.jboss.org/browse/JBIDE-15402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Radoslav Rábara
> Labels: jax-rs, warning_messages, webservices
> Fix For: 4.1.1.Alpha1
>
> Attachments: jax-rs warnings.jpg
>
>
> After creating multiple JAX-RS Activators in Dynamic Web Project with JAX-RS support, there are doubled warnings ("Multiple JAX-RS Activators are defined for the project.") for each activator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15402) Doubled warnings Multiple JAX-RS Activators
by Radoslav Rábara (JIRA)
Radoslav Rábara created JBIDE-15402:
---------------------------------------
Summary: Doubled warnings Multiple JAX-RS Activators
Key: JBIDE-15402
URL: https://issues.jboss.org/browse/JBIDE-15402
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.0.Final
Reporter: Radoslav Rábara
Fix For: 4.1.1.Alpha1
After creating multiple JAX-RS Activators in Dynamic Web Project with JAX-RS support, there are doubled warnings ("Multiple JAX-RS Activators are defined for the project.") for each activator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15400) openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15400?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-15400.
---------------------------------------
Resolution: Duplicate Issue
Zend studio seem to use older version of client library thus this is a duplicate of https://issues.jboss.org/browse/JBIDE-15396
> openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-15400
> URL: https://issues.jboss.org/browse/JBIDE-15400
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Attachments: add-openshift-target-failure.png
>
>
> Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
> The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
> Steps to reproduce:
> 1. open Zend Studio IDE
> 2. in the main menu, go to Window > Preferences and choose Openshift
> 3. click Apply, than OK (wizard should be closed)
> 4. click on Add new target button in down-right corner of the current
> Targets view (I am attaching a screenshot)
> 5. in the opened Add target wizard, choose Openshift and click Next button
> 6. in next screen, enter your credentials for your account at the Openshift
> (the RedHat's staging environment)
> 8. click on Generate button on the same screen (in order to generate new SSH
> Private key)
> 9. you will be asked if you wish to proceed creating the new private key in
> selected directory - click OK
> 10. click Finish button
> Expected result:
> Openshift target to be added successfully in targets list
> Actual result:
> I am attaching the result as well. (add openshift target failure.png)
> Error message is prompted to the user:
> {code}
> com.openshift.client.OpenShiftRequestException: Unknow request parameter
> type array
> {code}
> and only options are to go Back or to Cancel adding this target.
> !add-openshift-target-failure.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15401) CLONE - jbosstools-server API Compatibility for master
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15401?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15401:
--------------------------------
Description: Verify Latest version from jbosstools-server/master branch has no API Compatibility problems. (was: Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem:
"The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added".
According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2
|| Interface change || Conditions || Compatibility ||
|Add API field|If interface not implementable by Clients | Binary compatible|
|Add API field|If interface implementable by Clients| Breaks compatibility (2)|
(2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields.
)
> CLONE - jbosstools-server API Compatibility for master
> -------------------------------------------------------
>
> Key: JBIDE-15401
> URL: https://issues.jboss.org/browse/JBIDE-15401
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.1.Alpha1
> Reporter: Rob Stryker
> Priority: Blocker
> Labels: api-compatibility
> Fix For: 4.1.1.Alpha1
>
>
> Verify Latest version from jbosstools-server/master branch has no API Compatibility problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15401) CLONE - jbosstools-server API Compatibility for master
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-15401:
-----------------------------------
Summary: CLONE - jbosstools-server API Compatibility for master
Key: JBIDE-15401
URL: https://issues.jboss.org/browse/JBIDE-15401
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.1.Alpha1
Reporter: Rob Stryker
Priority: Blocker
Fix For: 4.1.1.Alpha1
Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem:
"The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added".
According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2
|| Interface change || Conditions || Compatibility ||
|Add API field|If interface not implementable by Clients | Binary compatible|
|Add API field|If interface implementable by Clients| Breaks compatibility (2)|
(2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15400) openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15400?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15400:
-------------------------------------
Description:
Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
Steps to reproduce:
1. open Zend Studio IDE
2. in the main menu, go to Window > Preferences and choose Openshift
3. click Apply, than OK (wizard should be closed)
4. click on Add new target button in down-right corner of the current
Targets view (I am attaching a screenshot)
5. in the opened Add target wizard, choose Openshift and click Next button
6. in next screen, enter your credentials for your account at the Openshift
(the RedHat's staging environment)
8. click on Generate button on the same screen (in order to generate new SSH
Private key)
9. you will be asked if you wish to proceed creating the new private key in
selected directory - click OK
10. click Finish button
Expected result:
Openshift target to be added successfully in targets list
Actual result:
I am attaching the result as well. (add openshift target failure.png)
Error message is prompted to the user:
{code}
com.openshift.client.OpenShiftRequestException: Unknow request parameter
type array
{code}
and only options are to go Back or to Cancel adding this target.
!add-openshift-target-failure.png!
was:
Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
Steps to reproduce:
1. open Zend Studio IDE
2. in the main menu, go to Window > Preferences and choose Openshift
3. add the following in the corresponding fields:
Server URL: https://ec2-54-227-159-152.compute-1.amazonaws.com
Domain: dev.rhcloud.com
4. click Apply, than OK (wizard should be closed)
5. click on Add new target button in down-right corner of the current
Targets view (I am attaching a screenshot)
6. in the opened Add target wizard, choose Openshift and click Next button
7. in next screen, enter your credentials for your account at the Openshift
(the RedHat's staging environment)
8. click on Generate button on the same screen (in order to generate new SSH
Private key)
9. you will be asked if you wish to proceed creating the new private key in
selected directory - click OK
10. click Finish button
Expected result:
Openshift target to be added successfully in targets list
Actual result:
I am attaching the result as well. (add openshift target failure.png)
Error message is prompted to the user:
{code}
com.openshift.client.OpenShiftRequestException: Unknow request parameter
type array
{code}
and only options are to go Back or to Cancel adding this target.
!add-openshift-target-failure.png!
> openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-15400
> URL: https://issues.jboss.org/browse/JBIDE-15400
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Attachments: add-openshift-target-failure.png
>
>
> Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
> The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
> Steps to reproduce:
> 1. open Zend Studio IDE
> 2. in the main menu, go to Window > Preferences and choose Openshift
> 3. click Apply, than OK (wizard should be closed)
> 4. click on Add new target button in down-right corner of the current
> Targets view (I am attaching a screenshot)
> 5. in the opened Add target wizard, choose Openshift and click Next button
> 6. in next screen, enter your credentials for your account at the Openshift
> (the RedHat's staging environment)
> 8. click on Generate button on the same screen (in order to generate new SSH
> Private key)
> 9. you will be asked if you wish to proceed creating the new private key in
> selected directory - click OK
> 10. click Finish button
> Expected result:
> Openshift target to be added successfully in targets list
> Actual result:
> I am attaching the result as well. (add openshift target failure.png)
> Error message is prompted to the user:
> {code}
> com.openshift.client.OpenShiftRequestException: Unknow request parameter
> type array
> {code}
> and only options are to go Back or to Cancel adding this target.
> !add-openshift-target-failure.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15400) openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15400?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15400:
-------------------------------------
Description:
Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
Steps to reproduce:
1. open Zend Studio IDE
2. in the main menu, go to Window > Preferences and choose Openshift
3. add the following in the corresponding fields:
Server URL: https://ec2-54-227-159-152.compute-1.amazonaws.com
Domain: dev.rhcloud.com
4. click Apply, than OK (wizard should be closed)
5. click on Add new target button in down-right corner of the current
Targets view (I am attaching a screenshot)
6. in the opened Add target wizard, choose Openshift and click Next button
7. in next screen, enter your credentials for your account at the Openshift
(the RedHat's staging environment)
8. click on Generate button on the same screen (in order to generate new SSH
Private key)
9. you will be asked if you wish to proceed creating the new private key in
selected directory - click OK
10. click Finish button
Expected result:
Openshift target to be added successfully in targets list
Actual result:
I am attaching the result as well. (add openshift target failure.png)
Error message is prompted to the user:
{quote}
com.openshift.client.OpenShiftRequestException: Unknow request parameter
type array
{quote}
and only options are to go Back or to Cancel adding this target.
!add-openshift-target-failure.png!
was:
Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
> openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-15400
> URL: https://issues.jboss.org/browse/JBIDE-15400
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Attachments: add-openshift-target-failure.png
>
>
> Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
> The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
> Steps to reproduce:
> 1. open Zend Studio IDE
> 2. in the main menu, go to Window > Preferences and choose Openshift
> 3. add the following in the corresponding fields:
> Server URL: https://ec2-54-227-159-152.compute-1.amazonaws.com
> Domain: dev.rhcloud.com
> 4. click Apply, than OK (wizard should be closed)
> 5. click on Add new target button in down-right corner of the current
> Targets view (I am attaching a screenshot)
> 6. in the opened Add target wizard, choose Openshift and click Next button
> 7. in next screen, enter your credentials for your account at the Openshift
> (the RedHat's staging environment)
> 8. click on Generate button on the same screen (in order to generate new SSH
> Private key)
> 9. you will be asked if you wish to proceed creating the new private key in
> selected directory - click OK
> 10. click Finish button
> Expected result:
> Openshift target to be added successfully in targets list
> Actual result:
> I am attaching the result as well. (add openshift target failure.png)
> Error message is prompted to the user:
> {quote}
> com.openshift.client.OpenShiftRequestException: Unknow request parameter
> type array
> {quote}
> and only options are to go Back or to Cancel adding this target.
> !add-openshift-target-failure.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15400) openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15400?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15400:
-------------------------------------
Attachment: add-openshift-target-failure.png
> openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-15400
> URL: https://issues.jboss.org/browse/JBIDE-15400
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Attachments: add-openshift-target-failure.png
>
>
> Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough.
> The only way they can fix this currently is by upgrading the client library to at least 2.0.3.
> Steps to reproduce:
> 1. open Zend Studio IDE
> 2. in the main menu, go to Window > Preferences and choose Openshift
> 3. add the following in the corresponding fields:
> Server URL: https://ec2-54-227-159-152.compute-1.amazonaws.com
> Domain: dev.rhcloud.com
> 4. click Apply, than OK (wizard should be closed)
> 5. click on Add new target button in down-right corner of the current
> Targets view (I am attaching a screenshot)
> 6. in the opened Add target wizard, choose Openshift and click Next button
> 7. in next screen, enter your credentials for your account at the Openshift
> (the RedHat's staging environment)
> 8. click on Generate button on the same screen (in order to generate new SSH
> Private key)
> 9. you will be asked if you wish to proceed creating the new private key in
> selected directory - click OK
> 10. click Finish button
> Expected result:
> Openshift target to be added successfully in targets list
> Actual result:
> I am attaching the result as well. (add openshift target failure.png)
> Error message is prompted to the user:
> {quote}
> com.openshift.client.OpenShiftRequestException: Unknow request parameter
> type array
> {quote}
> and only options are to go Back or to Cancel adding this target.
> !add-openshift-target-failure.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months