[JBoss JIRA] (JBDS-2868) Support multiple protocols when talking to OpenShift servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2868?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim closed JBDS-2868.
----------------------------------
Fix Version/s: 8.0.0.GA
(was: LATER)
Resolution: Out of Date
all new development will be made in the upcoming v3 OpenShift, backend- and tooling-wise. There is no immediate necessity nor resources to do this, I therefore close this issue as outdated.
> Support multiple protocols when talking to OpenShift servers
> ------------------------------------------------------------
>
> Key: JBDS-2868
> URL: https://issues.jboss.org/browse/JBDS-2868
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Andre Dietisheim
> Fix For: 8.0.0.GA
>
>
> The OpenShift backend offers different protocol version. Even though the OpenShift team is backporting new features to the current protocol 1.2 we're currently talking, we'll have to ramp up in protocol version at some point. Since we cannot loose the ability to talk to old servers (especially since OpenShift Enterprise is available), we have to be able to talk in different protocol versions.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-2868) Support multiple protocols when talking to OpenShift servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2868?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-2868:
-----------------------------------
Fix Version/s: LATER
(was: 8.0.x)
> Support multiple protocols when talking to OpenShift servers
> ------------------------------------------------------------
>
> Key: JBDS-2868
> URL: https://issues.jboss.org/browse/JBDS-2868
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Andre Dietisheim
> Fix For: LATER
>
>
> The OpenShift backend offers different protocol version. Even though the OpenShift team is backporting new features to the current protocol 1.2 we're currently talking, we'll have to ramp up in protocol version at some point. Since we cannot loose the ability to talk to old servers (especially since OpenShift Enterprise is available), we have to be able to talk in different protocol versions.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3000) Mylyn Atlassian (JIRA) connector - exceptions logged at JBDS startup - and when queries are performed
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3000?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3000:
--------------------------------------
3.2.3 repository is available at http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.7 and release notes are at https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> Mylyn Atlassian (JIRA) connector - exceptions logged at JBDS startup - and when queries are performed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-3000
> URL: https://issues.jboss.org/browse/JBDS-3000
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-certification, upstream
> Affects Versions: 8.0.0.Beta1
> Environment: JBDS 8.0.beta1.respin-a
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Fix For: 8.0.x
>
> Attachments: log.txt
>
>
> There doesn't seem to be any functional impact, but these exceptions are logged at JBDS startup - and when a query is run:
> !ENTRY com.atlassian.connector.eclipse.monitor.core 4 0 2014-04-04 11:55:23.502
> !MESSAGE Monitor failed to start
> !STACK 0
> java.lang.NoClassDefFoundError: org/jdom/JDOMException
> at com.atlassian.connector.eclipse.monitor.core.InteractionEventLogger.<init>(InteractionEventLogger.java:48)
> at com.atlassian.connector.eclipse.monitor.core.MonitorCorePlugin.getInteractionLogger(MonitorCorePlugin.java:184)
> at com.atlassian.connector.eclipse.core.monitoring.Monitoring.logJob(Monitoring.java:54)
> at com.atlassian.connector.eclipse.internal.jira.core.service.JiraClient.getAvailableActions(JiraClient.java:422)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.addOperations(JiraTaskDataHandler.java:1085)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.createTaskData(JiraTaskDataHandler.java:204)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.createTaskData(JiraTaskDataHandler.java:195)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.getTaskData(JiraTaskDataHandler.java:162)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraRepositoryConnector.getTaskData(JiraRepositoryConnector.java:504)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.synchronizeTask(SynchronizeTasksJob.java:260)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.synchronizedTaskRelations(SynchronizeTasksJob.java:170)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.run(SynchronizeTasksJob.java:154)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.run(SynchronizeTasksJob.java:135)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.run(SynchronizeQueriesJob.java:225)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.jdom.JDOMException cannot be found by osgi.identity; osgi.identity="com.thoughtworks.xs
> tream"; type="osgi.bundle"; version:Version="1.3.0.v20100826-1640"
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:416)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:336)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:328)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3000) Mylyn Atlassian (JIRA) connector - exceptions logged at JBDS startup - and when queries are performed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3000?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3000:
-------------------------------------------
Mickael - got a link for that 3.2.3 and release notes ?
> Mylyn Atlassian (JIRA) connector - exceptions logged at JBDS startup - and when queries are performed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-3000
> URL: https://issues.jboss.org/browse/JBDS-3000
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-certification, upstream
> Affects Versions: 8.0.0.Beta1
> Environment: JBDS 8.0.beta1.respin-a
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Fix For: 8.0.x
>
> Attachments: log.txt
>
>
> There doesn't seem to be any functional impact, but these exceptions are logged at JBDS startup - and when a query is run:
> !ENTRY com.atlassian.connector.eclipse.monitor.core 4 0 2014-04-04 11:55:23.502
> !MESSAGE Monitor failed to start
> !STACK 0
> java.lang.NoClassDefFoundError: org/jdom/JDOMException
> at com.atlassian.connector.eclipse.monitor.core.InteractionEventLogger.<init>(InteractionEventLogger.java:48)
> at com.atlassian.connector.eclipse.monitor.core.MonitorCorePlugin.getInteractionLogger(MonitorCorePlugin.java:184)
> at com.atlassian.connector.eclipse.core.monitoring.Monitoring.logJob(Monitoring.java:54)
> at com.atlassian.connector.eclipse.internal.jira.core.service.JiraClient.getAvailableActions(JiraClient.java:422)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.addOperations(JiraTaskDataHandler.java:1085)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.createTaskData(JiraTaskDataHandler.java:204)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.createTaskData(JiraTaskDataHandler.java:195)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.getTaskData(JiraTaskDataHandler.java:162)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraRepositoryConnector.getTaskData(JiraRepositoryConnector.java:504)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.synchronizeTask(SynchronizeTasksJob.java:260)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.synchronizedTaskRelations(SynchronizeTasksJob.java:170)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.run(SynchronizeTasksJob.java:154)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.run(SynchronizeTasksJob.java:135)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.run(SynchronizeQueriesJob.java:225)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.jdom.JDOMException cannot be found by osgi.identity; osgi.identity="com.thoughtworks.xs
> tream"; type="osgi.bundle"; version:Version="1.3.0.v20100826-1640"
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:416)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:336)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:328)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ]
Jeff Cantrill commented on JBDS-3298:
-------------------------------------
[~maxandersen] I will either find one or create one that includes an app server and database. I was working on the javaparks app that utilizes Mongo but never completely followed through to confirm that everything was wired and working.
> Push changes to Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3298
> URL: https://issues.jboss.org/browse/JBDS-3298
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Use Case #2 Push changes to Existing OpenShift Project
> a) assumes the steps in Use Case #1 JBDS-3297
> b) assumes the end-user has uploaded his SSH keys (to allow for git push)
> c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
> d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
> e) Eclipse user will test (JUnit, Arquillian)
> f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
> g) Eclipse user will git add and git commit as appropriate
> h) Eclipse user will git push to the original URL provided in Use Case #1
> i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
> j) Eclipse user will then be provided a URL and the browser can be opened automatically
> Note:
> i) auto-build=true, auto-deploy=true
> assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.
> A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear.
> If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Jiri Pallich (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Jiri Pallich updated JBDS-3249:
-------------------------------
Target Release: 8.1.0.GA (was: 9.0.0.GA)
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, updatesite
> Reporter: Max Rydahl Andersen
> Fix For: 8.1.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3000) Mylyn Atlassian (JIRA) connector - exceptions logged at JBDS startup - and when queries are performed
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3000?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3000:
--------------------------------------
Atlassian has released a 3.2.3 version of its connectors, where they apparently improved some dependency management. We can hope this newer Atlassian would fix this issue.
[~ldimaggio] Would it be possible for you to check whether this issue is still in last JBDS release, whether using Atlassian 3.2.3 fixes it, and whether we can Atlassian 3.2.3 as a substitute for next release? (Do you need a jira for that or is it ok to track it in this bug?)
> Mylyn Atlassian (JIRA) connector - exceptions logged at JBDS startup - and when queries are performed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-3000
> URL: https://issues.jboss.org/browse/JBDS-3000
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-certification, upstream
> Affects Versions: 8.0.0.Beta1
> Environment: JBDS 8.0.beta1.respin-a
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Fix For: 8.0.x
>
> Attachments: log.txt
>
>
> There doesn't seem to be any functional impact, but these exceptions are logged at JBDS startup - and when a query is run:
> !ENTRY com.atlassian.connector.eclipse.monitor.core 4 0 2014-04-04 11:55:23.502
> !MESSAGE Monitor failed to start
> !STACK 0
> java.lang.NoClassDefFoundError: org/jdom/JDOMException
> at com.atlassian.connector.eclipse.monitor.core.InteractionEventLogger.<init>(InteractionEventLogger.java:48)
> at com.atlassian.connector.eclipse.monitor.core.MonitorCorePlugin.getInteractionLogger(MonitorCorePlugin.java:184)
> at com.atlassian.connector.eclipse.core.monitoring.Monitoring.logJob(Monitoring.java:54)
> at com.atlassian.connector.eclipse.internal.jira.core.service.JiraClient.getAvailableActions(JiraClient.java:422)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.addOperations(JiraTaskDataHandler.java:1085)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.createTaskData(JiraTaskDataHandler.java:204)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.createTaskData(JiraTaskDataHandler.java:195)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraTaskDataHandler.getTaskData(JiraTaskDataHandler.java:162)
> at com.atlassian.connector.eclipse.internal.jira.core.JiraRepositoryConnector.getTaskData(JiraRepositoryConnector.java:504)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.synchronizeTask(SynchronizeTasksJob.java:260)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.synchronizedTaskRelations(SynchronizeTasksJob.java:170)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.run(SynchronizeTasksJob.java:154)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeTasksJob.run(SynchronizeTasksJob.java:135)
> at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.run(SynchronizeQueriesJob.java:225)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.jdom.JDOMException cannot be found by osgi.identity; osgi.identity="com.thoughtworks.xs
> tream"; type="osgi.bundle"; version:Version="1.3.0.v20100826-1640"
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:416)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:336)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:328)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-13381) ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick resolved JBIDE-13381.
---------------------------------------
Resolution: Done
> ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13381
> URL: https://issues.jboss.org/browse/JBIDE-13381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.3.0.Final-SOA
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Priority: Critical
> Fix For: 4.1.1.Final, 4.0.1.Final
>
> Attachments: JBIDE-13381-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png, JBIDE-13381_resolved.png
>
>
> When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way.
> When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername">
> <http-client-property name="file" value="httpclient.properties" />
> </property>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited)
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1-edited">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername"/>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months