November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15796) Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15796?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-15796: ----------------------------------- The problem is apparently that no JAX-RS endpoints have been generated. Adding: 'rest endpoint-from-entity --strategy ROOT_AND_NESTED_DTO --contentType application/json' will solve the problem. The best place in the scenario to do this is right before the scaffold generation. [~vineet.reynolds] has created FORGEPLUGINS-149 to track this problem. Not sure as to how much priority it will get though. In the meantime I'm going to resolve this issue. > Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15796 > URL: https://issues.jboss.org/browse/JBIDE-15796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.1.CR1 > > Attachments: forge-html5.server.log > > > Deployment with error: No servlet class has been specified for servlet javax.ws.rs.core.Application. > Prepare app in forge console: > 1) new-project --named testp --type war > 2) setup persistence (HIBERNATE, JBOSS_AS7) > 3) scaffold-x setup --scaffoldType angularjs --overwrite > 4) entity --named Customer > 5) field string --named name > Scaffold HTML5: > * scaffold-x from Customer.java > Build and deploy on the server. > See server.log attached for more description. > I assume this should work out of the box right? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15902) Regarding JSON to JSON Transfermation

by siva maturi (JIRA)

siva maturi created JBIDE-15902: ----------------------------------- Summary: Regarding JSON to JSON Transfermation Key: JBIDE-15902 URL: https://issues.jboss.org/browse/JBIDE-15902 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: siva maturi Hi, How to do JSON to JSON convertion using Smooks -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15901) Remote JMX connection broken (again)

by Martin Malina (JIRA)

