vin miller

Hello,

Does anyone know why OAS would set the status of a BMT UserTransaction object to marked for rollback?

We don't call setRollbackOnly() anywhere in our code, so I can only assume that OAS is doing it. This doesn't happen when run through JDeveloper and didn't happen in previous versions of OAS. The version we're using now is 10.1.3.4.

It also seems to be random. With the same exact procedure and data, sometimes it happens and sometimes it doesn't.

Any ideas would be greatly appreciated.

Thanks,
Vin

Here's an article about repairing the broken references. I'm not exactly sure how they 'validate' the reference to see if it needs to be refreshed.
http://www.javaworld.com/javaworld/jw-07-2002/jw-0703-service.html
What I don't understand is why it's ok to potentially allow multiple clients to have a reference to the same ejb object. Couldn't that cause problems?
Vin

Hi,
I have a few EJB/JNDI questions. I am very new to OAS/JDeveloper, and relatively new to EJB so please bear with me.
1. When I run my entity bean, and then run my client (both from JDeveloper), my jndi.properties file is not found. In my classpath, I have C:\vin\dev\classes. The properties file is located at C:\vin\dev\classes\gov\nysed\sams\properties\jndi.properties. I can't spell out the complete path in my classpath because I don't have the authorization to do so on my pc. Is this the reason why the file is not being picked up?
2. The property settings that seem to be in all the examples are:
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
# Embedded OC4J Server
java.naming.provider.url=ormi://localhost:23891/current-workspace-app
# edit username
java.naming.security.principal=admin
# edit password
java.naming.security.credentials=welcome
Are these just for testing? If so, how should these settings change for production?
3. With the above jndi settings established in my code instead of a properties file, I'm able to connect to the jndi server, but my lookup of my entity bean fails (NameNotFoundException) even though the name I am looking up is the same as the name in ejb-jar.xml. Is there something else I need to do when I run a bean in JDeveloper for testing?
Thanks,
Vin

I passed the SCJD in early March. It was an enjoyable experience - much more so than SCJP. I also learned a lot from it. However, I don't think it is helping my job search much.

Tony,
I noticed in your resume that you are from Orlando. I am trying to relocate to Ft Lauderdale, got any advice? I knows it's somewhat far from you, but you're a lot closer than I am (I'm in NY, where there is still some snow)
I think I have a decent resume (http://vinmiller.net/resume) and some good experience, but I haven't been getting many replies from the job sites.
Thanks

Thanks for the input.
I use textpad, which I didn't really consider a IDE. I have never really fully used and IDE before, but some of the posts have made me more open minded about them. I guess it's more of how you use them. So long as the code is not dependent on the tool.

Just curious how many people use text editors vs development environments (ide, app server, etc) at work and what you preference is.
I prefer text editors. Although they have their advantages, I feel that the development environments take away some creativity and control.

Does anyone know any good recruiting companies for South Florida (Ft Lauderdale to be specific)? I am not from that area and would liek to relocate their. I would greatly appreciate any help.

word for word.
I just ignored it.
1. You have forever to complete the assignment.
2. If you don't have the skills, develop them. I barely knew what rmi was when I started my assignment.
http://java.sun.com/docs/books/tutorial/ - It's free

Thinking of relocating to FL.
Which has better java jobs and which is a nicer place to live.
All opinions and information will be greatly appreciated.

Ajit,
I used ascii text format for the readme, gui doc, server doc, and design doc. The only documentation that I was in any other format was the javadoc.

Joey -
My design was somewhat similar. I kept my interface with my rmi code because that's where it seemd appropriate to me. However, you can put it anywhere you want so long as it is accessible at compile time.
Dhirendra -
One reason you would need lock and unlock is if the actual locking occurs in a separate class. Also, if you were to rely on synchronization, I think it would lock the entire databse instead of just one record, causing all other requests to wait - even if they are going after a different record.
I think the whole idea behind this record locking is to allow the client to make transactions. To support this, a lock would have to exist long enough for the client to do what it has to. Since the server cannot determine this, it is left up to the client to call unlock when it is done. Although I don't think it's necessary for the scope of this assignment, I used a timer to get rid of a lock if the client didn't.

joey,
I used an adapter class to instantiate either Data (local) or the RMI client.
Where appropriate, I passed DatabaseException all the way to the GUI to notify the user. I handled all remote exceptions in the RMI client, and threw new exceptions when necessary.

Skip -
By validation I mean having the GUI validate the input before it is processed. Not required, but a good idea.
Deb -
I designed my server to be used through a LAN connection, using a LAN address for the codebase i.e. //host/ . I also have an apache web server running on NT and one on Linux. I decided to test my server by using a http://host/ codebase. Stub was dynamically downloaded in both cases. For some reason, the permissions in my security manager were not enough when using a http codebase - access was denied to the class loader. I had to include a policy file in my distribution incase Sun tested in both modes. SocketPermission for port 80 in the policy file took care of it, although that permission was already in my security manager. weird.

Thanks.
My primary references were the Java API and Sun's Java Tutorial.
I did a lot more than required to make the best of the experience, which might have negatively afftected my score.
Some of my bigger decisions:
Chose RMI
modified Data instead of extending it
modified the signatures of lock, unlock, and modify
implemented a lock queue and a timer for each lock
used security managers for rmi instead of java.policy
used a menubar and toolbar for GUI
Be sure to test rmi in network and http mode. I found that the jvm handles permissions for each differently.
Also, trim the number of seats request, i.e. '5 ', so it will pass validation. I forgot to do that.