This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Svelte and Sapper in Action and have Mark Volkmann on-line!
See this thread for details.
Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!

Raj Konduru

Greenhorn
+ Follow
since Jun 04, 2003
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 Raj Konduru

Dear Friends,

I was wondering if we will get affected even if I am not using the TimeZone class. For instance, we do use Calendar, SimpleDateFormat, etc, however we do not use the TimeZone class. Please let me know if we still need to use the patch.

Thanks
13 years ago
Dear All,

Will the container create a instance of Stateful session bean each time the create method is onvoked on its home interface?

My home interface has a create method declaration as follows..
AuditClaimManager create(java.lang.Integer userID) throws javax.ejb.CreateException, java.rmi.RemoteException, AuditClaimLockException;

My bean has the ejbCreate() has follows..
public void ejbCreate(Integer userID){
this.userID = userID;
}

How many instance will be created if I invoke the creat() method on the home from the client with the same integer value... will the container return me the session bean which is already created or will it create a new instance even thought I passed in the same integer value in the create method..

Thanks...
<pre>
<ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="AuditClaimManager_Ext" name="AuditClaimManager" timeout="0">
<runAsSettings xmi:id="SecurityIdentity_7">
<methodElements xmi:id="MethodElement_13" name="*" type="Unspecified">
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
</methodElements>
<runAsMode xmi:type="ejbext:UseSystemIdentity" xmi:id="UseSystemIdentity_7"/>
</runAsSettings>
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
<isolationLevelAttributes xmi:id="IsolationLevelAttributes_7" isolationLevel="READ_COMMITTED">
<methodElements xmi:id="MethodElement_14" name="*" type="Unspecified">
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
</methodElements>
</isolationLevelAttributes>
<isolationLevelAttributes xmi:id="IsolationLevelAttributes_1047575906161" isolationLevel="REPEATABLE_READ">
<methodElements xmi:id="MethodElement_1047575906161" name="*" type="Home">
<parms xsi:nil="true"/>
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
</methodElements>
</isolationLevelAttributes>
</ejbExtensions>

</pre>
15 years ago
Dear All,

I have a question on stateful session bean timeout. A stateful session bean in our application is timing out frequently. Below is the deployment descriptor for the session bean..... Is there a way that I can make stateful session bean stay live forever....

<ejbExtensions xmi:type="ejbext:SessionExtension" xmi:id="AuditClaimManager_Ext" name="AuditClaimManager" timeout="0">
<runAsSettings xmi:id="SecurityIdentity_7">
<methodElements xmi:id="MethodElement_13" name="*" type="Unspecified">
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
</methodElements>
<runAsMode xmi:type="ejbext:UseSystemIdentity" xmi:id="UseSystemIdentity_7"/>
</runAsSettings>
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
<isolationLevelAttributes xmi:id="IsolationLevelAttributes_7" isolationLevel="READ_COMMITTED">
<methodElements xmi:id="MethodElement_14" name="*" type="Unspecified">
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
</methodElements>
</isolationLevelAttributes>
<isolationLevelAttributes xmi:id="IsolationLevelAttributes_1047575906161" isolationLevel="REPEATABLE_READ">
<methodElements xmi:id="MethodElement_1047575906161" name="*" type="Home">
<parms xsi:nil="true"/>
<enterpriseBean xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#AuditClaimManager"/>
</methodElements>
</isolationLevelAttributes>
</ejbExtensions>

Or I want it to be insync with the HttpSession....

Thanks,
Raj
15 years ago
Do you still have this position open. I like to be considered.

Originally posted by John-Isaac Clark:
Job Title: WebSphere/J2EE Architect
Location: ANYWHERE, USA
*** Can be based anywhere in US (Canadian candidates eligible for TN1
status considered as well) ***
*** 100% travel (Monday thru Fri) ***
*** Full-time Permanent Positions ***
*** US Citizens, Current Green Card, or Current H1B required ***
Quick Overview
- WAS/WSAD/XML/J2EE Architect
- Strong Infrastructure and Application Server (WAS) experience a must!!!
- Base salaries start at $80K and peak at around 120K for gods.
- Semi-annual bonuses 10-25% of base.
- 3 weeks vacation first year, benefits, 401k, options, etc.
Required Tech
WebSphere 3.x - 4.x - Admin/Infrastructure/Performance/Dev Experience
WSAD - Some knowledge (Preferably VAJ then WSAD - alternately Eclipse
in lieu of WSAD)
XML - gots to have it.
It is essential to have BOTH strong dev skillz as well as strong infrastructure and App Server (WAS) skillz.
Additional Desired Skillz
(got the above plus any of these and the first interview should be
sure thing)
WAS 5.0
WBI
WP
MQ
Distributed J2EE Environments
Role
Working as a consultant to companies that are 'attempting' to use
these technologies, being able to intimately
know how these technologies work together is crucial. Since analyzing
the client's application and infrastructure
is a big part of these roles, a background in infrastructure AND
development is a must. If the terms cloning,
clustering, IP sprayer, load balancing, and open connections mean
nothing to you, then rest assured this is
not the job for you.
Deep product knowledge of WebSphere is a MUST.
The Company
Perficient, Inc.
Based in Austin, TX
www.perficient.com
NASDAQ PRFT (don't laugh, we're still there)
Bottom line is this is a top notch group of people. I should know, I
hired nearly every one of them. Formerly
Director of Recruiting, I too felt the axe during the bubble boom -
but now I'm back. These folks have survived the storm
and are growing again.
Interview Process
1) Me - resume review and chit-chat - be prepared to talk about what
you've done w/the above technologies - believe it or not, I'll
actually understand what you're saying.
2) Tech Screen #1 - With Team Lead or Architect
3) Tech Screen #2 - With whoever you didn't talk to the first time.
4) Job Offer or TBNT (you or us)
Contact NFO
John Clark
Perficient, Inc.
jclark@corono.com?subject=JavaRanch%20Posting%20Response
**************************************************
Please feel free to email this posting to anyone who might be
interested so long as my contact nfo is included.
**************************************************

17 years ago