[JBoss JIRA] Created: (JBIDE-1388) support remote hosts/external started AS adapter
by Max Andersen (JIRA)
support remote hosts/external started AS adapter
------------------------------------------------
Key: JBIDE-1388
URL: http://jira.jboss.com/jira/browse/JBIDE-1388
Project: JBoss Tools
Issue Type: Feature Request
Components: JBossAS
Reporter: Max Andersen
Fix For: 2.1
people like to start there server manually and just hook up to it via remote debugging - we should make that easy (its trivial via eclipse support for remote debugging)
should be an option on the servers, doesnt require new server/runtime type if local server.
Only catch is that the server might not even be accessible via filesystem - how should we handle deploy and runtime lib situation ? (my best bet is just that these would be unspecified and not provide those features)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBDS-1016) Usability issue with Seam Web Project Wizard
by Joshua Wulf (JIRA)
Usability issue with Seam Web Project Wizard
--------------------------------------------
Key: JBDS-1016
URL: https://jira.jboss.org/jira/browse/JBDS-1016
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 3.0.0.M4
Environment: Mac OS X 10.4.11 32 bit PPC
Reporter: Joshua Wulf
The Seam Web Project Wizard changes the Configuration when the Target runtime is changed. Although it starts out with "Dynamic Web Application for Seam 2.0" selected by default, if the Target runtime is changed the Configuration selection is changed to match the Target Runtime. This results in an error "Seam facet must be enabled."
Changing the Target Runtime back to the original one does not remove the error. There are two ways to remove the error message. One is to manually change the Configuration back to "Dynamic Web Application for Seam 2.x". Since it is not possible to move forward from this page without enabling the Seam facet, the configuration should not automatically change to one that does not have Seam facet enabled.
The situation is more complicated, and worse, however, because the other way to remove the error message is to manually modify the Configuration using the "Modify" button. If the user does this, and enables JavaServer Faces and Seam, the error message will disappear and they will be able to move forward.
However, when it comes time to select the Seam runtime the user will run into a problem. In the Modify Configuration screen where the user enabled the Seam facet, the unique option there was fixed at version 2.2. If the Seam runtime the user wishes to use is not 2.2 then they will get an error that the Seam runtime is an incompatible version. They will be unable to select any other version in the version drop-down box.
So there are three problems:
1. The Configuration changes automatically to one incompatible with a Seam Web Project if the Target runtime is changed.
2 . Although a user may try to clear the resultant error message by changing the runtime back to the original one, the error message will remain, as the dialog will change the configuration to another incompatible one. If the user did not notice the original default configuration (which they may well not if they are moving from top to the bottom of the wizard, which will be the usual case), they have no way of knowing how to clear the error message.
3. If the user clicks on the tempting "Modify" button and manually enables Seam they can run into a problem several screens later (error message saying Seam version is incompatible and only 2.2 in the version drop-down box) with no obvious way to resolve it.
The workaround is to document this quirk, but that defeats the purpose of an intuitive in-IDE wizard that guides you through setting up the project.
I would recommend making the configuration stay on the default, even when the Target runtime is changed. If the user sees an incompatible version of Seam there when they scan down, they are likely to click it to see if a compatible version of Seam is there. If they see "Default configuration for X runtime" with a description saying "A good starting point... Additional facets can later be installed to add new functionality to the project" and an error message saying "Seam facet must be enabled", then their likely response will be to modify the configuration to "add new functionality" to the "good starting point" that the wizard has selected for them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBIDE-5535) New Web Service
by Burr Sutter (JIRA)
New Web Service
---------------
Key: JBIDE-5535
URL: https://jira.jboss.org/jira/browse/JBIDE-5535
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
Attachments: New_WebService_Wizard.jpg, New_Wizard.jpg
There should be a New Web Service Project wizard (the same as New Dynamic Web Project) and a New Web Service component wizard.
The New Web Service Project wizard creates the exact same thing as New Dynamic Web Project but with HelloWorldWS.java containing the following:
package com.jboss.lab;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService
public class MyWebService {
@WebMethod
public String sayHello(String name) {
return "Hello2 " + name + "!";
}
}
And the appropriate entries in the web.xml.
<servlet>
<servlet-name>MyWebServiceServlet</servlet-name>
<servlet-class>com.jboss.lab.MyWebService</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MyWebServiceServlet</servlet-name>
<url-pattern>/MyWebService</url-pattern>
</servlet-mapping>
See screenshots for current functionality.
This suggestion is based on how Visual Studio handles this scenario. For a New Web Service or New Web Service project, it drops in the annotated mywebservice.asmx automatically. You can deploy the project/component immediately without further editing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBIDE-1608) Hibernate Configuration view should display all database
by Vitali Yemialyanchyk (JIRA)
Hibernate Configuration view should display all database
---------------------------------------------------------
Key: JBIDE-1608
URL: http://jira.jboss.com/jira/browse/JBIDE-1608
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Priority: Minor
Fix For: LATER
Look at the attached file hibernate.cfg.xml - if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql</property>
Hibernate Configuration view -> ... -> Database display correctly mysql database - but if
<property name="hibernate.connection.url">jdbc:mysql://localhost:3306</property>
look like this
Hibernate Configuration view -> ... -> Database display nothing and the user can't understand what is wrong - I provide 2 screenshots
the same if
<property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql1</property>
mysql1 - there is no such DB
as I think in first case Hibernate Configuration should display all mysql DBs and in the second case the user should get message -
something like "Can't find shuch DB"
Other thing - then I press right mouse button on Hibernate Configuration view -> ... -> Database - I expect to get possibility to configure
DB URL and may be some other properties - the best thing here if I'll get some dialog - or at least possibility to open hibernate.cfg.xml for edit.
For this I'll create other new issue...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years