[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
[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
[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