[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, 5 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, 5 months
[JBoss JIRA] Created: (JBIDE-2760) Replace JMX in as.core and as.ui with more full-featured plugin
by Rob Stryker (JIRA)
Replace JMX in as.core and as.ui with more full-featured plugin
---------------------------------------------------------------
Key: JBIDE-2760
URL: https://jira.jboss.org/jira/browse/JBIDE-2760
Project: Tools (JBoss Tools)
Issue Type: Task
Reporter: Rob Stryker
Things to do:
1) Get Permission from owner of jmx-eclipse
2) Apply patches attached here to as.core and as.ui
3) Add all new plugins to as.feature
4) ensure build.properties and project versions etc are set to jboss standards
5) ensure build system accounts for new plugins
Things to verify in testing:
0) Server can still start and stop successfully ******
1) Event Log still works well and gives good information for starting / stopping
2) "More Information" dialog still shows up when used against a secure server
3) A new connection can be added / removed
4) Server connections can *not* be added or removed, but are added or removed automatically when created or destroyed
5) A Server's connection in the JMX view recognizes when the server starts and can be expanded
6) A server's connection in the JMX view recognizes when the server is stopped and is no longer expandable
7) All important exceptions are logged
--
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, 5 months