[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance
by Jim Tyrrell (JIRA)
Console not showing up when staritng a EAP/SOA-P Instance
---------------------------------------------------------
Key: JBDS-983
URL: https://jira.jboss.org/jira/browse/JBDS-983
Project: JBoss Developer Studio
Issue Type: Feature Request
Affects Versions: 3.0.0.M4
Reporter: Jim Tyrrell
For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3 months, 1 week
[JBoss JIRA] (JBIDE-13888) openshift-java-client: make sure useragent is sent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13888?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-13888 at 3/31/13 4:28 PM:
-------------------------------------------------------------------
In the openshift-java-client it currently looks like as if the useragent is not sent:
{code:title=RestServiceProperties}
public String getUseragent(String id) {
String version = getVersion();
String useragentPattern = getUseragentPattern();
if (!StringUtils.isEmpty(id)
&& !StringUtils.isEmpty(version)
&& !StringUtils.isEmpty(useragentPattern)) {
String userAgent = MessageFormat.format(getUseragentPattern(), getVersion(), id);
}
return null;
}
{code}
this method always returns *null*, thus the useragent should always be null.
It turned out that bill decoste unfortunately introduced this issue here: https://github.com/adietish/openshift-java-client/commit/b64d63fc50fc3911...
The http client will obviously not send the user agent since it would not set it if it's null:
{code:title=UrlConnectionHttpClient}
private void setUserAgent(HttpURLConnection connection) {
String userAgent = this.userAgent;
if (!StringUtils.isEmpty(authKey)) {
userAgent = USERAGENT_FOR_KEYAUTH;
}
if (userAgent != null){
connection.setRequestProperty(PROPERTY_USER_AGENT, userAgent);
}
}
{code}
was (Author: adietish):
In the openshift-java-client it currently looks like as if the useragent is not sent:
{code:title=RestServiceProperties}
public String getUseragent(String id) {
String version = getVersion();
String useragentPattern = getUseragentPattern();
if (!StringUtils.isEmpty(id)
&& !StringUtils.isEmpty(version)
&& !StringUtils.isEmpty(useragentPattern)) {
String userAgent = MessageFormat.format(getUseragentPattern(), getVersion(), id);
}
return null;
}
{code}
this method always returns *null*, thus the useragent should always be null.
The http client will obviously not send the user agent since it would not set it if it's null:
{code:title=UrlConnectionHttpClient}
private void setUserAgent(HttpURLConnection connection) {
String userAgent = this.userAgent;
if (!StringUtils.isEmpty(authKey)) {
userAgent = USERAGENT_FOR_KEYAUTH;
}
if (userAgent != null){
connection.setRequestProperty(PROPERTY_USER_AGENT, userAgent);
}
}
{code}
> openshift-java-client: make sure useragent is sent
> --------------------------------------------------
>
> Key: JBIDE-13888
> URL: https://issues.jboss.org/browse/JBIDE-13888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
--
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
13 years
[JBoss JIRA] (JBIDE-13888) openshift-java-client: make sure useragent is sent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13888?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13888:
------------------------------------------
There is also very weird code in the UrlConnectionHttpClientBuilder which holds user-agent building logic. IMHO this logic should be in the rest service, not in the builder since the user-agent should get built correctly even if you create the client directly or use the builder:
{code:title=UrlConnectionHttpClientBuilder}
public IHttpClient client() {
if (authKey != null && authKey.trim().length() > 0) {
if (userAgent == null) {
userAgent = "OpenShift";
} else if (!userAgent.startsWith("OpenShift")) {
userAgent = "OpenShift-" + userAgent;
}
}
return new UrlConnectionHttpClient(username, password, userAgent,
sslChecks, requestMediaType, acceptedMediaType, version,
authKey, authIV);
}
{code}
> openshift-java-client: make sure useragent is sent
> --------------------------------------------------
>
> Key: JBIDE-13888
> URL: https://issues.jboss.org/browse/JBIDE-13888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
--
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
13 years
[JBoss JIRA] (JBIDE-13888) openshift-java-client: make sure useragent is sent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13888?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13888:
------------------------------------------
In the openshift-java-client it currently looks like as if the useragent is not sent:
{code:title=RestServiceProperties}
public String getUseragent(String id) {
String version = getVersion();
String useragentPattern = getUseragentPattern();
if (!StringUtils.isEmpty(id)
&& !StringUtils.isEmpty(version)
&& !StringUtils.isEmpty(useragentPattern)) {
String userAgent = MessageFormat.format(getUseragentPattern(), getVersion(), id);
}
return null;
}
{code}
this method always returns *null*, thus the useragent should always be null.
The http client will obviously not send the user agent since it would not set it if it's null:
{code:title=UrlConnectionHttpClient}
private void setUserAgent(HttpURLConnection connection) {
String userAgent = this.userAgent;
if (!StringUtils.isEmpty(authKey)) {
userAgent = USERAGENT_FOR_KEYAUTH;
}
if (userAgent != null){
connection.setRequestProperty(PROPERTY_USER_AGENT, userAgent);
}
}
{code}
> openshift-java-client: make sure useragent is sent
> --------------------------------------------------
>
> Key: JBIDE-13888
> URL: https://issues.jboss.org/browse/JBIDE-13888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
--
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
13 years