[JBoss JIRA] Created: (JBIDE-3005) JBossWS Property Page isn't defined correctly
by Snjezana Peco (JIRA)
JBossWS Property Page isn't defined correctly
---------------------------------------------
Key: JBIDE-3005
URL: https://jira.jboss.org/jira/browse/JBIDE-3005
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.0.0.beta1
Reporter: Snjezana Peco
Steps to reproduce:
- create any project
- right-click some folder/file within the project and select Properties
You will get a dialog showing "The currently displayed page contains invalid values".
You will also get this error if you select Properties for some item in the Problems view.
The issue happens because this property page is defined for a project, but doesn't contain a filter.
If you want the property page to be defined for the project, you should add the following filter :
<enabledWhen>
<adapt
type="org.eclipse.core.resources.IProject">
</adapt>
</enabledWhen>
If you want the page to be defined only for projects containing the WS facet, the filter would look like as follows:
<enabledWhen>
<adapt
type="org.eclipse.core.resources.IProject">
<test
property="org.eclipse.wst.common.project.facet.core.projectFacet"
value="jbossws.core"/>
</adapt>
</enabledWhen>
--
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
17 years, 8 months
[JBoss JIRA] Created: (JBIDE-3045) Smooks needs to be better to handle errors
by Max Rydahl Andersen (JIRA)
Smooks needs to be better to handle errors
------------------------------------------
Key: JBIDE-3045
URL: https://jira.jboss.org/jira/browse/JBIDE-3045
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.0.0.beta1
Reporter: Max Rydahl Andersen
Fix For: 3.0.0.cr1
The Smooks editor starts behaving funny if I just add simple element such as <param name="myOwnParam"/> which is perfectly valid according to the xml.
Then it just says: boolean <Can't find the class : boolean> ..no idea what the user should do about that ?
The Graph/Normal tabs (what does Normal mean anyway?) should be disabled with a message about
something is wrong and then we should have a source tab in which you can use the normal WTP XML editor to fix any possible errors AND when the errors are fixed the "broken" tabs should start working again.
--
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
17 years, 9 months
[JBoss JIRA] Created: (JBIDE-2967) change sourcepath directory names to coordinate w/ seam-gen
by Dan Allen (JIRA)
change sourcepath directory names to coordinate w/ seam-gen
-----------------------------------------------------------
Key: JBIDE-2967
URL: https://jira.jboss.org/jira/browse/JBIDE-2967
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Seam
Affects Versions: 3.0.0.alpha
Reporter: Dan Allen
Priority: Minor
Fix For: 3.0.0.beta1
seam-gen changed the source paths for the action and model directories as follows:
src/action -> src/hot
src/model -> src/main
The purpose of this renaming was to reflect how the two sourcepaths are compiled and not by which types of components and classes they might originally contain. Internally, we will still refer to src/hot as the action directory and src/main as the model directory, but it opens up the possibility of the user adding non-hot deployable components to src/main without feeling a semantic mismatch.
--
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
17 years, 9 months
[JBoss JIRA] Created: (JBIDE-2758) Seam project with Portlets facet enabled can't start in JBoss AS server
by Aliaksey Nis (JIRA)
Seam project with Portlets facet enabled can't start in JBoss AS server
-----------------------------------------------------------------------
Key: JBIDE-2758
URL: https://jira.jboss.org/jira/browse/JBIDE-2758
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal
Affects Versions: 3.0.0.beta1
Environment: WindowsXP SP2
JBoss Tools
Version: 3.0.0.Beta1
Build id: 200809100010-nightly
JDK 1.5_08
Reporter: Aliaksey Nis
EXECUTE: New > New Seam project.
EXECUTE: Input name for project - testproject.
EXECUTE: In Configuration Filed select Seam project with Portlets 2.0 (Portlets Core 2.0, JSF Portlets 1.0, Seam Portlets 1.0).
EXECUTE: Press Next til Seam facet page, select War deployment, press Finish.
EXECUTE: Copy testproject-ds.xml to JBoss AS deploy folder(JBIDE-2736).
EXECUTE: Start server - 4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657).
EXECUTE: Try to run this test project.
FAILURE: Multiply exceptions appears in server console, project didn't start.
Attached server log(6Mb+ :) ). In log - Server startup, Seam War project runned(all work fine), then Seam War project with Portlets runned(exceptions...).
--
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
17 years, 9 months
[JBoss JIRA] Created: (JBIDE-2411) Intermitent jdbc driver not found when creating a new Seam project
by Jay Balunas (JIRA)
Intermitent jdbc driver not found when creating a new Seam project
------------------------------------------------------------------
Key: JBIDE-2411
URL: http://jira.jboss.com/jira/browse/JBIDE-2411
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Environment: RHEL 5
Java 1.5
JBDS 1.1.CR1
Reporter: Jay Balunas
Attachments: Screenshot-Edit Driver Definition .png
This was an issue with multiple machine during the JBDS lab at the Redhat summit. Not all users saw this. All users in the lab used the same JDK, JBDS, and database from the USB sticks. the users were following through the steps provided in the JBDS lab PDF.
On some of the machines ( not all of them ) the path to the hsqldb.jar was not found - even though the path seemed correct - although very long. I manually set the path and it seemed to take. See attached screen shot for the long path to the jar that was set 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
17 years, 9 months