[JBoss JIRA] Created: (JBDS-1795) Runtime Detection Dialog during first start gets over modal dialog with request to let usage reporting.
by Denis Golovin (JIRA)
Runtime Detection Dialog during first start gets over modal dialog with request to let usage reporting.
-------------------------------------------------------------------------------------------------------
Key: JBDS-1795
URL: https://issues.jboss.org/browse/JBDS-1795
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
Affects Versions: 5.0.0.M3
Reporter: Denis Golovin
Fix For: 5.0.0.M3
Request to let usage reporting modal dialog is opened first and then it is covered by bigger Runtime Detection Dilaog. Usage dialog is modal and nothing can be pressed and changed in Runtime Detection dialog. Sometimes I even didn't notice usage dialog and it was confusing because runtime detection dialog just didn't respond to mouse events.
There should be a way to show such dialogs one by one and not all at once blocking each other.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-8289) Generated Seam portled does not work on EPP 4.3
by Dominik Pospisil (JIRA)
Generated Seam portled does not work on EPP 4.3
-----------------------------------------------
Key: JBIDE-8289
URL: https://issues.jboss.org/browse/JBIDE-8289
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal/GateIn
Affects Versions: 3.2.0.CR1
Reporter: Dominik Pospisil
Assignee: Snjezana Peco
Fix For: 3.2.0.CR2 (tentative)
Generated Seam portled does not work on EPP 4.3. This is due to incompatibility of Potletbridge 2.0.Final and Seam 2.0.2.FP in EPP 4.3. See PBR-186.
Steps to reproduce:
1) Create Seam Project on EPP 4.3 with included Seam 2.0 and Seam portlet facet
2) Add Seam portlet to the project
3) Deploy on EPP 4.3
Snjezana, where are portledbridge libraries generated by the wizard comming from?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-7293) Dynamic Web Project isn't created properly when JBoss Portlet Tool installed
by Michael Tanz (JIRA)
Dynamic Web Project isn't created properly when JBoss Portlet Tool installed
----------------------------------------------------------------------------
Key: JBIDE-7293
URL: https://jira.jboss.org/browse/JBIDE-7293
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.M2, 3.1.0.GA
Environment: Windows XP 32bit
Reporter: Michael Tanz
When I run the wizard for creating a "Dynamic Web Project" when JBoss Portlet Tool is installed and I hit "Finish" a project is created but the dialog doesn't disappear. When I then hit "Finish" a second time I get an error message stating:
---------------------------------------------------------------------
One or more constraints have not been satisfied.
Cannot install project facet Java 6.0. Some version of this project facet is already installed.
---------------------------------------------------------------------
When I then click "OK" the dialog disappears. Nevertheless the created project only contains a "src" and "build" folder. "WebContent" is missing.
I could reproduce this issue on several machines, each with a clean Eclipse (Galileo and/or Helios) and the latest stable release of JBoss Tools in the Galileo case and the latest development milestone in the Helios case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-8656) Split SOA components out of JBoss Tools aggregate site; create 2nd aggregate for SOA Tooling
by Nick Boldt (JIRA)
Split SOA components out of JBoss Tools aggregate site; create 2nd aggregate for SOA Tooling
--------------------------------------------------------------------------------------------
Key: JBIDE-8656
URL: https://issues.jboss.org/browse/JBIDE-8656
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm, drools, esb, jbpm, modeshape, smooks, teiid
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
The following components should be aggregated in a NEW aggregate build and removed from the existing one:
Drools 5.2
Flow/jBPM
BPMN2 (there is no JIRA component for this yet)
BPEL (moving to Eclipse.org)
Teiid
Modeshape
ESB
Smooks
1. Fix ~/trunk/build/aggregate/ - remove components from site.xml
2. Create new ~/trunk/build/aggregate-soa/ - add components to site.xml
3. Create new http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.3... (or similar)
4. get new www.jboss.org/soatools/ site, publish there instead of www.jboss.org/tools/, and cross link project pages.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBDS-1538) ws user guide issues
by Lukas Jungmann (JIRA)
ws user guide issues
--------------------
Key: JBDS-1538
URL: https://issues.jboss.org/browse/JBDS-1538
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Doc - JBossWS
Affects Versions: 4.0.0.CR2
Reporter: Lukas Jungmann
JBoss Web Services User Guide
chapter 1: JBossWS Runtime Overview
-it is not true that JBossWS implements JAX-WS and JAX-RS - JBossWS implements JAX-WS and JAX-RPC, for JAX-RS there's RESTEasy
-would be good if other resources would list http://www.jboss.org/jbossws and perhaps also http://community.jboss.org/wiki/JBossWS-FAQ
chapter3:
3.3. Creating a Web Service from a WSDL document using JBossWS runtime
-there's a note about about simple ws wizard which does not make sense in from wsdl context, therefore this note should be removed
-no description of items from the screenshot - compare with sec 3.4 to see what I mean
3.4.
-the description of the stages of Web service development should be moved to sec. 3.3 where they can be seen on the screenshot for the first time; or do copy paste of the particular paragraph or provide a link between those two occurrences
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBDS-1829) CLONE - Navigation between links on welcome screen should be uninterrupted
by Denis Golovin (JIRA)
CLONE - Navigation between links on welcome screen should be uninterrupted
--------------------------------------------------------------------------
Key: JBDS-1829
URL: https://issues.jboss.org/browse/JBDS-1829
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ui/branding
Reporter: Lukas Jungmann
Assignee: Victor Rubezhny
Priority: Minor
Fix For: 5.0.0.M2
-shrink the JBDS window a bit and click on links on the welcome screen
I can see two issues here:
-the loading of the link should be uninterrupted, as of now one can see white/empty page between clicking on the link and displaying the contents of the link
-the white strip (the one containing the RH and JBoss logos) does not have fixed position at the bottom of the window, ie if one needs to scroll, he may not be able to follow link hidden by the strip
video from ubuntu 10.10 is attached
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-9360) NoSuchMethodError: org.jboss.logging.Logger.tracef
by Juergen Zimmermann (JIRA)
NoSuchMethodError: org.jboss.logging.Logger.tracef
--------------------------------------------------
Key: JBIDE-9360
URL: https://issues.jboss.org/browse/JBIDE-9360
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Max Rydahl Andersen
We are migrating from JBossAS 6 to 7, and also switched to JBoss Logging (from SLF4J). When submitting a JPA query there is a stacktrace (see below). The Eclipse project which provides the entity classes is a "Utility project" and its classpath contains %JBOSS_LOGGING%\modules\org\jboss\logging\main\jboss-logging-3.0.0.GA.jar.
I'll attach 2 screenshots:
* the error window
* the window showing the classpath (The user library "JBoss HSKA" contains jboss-logging-...jar)
The stacktrace:
java.lang.RuntimeException: java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;Ljava/lang/Object;)V
at org.hibernate.ejb.event.BeanCallback.invoke(BeanCallback.java:45)
at org.hibernate.ejb.event.EntityCallbackHandler.callback(EntityCallbackHandler.java:94)
at org.hibernate.ejb.event.EntityCallbackHandler.postLoad(EntityCallbackHandler.java:87)
at org.hibernate.ejb.event.EJB3PostLoadEventListener.onPostLoad(EJB3PostLoadEventListener.java:47)
at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:234)
at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:898)
at org.hibernate.loader.Loader.doQuery(Loader.java:773)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270)
at org.hibernate.loader.Loader.doList(Loader.java:2449)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2192)
at org.hibernate.loader.Loader.list(Loader.java:2187)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:452)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1258)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
at org.hibernate.console.HQLQueryPage.getList(HQLQueryPage.java:50)
at org.hibernate.eclipse.console.views.QueryPageViewer$ContentProviderImpl.getElements(QueryPageViewer.java:120)
at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1010)
at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:703)
at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1087)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917)
at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1067)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:701)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636)
at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690)
at org.hibernate.eclipse.console.views.QueryPageViewer.createTable(QueryPageViewer.java:225)
at org.hibernate.eclipse.console.views.QueryPageViewer.createControl(QueryPageViewer.java:203)
at org.hibernate.eclipse.console.views.QueryPageViewer.<init>(QueryPageViewer.java:160)
at org.hibernate.eclipse.console.views.QueryPageTabView.rebuild(QueryPageTabView.java:109)
at org.hibernate.eclipse.console.views.QueryPageTabView$1.contentsChanged(QueryPageTabView.java:75)
at org.hibernate.eclipse.console.views.QueryPageTabView$1.intervalAdded(QueryPageTabView.java:85)
at javax.swing.AbstractListModel.fireIntervalAdded(AbstractListModel.java:130)
at org.hibernate.console.QueryPageModel.add(QueryPageModel.java:67)
at org.hibernate.console.KnownConfigurations$1.queryPageCreated(KnownConfigurations.java:88)
at org.hibernate.console.ConsoleConfiguration.fireQueryPageCreated(ConsoleConfiguration.java:312)
at org.hibernate.console.ConsoleConfiguration.access$4(ConsoleConfiguration.java:310)
at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:272)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72)
at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:265)
at org.hibernate.eclipse.hqleditor.HQLEditor.executeQuery(HQLEditor.java:449)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:84)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;Ljava/lang/Object;)V
at de.swe.kundenverwaltung.domain.Privatkunde.postLoad(Privatkunde.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.hibernate.ejb.event.BeanCallback.invoke(BeanCallback.java:37)
... 78 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBIDE-8529) Duplicate EJB wizards
by Libor Zoubek (JIRA)
Duplicate EJB wizards
---------------------
Key: JBIDE-8529
URL: https://issues.jboss.org/browse/JBIDE-8529
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: ejb3
Affects Versions: 3.2.0.Final
Reporter: Libor Zoubek
There are dupliate wizards for creating EJB3 Message-driven bean and EJB3 Session Bean.
For creating Message Driven bean there is:
* EJB/EJB3 Message Driven Bean
* EJB/Message-Driven Bean (EJB3.x)
For creating Session bean theere is:
* EJB/EJB3 Session Bean
* EJB/Session Bean (EJB 3.x)
Both variants create classes, the 2nd variant of both is quite better (generates additional annotations)
Those duplicates should be removed if possible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months