November 2007 - jbosstools-issues

[JBoss JIRA] Closed: (JBIDE-260) Selecting EJB3 Classpath container, then going back, and choosing another container causes an EJB3 CP error message

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-260?page=all ] Max Andersen closed JBIDE-260. ------------------------------ > Selecting EJB3 Classpath container, then going back, and choosing another container causes an EJB3 CP error message > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-260 > URL: http://jira.jboss.com/jira/browse/JBIDE-260 > Project: JBoss Tools > Issue Type: Bug > Components: ejb3 > Affects Versions: 1.5 Release Candidate 2 > Reporter: Marshall Culpepper > Assigned To: Marshall Culpepper > Fix For: 1.5 Final > > > If you select the JBoss EJB3 Classpath container (Project Properties > Java Build Path > Libraries > Add Library), then go back and try to use a different classpath container, and press Finish, JBossIDE gives an EJB3-related error message about not having a supported version of JBoss for EJB3 (this should only happen when EJB3 CP is selected) -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-252) Port JBossIDE WTP dependencies to WTP 1.0

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-252?page=all ] Max Andersen closed JBIDE-252. ------------------------------ > Port JBossIDE WTP dependencies to WTP 1.0 > ----------------------------------------- > > Key: JBIDE-252 > URL: http://jira.jboss.com/jira/browse/JBIDE-252 > Project: JBoss Tools > Issue Type: Task > Affects Versions: 1.5 Release Candidate 1 > Reporter: Marshall Culpepper > Assigned To: Marshall Culpepper > Fix For: 1.5 Release Candidate 2 > > > Update the webtools integration in JBossIDE to Webtools 1.0. The initial update will use WTP 1.0M9. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-251) add hibernate-annotations.jar into JBoss EJB3 Libraries

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-251?page=all ] Max Andersen closed JBIDE-251. ------------------------------ > add hibernate-annotations.jar into JBoss EJB3 Libraries > ------------------------------------------------------- > > Key: JBIDE-251 > URL: http://jira.jboss.com/jira/browse/JBIDE-251 > Project: JBoss Tools > Issue Type: Feature Request > Components: ejb3 > Affects Versions: 1.5 Release Candidate 1 > Reporter: Rafal Piotrowski > Assigned To: Marshall Culpepper > Priority: Trivial > Fix For: 1.5 Release Candidate 2 > > -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-254) Cache of ITypes incomplete compared to what should be there

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-254?page=all ] Max Andersen closed JBIDE-254. ------------------------------ > Cache of ITypes incomplete compared to what should be there > ----------------------------------------------------------- > > Key: JBIDE-254 > URL: http://jira.jboss.com/jira/browse/JBIDE-254 > Project: JBoss Tools > Issue Type: Bug > Components: aop > Affects Versions: 1.5 Release Candidate 1 > Reporter: Rob Stryker > Assigned To: Rob Stryker > Fix For: 1.5 Release Candidate 2 > > > Requests to get ITypes from model's IType cache returning null. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-253) Introductions not implemented correctly (class="" vs expr="")

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-253?page=all ] Max Andersen closed JBIDE-253. ------------------------------ > Introductions not implemented correctly (class="" vs expr="") > ------------------------------------------------------------- > > Key: JBIDE-253 > URL: http://jira.jboss.com/jira/browse/JBIDE-253 > Project: JBoss Tools > Issue Type: Bug > Components: aop > Affects Versions: 1.5 Release Candidate 1 > Reporter: Rob Stryker > Assigned To: Rob Stryker > Fix For: 1.5 Release Candidate 2 > > > Exceptions were being thrown when expressions were being saved in the xml descriptor under the class attribute instead of the expr attribute. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-255) Provide additional error details on JBoss-IDE configuration page

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-255?page=all ] Max Andersen closed JBIDE-255. ------------------------------ > Provide additional error details on JBoss-IDE configuration page > ---------------------------------------------------------------- > > Key: JBIDE-255 > URL: http://jira.jboss.com/jira/browse/JBIDE-255 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Release Candidate 1 > Environment: Eclipse 3.1.1 with JBoss-IDE 1.5RC1 on Windows XP SP2 > Reporter: Kevin Kane > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 1.5.1 > > > There was a problem creating a new Debug configuration after installing a fresh copy of 4.0.3SP1 with the "Tomcat only" option selected (using the installer jar). Eventually it was presumed that the IDE was looking for a particular file or directory not included by default with the "Tomcat only" installation, since re-installing JBoss with the "all" option made the problem go away. > Although there was a work around, it took some time and effort to find. It would therefore be beneficial if this configuration page could provide more details in the error messages to help developers resolve configuration issues more quickly. For example, in this case it would have been useful to know what file, directory, etc. that it was looking for (or at least a hint about where this information could be found in a log or something). -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-250) JBoss IDE feature registration not working

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-250?page=all ] Max Andersen closed JBIDE-250. ------------------------------ > JBoss IDE feature registration not working > ------------------------------------------ > > Key: JBIDE-250 > URL: http://jira.jboss.com/jira/browse/JBIDE-250 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Release Candidate 1, 1.5 Milestone 3 > Environment: Win32, JDK5.0, Eclipse 3.1.0 > Reporter: brett_s_r > Priority: Optional > > The JBoss IDE package seems to include several Eclipse feature definitions, but these may not be being registered correctly. They do not show up on Help->About->Feature Details. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-248) Create an automated builder that generates xdoclet-build.xml and packaging-build.xml

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-248?page=all ] Max Andersen closed JBIDE-248. ------------------------------ > Create an automated builder that generates xdoclet-build.xml and packaging-build.xml > ------------------------------------------------------------------------------------ > > Key: JBIDE-248 > URL: http://jira.jboss.com/jira/browse/JBIDE-248 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Release Candidate 1 > Reporter: Marshall Culpepper > Assigned To: Marshall Culpepper > Fix For: 1.5 Release Candidate 2 > > > If .xdoclet and .packaging files are committed in version control, the user needs to go into Packaging and XDoclet configuration and hit "Apply" to create the xdoclet-build.xml and packaging-build.xml in order for "Run XDoclet" and "Run Packaging" to work. Creating an automated builder for this process will make this much more seemless. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-247) JSP Compilation support option no longer available in a JBossIDE generated J2EE Project.

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-247?page=all ] Max Andersen closed JBIDE-247. ------------------------------ > JSP Compilation support option no longer available in a JBossIDE generated J2EE Project. > ---------------------------------------------------------------------------------------- > > Key: JBIDE-247 > URL: http://jira.jboss.com/jira/browse/JBIDE-247 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Release Candidate 1 > Environment: JBossIDE 1.5RC1, Eclipse 3.1.1, Win32 (XP Pro) > Reporter: David Webster > Assigned To: Marshall Culpepper > Fix For: 1.5 Release Candidate 2 > > > While the JSP editor seems to be working fine, there are still no options to configure JSP compilation as part of a JBossIDE J2EE project. No way to build or pre-compile JSPs at all from what I can see, much less configure what to do with intermediate servlet .java files, configure specifics about JSP debugging, 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-242) After installing the Web Tools Platform from the Eclipse.org Update Site the graphical xdoclect component ceases to work

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-242?page=all ] Max Andersen closed JBIDE-242. ------------------------------ > After installing the Web Tools Platform from the Eclipse.org Update Site the graphical xdoclect component ceases to work > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-242 > URL: http://jira.jboss.com/jira/browse/JBIDE-242 > Project: JBoss Tools > Issue Type: Bug > Environment: Version: 3.1.0 > Build id: I20050627-1435 > Reporter: Ricardo C?mara > > The Web Tool Platform, when installed from the eclipse.org update site allows the automatic installation of several upgrades and/or used projects that allow it to display graphical XSD diagrams. > Once I installed the Web Tool Platform, JBoss IDE seems unable to display the contents of the .xdoclet file (via the [Right Click on project]->properties->XDoclet Configuration. ) Eclipse displays a dialog box "The currently displayed page contains invalid values" and the error log displays the following stack trace: > java.lang.NoClassDefFoundError: org/eclipse/ui/internal/dialogs/ListContentProvider > at org.jboss.ide.eclipse.xdoclet.run.ui.ConfigurationListViewer.<init>(ConfigurationListViewer.java:90) > at org.jboss.ide.eclipse.xdoclet.run.ui.properties.ConfigurationPropertyPage.createContents(ConfigurationPropertyPage.java:275) > at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232) > at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1371) > at org.eclipse.jface.preference.PreferenceDialog$12.run(PreferenceDialog.java:1138) > at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044) > at org.eclipse.core.runtime.Platform.run(Platform.java:783) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148) > at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1132) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:351) > at org.eclipse.jface.preference.PreferenceDialog$8.selectionChanged(PreferenceDialog.java:638) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763) > at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044) > at org.eclipse.core.runtime.Platform.run(Platform.java:783) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:761) > at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1042) > at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1062) > at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:231) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:226) > at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:392) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3057) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:809) > at org.eclipse.jface.window.Window.open(Window.java:787) > at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:157) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:996) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538) > While I was testing this problem, I also tried to install the 1.5 Milestone 3 and, though I was able to see the XDoclet properties again, I was unable to either view the graphical representation of an XSD or to revert my installation to a stable configuration. -- 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

16 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2007