November 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-495) Changes seam preferences

by Svetlana mukhina (JIRA)

Changes seam preferences ------------------------ Key: JBDS-495 URL: https://jira.jboss.org/jira/browse/JBDS-495 Project: Developer Studio Issue Type: Task Components: Doc - RHDS GSG, Doc - Seam Affects Versions: 2.0.0.beta1 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.cr1 the action is removed and there is changes in the validation in Seam Settings preference page to report empty runtime as a warning rather than an error and not disable finish for such settings. see the linked task -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2718) Archives view broken.

by Aliaksey Nis (JIRA)

Archives view broken. --------------------- Key: JBIDE-2718 URL: https://jira.jboss.org/jira/browse/JBIDE-2718 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.0.0.alpha Environment: WindowsXP SP2 JBoss Tools Version: 3.0.0.Alpha1 Build id: 200809010011-nightly Build date: 01 september 2008 JDK 1.5_08 Reporter: Aliaksey Nis Priority: Blocker EXECUTE: Create Seam project (or JSF). EXECUTE: Open Archives view. EXECUTE: Right click on Archives view > New Archive. FAILURE: In proposal list shown only JAR archive type. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3033) Generate Hibernate/JPA - ManyToOne is more preferable choice than OneToOne

by Vitali Yemialyanchyk (JIRA)

Generate Hibernate/JPA - ManyToOne is more preferable choice than OneToOne -------------------------------------------------------------------------- Key: JBIDE-3033 URL: https://jira.jboss.org/jira/browse/JBIDE-3033 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.beta1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Fix For: 3.0.0.cr1 OneToOne relation is much more constrained than ManyToOne. So if there is no back reference - it is more likely this is ManyToOne relation. In the case of back reference existence - ManyToOne will always be a safe bet, so in this ambiguous case ManyToOne seems is a better choice - but this is thing for discussion - there are some questions here. + may be we should add some comments into sources. -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-2891) Documentation for ESB wizard and deploy

by John Graham (JIRA)

Documentation for ESB wizard and deploy --------------------------------------- Key: JBIDE-2891 URL: https://jira.jboss.org/jira/browse/JBIDE-2891 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Reporter: John Graham Assignee: Denny Xu Fix For: 3.0.0.beta1 Since many of the SOA tools users will be new to the WTP way of dealing with projects (facets) and deployment, we need a brief document running through a sample showing how to create a simple ESB project (based on the Quick Starts/HelloWorld sample) and how to deploy it to the ESB server. -- 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, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-1542) Empty "Driver Class" property for modified connection profiles

by Alexandros Karypidis (JIRA)

Empty "Driver Class" property for modified connection profiles -------------------------------------------------------------- Key: JBIDE-1542 URL: http://jira.jboss.com/jira/browse/JBIDE-1542 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam, seam-gen Affects Versions: 2.0.0.GA Environment: 32-bit Ubuntu Linux 7.10, Eclipse 3.3.1.1 (M20071023-1652), WTP 2.0.1 (v200709110510), DTP 1.5.1 Reporter: Alexandros Karypidis Priority: Minor The Seam Web Project wizard complains that "Driver Class proberty is empty for selected 'x' connection profile" on the Seam Facet page and will not proceed. This occurs for perfectly valid connection profiles, when they have been modified since their creation. To reproduce: 1) Open the Database Development perspective 2) Create a connection profile. Type an incorrect JDBC connection URL. 3) Edit the connection profile. Fix the JDBC connection URL. 4) Start the Seam Web Project wizard and select the connection profile. 5) The wizard does not accept the connection and will not move forward from the "Seam Facet" page. If you skip step 3 and not modify the connection profile, the problem does not occur. -- 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, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2953) Seam wizards no longer starts up with the project field filled based on selection

by Max Rydahl Andersen (JIRA)

Seam wizards no longer starts up with the project field filled based on selection --------------------------------------------------------------------------------- Key: JBIDE-2953 URL: https://jira.jboss.org/jira/browse/JBIDE-2953 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.0.0.beta1, 3.0.0.cr1 The project field was always initialized based on selection in previous versions - seems like that code is never called -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3105) Splash window and JBDS version information not updated via updatesite

by Galder Zamarreno (JIRA)

Splash window and JBDS version information not updated via updatesite --------------------------------------------------------------------- Key: JBIDE-3105 URL: https://jira.jboss.org/jira/browse/JBIDE-3105 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.0.0.cr1 Reporter: Galder Zamarreno Fix For: 3.0.0.GA I downloaded JBDS 2.0.0.Beta1 Build id: N200810201928 but in spite of updating it with latest from trunk, the welcome splash image still says JBDS 1.1.0.GA and "About JBoss Developer Studio" says: JBoss Developer Studio Version: 2.0.0.Beta1 Build id: N200810201928 Build date: 10/20/2008 19:34 It's only when I go into individual plugins that I can see which update version I'm using, i.e: JBossAS Tools Version: 2.0.0.CR1-N200811042358 -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3281) JMX(?) seem to freeze eclipse when a timeout occurs

by Max Rydahl Andersen (JIRA)

JMX(?) seem to freeze eclipse when a timeout occurs --------------------------------------------------- Key: JBIDE-3281 URL: https://jira.jboss.org/jira/browse/JBIDE-3281 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.cr1 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.0.0.cr1 Not sure if this is JMX or our AS Adapter having problems but I got the stacktrace below in my console after having a PDE instance with jbosstools running all night (laptop got suspended) . That normally works fine - but with JMX it seem to fail. java.io.IOException: Cannot bind to URL [rmi://:3000/jmxrmi]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.1.45; nested exception is: java.net.ConnectException: Connection timed out: connect] at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417) at org.jboss.tools.jmx.ui.test.interactive.Activator.start(Activator.java:69) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:444) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:313) at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227) at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1274) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:867) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51) at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:267) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:263) at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:117) at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.ui.internal.Workbench$54.run(Workbench.java:2169) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.1.45; nested exception is: java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:126) at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208) at javax.naming.InitialContext.bind(InitialContext.java:400) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:625) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412) ... 32 more Caused by: java.rmi.ConnectException: Connection refused to host: 192.168.1.45; nested exception is: java.net.ConnectException: Connection timed out: connect at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198) at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:120) ... 36 more Caused by: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Assigned: (JBIDE-534) "javadoc" hover for tagdoc's

by Alexey Kazakov (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-534?page=com.atlassian.jira.plug... ] Alexey Kazakov reassigned JBIDE-534: ------------------------------------ Assignee: Alexey Kazakov > "javadoc" hover for tagdoc's > ---------------------------- > > Key: JBIDE-534 > URL: https://jira.jboss.org/jira/browse/JBIDE-534 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JSF > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: LATER > > > show tagdoc for jsf tags/attributes (similar to property/classes in java) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-2615) CA for #{application}

by Adrian Mitev (JIRA)

CA for #{application} --------------------- Key: JBIDE-2615 URL: https://jira.jboss.org/jira/browse/JBIDE-2615 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Adrian Mitev #{application} was introduced in JSF 1.2 and corresponds to the implicit object named application from JSP. -- 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, 4 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2008