Yoshita Jain

+ Follow
since Sep 15, 2007
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Yoshita Jain


Could you resolve your issue?

I am also facing a similar issue... Please advise!

11 years ago
Hi Jaikiran,

Thanks for your reponse.

When we include the jboss-common-jdbc-wrapper.jar (which contains org.jboss.resource.adapter.jdbc.WrappedConnection) we can't seem to get the connection right and we get an exception while executing a regular select statement through iBatis.

[ April 11, 2008: Message edited by: Yoshita Jain ]
Hello Everyone,

We are using Spring and iBatis in our application which is deployed on JBoss.

Our datasource is configured on JBoss which we lookup through JNDI.

In one of our funtions, we are required to make a call to a stored procedure which has an Oracle.ARRAY as IN parameter. Now in order to create a StructDescriptor/ArrayDescriptor, we need to pass the connection object to the createDescriptor.

However, when weI get the connection object from the datasource and pass it to the createDescriptor method

java.sql.Connection conn = setter.getPreparedStatement().getConnection();

StructDescriptor structDescriptor = StructDescriptor.createDescriptor("OBJECT_NAME", conn);

We get a
java.sql.SQLException: org.jboss.resource.adapter.jdbc.WrappedConnection

a) If we create a regular direct JDBC connection, it runs fine.
b) If we load the sql-map-config.xml at run time (it has a datasource object defined in it), it runs fine.

We would however like to use the already created datasource for all db purposes.

Any help would be appreciated.

Thanks and Regards,

Hi Friends,

Cleared the SCWCD exam today with 89%. I am quite happy with the score.
The exam had 80 questions, 10 for SUN survey purposes with 40 minutes extra.
About my preparation:
I had started my preparation quite a while back, but kept losing touch with the study. The past month and a half is when I got serious (and also joined the forum)
Here�s what I used:
1.Read HFSJ 2 times. Browsed through it a third time over a period of 1 week. The first read was quite a while back and familiarized me with the topics. It was only the second read which was exam oriented.
2.Mikalai Zaikin�s notes: Great stuff� covers quite a few points that are not mentioned in HFSJ.
3.Frederic Esnault�s notes.
4.Free Mock Tests available on the net.
5.Enthuware tests: Good learnings from those.
6.Went through the JSTL specs for core tags.
7.HFSJ Mock Exam: Gives a very good idea about the level of the actual test.
8.And last but not the least: This Forum. The links section is very comprehensive and helpful. The forum kept up my enthusiasm and helped clear many doubts.
9.I also maintained a notebook of my learnings from the practice tests.

One thing I�d like to say is actually implementing the concepts in a sample project went a long way in helping me get things right, especially in topics like EL and tags.

Would like to wish fellow ranchers all the best and thanks for all the help I�ve got on this forum.

I mean

in the tld.

Swathi, yes thanks... that helps... that is in keeping with the answer I got when I tried it out.

Got you point Michael. Thanks a ton. (Guess I'm seeing double these days )I tried this using RAD and got BUBBUB.

Hmm So this is container dependent too....

Hi folks,

Another doubt in HFSJ :

Here's a snippet similar to the Question 55: (pg 790,828)

session.setAttribute("dab", new DealerAddrBean());
session.setAttribute("dab", new DealerAddrBean());

The DealerAddrBean class implements HttpSessionBindingListener

public class DealerAddrBean implements HttpSessionBindingListener


public void valueBound(HttpSessionBindingEvent hsbe)


public void valueUnbound(HttpSessionBindingEvent hsbe)



The result I get is BUBBUB

The HFSJ answer is BBUBUB (the closest one)

I am fairly confident that the extra 'B' is an error.
However I'd like you guys to confirm that.

(The third setAttribute is Simply setting a string.. so we can't expect the listener to be called for that)

Thanks & Regards,


May be they need TLD also...

Yes, as per the explanation.
To determine a valid invocation we need to know the value of <name>...</name>

With any of the other answers we would have to assume that 'repeat' is the function name.

Thanks all of you...

But I'm still puzzled coz as I said.. for me..this worked

<jsp:useBean id="dab" class="com.bean.DealerAddrBean">
<jsp:setProperty name="dab" property="dealerName" >
<bean:write name="dealerAddrBean" property="cityName"/>ABCDEFG

and for ${dab.dealerName} it gave me the output 'New DelhiABCDEFG'

And yeah Tarun, 'nested' is incorrect for what I was referring to.. mebbe 'embeded makes more sense..and embeded tags are disallowed.


Guess the embeded thing doesn't work

'dealerAddrBean' has been previously defined and its 'cityName' set to 'New Delhi'

<jsp:useBean id="dab" class="com.bean.DealerAddrBean">
<jsp:setProperty name="dab" property="dealerName" value='<bean:write name="dealerAddrBean" property="cityName"/>'/>

and then I did a ${dab.dealerName} it resulted in printing
<bean:write name="dealerAddrBean" property="cityName"/>
rather than 'New Delhi', which I was expecting.

However,the following worked and set the value correctly as

'New DelhiABCDEFG'

<jsp:useBean id="dab" class="com.bean.DealerAddrBean">
<jsp:setProperty name="dab" property="dealerName" >
<bean:write name="dealerAddrBean" property="cityName"/>ABCDEFG
[ October 21, 2007: Message edited by: Yoshita Jain ]
What is the <body-content> of the <jsp:setProperty> tag? Don't remember reading anywhere that its empty.

I was also wondering if we could use a embeded tag to assign the the <jsp:setProperty> value....

Something like this:

<jsp:useBean id="person" type="foo.Person" class="foo.Employee">
<jsp:setProperty name="person" property="name" value="<myTag:test/>"/>

where <myTag:test/> returns a String value
[ October 21, 2007: Message edited by: Yoshita Jain ]
Goes like this:

Listeners in the are instantiated.
contextInitialized method on the ServletContextListener implementor called.
Filters initialized.
Servlet loaded. (if you have only one servlet with load on startup value as 1, it really doesn't matter... you've got just one servlet to load anyway)