September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15429) openshift-java-client: add support for downloadable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15429?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15429: ------------------------------------------ The next problem I had to deal with is an internal library problem: When you submit the cartridge to the backend you only know about it's url. The name is then set by the backend when it deploys the cartridge (it takes it from the cartridge manifest when it checks it out). I thus had to change the ICartridge and IApplication classes. It now allows you to submit a cartridge with an url and returns you the full cartridge as it is reported by the REST response: {code} "additional_gear_storage":0, "base_gear_storage":1, "collocated_with":[ "smarterclayton-go-1.1", "mysql-5.1" ], "current_scale":1, "description":"Foreman TODO", "display_name":"Foreman", "gear_profile":"small", "help_topics":{ "Building with MySQL":"http://docs.redhat.com/docs/en-US/OpenShift/2.0/html/User_Guide/sect-User..." }, "license":"ASL 2.0", "license_url":"http://www.apache.org/licenses/LICENSE-2.0.txt", "links":{ "GET":{ "href":"https://openshift.redhat.com/broker/rest/domains/foobarz/applications/dow...", "method":"GET", "optional_params":[ ], ... {code} > openshift-java-client: add support for downloadable cartridges > -------------------------------------------------------------- > > Key: JBIDE-15429 > URL: https://issues.jboss.org/browse/JBIDE-15429 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.2.0.Alpha1 > > > OpenShift added support for downloadable cartridges lately. This allows you to provide your very own cartridge by providing a git-url where it may be checked out. > Fusesource provided a PR on github that we should merge in: https://github.com/openshift/openshift-java-client/pull/68 > The PR seems perfectly functional but it has a few shortcomings though that we have to fix though (see comments in the PR) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15429) openshift-java-client: add support for downloadable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15429?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15429: ------------------------------------------ The first problem that arose is that OpenShift apparently wont handle parameter arrays and maps correctly: If I try to create a web-cartridge jbossas-7 with a downloadable cartridge foreman the app is created but the embedded foreman cartridge is ignored: {code} curl -H "Accept: application/json; version=1.2" --user USER:PASSWORD https://openshift.redhat.com/broker/rest/domains/foogoo/applications -X POST -d name=scalable2 -dcartridges[][name]=jbossas-7 -dcartridges[][name]="http://cartreflect-claytondev.rhcloud.com/reflect?github=ncdc/openshift-f... {code} The resulting app has no foreman cartridge embedded (empty "embedded"): {code} { "api_version":1.2, "data":{ "aliases":[ ], "app_url":"http://scalable2-foogoo.rhcloud.com/", "build_job_url":null, "building_app":null, "building_with":null, "creation_time":"2013-09-23T14:47:53Z", "domain_id":"foogoo", "embedded":{ }, "framework":"jbossas-7", {code} If on the other hand, I try to create an app with a downloadable web-cartridge and a normal add-on cartridge, the request errors and complains that there is no web-cartridge being supplied: {code} curl -H "Accept: application/json; version=1.2" --user USER:PASSWORD https://openshift.redhat.com/broker/rest/domains/foogoo/applications -X POST -d name=scalable3 -dcartridges[][url]=claytondev.rhcloud.com/reflect?github=smarterclayton/openshift-go-cart -dcartridges[][name]=mysql {code} The error that is reported by the REST service: {code} { "api_version":1.2, "data":null, "messages":[ { "exit_code":109, "field":"cartridge", "severity":"error", "text":"Each application must contain one web cartridge. None of the specified cartridges mysql is a web cartridge. Please include one of the following cartridges: nodejs-0.6, nodejs-0.10, python-3.3, python-2.7, python-2.6, zend-5.6, ruby-1.9, ruby-1.8, jenkins-1, jbossews-2.0, jbossews-1.0, perl-5.10, php-5.3, jbosseap-6, diy-0.1, and jbossas-7 or supply a valid url to a custom web_framework cartridge." } ], "status":"unprocessable_entity", "supported_api_versions":[ 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6 ], "type":null, "version":"1.2" } {code} I did some googling and found some references that show that older Rails version were supporting these parameter arrays and maps: https://github.com/RestKit/RestKit/pull/697 But for some unknown reason this support is not present any more as the above request show. In result I had to switch to json encoded parameters which works flawlessly. Requesting the above in json looks as follows: {code} curl -H "Content-Type: application/json" -H "Accept: application/json; version=1.2" --user USER:PASSWORD https://openshift.redhat.com/broker/rest/domains/foobarz/applications -X POST -d '{ "name":"as71", "cartridges":[ { "name":"jbossas-7" }, { "url":"http://cartreflect-claytondev.rhcloud.com/reflect?github=ncdc/openshift-f..." } ] }' {code} > openshift-java-client: add support for downloadable cartridges > -------------------------------------------------------------- > > Key: JBIDE-15429 > URL: https://issues.jboss.org/browse/JBIDE-15429 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.2.0.Alpha1 > > > OpenShift added support for downloadable cartridges lately. This allows you to provide your very own cartridge by providing a git-url where it may be checked out. > Fusesource provided a PR on github that we should merge in: https://github.com/openshift/openshift-java-client/pull/68 > The PR seems perfectly functional but it has a few shortcomings though that we have to fix though (see comments in the PR) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15508) Incorrect problem marker when refactoring a custom Qualifier

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15508?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15508: ---------------------------------- Description: When I refactor (rename or move in another package) a CDI Qualifier such as: {code} @Retention(RUNTIME) @Target({TYPE, METHOD, FIELD, PARAMETER}) @Qualifier public @interface ConsumerSessionQualifier { } {code} I get error markers on the @Target annotation with the following message: {quote} @Target annotation value is not correct. It should be ElementType.METHOD {quote} was: When I refactor (rename or move in another package) a CDI Qualifier such as: {code} @Retention(RUNTIME) @Target({TYPE, METHOD, FIELD, PARAMETER}) @Qualifier public @interface ConsumerSessionQualifier { } {code} I get error markers on the @Target annotation with the following message: "@Target annotation value is not correct. It should be ElementType.METHOD" > Incorrect problem marker when refactoring a custom Qualifier > ------------------------------------------------------------ > > Key: JBIDE-15508 > URL: https://issues.jboss.org/browse/JBIDE-15508 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > > When I refactor (rename or move in another package) a CDI Qualifier such as: > {code} > @Retention(RUNTIME) > @Target({TYPE, METHOD, FIELD, PARAMETER}) > @Qualifier > public @interface ConsumerSessionQualifier { > } > {code} > I get error markers on the @Target annotation with the following message: > {quote} > @Target annotation value is not correct. It should be ElementType.METHOD > {quote} > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15508) Incorrect problem marker when refactoring a custom Qualifier

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15508: ------------------------------------- Summary: Incorrect problem marker when refactoring a custom Qualifier Key: JBIDE-15508 URL: https://issues.jboss.org/browse/JBIDE-15508 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdi Affects Versions: 4.1.0.Final Reporter: Xavier Coulon When I refactor (rename or move in another package) a CDI Qualifier such as: {code} @Retention(RUNTIME) @Target({TYPE, METHOD, FIELD, PARAMETER}) @Qualifier public @interface ConsumerSessionQualifier { } {code} I get error markers on the @Target annotation with the following message: "@Target annotation value is not correct. It should be ElementType.METHOD" -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15507) Support injection of JMSContext

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15507: ------------------------------------- Summary: Support injection of JMSContext Key: JBIDE-15507 URL: https://issues.jboss.org/browse/JBIDE-15507 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdi Affects Versions: 4.1.0.Final Reporter: Xavier Coulon if I try to inject a JMSContext (part of JMS 2.0 in JavaEE7) into a bean (CDI bean or EJB): @Inject JMSContext context; I get the following warning: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]". Yet, there's no problem when I deploy the application on Wildfly (8.0.0.Alpha4, the latest release so far) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-179) ModeShape Client is in wrong categories

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-179?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-179. ----------------------------------- Verified with JBDSIS 7.0.0.Beta3 / JBTIS 4.1.3.Beta3 > ModeShape Client is in wrong categories > --------------------------------------- > > Key: JBTIS-179 > URL: https://issues.jboss.org/browse/JBTIS-179 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 7.0.0-JBDS > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/integration/kepler/integrat... > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 4.1.3 > > > Now, the ModeShape Cient in the following categories > * JBoss Business Process and Rules Development (there's nothing in common with ModeShape) > * JBoss Data Virtualization Development (OK) > * JBoss SOA 5.x Development (maybe OK, but EDS is needed) > * JBoss SOA Development (wrong, we need DV for ModeShape) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-179) ModeShape Client is in wrong categories

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-179?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-179. ------------------------------ Fix Version/s: 4.1.3 Resolution: Done ModeShape component categorization corrected in JBTIS 4.1.3.Beta3/ JBDSIS 7.0.0.Beta3 > ModeShape Client is in wrong categories > --------------------------------------- > > Key: JBTIS-179 > URL: https://issues.jboss.org/browse/JBTIS-179 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 7.0.0-JBDS > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/integration/kepler/integrat... > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 4.1.3 > > > Now, the ModeShape Cient in the following categories > * JBoss Business Process and Rules Development (there's nothing in common with ModeShape) > * JBoss Data Virtualization Development (OK) > * JBoss SOA 5.x Development (maybe OK, but EDS is needed) > * JBoss SOA Development (wrong, we need DV for ModeShape) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-177) Cannot save process definition which contains a local variable

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-177?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-177. ------------------------------ Fix Version/s: 4.1.3 Resolution: Done Issue correted in JBTIS 4.1.3.Beta3/ JBDSIS 7.0.0.Beta3 > Cannot save process definition which contains a local variable > -------------------------------------------------------------- > > Key: JBTIS-177 > URL: https://issues.jboss.org/browse/JBTIS-177 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPMN2 > Reporter: Len DiMaggio > Assignee: Paul Leacu > Fix For: 4.1.3 > > > Eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=417203 Will be resolved in JBTIS 4.1.3.beta2 and JBDSIS 7.0.0.beta2 -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-178) In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-178. ------------------------------ Resolution: Cannot Reproduce Bug >From Kris - there is no issue - the current drools/jBPM has backward compatibility built into them: The idea is that the Drools & jBPM plugins would support older versions too. So, based on the ability to configure your own runtime and backwards compatibility of resource files, that should be possible. > In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5 > ------------------------------------------------------------------------------------------------------- > > Key: JBTIS-178 > URL: https://issues.jboss.org/browse/JBTIS-178 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools/ jBPM5 > Reporter: Len DiMaggio > Assignee: Paul Leacu > Attachments: drools1.png > > > See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6? -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Sande Gilda commented on JBDS-2727: ----------------------------------- 1) HTML5 - Created https://issues.jboss.org/browse/JDF-497 for the kitchensink-html5-mobile cheat sheet and asked [~vineet.reynolds] to take a look at it. 2) Java EE Web - Completed by [~snjeza] and updated by [~fbricon]. 3) RichFaces - Created https://issues.jboss.org/browse/JDF-498 for the kitchensink-rf cheat sheet and asked [~bleathem] to take a look at it. > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Burr Sutter > Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md > > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013