Ankit Thakkar

Ranch Hand
+ Follow
since Apr 29, 2005
Ankit likes ...
Android Mac PPC Java
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Ankit Thakkar

Dear All,

We have a requirement in which we need to change the namespace in coming Soap Message and set it to a different process-able namespace. We are able to change it using a Handler class, It transforms the message to desired soap message but when it is hitting the actual service it’s still referring to incoming namespace only and not the new Namespace which we have replaced in handler.

In SoapEnvelope we are trying to override the incoming namespace-prefix with common namespace URI.
se.addNamespaceDeclaration(prefix, commonNS);

We are using a IBM Websphere. We are suspecting the web services framework jars might be ignoring the modified namespace as this may not be permissible or any other reason? But then there is an exposed method to modify the name space and we are able to do it using that method only. So not sure why the old namespace is retained. Just to add, we tried to modify the SOAP body and added additional element in the handler, the web service is processing those elements fine, but only for namespace it’s not taking the changed one.

Did anyone face similar issues? Any clue if we can manipulate the incoming namespaces in the input Soap Request? Any pointers will be appreciated.

Thanks,
12 years ago
Hi All,
Can anyone please help me, provide thoughts or share some useful links? I am stuck up to decide which approach should I opt to lookup EJB.

Thanks,
Ankit
Hi All,
I am trying to lookup local EJB reference in Websphere.

I was trying to lookup using JNDI i.e. /ejb/testEJB and it always returned remote EJB reference. I came to know that using jndi local:ejb/ejb/testEJB, local EJB reference can be looked up. I tried and it's working in websphere.

However, I am still not able to identify difference between java:comp/env/, local:ejb/ and normal JNDI (without any prefix). Which one should be used? Can anyone please help me, share some links or thoughts on the same?

Thanks,
Hi Kajal,

By looking at you code, looks like from employee table you fetch employee data and seach attendance records in attendance table. I would recommend to create join query to get data from employee, attendance tables in single db call. Also you should use "?" when you have PreparedStatement.

for your query, try after changing query as below
"select att_status from attendance where e_id="+employeeId;

Thanks,
12 years ago
JSF
Hi Shruti,

You can change transaction lifetime timeout using Websphere Admin console (Application servers > server1 > Transaction Service).

If you set this timeout to 0, the timeout does not apply and the value of the maximum transaction timeout is used instead.

Data type Integer
Units Seconds
Default 120
Range 0 to 2 147 483 647

Thanks,
12 years ago
Hi Patrick,

could you please provide more info on your suggestion? We have the smililar requirement to load balance RMI transactions and really stuck up with this part.

Thanks,
12 years ago
Hey thanks, it really helped me
12 years ago
JSF
Anyone having any idea please help us, we really stuck up with RMI load balancing?

Thanks,
Ankit
12 years ago
try debugging issue with <h:messages> to know whether validation messages are got added. If you want to capture validation messages for a particular component then you need to pass component id while adding messages to facesContext like.... component.getClientId(getFacesContext())

Thanks,
Ankit
12 years ago
JSF
Ideally this code should work without any exception, because com.ibm.mq.jms.MQQueue implements javax.jms.Queue. please share full exception stack trace.

Thanks,
Ankit
Hi All,

We have one J2EE application deployed on Websphere v6.1 clustered environment(Network deployment) and have another java client application which interacts with this application via IIOP-RMI transactions.

We have a need to do load balancing for RMI transactions. So different requests will be routed to different servers available in websphere clusters. How can we achieve "RMI-IIOP Load Balancing and Failover"? Please share your thoughts.

Thanks,
Ankit
Hi All,

We have an J2EE application deployed on Websphere v6.1 clustered environment and have one another client application which calls this application via RMI transactions.

Therefore, we have a need to do load balancing for RMI transactions. How can we achieve "RMI-IIOP Load Balancing and Failover"? Please share your thoughts.

Thanks,
Ankit
12 years ago
Hi All,

I have deployed a EJB application on Websphere 6.1 application server, trying to get Initial Context to get EJB reference using JNDI. But while instantiating InitialContext object, it's giving some exception -

javax.naming.NamingException: Error during resolve [Root exception is java.lang.NullPointerException]
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1939)
...................................................
Caused by: java.lang.NullPointerException
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3233)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3225)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3014)

=====================================================================

I have disabled Administrative, Application, J2SE security in application server. still exception is thrown.

I observed one thing, while creating InitialContext, if I pass -
java.naming.security.principal=""
java.naming.security.credentials=""
in HashMap, then only it's throwing above mentioned exception.

If I skip these two parameters while creating HashMap it's going through. But we have one class in which these two parameters are present and values are coming from property file. So we can't change code to ignore these two parameters while creating InitialContext. As we don't have control on this class.

Please help me to resolve this issue.

Thanks,
Ankit
Hi All,

We have one query on 'wsPessimisticUpdate-Exclusive' feature in EJB.

We are migrating EJB application to Java. Only purpose of migration is to remove entity bean from application, replacing by JDBC.
In older EJb application we had 'wsPessimisticUpdate-Exclusive' in deployment descriptor. Which converts normal select query with 'For Update' clause at runtime.
But in JDBC Java how can we achieve same kind of functionality.

Same query we have for wsPessimisticUpdate- NoCollision

Regards,
Hi All,

I am new to webservices.

From where I can download JAXM lib, JAXM provider, also integration with JWSDP 2 ?

Thanks
13 years ago