|
Apparently, the new Pet Store 1.1.2 doesn't use the 'problematic'
J2eeSecurityAdapter. This got me to thinking that a new
patch would not involve changes to the code or a recompile. In
this direction, I have been plodding along hoping to get the new store up and
running with JBoss 2.2.1/Tomcat on Windows ME. Being that I am new to all
of this, a few things have slowed me down. I am hoping that someone can rescue me
- now that I am knee deep. ;-)
My questions are:
In the web.xml file for pet store, what value should I use to
reference the JBoss 2.2.1 server? The previous patch
used "JBoss 2.1 Pre (www.jboss.org)" inside of
<env-entry-value></env-entry-value>. My only guess has been to
replace the "2.1 Pre" with a "2.2.1" but this has not worked.
The petstore.ear file seems to deploy fine (but I never scrutinized all of
those messages yet). Pointing my browser at http://localhost:8082 shows me a list of
MBeans, but I see a pet store at http://localhost:8080. By
running "netstat -a", I even know that nothing is listening on that
port. How does Tomcat port get configured? Any
suggestions?
With respect to cloudscape, the patch said to simply start it. The
only way that I been able to do this is through Sun's J2EE server (i.e.
"cloudscape -start"). How should I start cloudscape when using
it with JBoss?
Anyways, thanks in advance for any help that I might get.
Cheers,
Mike Donnelly
|
