Some One

Greenhorn
+ Follow
since Oct 15, 2004
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 Some One

Undeploy the application in the console.

Then clear your application from the WebLogic's cache by deleting it from yourDomain/servers/AdminServer/tmp. Afterwards, try to redeploy your application.

Kind regards,
16 years ago
As you might now, POI stands for Poor Obfuscation Implementation. It's your way to hack from Java into the filthy MS-Office docs. Even the guys from Apache POI are talking, if you read their API's, about things like HSSF, which stands for Horrible Spreadsheet Format or about HWPF which stands for Horrible Word Processing Format.

Conclusion: newer use POI as a database stategy, it will be cenrtainly less efficient than setting up your own db.
You might try to increase the number of seconds before a time-out occurs by specifying a 'TimeoutSeconds' node in the config.xml of your WebLogic domain.
16 years ago
Sure you can, but make sure, when you create a new WebLogic domain that it runs on a different port than your tomcat is running on.
16 years ago
The problem your're facing micht have something to do with the WebLogic caching strategy.

First, you might undeploy all your concerning web-applications and secondly, delete the entire .wlnodelete. Afterwards redeploy your apps and go futher from that point.
16 years ago
Why do you import in your jsp if you don't use it in your jsp?

Kind regards,
16 years ago
The error you're having:

the JNDI name
'ejb/XXXRemote'
is already in use. You must set a different JNDI name in the
weblogic-ejb-jar.x
ml deployment descriptor for this EJB before it can be deployed.

, might occur because your first application is still deployed.

A possible solution could be to undeploy your testEar and testEar_1, clean the cache, which you can find in youDomain/servers/Adminserver/tmp/_WL_USER/, where you delete both testEar as well as testEar_1, afterwards you can try to redeploy your testEar_1.

If this is not possible, speciy an other JNDI name for your EJB's.

Hope this helps...
16 years ago
Why would you 'dump' it in a file? This would definitely pollute your file-system.

You might consider using an appropriate solution such as DisplayTag.
16 years ago
JSP
The J2EE 1.4 spec defines:

Each web module must be given a distinct and non-overlapping
name for its context root.




You might read the doc @ J2EE 1.4 spec
16 years ago