Jdev9irc initial observations

Question

I just downloaded the Jdev9irc and installed it on my Win 2000
machine.
I migrated my BC4J/JSP project from Jdev 3.2.3 and then deployed
it to the newest OC4J 2.0. Here are my observations:
1. The new Jdev9irc software looks very promising. The
connections pooling has been fixed and it works reaaly well.
2. The migration was also not very difficult.
3. I had some <%@ include file="pagehdr.html" %> statements in
my jsp. Jdev 3.2.3 would find this file under
myhtml\soJsp_html\pagehdr.html, but under the jdev9irc, the file
has to be under myhtml.
But this cuases a problem when you deploy the project, OC4J
expects it to be under \soJsp_html directory. I had to put the
file in both locations.
4. I was also referring to some images
under /webapp/images/MDCHBanner.gif. I had tough time locating
where this should go. Under development it needs to go under
%jdev_home%\jdev\system\oc4j-
config\applications\bc4j\webapp\images.
For production(deployed to OC4J) it needs to be located under %
jdev_home\bc4j\redist\bc4j\webapp\images.
Maybe this is because I am referring to "webapp" which is a
defined virtual web-app.
5. I had some trouble with PCST_TXN and PCOLL_CONTROL tables. I
dropped the tables but JSP app would not re-create them. I then
recreated them using jdev 3.2.3
6. I had some trouble with <jbo:SetAttribute dataitem="*" />. I
was using this tag to create an auditlog of my original table.
In jdev 9i setattribute dataitem="*" checks for entity name and
would allow you to duplicate the data to another entity.
7. Some trouble with jbo:ShowValue tag. If the value is null,
jdev 3.2.3 used &nbsp but jdev 9i puts blank. If you are using
html tables, this does not look nice.
8. Deployment to OC4J documentation is still not very clear. It
talks about a sitename for the URL e.g
http://hostname:<portnumber>/<virtul path>/<sitename>/main.html.
But there is no explanation what a sitename is. The sitename is
the default packgae name. In my case soJsp_html.
9. Overall the docs have improved a lot.
10. Built in OC4J(inside jdev IDE) seems to work most of the
time,but sometimes I would get "file not found" error. I have to
then terminate the OC4J server (from run manager) and then it
would work.
11. Appmodule now has releasemode clause and that clears up all
the confusion about stateless and stateful modes.
12. Use of webbean has improved and it now use the datasource
tag. This integrates the webbeans with appmodule and datasource.
All in all a great product and it very close to being a usable
product for production JSP applications.
Thank you Jdev team.

Answer 1

Going through the same thing. we have to find all the loops holes to be able to gets stuff. our group is small enough that we just made everyone one set up their own account using their work email. if we want to buy apps we just have the person who has the credit card by online gift cards and let people load the money to their account.
from what I haVe read Apple does not intend to change their way to making Apple friendly to enterprise use. which is a shame because more and more companies want to use them for that way and are having the same issues.