[JBoss JIRA] (JBIDE-15839) Exception while saving Provider in JAX-RS application
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15839?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15839:
----------------------------------
Summary: Exception while saving Provider in JAX-RS application (was: Exception while saving Server Filter in JAX-RS application)
> Exception while saving Provider in JAX-RS application
> -----------------------------------------------------
>
> Key: JBIDE-15839
> URL: https://issues.jboss.org/browse/JBIDE-15839
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.CR1
>
>
> Following exception was logged while working on a sample application, in which a Server Filter was edited and saved (error occurred while saving)
> {code}
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101)
> at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.addMarker(JaxrsMetamodelValidator.java:433)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsProviderValidatorDelegate.validateAtLeastOneImplementation(JaxrsProviderValidatorDelegate.java:161)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsProviderValidatorDelegate.internalValidate(JaxrsProviderValidatorDelegate.java:72)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsProviderValidatorDelegate.internalValidate(JaxrsProviderValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:33)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:315)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validateAll(JaxrsMetamodelValidator.java:282)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:157)
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:117)
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> ... 2 more
> {code}
--
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, 5 months
[JBoss JIRA] (JBIDE-15037) Runtime download progress not shown correctly on mac
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15037?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-15037.
---------------------------------
Fix Version/s: 4.1.1.Beta1
(was: 4.1.1.Final)
Resolution: Done
Closing.
> Runtime download progress not shown correctly on mac
> ----------------------------------------------------
>
> Key: JBIDE-15037
> URL: https://issues.jboss.org/browse/JBIDE-15037
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Environment: OS X Mountain Lion
> JBDS 7.0.0.Beta2
> Oracle Java 1.7
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Beta1
>
>
> Copied from JBIDE-14906
> {quote}
> This still doesn't work as expected - the speed is shown correctly, but the progress is close to zero. See this screencast:
> http://screencast.com/t/iGzkp5KG
> I remember seeing something similar when downloading project examples in the past.
> {quote}
> When you download a runtime on mac, the progress does not reflect the actual progress - the speed is accurate, but for example after 1 minut at 1 MB/s, the progress bar shows a total of 5 MB downloaded.
--
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, 5 months
[JBoss JIRA] (JBIDE-15037) Runtime download progress not shown correctly on mac
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15037?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-15037:
-------------------------------------
Assignee: Rob Stryker (was: Martin Malina)
I just tried this in JBDS 7.1.0.Beta1b B493 and there is no problem. I believe we discussed this in the past and you made some tweaks which made the problem go away for me - perhaps you added some delay so it wouldn't try to update the status all the time. So this can be safely resolved.
> Runtime download progress not shown correctly on mac
> ----------------------------------------------------
>
> Key: JBIDE-15037
> URL: https://issues.jboss.org/browse/JBIDE-15037
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Environment: OS X Mountain Lion
> JBDS 7.0.0.Beta2
> Oracle Java 1.7
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Final
>
>
> Copied from JBIDE-14906
> {quote}
> This still doesn't work as expected - the speed is shown correctly, but the progress is close to zero. See this screencast:
> http://screencast.com/t/iGzkp5KG
> I remember seeing something similar when downloading project examples in the past.
> {quote}
> When you download a runtime on mac, the progress does not reflect the actual progress - the speed is accurate, but for example after 1 minut at 1 MB/s, the progress bar shows a total of 5 MB downloaded.
--
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, 5 months
[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15830 at 11/5/13 8:36 AM:
-------------------------------------------------------------------
I see the jboss tools using the following user-agent:
{code}
"Java OpenShift REST/2.5.0-SNAPSHOT (org.jboss.tools.openshift.express.core 2.5.1.qualifier)"
{code}
I think I found the issue in the client:
The check for authkey (and the resulting prepending/using of "OpenShift") is not executed if the useragent is set AFTER the client instance is created. It's only executed when the useragent is passed at client creation time (the above snippet is executed at client creation time).
The current implementation would set the user-agent to the client AFTER it is created (this setup allows client users to provide their own client implementation). To fix this we would simply add the check to get executed if the useragent is passed in after instance creation.
Nevertheless, I think that we should move this logic to the jenkins plugin, this should not be part of the openshift-java-client since it's jenkins-plugin specific. IMHO we should make sure the jenkins-plugin can set the useragent it needs.
was (Author: adietish):
I see the jboss tools using the following user-agent:
{code}
"Java OpenShift REST/2.5.0-SNAPSHOT (org.jboss.tools.openshift.express.core 2.5.1.qualifier)"
{code}
I think I found the issue in the client:
The check for authkey (and the resulting prepending/using of "OpenShift") is not executed if the useragent is set AFTER the client instance is created. It's only executed when the useragent is passed at client creation time. The current implementation would set the user-agent to the client AFTER it is created (this setup allows client users to provide their own client implementation). To fix this we would simply add the check to get executed if the useragent is passed in after instance creation. Nevertheless, I think that we should move this logic to the jenkins plugin, this should not be part of the openshift-java-client since it's jenkins-plugin specific. IMHO we should make sure the jenkins-plugin can set the useragent it needs.
> openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15830
> URL: https://issues.jboss.org/browse/JBIDE-15830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Brenton Leanhardt
> Assignee: Andre Dietisheim
> Labels: openshift-java-client
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
>
> OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin.
> In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling.
> You can see this for details:
> https://github.com/openshift/origin-server/blob/master/documentation/arch...
> In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45).
--
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, 5 months
[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15830:
------------------------------------------
I see the jboss tools using the following user-agent:
{code}
"Java OpenShift REST/2.5.0-SNAPSHOT (org.jboss.tools.openshift.express.core 2.5.1.qualifier)"
{code}
I think I found the issue in the client:
The check for authkey (and the resulting prepending/using of "OpenShift") is not executed if the useragent is set AFTER the client instance is created. It's only executed when the useragent is passed at client creation time. The current implementation would set the user-agent to the client AFTER it is created (this setup allows client users to provide their own client implementation). To fix this we would simply add the check to get executed if the useragent is passed in after instance creation. Nevertheless, I think that we should move this logic to the jenkins plugin, this should not be part of the openshift-java-client since it's jenkins-plugin specific. IMHO we should make sure the jenkins-plugin can set the useragent it needs.
> openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15830
> URL: https://issues.jboss.org/browse/JBIDE-15830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Brenton Leanhardt
> Assignee: Andre Dietisheim
> Labels: openshift-java-client
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
>
> OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin.
> In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling.
> You can see this for details:
> https://github.com/openshift/origin-server/blob/master/documentation/arch...
> In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45).
--
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, 5 months
[JBoss JIRA] (JBIDE-15858) Application wizard: server that does not support env variables causes error when creating app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15858?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15858:
-------------------------------------
Summary: Application wizard: server that does not support env variables causes error when creating app (was: No supported modifying environment variables cause error)
> Application wizard: server that does not support env variables causes error when creating app
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-15858
> URL: https://issues.jboss.org/browse/JBIDE-15858
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: environment_variables.png
>
>
> If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..."
> Another one is show after attempt to add variable.
> Other "Processing environment variables..."
> Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion).
--
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, 5 months
[JBoss JIRA] (JBIDE-15858) No supported modifying environment variables cause error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15858?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15858:
-------------------------------------
Fix Version/s: 4.1.1.Beta1
4.2.0.Alpha1
> No supported modifying environment variables cause error
> --------------------------------------------------------
>
> Key: JBIDE-15858
> URL: https://issues.jboss.org/browse/JBIDE-15858
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: environment_variables.png
>
>
> If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..."
> Another one is show after attempt to add variable.
> Other "Processing environment variables..."
> Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion).
--
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, 5 months
[JBoss JIRA] (JBIDE-15858) No supported modifying environment variables cause error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15858?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15858:
-------------------------------------
Priority: Major (was: Critical)
> No supported modifying environment variables cause error
> --------------------------------------------------------
>
> Key: JBIDE-15858
> URL: https://issues.jboss.org/browse/JBIDE-15858
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: environment_variables.png
>
>
> If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..."
> Another one is show after attempt to add variable.
> Other "Processing environment variables..."
> Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion).
--
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, 5 months
[JBoss JIRA] (JBIDE-15858) No supported modifying environment variables cause error
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15858?page=com.atlassian.jira.plugi... ]
Marián Labuda reassigned JBIDE-15858:
-------------------------------------
Assignee: Marián Labuda
> No supported modifying environment variables cause error
> --------------------------------------------------------
>
> Key: JBIDE-15858
> URL: https://issues.jboss.org/browse/JBIDE-15858
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Priority: Critical
> Attachments: environment_variables.png
>
>
> If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..."
> Another one is show after attempt to add variable.
> Other "Processing environment variables..."
> Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion).
--
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, 5 months