[JBoss JIRA] (JBIDE-11828) Unable to install BPEL Editor from the JBDS SOA Tooling 5.0.0.Beta1 updatesite
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-11828:
----------------------------------
Summary: Unable to install BPEL Editor from the JBDS SOA Tooling 5.0.0.Beta1 updatesite
Key: JBIDE-11828
URL: https://issues.jboss.org/browse/JBIDE-11828
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: updatesite
Affects Versions: 3.3.0.Beta1-SOA
Reporter: Pavol Srna
Assignee: Nick Boldt
Priority: Blocker
Fix For: 3.3.0.Beta1-SOA
Attachments: Screenshot.png
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: BPEL Editor (Certified) 1.1.0.v20120501-0347-H6-Beta1-SOA (com.jboss.jbds.bpel.feature.feature.group 1.1.0.v20120501-0347-H6-Beta1-SOA)
Missing requirement: BPEL Editor (Incubation) 0.8.0.v20120209-1201-H138-CI (org.eclipse.bpel.ui 0.8.0.v20120209-1201-H138-CI) requires 'bundle org.eclipse.bpel.common.wsdl 0.0.0' but it could not be found
Cannot satisfy dependency:
From: BPEL Editor (Certified) 1.1.0.v20120501-0347-H6-Beta1-SOA (com.jboss.jbds.bpel.feature.feature.group 1.1.0.v20120501-0347-H6-Beta1-SOA)
To: org.eclipse.bpel.apache.ode.runtime.feature.feature.group [0.8.0.v20120209-1201-H138-CI]
Cannot satisfy dependency:
From: Runtime Adapter for Apache ODE 1.3 0.8.0.v20120209-1201-H138-CI (org.eclipse.bpel.apache.ode.runtime.feature.feature.group 0.8.0.v20120209-1201-H138-CI)
To: org.eclipse.bpel.ui 0.8.0
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBIDE-11267) Remote Configuration, Runtime Server config missing field "Remote Configuration"
by Leo Breuss (JIRA)
Leo Breuss created JBIDE-11267:
----------------------------------
Summary: Remote Configuration, Runtime Server config missing field "Remote Configuration"
Key: JBIDE-11267
URL: https://issues.jboss.org/browse/JBIDE-11267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, JBossAS/Servers
Affects Versions: 3.3.0.Beta2
Reporter: Leo Breuss
Assignee: Snjezana Peco
In the JBoss Runtime Server configuration, I am no longer able to specify the Remote Configuration (e.g. standalong-full.xml). It seems like this field has been dropped between 20111208 and today's 3.3.0b2.
In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the problems disucussed in the Forum Reference.
1. The path on the server to look for the existence of the configuration was the concatenation of <Remote Server Home> + "/server/" + <Remote Server Configuration>. But JBoss 7 has a different layout structure. No /server/ directory. Interestingly enough, the field Remote Server Home can be set by browsing the remote file system.
2. In the field "Remote Configuration" you should be able to select the appropriate configuration file from the remote server file system. Instead, one could browse for a local configuration, but had to manually strip the absolute path. Only the filename may remain, because of the concatenation. And the local JBoss installation has to reflect the remote JBoss regarding the configuration file names. The default value "default" did not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months