[
https://issues.jboss.org/browse/JBIDE-13559?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-13559 at 2/13/13 6:55 PM:
-------------------------------------------------------------------
What I cannot understand is that JBT 4.0 / JBDS6 behave exactly the same even though they
request protocol 1.0
!JBDS6-listing-type-as-cartridge.png!
To me it looks as if there's a regression in OpenShift since protocol 1.0 now lists
the application type as embedded cartridge:
If you list the cartridges of one of your applications
{code}
[adietish@adietish-thinkpad studio]$ curl -k -H "Accept: application/xml;
version=1.0" --user "USERNAME:PASSWORD"
https://openshift.redhat.com/broker/rest/domains/myops/applications/kitch... -X
GET
{code}
You get the application type (and embedded cartridges there are)
{code}
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>jbossas-7</name>
<type>standalone</type>
<status-messages nil="true"></status-messages>
<properties>
</properties>
</cartridge>
</data>
<messages/>
<version>1.0</version>
<supported-api-versions>
<supported-api-version>1.0</supported-api-version>
<supported-api-version>1.1</supported-api-version>
<supported-api-version>1.2</supported-api-version>
<supported-api-version>1.3</supported-api-version>
</supported-api-versions>
</response>
{code}
In
https://bugzilla.redhat.com/show_bug.cgi?id=838611 this request was fixed to only
return embeddable cartridges, not the standalone/application-type. Now apparently
there's a regression.
was (Author: adietish):
What I cannot understand is that JBT 4.0 / JBDS6 behave exactly the same even though
they request protocol 1.0
!JBDS6-listing-type-as-cartridge.png!
To me it looks as if there's a regression in OpenShift since protocol 1.0 now lists
the application type as embedded cartridge:
If you list the cartridges of one of your applications
{quote}
[adietish@adietish-thinkpad studio]$ curl -k -H "Accept: application/xml;
version=1.0" --user "USERNAME:PASSWORD"
https://openshift.redhat.com/broker/rest/domains/myops/applications/kitch... -X
GET
{quote}
You get the application type (and embedded cartridges there are)
{quote}
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>jbossas-7</name>
<type>standalone</type>
<status-messages nil="true"></status-messages>
<properties>
</properties>
</cartridge>
</data>
<messages/>
<version>1.0</version>
<supported-api-versions>
<supported-api-version>1.0</supported-api-version>
<supported-api-version>1.1</supported-api-version>
<supported-api-version>1.2</supported-api-version>
<supported-api-version>1.3</supported-api-version>
</supported-api-versions>
</response>
{quote}
In
https://bugzilla.redhat.com/show_bug.cgi?id=838611 this request was fixed to only
return embeddable cartridges, not the standalone/application-type. Now apparently
there's a regression.
Cannot embed cartridges
-----------------------
Key: JBIDE-13559
URL:
https://issues.jboss.org/browse/JBIDE-13559
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
Attachments: cannot-remove-apptype.png
If you try to embed cartridges (or remove embedded cartridges) in Alpha2 (not released
yet), then you wont be able to do it. The Eclipse toolign is complaining that it cannot
remove an embeddable cartridge that's actually matching the application type.
--
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