Martin Malina created JBIDE-15901: ------------------------------------- Summary: Remote JMX connection broken (again) Key: JBIDE-15901 URL: https://issues.jboss.org/browse/JBIDE-15901 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.Beta1 Environment: JBDS 7.1.0.Beta1b B493 Reporter: Martin Malina Fix For: 4.1.1.CR1 I just found out that JMX connection to any JBoss servers does not work. Tried with EAP 6.1.1, EAP 6.2.0.ER7, WildFly 8.0.0.Beta1. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15901) Remote JMX connection broken (again)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15901?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-15901: ---------------------------------- Priority: Critical (was: Major) > Remote JMX connection broken (again) > ------------------------------------ > > Key: JBIDE-15901 > URL: https://issues.jboss.org/browse/JBIDE-15901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0.Beta1b B493 > Reporter: Martin Malina > Priority: Critical > Fix For: 4.1.1.CR1 > > > I just found out that JMX connection to any JBoss servers does not work. > Tried with EAP 6.1.1, EAP 6.2.0.ER7, WildFly 8.0.0.Beta1. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15899) OpenShift: Wrong title of Manage SSH keys shell

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15899?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15899: ------------------------------------- Fix Version/s: 4.1.1.CR1 4.2.0.Alpha1 > OpenShift: Wrong title of Manage SSH keys shell > ----------------------------------------------- > > Key: JBIDE-15899 > URL: https://issues.jboss.org/browse/JBIDE-15899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Priority: Optional > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > Attachments: wrong_title.png > > > Manage SSH key shell (invoked from context menu of connection in the OpenShift Explorer) has title Select Domain instead of something like "Manage SSH keys"... > See attached image -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15808) "Tail files" cannot not load application gear list for recently created scaling apps

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15808?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15808 at 11/7/13 9:04 AM: ------------------------------------------------------------------- curl command to scale an application up (to several gears) is the following - taken from https://issues.jboss.org/browse/JBIDE-15484?focusedCommentId=12807002&pag...: {code} curl -H "Accept: application/xml; version=1.2" --user USERNAME:PASS https://openshift.redhat.com/broker/rest/domains/foogoo/applications/scal... -X POST -devent=scale-up {code} was (Author: adietish): curl command to scale an application up (to several gears) is the following - taken from JBIDE-15484/https://issues.jboss.org/browse/JBIDE-15484?focusedCommentId=...: {code} curl -H "Accept: application/xml; version=1.2" --user USERNAME:PASS https://openshift.redhat.com/broker/rest/domains/foogoo/applications/scal... -X POST -devent=scale-up {code} > "Tail files" cannot not load application gear list for recently created scaling apps > ------------------------------------------------------------------------------------ > > Key: JBIDE-15808 > URL: https://issues.jboss.org/browse/JBIDE-15808 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: respin-b > Fix For: 4.1.1.Beta1 > > Attachments: could-not-load-application-gears.png > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15808) "Tail files" cannot not load application gear list for recently created scaling apps

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15808?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15808: ------------------------------------------ curl command to scale an application up (to several gears) is the following - taken from JBIDE-15484/https://issues.jboss.org/browse/JBIDE-15484?focusedCommentId=...: {code} curl -H "Accept: application/xml; version=1.2" --user USERNAME:PASS https://openshift.redhat.com/broker/rest/domains/foogoo/applications/scal... -X POST -devent=scale-up {code} > "Tail files" cannot not load application gear list for recently created scaling apps > ------------------------------------------------------------------------------------ > > Key: JBIDE-15808 > URL: https://issues.jboss.org/browse/JBIDE-15808 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: respin-b > Fix For: 4.1.1.Beta1 > > Attachments: could-not-load-application-gears.png > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15357) Unexpected state of deployed project when project is deleted

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15357?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15357. --------------------------------- Works as expected. Verified in JBDS 7.1.0.Beta1b B493. Closing. > Unexpected state of deployed project when project is deleted > ------------------------------------------------------------ > > Key: JBIDE-15357 > URL: https://issues.jboss.org/browse/JBIDE-15357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA, L64 > Reporter: Jiri Peterka > Assignee: Rob Stryker > Labels: respin-b > Fix For: 4.1.1.Beta1 > > > When project is deployed in IDE and then removed expected behavior would expect project would be undeployed. When I've tried that everything seemed as undeployed (I mean Server view) but project is still deployed. This is not user expected behavior IMO. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15874) Typo in JBoss Central Updates tab: plugins > plug-ins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15874?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-15874. --------------------------------- Assignee: Fred Bricon Fix Version/s: 4.1.1.CR1 Resolution: Done Fixed master : https://github.com/jbosstools/jbosstools-discovery/commit/4f29e9374a76b24... jbosstools-4.1.x : https://github.com/jbosstools/jbosstools-discovery/commit/6ca81a9195d69f9... > Typo in JBoss Central Updates tab: plugins > plug-ins > ----------------------------------------------------- > > Key: JBIDE-15874 > URL: https://issues.jboss.org/browse/JBIDE-15874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.1.CR1 > > Attachments: Central_updates_plugin.png > > > JBoss Central Updates tab uses spelling "plugin" and "plugins". > There are two common spellings of this word: plugin and plug-in. Within Red Hat content services we follow the IBM style guide. It states that the hyphenated version should be used, so "plug-in". > So mispellings in updates tab should be fixed: > * plugin > plug-in > * plugins > plug-ins > Some example instances in image, more in actual tab: > !Central_updates_plugin.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15874) Typo in JBoss Central Updates tab: plugins > plug-ins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15874?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15874: -------------------------------- Priority: Trivial (was: Major) > Typo in JBoss Central Updates tab: plugins > plug-ins > ----------------------------------------------------- > > Key: JBIDE-15874 > URL: https://issues.jboss.org/browse/JBIDE-15874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Fred Bricon > Priority: Trivial > Fix For: 4.1.1.CR1 > > Attachments: Central_updates_plugin.png > > > JBoss Central Updates tab uses spelling "plugin" and "plugins". > There are two common spellings of this word: plugin and plug-in. Within Red Hat content services we follow the IBM style guide. It states that the hyphenated version should be used, so "plug-in". > So mispellings in updates tab should be fixed: > * plugin > plug-in > * plugins > plug-ins > Some example instances in image, more in actual tab: > !Central_updates_plugin.png! -- 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, 5 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 November 2013