Websphere 类加载器委托模式
我们使用带有默认类加载器委托模式的 WebSphere 6.1 应用程序服务器，即 PARENT-FIRST。 我们考虑将其更改为 PARENT-LAST 以便能够选择我们的 jsf 实现或 Web 服务堆栈。
由于 PARENT-FIRST 是默认设置，我想知道有多少人切换到 PARENT-LAST，切换的原因是什么，以及切换后您的生活是否变得更好:)
我们有很多应用程序正在生产中，所以我不能只是切换看看会发生什么，如果我们这样做，我们将进行大量测试，因此如果您已切换到“父级最后”，我希望获得一些反馈。
谢谢
We are using WebSphere 6.1 application server with default classloader delegation mode i.e. PARENT-FIRST. We think about changing it to PARENT-LAST to be able to choose our jsf implementation or our webservices stack.
As PARENT-FIRST is the default I wonder how many people switched to PARENT-LAST, and what was the reason to switch, and if your life became better since you switched :)
We have a lot of applications in production so I cannot just switch to see what happens, if we do it we will have a lot of testing so I’d like to have to some feedback if you have switched to PARENT-LAST.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在我分配的项目中，我们的大多数应用程序实际上都切换到了 PARENT-LAST。 其原因通常是特定于应用程序的某些实现，或者需要 Websphere 也使用的特定于应用程序的属性包（例如，覆盖公共日志记录的 Websphere 设置）。
如果切换后出现问题，通常是因为突然开始使用的应用程序设置有些错误（而在切换之前它被 Websphere 的资源覆盖）。
On projects that I'm assigned to, we actually do switching to PARENT-LAST for most of our applications. The reason for that is usually an app-specific implementation of something, or a need for app-specific property bundle that Websphere uses too (overriding the Websphere setup of commons-logging, for example).
If something breaks after the switch, it is usually because of somewhat wrong setup of the application that suddently starts to be used (while before the switch it was overriden by Websphere's resources).
Portlet 应用程序（部署在WebSphere Portal Server 上）总是最后将其配置切换到父级。 根据我的经验，最后切换到父级总是更好，特别是如果您使用公共日志记录。 这是因为 WebSphere 在它自己的类加载器中包含了大量的东西，这些类加载器通常与您想要使用的版本/配置不同。
如果您正在这样做，我建议您编写应用程序部署的脚本，因为它可能是您在进行部署时错过的事情之一。
Portlet applications (deployed on WebSphere Portal Server) always switch their configuration to parent last. In my experience it is always better to switch to parent last, especially if you are using commons logging. This is because WebSphere includes a truck load of stuff in its own classloaders which are often a different versions/configurations to the one that you want to use.
If you are doing it, I would recommend that you script up the deployment of the application because it can be one of those things that are missed when you do a deployment.