websphere-7

In Websphere 6 ibm-web-bnd.xmi file I have <?xml version="1.0" encoding="UTF-8"?> <webappbnd:WebAppBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:webappbnd="webappbnd.xmi" xmi:id="WebAppBinding_1294064796872" virtualHostName="default_host"> <webapp href="WEB-INF/web.xml#WebApp_ID"/> <resRefBindings xmi:id="ResourceRefBinding_1294083767913" jndiName="jdbc/ABC_DEFG"> <bindingResourceRef href="WEB-INF/web.xml#ResourceRef_1294083767913"/> </resRefBindings> </webappbnd:WebAppBinding> I would like to upgrade to the Websphere 7 and use the default ibm-web-bnd.XML file, but I am

I am trying to consume a RESTful service from url https://someurl.com . I have added the following properties in my code: Security.setProperty("ssl.SocketFactory.provider", "com.ibm.jsse2.SSLSocketFactoryImpl"); Security.setProperty("ssl.ServerSocketFactory.provider", "com.ibm.jsse2.SSLServerSocketFactoryImpl"); Security.setProperty("javax.net.ssl.trustStore", "cacerts.jks"); Security.setProperty("javax.net.ssl.keyStore", "keystore.jks"); Security.setProperty("javax.net.ssl.keyStoreType", "pkcs12"); Security.setProperty("javax.net.ssl.trustStoreType", "JKS"); The configuration changes that I

I am deploying one application Apache CXF-2.7.5 with neethi-3.0.2 in websphere 7. I am getting below error. My Application is spring driven. When I degraded Apache CXF to apache CXF-2.3.5. Application successfully deployed. The same is working perfectly in Tomcat7. I am able to reproduce this issue on Tomcat by adding (or overriding) a dependency of neethi.jar (with an older version --> 2.5.x) in pom.xml file. Note: Apache CXF 2.7.5 comes with a latest version of neethi.jar (3.0.2), hence not causing issue on Tomcat7. Is Web sphere picking up an older version of neethi.jar Stack Trace is below

I want to not use the built in Websphere 7 jpa plugin, instead use an application WEB-INF/lib/open-jpa 2 and a proprietary persistence provider. I cannot install the OSGI and JPA 2 feature pack for Websphere. Originally, I was getting a sax parse error simply trying to load the persistence.xml (version="2" not supported). The error was thrown by a class in open-jpa 1.2.3. When I run websphere/appserver/bin/wsjpaversion.bat, the open-jpa 1.2.3 jar is displayed. By default it overrides the open-jpa 2 jar in the app. I created a shared library containing the open-jpa 2 jar with this config option

Can JSF 2.0 be used with WebSphere Application Server version 7.x? If so, how? RDean The WebSphere Infocenter indicates that the right way to change to an alternative JSF implementation is to create a WebSphere Shared Library with the isolated classloader option enabled. Any modules that need JSF 2 would be associated with the new shared library, and then the application would start with JSF 2 instead of JSF 1.2. It is also necessary to have fix pack 7.0.0.19 or later installed . Websphere ships with JSF 1.2.something and it loads that by default. To use a different JSF library (or any other

I wrote 2 webservices, one with Jax-WS and one with Jax-RPC. They just return a String. I stress-tested both with jMeter and, strangely, thereby Jax-RPC was a bit faster. When do I really profit of Jax-WS in aspects of performance (response time, CPU-time, heap)? How can I proof it? thanks for your time! =) Pascal Thivent You didn't mention anything about the implementations you're using so it's hard to say anything about them :) I don't know if your benchmark is representative of anything, I'm not sure it allows to make any valid conclusion. JAX-WS is supposed to perform better in general