[ http://jira.jboss.com/jira/browse/JBIDE-757?page=all ]
Max Andersen updated JBIDE-757:
-------------------------------
Fix Version/s: LATER
(was: 2.0.0.Beta4)
from the list of questions/issues (analyzer thread running long and assumption that schema==username for validation) we have found with JPA support in Eclipse WTP I think we should not do this by default before that is fixed.
> Seam projects should have JPA support by default
> ------------------------------------------------
>
> Key: JBIDE-757
> URL: http://jira.jboss.com/jira/browse/JBIDE-757
> Project: JBoss Tools
> Issue Type: Feature Request
> Reporter: Michael Yuan
> Assigned To: Denis Golovin
> Fix For: LATER
>
>
> In the Seam New Project wizard, the "Project Facet" screen shows that JPA support is not included by default for the project. Since 99% of Seam web apps do use JPA, I think we should select that by default.
--
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
Seam-Jboss 4.2.0 project created with myfaces listener
------------------------------------------------------
Key: JBIDE-561
URL: http://jira.jboss.com/jira/browse/JBIDE-561
Project: JBoss Tools
Issue Type: Bug
Environment: Jdk 5
Reporter: Fabricio Lemos
Steps to reproduce the bug:
1. Begin to create a new Seam Project.
2. Choose a Jboss 4.2 Target Runtime
3. Enable Seam 1.2 and JSF 1.2 facets
4. Point the Jboss AS Home Folder to the Jboss installation directory.
5. Choose deploy as ear.
6. Press finish.
The web.xml contains:
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
</listener>
The JSF 1.2 RI configuration should be used.
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-357?page=all ]
Max Andersen updated JBIDE-357:
-------------------------------
Fix Version/s: LATER
(was: 2.0.0.Beta4)
slipping
> "New JBossWS Project" wizard
> ----------------------------
>
> Key: JBIDE-357
> URL: http://jira.jboss.com/jira/browse/JBIDE-357
> Project: JBoss Tools
> Issue Type: Task
> Components: Webservices
> Affects Versions: LATER
> Reporter: Ole Matzura
> Assigned To: Lars Høidahl
> Fix For: LATER
>
>
> It should be possible to create an empty java / jbossws project ready to go for webservice development
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-358?page=all ]
Max Andersen updated JBIDE-358:
-------------------------------
Fix Version/s: LATER
(was: 2.0.0.Beta4)
> Look into WTP Facet's as a unified api for handling "lib" and "project" configuration
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-358
> URL: http://jira.jboss.com/jira/browse/JBIDE-358
> Project: JBoss Tools
> Issue Type: Task
> Affects Versions: 2.0.0.Beta1
> Reporter: Max Andersen
> Assigned To: Marshall Culpepper
> Fix For: LATER
>
>
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-348?page=all ]
Max Andersen updated JBIDE-348:
-------------------------------
Fix Version/s: LATER
(was: 2.0.0.Beta4)
slipping
> Add prompt for wstools location to jbossws related wizards
> ----------------------------------------------------------
>
> Key: JBIDE-348
> URL: http://jira.jboss.com/jira/browse/JBIDE-348
> Project: JBoss Tools
> Issue Type: Task
> Components: Webservices
> Affects Versions: LATER
> Reporter: Ole Matzura
> Assigned To: Ole Matzura
> Fix For: LATER
>
>
> When invoking any of the jbossws-related wizards, the user should first be prompted for the wstools location if it has not been specified in the jbossws preferences page..
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-356?page=all ]
Max Andersen updated JBIDE-356:
-------------------------------
Fix Version/s: LATER
(was: 2.0.0.Beta4)
slipping
> Bundle jbossws with jbossws-plugin
> ----------------------------------
>
> Key: JBIDE-356
> URL: http://jira.jboss.com/jira/browse/JBIDE-356
> Project: JBoss Tools
> Issue Type: Task
> Components: Webservices
> Affects Versions: LATER
> Reporter: Ole Matzura
> Assigned To: Lars Høidahl
> Fix For: LATER
>
>
> We should bundle jbossws with the plugin allowing developers to have everything up-and-running when they jbossws-enable a project. It would be nice if it still would be possible to select an "external" installation (for testing, etc..)
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-348?page=all ]
Max Andersen updated JBIDE-348:
-------------------------------
Affects Version/s: LATER
(was: 2.0.0.Beta2)
slipping
> Add prompt for wstools location to jbossws related wizards
> ----------------------------------------------------------
>
> Key: JBIDE-348
> URL: http://jira.jboss.com/jira/browse/JBIDE-348
> Project: JBoss Tools
> Issue Type: Task
> Components: Webservices
> Affects Versions: LATER
> Reporter: Ole Matzura
> Assigned To: Ole Matzura
> Fix For: 2.0.0.Beta4
>
>
> When invoking any of the jbossws-related wizards, the user should first be prompted for the wstools location if it has not been specified in the jbossws preferences page..
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-356?page=all ]
Max Andersen updated JBIDE-356:
-------------------------------
Affects Version/s: LATER
(was: 2.0.0.Beta2)
slipping
> Bundle jbossws with jbossws-plugin
> ----------------------------------
>
> Key: JBIDE-356
> URL: http://jira.jboss.com/jira/browse/JBIDE-356
> Project: JBoss Tools
> Issue Type: Task
> Components: Webservices
> Affects Versions: LATER
> Reporter: Ole Matzura
> Assigned To: Lars Høidahl
> Fix For: 2.0.0.Beta4
>
>
> We should bundle jbossws with the plugin allowing developers to have everything up-and-running when they jbossws-enable a project. It would be nice if it still would be possible to select an "external" installation (for testing, etc..)
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-357?page=all ]
Max Andersen updated JBIDE-357:
-------------------------------
Affects Version/s: LATER
(was: 2.0.0.Beta2)
slipping
> "New JBossWS Project" wizard
> ----------------------------
>
> Key: JBIDE-357
> URL: http://jira.jboss.com/jira/browse/JBIDE-357
> Project: JBoss Tools
> Issue Type: Task
> Components: Webservices
> Affects Versions: LATER
> Reporter: Ole Matzura
> Assigned To: Lars Høidahl
> Fix For: 2.0.0.Beta4
>
>
> It should be possible to create an empty java / jbossws project ready to go for webservice development
--
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
[ http://jira.jboss.com/jira/browse/JBIDE-657?page=all ]
Max Andersen updated JBIDE-657:
-------------------------------
Fix Version/s: LATER
(was: 2.0.0.Beta4)
not a priority - Eclipse WTP projects are more important to handle smoothly.
> Support deploy of Seam Gen projects via JBoss AS
> ------------------------------------------------
>
> Key: JBIDE-657
> URL: http://jira.jboss.com/jira/browse/JBIDE-657
> Project: JBoss Tools
> Issue Type: Feature Request
> Components: Seam
> Reporter: Max Andersen
> Assigned To: Rob Stryker
> Fix For: LATER
>
>
> We should see if we could do deployment effectively of native seam-gen projects
--
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