websphere-8

Should I choose == or eq for comparing string in EL?

为君一笑 提交于 2019-12-18 10:47:12
问题 == and eq give the same result using EL to do my string comparison tests: <c:if test="${person.sokande_i == 'endast_usa'}">Endast USA</c:if> <c:if test="${person.sokande_i == 'alla'}">Alla länder</c:if> <c:if test="${person.sokande_i == 'alla_utom_usa'}">Alla utom USA</c:if> Should I use eq instead? Is == for integers only? But it works also for strings. AFAIK == test whether hashCodes are equal and eq means "meaningfully different". Another question says == and eq do the same thing. Is there

How to check (replace) the MyFaces version used by Websphere 8.5

烂漫一生 提交于 2019-12-18 07:13:05
问题 After upgrading to WebSphere 8.5 I've experienced some incompatibilites in my JSF application. It is possible that they were caused by uncanonical use of JSF components, but I wanted to simply check what version is used According to that document: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Fae%2Frovr_specs.html WebSphere 8.5 uses Apache MyFaces 2.0.x (without specifying the version). I was searching for myfaces*.jar withing WebSphere

Disable chunked transfer-encoding for JAX-WS Client in WebSphere Application Server 8.5

会有一股神秘感。 提交于 2019-12-14 03:58:15
问题 In a web application that runs on top of IBM WebSphere Application Server (WAS) V8.5.5.11, there is a JAX-WS client piece (using WAS built-in JAX-WS component) that calls an external web service. For any web service call with an HTTP body larger than 32 KB, WAS will use chunked transfer-encoding. Unfortunately, the external web service cannot handle chunked transfer encoding, and will error out. How do I disable chunked transfer-encoding within WAS JAX-WS client code? 回答1: You need to create

Unable to lookup if SSL is enabled in Websphere 8.5

此生再无相见时 提交于 2019-12-13 14:12:47
问题 I have written a simple ejb thin client to look up the bean deployed in IBM WebSphere 8.5. When SSL was not enabled on the server I was successfully able to lookup the bean , but as soon as I enabled the SSL , I started getting the below mentioned exception. This is how I enabled the security thru admin console : Exception: javax.naming.NamingException: Error getting WsnNameService properties [Root exception is org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: IBM minor

Error during EJB3 call

本秂侑毒 提交于 2019-12-13 08:36:05
问题 I have written a simple Ejb program, by looking from http://mrbool.com/how-to-use-enterprise-java-beans-3-x-based-application-with-websphere-8-5-application-server/28063 The files are package ejb3.test; import javax.ejb.Remote; /** * TODO: Document me! * * @author aprashanth * */ @Remote public interface ITestEJBRemoteInterface { public boolean checkNames(String fsName); } Implementation Class: package ejb3.test; /** * TODO: Document me! * * @author aprashanth * */ import java.util.Arrays;

Classcast exception during Rendering while using AXIOM in WAS 8.5.5.2

时间秒杀一切 提交于 2019-12-13 07:25:11
问题 I am working on application deployed in WAS 8.5.5.2. I am getting the below error while rendering TIF image. I have kept Axiom 1.2.14 which is latest in classpath and restarted the server. Got a classcast exception. Then, i have searched the entire WAS for any internal builtin jars and found few instances under org.apache.axis2 jar (builtin jar in WAS runtimes folder). SO i have removed my jar from the classpath. Still i am getting the same error. Any clues will really helpful .. Unable to

Passed argument to method inside composite component does not work on MyFaces

霸气de小男生 提交于 2019-12-13 04:36:40
问题 I have successfully able to pass in argument to method inside composite component using this technique from BalusC (Pass Argument to a composite-component action attribute), however this seems to work on Mojarra, but not on MyFaces 2.0.4-2.0.5 (packaged inside Websphere 8.5 + OpenWebBeans) . I post my code below This is my cc <cc:interface> <cc:attribute name="value" /> <cc:attribute name="bean" /> <cc:attribute name="myAction" /> <cc:attribute name="property" /> </cc:interface> <cc

Update ear in web sphere from command line

旧巷老猫 提交于 2019-12-12 14:24:25
问题 I have developed an java ear that i deploy from my local eclipse to my local websphere 8.5 by using the publish button in eclipse. When I try to deploy my ear from command line I get an error after I try to access the webpage. I update my ear from common line like this: ${was.dir}/profiles/${was.profile}/bin/wsadmin.sh -lang jython -username ${was.username} -password ${was.password} -c AdminApplication.updateApplicationUsingDefaultMerge('${was.app.name}', '${build.dir}/${ear.name}') The

IBM Worklight 6.0 - “project not initialized” error

不想你离开。 提交于 2019-12-12 02:50:02
问题 The following is my setup: WebSphere Application Server v8.0 express Edition IBM DB2 10.1 Server Edition IBM Worklight Server Consumer Edition v6.0 Worklight Studio v6.0 Consumer edition Eclipse plug-in JDK 1.7 To perform installation task i followed the IBM Worklight v6.0.0 infocenter "Installing & Configuring" section. After Deploying app on the Application Server when i am accessing app using localhost:9080/Hello/console it shows the error of "Worklight Project not initialized". Thanks,

Session is not persistence between adapter and java class (servlet) in mobilefirst server/websphere application server

断了今生、忘了曾经 提交于 2019-12-12 02:44:52
问题 I am working on mobilefirst 7.1 application which is deployed on websphere application server - network deployment.Earlier version this application is working on worklight 6.1 and everything is working fine. As per code, we are setting an attribute in session within adapter and try to access it from java class (servlet) which is part of the application and exposed as servlet using configuration in web.xml file. My worklight properties configuration : mfp.session.independent=false mfp