November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15846) Error in Error Log while creating Dynamic Web Project with Seam facet

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-15846: --------------------------------------- Summary: Error in Error Log while creating Dynamic Web Project with Seam facet Key: JBIDE-15846 URL: https://issues.jboss.org/browse/JBIDE-15846 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Affects Versions: 4.1.1.Beta1 Reporter: Radoslav Rábara Fix For: 4.1.1.CR1 Error shows in Error Log when creating Dynamic Web Project that uses Seam: Can't get project name to initialize SeamInstallWizardPage for ModifyFacetedProjectWizard (An exception stack trace is not available.) -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15397) Ignore 3rd party jar files in wildfly8 management plugin downloaded by maven-dependency-plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15397?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15397: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 > Ignore 3rd party jar files in wildfly8 management plugin downloaded by maven-dependency-plugin > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-15397 > URL: https://issues.jboss.org/browse/JBIDE-15397 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.1.Alpha1, 4.2.0.Alpha1 > Reporter: Denis Golovin > Fix For: 4.1.1.Alpha1 > > > After local maven build files from as.management.wildfly8/lib folder are shown as new in git status where as they should be ignored by git. > .gitignore file should be added. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13398: --------------------------------------------- We should find a place on jboss tools wiki or github.com/jbosstools/jbosstools-devdoc to put this info so it is not just hidden inside jira anymore. > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.1.1.Final > > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, launch a server.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15185: --------------------------------------------- [~ghjboss] I'm finding it really hard to see how it brings a lot of flexibility. The only flexibility I can see is that the user can go and add in jbds.ini/eclipse.ini -Dmyjboss.home=<serverlocation> and then have the server in the workspace use that location instead. That means the user now can define a server adapter in his workspace with ${system_property:jboss.home} as the path and he can now change it in jbds.ini/eclipse.ini instead of editing the runtime/server adapter. He can't share it with anyone. He has to set this up in each workspace he uses. Is that the "lot of flexibility" you mean ? > add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15185 > URL: https://issues.jboss.org/browse/JBIDE-15185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > > The current jbds version only allow users to specify an absolute path for "Home Directory" when creating JBoss Runtime Server. Is it possible to use a user defined variable here? -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15185: ---------------------------------------- Fix Version/s: 4.2.x > add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15185 > URL: https://issues.jboss.org/browse/JBIDE-15185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Fix For: 4.2.x > > > The current jbds version only allow users to specify an absolute path for "Home Directory" when creating JBoss Runtime Server. Is it possible to use a user defined variable here? -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13398: ---------------------------------------- Fix Version/s: 4.1.1.Final > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.1.1.Final > > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, launch a server.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15399) openshift-java-client: dont fail on unknown link-type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15399?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-15399. ------------------------------------ > openshift-java-client: dont fail on unknown link-type > ----------------------------------------------------- > > Key: JBIDE-15399 > URL: https://issues.jboss.org/browse/JBIDE-15399 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > When unmarshalling responses from the server there are among other objects links that shall get created. Links look like the following: > {code} > "links":{ > "UPDATE":{ > "href":"/domains/foobar", > "optional_params":[ > > ], > "required_params":[ > { > "name":"id", > "valid_options":[ > > ], > "description":"Name of the domain", > "type":"string" > } > ], > "method":"PUT", > "rel":"Update domain" > ... > {code} > The unmarshalling code currently turns the "type" property into an enum. If the type that's provided is not known, then an exception is thrown: > {code} > public enum LinkParameterType { > STRING, BOOLEAN, INTEGER, ARRAY; > > public static LinkParameterType valueOfIgnoreCase(String name) throws OpenShiftRequestException { > if (name == null) { > // no type provided (this is valid, not an error) > return null; > } > try { > return valueOf(name.toUpperCase()); > } catch(IllegalArgumentException e) { > throw new OpenShiftRequestException("Unknow request parameter type {0}", name); > } > } > {code} > This is not a good approach. The client library should be tolerant, it should ignore things it doesn't know to ensure it works with future responses. This is even more true as responses evolve over time even in the same protocol version: OpenShift is backporting new features (additions only) to old protocols! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15399) openshift-java-client: dont fail on unknown link-type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15399?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15399: ------------------------------------- Fix Version/s: 4.1.1.Beta1 4.2.0.Alpha1 > openshift-java-client: dont fail on unknown link-type > ----------------------------------------------------- > > Key: JBIDE-15399 > URL: https://issues.jboss.org/browse/JBIDE-15399 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > When unmarshalling responses from the server there are among other objects links that shall get created. Links look like the following: > {code} > "links":{ > "UPDATE":{ > "href":"/domains/foobar", > "optional_params":[ > > ], > "required_params":[ > { > "name":"id", > "valid_options":[ > > ], > "description":"Name of the domain", > "type":"string" > } > ], > "method":"PUT", > "rel":"Update domain" > ... > {code} > The unmarshalling code currently turns the "type" property into an enum. If the type that's provided is not known, then an exception is thrown: > {code} > public enum LinkParameterType { > STRING, BOOLEAN, INTEGER, ARRAY; > > public static LinkParameterType valueOfIgnoreCase(String name) throws OpenShiftRequestException { > if (name == null) { > // no type provided (this is valid, not an error) > return null; > } > try { > return valueOf(name.toUpperCase()); > } catch(IllegalArgumentException e) { > throw new OpenShiftRequestException("Unknow request parameter type {0}", name); > } > } > {code} > This is not a good approach. The client library should be tolerant, it should ignore things it doesn't know to ensure it works with future responses. This is even more true as responses evolve over time even in the same protocol version: OpenShift is backporting new features (additions only) to old protocols! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15399) openshift-java-client: dont fail on unknown link-type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15399?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-15399. -------------------------------------- Resolution: Done > openshift-java-client: dont fail on unknown link-type > ----------------------------------------------------- > > Key: JBIDE-15399 > URL: https://issues.jboss.org/browse/JBIDE-15399 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > When unmarshalling responses from the server there are among other objects links that shall get created. Links look like the following: > {code} > "links":{ > "UPDATE":{ > "href":"/domains/foobar", > "optional_params":[ > > ], > "required_params":[ > { > "name":"id", > "valid_options":[ > > ], > "description":"Name of the domain", > "type":"string" > } > ], > "method":"PUT", > "rel":"Update domain" > ... > {code} > The unmarshalling code currently turns the "type" property into an enum. If the type that's provided is not known, then an exception is thrown: > {code} > public enum LinkParameterType { > STRING, BOOLEAN, INTEGER, ARRAY; > > public static LinkParameterType valueOfIgnoreCase(String name) throws OpenShiftRequestException { > if (name == null) { > // no type provided (this is valid, not an error) > return null; > } > try { > return valueOf(name.toUpperCase()); > } catch(IllegalArgumentException e) { > throw new OpenShiftRequestException("Unknow request parameter type {0}", name); > } > } > {code} > This is not a good approach. The client library should be tolerant, it should ignore things it doesn't know to ensure it works with future responses. This is even more true as responses evolve over time even in the same protocol version: OpenShift is backporting new features (additions only) to old protocols! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15834) Server error while deleting application on Openshift Enterprise

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15834?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-15834. ----------------------------------------- Resolution: Rejected Rejected since no info indicate it is a client side issue. Please report against openshift enterprise and if it is shown it has details showing the client is doing something wrong reopen or link to this issue in a new jira. Thanks. > Server error while deleting application on Openshift Enterprise > --------------------------------------------------------------- > > Key: JBIDE-15834 > URL: https://issues.jboss.org/browse/JBIDE-15834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > > Sometimes attempt to delete application in Openshift Enterprise (in Openshift Online I didn't notice such bug) cause internal server error - HTTP error 500. > Application (after showed dialog) is not deleted in Openshift Enterprise. Second attempt delete application succesfully. > Unfortunately, I have no idea how to reproduce it (many various attempts done). It occurs sometimes. > Eclipse log: > {code} > com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>500 Internal Server Error</title> > </head><body> > <h1>Internal Server Error</h1> > <p>The server encountered an internal error or > misconfiguration and was unable to complete > your request.</p> > <p>Please contact the server administrator, > root@localhost and inform them of the time the error occurred, > and anything you might have done that may have > caused the error.</p> > <p>More information about this error may be available > in the server error log.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address> > </body></html> > at com.openshift.internal.client.RestService.request(RestService.java:136) > at com.openshift.internal.client.RestService.request(RestService.java:109) > at com.openshift.internal.client.RestService.request(RestService.java:92) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142) > at com.openshift.internal.client.ApplicationResource.destroy(ApplicationResource.java:256) > at org.jboss.tools.openshift.express.internal.ui.job.DeleteApplicationsJob.doRun(DeleteApplicationsJob.java:47) > at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: com.openshift.internal.client.httpclient.InternalServerErrorException: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>500 Internal Server Error</title> > </head><body> > <h1>Internal Server Error</h1> > <p>The server encountered an internal error or > misconfiguration and was unable to complete > your request.</p> > <p>Please contact the server administrator, > root@localhost and inform them of the time the error occurred, > and anything you might have done that may have > caused the error.</p> > <p>More information about this error may be available > in the server error log.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address> > </body></html> > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:169) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.delete(UrlConnectionHttpClient.java:113) > at com.openshift.internal.client.RestService.request(RestService.java:183) > at com.openshift.internal.client.RestService.request(RestService.java:123) > ... 7 more > Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati... > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146) > ... 11 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

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 November 2013