Bug 87123 - Deployment of application utilizing DB failed after changing deployment server
Deployment of application utilizing DB failed after changing deployment server
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: Infrastructure
5.x
All All
: P2 (vote)
: TBD
Assigned To: Petr Hejl
issues@serverplugins
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-13 16:35 UTC by Marco Walther
Modified: 2007-08-30 17:36 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments
Server log from the Sun bug. (1.22 MB, text/plain)
2006-10-16 17:08 UTC, Marco Walther
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Walther 2006-10-13 16:35:10 UTC
Filed as Sun Bug 6481775.

NB 5.5rc1+
VWP

That's a known limitation which should be addressed in the release.

1. Create project for Tomcat 5.0.
2. Add Table component.
3. Bind it to DB (I bind ).
4. Deploy it to Tomcat 5.0. Everything is fine.
5. Change Server in Properties of the project to JBoss.
6. Deploy project to JBoss.

Result: Message "HTTP Status 404" appear in browser and there is no deployed 
project in JBoss->Applications->Web Applications.
JBoss server log in attach.
Comment 1 Petr Jiricka 2006-10-16 12:12:31 UTC
Marco, I don't see he log file. Can you please attach it? Thanks.
Comment 2 Marco Walther 2006-10-16 17:08:55 UTC
Created attachment 35237 [details]
Server log from the Sun bug.
Comment 3 Sherold Dev 2006-10-17 10:12:56 UTC
If I remember correctly, it was decided not to support actions like "Use
database" after switching the server - datasources missing on the new target
server are not regenerated. Since this was intentional changing the issue type
to enhancement.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo