October 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBIDE-180) New EJB 2.1 Deployment Descriptor creates 2.0 version

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-180?page=all ] Rob Stryker closed JBIDE-180. ----------------------------- Resolution: Done JIRA cleanup: Closing old bugs > New EJB 2.1 Deployment Descriptor creates 2.0 version > ----------------------------------------------------- > > Key: JBIDE-180 > URL: http://jira.jboss.com/jira/browse/JBIDE-180 > Project: JBoss Tools > Issue Type: Bug > Environment: Win 2000, Eclipse 3.0.2, Jboss IDE v 1.4.1.e30, JDK 1.4.2_08-b03 > Reporter: MrSlinkyman > > Using the Jboss IDE tools I created a J2EE 1.4 Project. Once the project was created I created a new "EJB 2.1 Deployment Descriptor". > The following is the file that was created and what is also generated if the "EJB 2.0 Deployment Descriptor" is selected. > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE ejb-jar PUBLIC > "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" > "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> > <ejb-jar> > <enterprise-beans> > <session> > <ejb-name></ejb-name> > <ejb-class></ejb-class> > <session-type></session-type> > <transaction-type></transaction-type> > </session> > <entity> > <ejb-name></ejb-name> > <ejb-class></ejb-class> > <persistence-type></persistence-type> > <prim-key-class></prim-key-class> > <reentrant></reentrant> > </entity> > <message-driven> > <ejb-name></ejb-name> > <ejb-class></ejb-class> > <transaction-type></transaction-type> > </message-driven> > </enterprise-beans> > </ejb-jar> -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-104) Internal error in run packaging

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-104?page=all ] Rob Stryker closed JBIDE-104. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > Internal error in run packaging > ------------------------------- > > Key: JBIDE-104 > URL: http://jira.jboss.com/jira/browse/JBIDE-104 > Project: JBoss Tools > Issue Type: Bug > Environment: Eclipse 3.1 M4 > Reporter: Martin Lopez > > An internal error popup appears when I click on "Run Packaging". But the jars are created successfully. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-211) Renaming/deleting the default server configuration causes looping

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-211?page=all ] Rob Stryker closed JBIDE-211. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs. JBoss IDE 1.5 no longer supported > Renaming/deleting the default server configuration causes looping > ----------------------------------------------------------------- > > Key: JBIDE-211 > URL: http://jira.jboss.com/jira/browse/JBIDE-211 > Project: JBoss Tools > Issue Type: Bug > Environment: Eclipse3.1 > WindowsXPSP2 > Reporter: edikus > > Create a server configuration within the Server Navigator. > Go to Preferences | JBoss-IDE | Launcher and select the new config as the default server. > Go back to the server navigator and edit the name of the config or delete. > You get an Error dialog: > org.eclipse.debug.core.DebugException Launch configuration-<server name> at <workspace>\.metadata\.plugins\org.eclipse.debug does not exist. > You cannot dismiss the dialog -- it reappears about 16 times. If you do this procedure more than once, it appears the the number of times starts to multiply by 2's and you eventually have to kill the Eclipse process. You cannot make any edits in the configuration without the dialog reappearing. You have to go back to the Preferences page, although at that point you don't have to do anything else, because the IDE will clear the value. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-249) Run Server in Profile Mode

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-249?page=all ] Rob Stryker updated JBIDE-249: ------------------------------ Summary: Run Server in Profile Mode (was: JBoss Profiler in JBoss IDE) Component/s: JBossAS Affects Version/s: 2.0.0.Beta4 (was: 1.5 Release Candidate 1) > Run Server in Profile Mode > -------------------------- > > Key: JBIDE-249 > URL: http://jira.jboss.com/jira/browse/JBIDE-249 > Project: JBoss Tools > Issue Type: Feature Request > Components: JBossAS > Affects Versions: 2.0.0.Beta4 > Reporter: Max Andersen > Assigned To: Rob Stryker > > Ideas for JBoss Profiler integration while being in Brazil ;) > A. Allow configuration of JBoss Profiler from JBossIDE > - add a "Profiler" launcher for JBoss proffiler which configure jboss profiler via the javaopts settings > - will add a the dll/so file to the launcher > (do not need attempt to integrate the .sar/viewer stuff) > Aa Allow to launch jboss witht the viewer to read result. > B. Add views based on the jboss profiler model -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBIDE-249) JBoss Profiler in JBoss IDE

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-249?page=all ] Rob Stryker reassigned JBIDE-249: --------------------------------- Assignee: Rob Stryker > JBoss Profiler in JBoss IDE > --------------------------- > > Key: JBIDE-249 > URL: http://jira.jboss.com/jira/browse/JBIDE-249 > Project: JBoss Tools > Issue Type: Feature Request > Components: JBossAS > Affects Versions: 2.0.0.Beta4 > Reporter: Max Andersen > Assigned To: Rob Stryker > > Ideas for JBoss Profiler integration while being in Brazil ;) > A. Allow configuration of JBoss Profiler from JBossIDE > - add a "Profiler" launcher for JBoss proffiler which configure jboss profiler via the javaopts settings > - will add a the dll/so file to the launcher > (do not need attempt to integrate the .sar/viewer stuff) > Aa Allow to launch jboss witht the viewer to read result. > B. Add views based on the jboss profiler model -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-120) generate wrong jbosscmp-jdbc.xml in JBossIDE-1.4.1

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-120?page=all ] Rob Stryker closed JBIDE-120. ----------------------------- Resolution: Out of Date JBossIDE 1.4 no longer supported > generate wrong jbosscmp-jdbc.xml in JBossIDE-1.4.1 > --------------------------------------------------- > > Key: JBIDE-120 > URL: http://jira.jboss.com/jira/browse/JBIDE-120 > Project: JBoss Tools > Issue Type: Bug > Reporter: Klaus Schultz > Priority: Minor > > using the JBossIDE JBossIDE-1.4.1-e30.zip and JBoss Server 3.2.3, I got the following error though I defined a correct CMR named "Positionen" > "org.jboss.deployment.DeploymentException: Atleast one role of a foreign-key mapped relationship must have key fields (or <primkey-field> is missing from ejb-jar.xml): ejb-relation-name=hatPositionen" > The generated ejb-jar.xml is correct, but the generated jbosscmp-jdbc.xml is wrong: > <relationships> > <ejb-relation> > <ejb-relation-name>Positionen</ejb-relation-name> > <foreign-key-mapping/> > <ejb-relationship-role> > <ejb-relationship-role-name>pos</ejb-relationship-role-name> > <key-fields/> > </ejb-relationship-role> > <ejb-relationship-role> > <ejb-relationship-role-name>Bestellung</ejb-relationship-role-name> > <key-fields/> > </ejb-relationship-role> > </ejb-relation> > <ejb-relation> > The solution is very simple: deleting jbosscmp-jdbc.xml ! All informations for CMP/CMR are in the ejb-jar.xml. > So I don't know, whether there are cases in which jbosscmp-jdbc.xml remains necessary, but in my case it would be better not to generate it at all. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-241) JSP template ad /n/ after title cloure tag.

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-241?page=all ] Rob Stryker closed JBIDE-241. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs JSP contributed by WTP now > JSP template ad /n/ after title cloure tag. > ------------------------------------------- > > Key: JBIDE-241 > URL: http://jira.jboss.com/jira/browse/JBIDE-241 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 2, 1.5 Milestone 3 > Environment: w2k, jdk15 > Reporter: Cedric Simon > Priority: Trivial > > When creating new JSP page, a code '/n/' sticks to the </title> tag, and s shown on page. > I did not found how to modify the JSP template to remove this. -- 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, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-242?page=all ] Rob Stryker resolved JBIDE-242. ------------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-215) Installing JBoss IDE 1.5M2 breaks QuickFix

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-215?page=all ] Rob Stryker resolved JBIDE-215. ------------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > Installing JBoss IDE 1.5M2 breaks QuickFix > ------------------------------------------ > > Key: JBIDE-215 > URL: http://jira.jboss.com/jira/browse/JBIDE-215 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 2 > Environment: Windows Professional XP SP2 > Sun Java SE 1.5.0_04 > JBoss 4.0.3RC1 > Reporter: Mike Feldmeier > Attachments: org-jboss-ide-eclipse-jdt-aop-core.jar, org-jboss-ide-eclipse-jdt-aop-ui.jar > > > After installing JBoss IDE 1.5M2, QuickFix by clicking on the margin icon for class lookups no longer function. The same is true for the QuickFix option on the context menu. > Manually typing in the package name of the class in question resolves the error. > Deleting all JBoss IDE files returns QuickFix to operational status. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-122) Using 'User Libraries' in JBossIDE Packaging tool...

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-122?page=all ] Rob Stryker updated JBIDE-122: ------------------------------ Component/s: Archives > Using 'User Libraries' in JBossIDE Packaging tool... > ---------------------------------------------------- > > Key: JBIDE-122 > URL: http://jira.jboss.com/jira/browse/JBIDE-122 > Project: JBoss Tools > Issue Type: Feature Request > Components: Archives > Environment: Eclipse 3.0.1 M5a > Reporter: Pavel Krupets > Priority: Minor > > Hello, > It would be nice if I could add 'User Libraries' references into project packaging configuration, so I could change libraries location and content in one place. > With regards, > Pavel Krupets -- 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, 9 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 October 2007