[JBoss JIRA] Created: (JBIDE-1349) Cannot deploy/publish WAR to JBoss AS
by Rob Hasselbaum (JIRA)
Cannot deploy/publish WAR to JBoss AS
-------------------------------------
Key: JBIDE-1349
URL: http://jira.jboss.com/jira/browse/JBIDE-1349
Project: JBoss Tools
Issue Type: Bug
Components: Archives
Affects Versions: 2.0.0.CR1
Environment: Eclipse 3.3.1.1 on openSUSE 10.3
Reporter: Rob Hasselbaum
I'm trying to deploy a WAR to JBoss AS. I created a WAR via the "Project Archives" view and confirmed that it gets created in a subfolder I selected within my Eclipse project. However, when I try to deploy/publush the WAR to a running instance of JBoss AS, I get an error in the event log saying that it failed to copy the file, and in the error details, I can see that the source path is wrong. It's looking for the file in a subfolder under "<eclipse_workspace_dir>/<project_name>". But, in my environment, the project root folder is not located under the workspace folder, and the root folder name is not equal to the project name, so it's trying to copy from a directory that doesn't exist.
I went back to the WAR configuration and tried specifying the explicit path (using the "Filesystem" button instead of the "Workspace" button), but it still doesn't work.
--
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, 11 months
[JBoss JIRA] Created: (JBIDE-1353) Deploy Only runtime/ System copy Server inconsistencies
by Max Andersen (JIRA)
Deploy Only runtime/ System copy Server inconsistencies
-------------------------------------------------------
Key: JBIDE-1353
URL: http://jira.jboss.com/jira/browse/JBIDE-1353
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.CR1
Reporter: Max Andersen
Assigned To: Rob Stryker
Fix For: 2.0.0.GA, 2.0.1
Attachments: jbosstools-diagnostics-20071121222547.zip
New Seam Web Project
Click new runtime - select "Deploy only runtime"
1) why does the "create server" option go away ?
2) click ok - and it is not selectable in the web project wizard?!
Click new server - select "System copy server"
1) what is the relationship betwen the runtime and server here? they have a different name, but same purpose or ?
2) I click ok and continues and after a while I get an NPE (see attached)
--
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, 11 months
[JBoss JIRA] Created: (JBIDE-1358) Collection initialization error
by Mikle Dryakhlenkov (JIRA)
Collection initialization error
-------------------------------
Key: JBIDE-1358
URL: http://jira.jboss.com/jira/browse/JBIDE-1358
Project: JBoss Tools
Issue Type: Bug
Components: Hibernate
Affects Versions: 2.0.0.CR1
Environment: RHDS 1.0.0 CR1
Reporter: Mikle Dryakhlenkov
Assigned To: Max Andersen
Testcase:
EXECUTE: Create test seam project.
EXECUTE: Create hibernate configuration for project with connection to MS SQL Server test DB Northwind.
EXECUTE: Create reverse engineering for tables EmployeeTerritories, Employees, Orders, Territories.
EXECUTE: Open HQL Editor for configuration. Type "from Territories".
ASSERT: Objects "Territories" are present in "Hibernate Query Result" view.
EXECUTE: Select one object in "Hibernate Query Result" view.
ASSERT: Values of fields of this object are displayed in "Properties" view. There is no exception in "Error Log" view on selection objects in "Hibernate Query Result" view.
--
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, 11 months
[JBoss JIRA] Created: (JBIDE-1348) New Seam EAR projects don't include jboss-app.xml, causing classloader confusion for the inexperienced
by Marcus Adair (JIRA)
New Seam EAR projects don't include jboss-app.xml, causing classloader confusion for the inexperienced
------------------------------------------------------------------------------------------------------
Key: JBIDE-1348
URL: http://jira.jboss.com/jira/browse/JBIDE-1348
Project: JBoss Tools
Issue Type: Feature Request
Components: Seam
Affects Versions: 2.0.0.CR1
Reporter: Marcus Adair
When a new Seam EAR project is created with JBoss Tools or RHDS, there is no jboss-app.xml included in the EAR META-INF directory. An inexperienced user then creating and deploying additional projects will be confused to find that both classloader namespace and component namespace conflicts occur.
I think it's fairly well established that these classloader conflicts are a source of particularly disheartening pain for new users to a Java application server platform, whether or not one agrees with a particular implementation. Generating new projects in their own classloader namespace will go a long way toward reducing the bloodletting.
--
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, 11 months