[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26694:
-------------------------------------
Description:
For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
Steps:
# EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
# ASSERT: *websocket-chat* application is imported into your workspace
# ASSERT: server adapter *jboss-webserver31-tomcat* is created
# ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
# EXEC: start the server adapter
# ASSERT: RSync is executed and the output is visible in the "Console"
Result:
If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
!console-output-1.png!
Expected result:
I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
Currently, to achieve this I have to do the following:
# EXEC: create the following xml snippet (notice the *outputName* property for the module)
and make sure it reads as follows:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<deployment>
<local>
<module id="org.eclipse.jst.jee.server:websocket-chat">
<property key="tempLocation" value="" />
<property key="location" value="" />
<property key="outputName" value="ROOT" />
</module>
</local>
</deployment>
{code}
# EXEC: html-encode, join it into a single line and copy it (into the clipboard)
# EXEC: open the properties for the server adapter and hit "Switch Location"
!switch-location.png!
# ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
!server-adapter-configuration.png!
# EXEC: open the file with the *XML Editor*
# EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
<list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
</server>
{code}
# EXEC: Save the editor and restart the server
Result:
Syncing now happens into a folder *ROOT*
!console-output-2.png!
was:
For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
Steps:
# EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
# ASSERT: *websocket-chat* application is imported into your workspace
# ASSERT: server adapter *jboss-webserver31-tomcat* is created
# ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
# EXEC: start the server adapter
# ASSERT: RSync is executed and the output is visible in the "Console"
Result:
If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
!console-output-1.png!
Expected result:
I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
Currently, to achieve this I have to do the following:
# EXEC: open the properties for the server adapter and hit "Switch Location"
!switch-location.png!
# ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
!server-adapter-configuration.png!
# EXEC: open the file with the *XML Editor*
# EXEC: create the following xml snippet (notice the *outputName* property for the module)
and make sure it reads as follows:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<deployment>
<local>
<module id="org.eclipse.jst.jee.server:websocket-chat">
<property key="tempLocation" value="" />
<property key="location" value="" />
<property key="outputName" value="ROOT" />
</module>
</local>
</deployment>
{code}
# EXEC: html-encode and join it into a single line
# EXEC: in your *XML* editor for the server adapter: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
<list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
</server>
{code}
# EXEC: Save the editor and restart the server
Result:
Syncing now happens into a folder *ROOT*
!console-output-2.png!
> Server adapter: should be able to freely set a war name
> -------------------------------------------------------
>
> Key: JBIDE-26694
> URL: https://issues.jboss.org/browse/JBIDE-26694
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.12.x
>
> Attachments: console-output-1.png, console-output-2.png, server-adapter-configuration.png, switch-location.png
>
>
> For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
> Steps:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # ASSERT: RSync is executed and the output is visible in the "Console"
> Result:
> If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
> !console-output-1.png!
> Expected result:
> I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
> Currently, to achieve this I have to do the following:
> # EXEC: create the following xml snippet (notice the *outputName* property for the module)
> and make sure it reads as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment>
> <local>
> <module id="org.eclipse.jst.jee.server:websocket-chat">
> <property key="tempLocation" value="" />
> <property key="location" value="" />
> <property key="outputName" value="ROOT" />
> </module>
> </local>
> </deployment>
> {code}
> # EXEC: html-encode, join it into a single line and copy it (into the clipboard)
> # EXEC: open the properties for the server adapter and hit "Switch Location"
> !switch-location.png!
> # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
> !server-adapter-configuration.png!
> # EXEC: open the file with the *XML Editor*
> # EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
> </server>
> {code}
> # EXEC: Save the editor and restart the server
> Result:
> Syncing now happens into a folder *ROOT*
> !console-output-2.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26694:
-------------------------------------
Description:
For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
Steps:
# EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
# ASSERT: *websocket-chat* application is imported into your workspace
# ASSERT: server adapter *jboss-webserver31-tomcat* is created
# ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
# EXEC: start the server adapter
# ASSERT: RSync is executed and the output is visible in the "Console"
Result:
If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
!console-output-1.png!
Expected result:
I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
Currently, to achieve this I have to do the following:
# EXEC: open the properties for the server adapter and hit "Switch Location"
!switch-location.png!
# ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
!server-adapter-configuration.png!
# EXEC: open the file with the *XML Editor*
# EXEC: create the following xml snippet (notice the *outputName* property for the module)
and make sure it reads as follows:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<deployment>
<local>
<module id="org.eclipse.jst.jee.server:websocket-chat">
<property key="tempLocation" value="" />
<property key="location" value="" />
<property key="outputName" value="ROOT" />
</module>
</local>
</deployment>
{code}
# EXEC: html-encode and join it into a single line
# EXEC: in your *XML* editor for the server adapter: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
<list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
</server>
{code}
# EXEC: Save the editor and restart the server
Result:
Syncing now happens into a folder *ROOT*
!console-output-2.png!
was:
For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
Steps:
# EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
# ASSERT: *websocket-chat* application is imported into your workspace
# ASSERT: server adapter *jboss-webserver31-tomcat* is created
# ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
# EXEC: start the server adapter
# ASSERT: RSync is executed and the output is visible in the "Console"
Result:
If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
!console-output-1.png!
Expected result:
I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
Currently, to achieve this I have to do the following:
# EXEC: open the properties for the server adapter and hit "Switch Location"
!switch-location.png!
# ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
!server-adapter-configuration.png!
# EXEC: open the file with the *XML Editor* and make sure it reads as follows:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<deployment>
<local>
<module id="org.eclipse.jst.jee.server:websocket-chat">
<property key="tempLocation" value="" />
<property key="location" value="" />
<property key="outputName" value="ROOT" />
</module>
</local>
</deployment>
{code}
# EXEC: html-encode and join it into a single line:
# EXEC: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
<list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
</server>
{code}
# EXEC: Save the editor and restart the server
Result:
Syncing now happens into a folder *ROOT*
!console-output-2.png!
> Server adapter: should be able to freely set a war name
> -------------------------------------------------------
>
> Key: JBIDE-26694
> URL: https://issues.jboss.org/browse/JBIDE-26694
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.12.x
>
> Attachments: console-output-1.png, console-output-2.png, server-adapter-configuration.png, switch-location.png
>
>
> For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
> Steps:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # ASSERT: RSync is executed and the output is visible in the "Console"
> Result:
> If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
> !console-output-1.png!
> Expected result:
> I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
> Currently, to achieve this I have to do the following:
> # EXEC: open the properties for the server adapter and hit "Switch Location"
> !switch-location.png!
> # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
> !server-adapter-configuration.png!
> # EXEC: open the file with the *XML Editor*
> # EXEC: create the following xml snippet (notice the *outputName* property for the module)
> and make sure it reads as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment>
> <local>
> <module id="org.eclipse.jst.jee.server:websocket-chat">
> <property key="tempLocation" value="" />
> <property key="location" value="" />
> <property key="outputName" value="ROOT" />
> </module>
> </local>
> </deployment>
> {code}
> # EXEC: html-encode and join it into a single line
> # EXEC: in your *XML* editor for the server adapter: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
> </server>
> {code}
> # EXEC: Save the editor and restart the server
> Result:
> Syncing now happens into a folder *ROOT*
> !console-output-2.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26694:
-------------------------------------
Description:
For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
Steps:
# EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
# ASSERT: *websocket-chat* application is imported into your workspace
# ASSERT: server adapter *jboss-webserver31-tomcat* is created
# ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
# EXEC: start the server adapter
# ASSERT: RSync is executed and the output is visible in the "Console"
Result:
If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
!console-output-1.png!
Expected result:
I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
Currently, to achieve this I have to do the following:
# EXEC: open the properties for the server adapter and hit "Switch Location"
!switch-location.png!
# ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
!server-adapter-configuration.png!
# EXEC: open the file with the *XML Editor* and make sure it reads as follows:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<deployment>
<local>
<module id="org.eclipse.jst.jee.server:websocket-chat">
<property key="tempLocation" value="" />
<property key="location" value="" />
<property key="outputName" value="ROOT" />
</module>
</local>
</deployment>
{code}
# EXEC: html-encode and join it into a single line:
# EXEC: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
<list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
</server>
{code}
# EXEC: Save the editor and restart the server
Result:
Syncing now happens into a folder *ROOT*
!console-output-2.png!
was:
For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
Steps:
# EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
# ASSERT: *websocket-chat* application is imported into your workspace
# ASSERT: server adapter *jboss-webserver31-tomcat* is created
# ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
# EXEC: start the server adapter
# ASSERT: RSync is executed and the output is visible in the "Console"
Result:
If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
!console-output-1.png!
Expected result:
I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
Currently, to achieve this I have to do the following:
# EXEC: open the properties for the server adapter and hit "Switch Location"
!switch-location.png!
# ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
!server-adapter-configuration.png!
# EXEC: open the file with the *XML Editor*
# EXEC: html-encode and join the following xml into a single line:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<deployment>
<local>
<module id="org.eclipse.jst.jee.server:websocket-chat">
<property key="tempLocation" value="" />
<property key="location" value="" />
<property key="outputName" value="ROOT" />
</module>
</local>
</deployment>
{code}
# EXEC: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
<list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
</server>
{code}
# EXEC: Save the editor and restart the server
Result:
Syncing now happens into a folder *ROOT*
!console-output-2.png!
> Server adapter: should be able to freely set a war name
> -------------------------------------------------------
>
> Key: JBIDE-26694
> URL: https://issues.jboss.org/browse/JBIDE-26694
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.12.x
>
> Attachments: console-output-1.png, console-output-2.png, server-adapter-configuration.png, switch-location.png
>
>
> For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
> Steps:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # ASSERT: RSync is executed and the output is visible in the "Console"
> Result:
> If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
> !console-output-1.png!
> Expected result:
> I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
> Currently, to achieve this I have to do the following:
> # EXEC: open the properties for the server adapter and hit "Switch Location"
> !switch-location.png!
> # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
> !server-adapter-configuration.png!
> # EXEC: open the file with the *XML Editor* and make sure it reads as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment>
> <local>
> <module id="org.eclipse.jst.jee.server:websocket-chat">
> <property key="tempLocation" value="" />
> <property key="location" value="" />
> <property key="outputName" value="ROOT" />
> </module>
> </local>
> </deployment>
> {code}
> # EXEC: html-encode and join it into a single line:
> # EXEC: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
> </server>
> {code}
> # EXEC: Save the editor and restart the server
> Result:
> Syncing now happens into a folder *ROOT*
> !console-output-2.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (JBIDE-26701) Installation of JBT 4.12.0.AM1 introduces OS package requirement installation
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-26701:
-------------------------------------
Summary: Installation of JBT 4.12.0.AM1 introduces OS package requirement installation
Key: JBIDE-26701
URL: https://issues.jboss.org/browse/JBIDE-26701
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: updatesite
Affects Versions: 4.12.0.AM1
Reporter: Ondrej Dockal
Attachments: Screenshot_20190628_100314.png
After installation of JBT via composite update site [1] into eclipse 2019-06, new "Install native software packages" dialog appeared.
[1]: Right now I am not sure where to find 4.12.0.Am1 update site as we are staging.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (JBIDE-26569) Cannot create hibernate config file for hibernate 5.3 and 5.4
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26569?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26569:
------------------------------------------
[~koen.aers] The root cause is in
{code:title=org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl}
public Dialect buildDialect(Map configValues, DialectResolutionInfoSource resolutionInfoSource) throws HibernateException {
final Object dialectReference = configValues.get( AvailableSettings.DIALECT );
if ( !isEmpty( dialectReference ) ) {
return constructDialect( dialectReference );
}
else {
return determineDialect( resolutionInfoSource );
}
}
{code}
The *configValues* dont contain *hibernate.dialect* and thus DialectResolutionInfoSource is tried and fails, too. I can make it succeed by forcing the missing key in:
{code:title=org.jboss.tools.hibernate.runtime.v_5_4.internal.ConfigurationFacadeImpl}
public Metadata getMetadata() {
if (metadata == null) {
Object target = getTarget();
if (target instanceof Configuration) {
+ Configuration configuration = (Configuration) target;
+ configuration.getProperties().put("hibernate.dialect", "H2");
metadata = MetadataHelper.getMetadata((Configuration)target);
} else if (target instanceof JdbcMetadataConfiguration) {
metadata = ((JdbcMetadataConfiguration)target).getMetadata();
}
}
return metadata;
}
{code}
The *configValues* only contain the parameters that the jvm was launched with.
My question thus is, why is the entry missing?
> Cannot create hibernate config file for hibernate 5.3 and 5.4
> -------------------------------------------------------------
>
> Key: JBIDE-26569
> URL: https://issues.jboss.org/browse/JBIDE-26569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.11.0.Final
> Reporter: Josef Kopriva
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.12.0.Final
>
> Attachments: JBIDE-26569-console.mov, JBIDE-26569-copy-1.mov, JBIDE-26569-copy-2.mov, JBIDE-26569-import.mov, Screenshot 2019-04-11 15.26.00.png, image-2019-03-08-10-38-30-318.png
>
>
> This workflow works for Hibernate 5.2
> Error from error log:
> {code:java}
> eclipse.buildId=12.11.0.AM1-v20190221-1020-B4114
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.ui
> Error
> Fri Mar 08 10:30:50 CET 2019
> Unhandled event loop exception
> org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
> at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
> at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.build(MetadataBuildingProcess.java:84)
> at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:474)
> at org.hibernate.boot.internal.MetadataBuilderImpl.build(MetadataBuilderImpl.java:85)
> at org.hibernate.boot.MetadataSources.buildMetadata(MetadataSources.java:184)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.MetadataHelper.buildFromMetadataSources(MetadataHelper.java:49)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.MetadataHelper.getMetadata(MetadataHelper.java:21)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:174)
> at org.jboss.tools.hibernate.runtime.v_5_3.internal.util.ConfigurationMetadataDescriptor.createMetadata(ConfigurationMetadataDescriptor.java:20)
> at org.hibernate.tool.hbm2x.AbstractExporter.buildMetadata(AbstractExporter.java:207)
> at org.hibernate.tool.hbm2x.AbstractExporter.getMetadata(AbstractExporter.java:57)
> at org.hibernate.tool.hbm2x.AbstractExporter.setupContext(AbstractExporter.java:178)
> at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:105)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:43)
> at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.start(AbstractExporterFacade.java:72)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:301)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$2(NewConfigurationWizard.java:295)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$1.getInitialContents(NewConfigurationWizard.java:163)
> at org.eclipse.ui.dialogs.WizardNewFileCreationPage.createNewFile(WizardNewFileCreationPage.java:383)
> at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.performFinish(NewConfigurationWizard.java:198)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:775)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:414)
> at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:622)
> at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:84)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:822)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:272)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:293)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:96)
> at jdk.internal.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:320)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:254)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:164)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:497)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:490)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:403)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:154)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:568)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:400)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1474)
> Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set
> at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
> at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
> at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
> at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
> ... 89 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (JBIDE-26698) Hibernate 3.5 - Can’t open connection
by Juan Marchionatto (Jira)
[ https://issues.jboss.org/browse/JBIDE-26698?page=com.atlassian.jira.plugi... ]
Juan Marchionatto commented on JBIDE-26698:
-------------------------------------------
To avoid misleading the developers, the second comment is not true. It was just caused by multiple installation/removal of the plugin and trying older versions.
On a clean environment with current plugin version installed, the SessionFactoryImpl involved is of the selected hibernate version. Still, the first part applies. Just changing the version to 5.0 or over works fine, selecting any version lower than 5.0, fails with the reported exception.
Regards
> Hibernate 3.5 - Can’t open connection
> -------------------------------------
>
> Key: JBIDE-26698
> URL: https://issues.jboss.org/browse/JBIDE-26698
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.12.0.Final
> Reporter: Josef Kopriva
> Assignee: Koen Aers
> Priority: Major
>
> From https://developer.jboss.org/people/jrmarchio from thread https://developer.jboss.org/message/989820?et=watches.email.thread#989820
> {code:java}
> Hi, I have a problem with Hibernate Tools 5.4.4.v20190328-1505
>
> I am trying to make Hibernate Console work on my new eclipse installation (Version: 2019-03 (4.11.0)).
>
> Exception is: org.hibernate.exception.JDBCConnectionException: Cannot open connection
> …
> Caused by: java.sql.SQLException: No suitable driver found for jdbc:jtds:sqlserver://hidden-hostname:1433/hidden-db-name
>
>
> Now, the driver is in the connection classpath, and I know it is OK, because if I only change the hibernate version to 4.3 or later, it works. With 4.0 or less, same exception.
>
> I can’t just use it with version 4.3, because in my real configuration (many more mappings) I have all mapping files with 3.5 DTD and other characteristics not supported after 3.5 (LONG definitions, etc).
>
> I have used hibernate console since long ago. I have had little struggle to make configuration work on other plugin installations, but this time I am getting out of ideas..
>
> Previous working combination was not much older: eclipse Mars. 2 Release (4.5.2), same hibernate (3.5) Hibernate tools 5.0.1.Final-v20160331-1852-B88
>
> Can anybody help me to find out what could be generating the problem?
>
> Any information about some important changes between 5.0.1 and 5.0.4?
>
> Thank you in advance
> ---
> Juan
> {code}
> {code:java}
> Trying to debug the code, I found that no matter which hibernate target version is selected, code always calls a SessionFactoryImpl from hibernate 4.0-Final, which could be the reason why queries start working selecting hibernate version 4.3 or higher (4.3 is the lowest selectable version higher than 4.0).
>
> Could anybody who knows this project check this?
>
> Thank you
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months