This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Setup required for JAX-WS webservices on Tomcat 6 w/ JDK 6 | ||
---|---|---|---|
Product: | installer | Reporter: | Quy Nguyen <quynguyen> |
Component: | Code | Assignee: | issues@installer <issues> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | blocker | CC: | romanmostyka |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 108523 |
Description
Quy Nguyen
2007-07-16 18:31:52 UTC
Quy, where endorsed direcotry should be created? in <tomcat-install-dir>/lib or <javahome>/lib? If it is <javahome>\lib\endorsed then what should be done if the user don`t have enought permissions to write to java directory? What should we do if only tomcat is installed (and NetBeans is not)? What should we do if we install several netbeans builds? should we place these files each time? Is there any side effects that causes placement of these files to endorsed directory? I can definitely say that now no such a logic is performed during glassfish installation. Glassfish includes the jax-ws 2.1 API jars in its endorsed library folder, so this issue does not occur on that app server. We would expect that the jars would go into <tomcat-install-dir>/lib if tomcat is installed with NetBeans to improve the out-of-the-box experience. The only side effect of including these jars in the endorsed folder is that the JAX-WS 2.0 library will no longer be available. Considering that glassfish does the same thing, I don't believe that this would be a problem. |