This is probably not implemented yet. It certainly doesn't work with
jetty6 yet.
We're going to need to scan the code and hook the output of the
annotation scanner into the naming builder framework to get the stuff
needed bound in jndi, and then do something to inject these
resources.
WTP 2.0 isn't yet supported. Please use WTP 1.5.2.
--
Shiva
On 12/12/06, Johannes Weberhofer, Weberhofer GmbH [EMAIL PROTECTED]
wrote:
Do you use WTP 2.0? Geronimo 1.1 does not work there.
Sachin Patel schrieb:
From what I've been told by someone on WTP Web Services, when using the
wizard
On Dec 11, 2006, at 2:19 PM, Aaron Mulder wrote:
On 12/11/06, David Jencks [EMAIL PROTECTED] wrote:
Sensible??? whats that mean ? :-)
I like this idea a lot, especially if I don't have to implement
it :-)
Sure. I would lean toward adding an element like embedded-jar to
the EAR
Please read:
1) Webcast: Using the Geronimo Eclipse Plugin**
http://tinyurl.com/ycyjvg
2) IBM developerWorks article on Create, deploy, and debug Apache Geronimo
applications
http://www-128.ibm.com/developerworks/opensource/library/os-gerplug/
--
Shiva
On 12/12/06, Srikanth M [EMAIL PROTECTED]
Do you get an error if you don't list any EJBs at all? It looks like
that technically violates the schema, but it's worth a try.
I did not try it, because as you mention, it does violate the schema.
Otherwise, can you post your dummy bean implementation class? Perhaps
it's missing one of
Correct - annotations are not implemented in the tomcat6-jee5 assembly
yet. I am planning to start looking at that after the holidays. My
very early thoughts were that the annotations could be merged into the
deployment descriptor before the builder processes it. But at this
point I've spent
Ray,
What release of Geronimo were you using (and which web container)?
What were you doing when you hit this problem? Was it from the Geronimo
Web Console or one of your own applications?
Thanks,
Joe
Ray Hurst wrote:
HTTP Status 500 -
Thats assuming there is a 1-1 mapping for all annotations to dd xml
elements. Do you know if that is the case?
On Dec 12, 2006, at 9:33 AM, Paul McMahan wrote:
My
very early thoughts were that the annotations could be merged into the
deployment descriptor before the builder processes it.
Not all of the annotations that can appear in a webapp have a 1:1
correspondence with the DD but some do. The rationale behind merging
the annotation into the DD is to support the management APIs which can
ask for a deployed object's DD which should include its annotations.
This was discussed a
Joe Bohn wrote:
Ray,
What release of Geronimo were you using (and which web container)?
What were you doing when you hit this problem? Was it from the Geronimo
Web Console or one of your own applications?
Thanks,
Joe
Ray Hurst wrote:
HTTP Status 500 -
Ray,
Yes, that will work. However, for Java EE 5 compliance JSTL 1.2 must be
supported by the server and would not need to be included in your web
app. We've made a start at Java EE 5 in preparation for Geronimo 2.0.
The work is currently only included in trunk but will soon be delivered
Joe,
I currently have the Geronimo 1.1 version merged with Eclipse 3.2.1 and
WTP 1.5.2. Good to know that it is in the next release. I'm learning how
to write JSP pages and it drove me nuts because I also have the Sun PE9
server installed at it worked out of the box.
Ray
Joe Bohn wrote:
Hello:
I am trying to port an application from JBoss to Geronimo 1.1.1.
Some of what follows is from my memory not from existing deployments, so
there may be small errors in the examples.
In the JBoss application, there is an exploded .war deployed in the JBoss
deploy directory, like this:
Hello,
I have installed geronimo. I am not able to start the server, I keep getting
this error. Please advice.
Booting Geronimo Kernel (in Java 1.4.2_13)...
Starting Geronimo Application Server v1.1.1
[*** ] 16% 192s Starting
geronimo/j2ee-security/1...14:38:08,885 WARN
Anyone? We cannot support Geronimo in our app without this.
On 12/5/06, Mike Perham [EMAIL PROTECTED] wrote:
I'm using WAS CE 1.1.0.1 and used the console to create a
Topic/Queue/ConnFactory, saved the plan and modified it slightly (to
use XA instead of local transactions). The command I'm
Have you tried to deploy with the --inPlace option. It would be some thing like
this
java -jar deployer.jar --user system --password manager deploy --inplace
app_home
and point app_home to your exploded app dir.
HTH
Cheers!
Hernan
Geronimo User wrote:
Hello:
I am trying to port an
problems mail [EMAIL PROTECTED] writes:
Hello,
I have installed geronimo. I am not able to start the server, I keep getting
this error. Please advice.
Booting Geronimo Kernel (in Java 1.4.2_13)...Starting Geronimo Application
Server v1.1.1[*** ] 16% 192s
I copied your plan (jms.xml) into Notepad++ and then saved it and it
deployed w/o any errors on WASCE 1.1.0.1 on Windows XP. Does your copy of
jms.xml file have any funky non-readable characters in it ?
On 12/12/06, Mike Perham [EMAIL PROTECTED] wrote:
Anyone? We cannot support Geronimo in
On 12/12/06, Hernan Cunico [EMAIL PROTECTED] wrote:
Have you tried to deploy with the --inPlace option. It would be some thing
like this
java -jar deployer.jar --user system --password manager deploy --inPlace
app_home
and point app_home to your exploded app dir.
HTH
Hernan:
Thanks,
Joe,
Correction, Geronimo 1.1.1.
By the way, I have ascertained that the repository holds the libraries.
Is this correct? Is it that simple if I just add the Jakarta directory
to the repository and all of this goes away?
Ray
Joe Bohn wrote:
Ray,
Yes, that will work. However, for Java EE 5
On Dec 12, 2006, at 2:55 PM, Geronimo User wrote:
On 12/12/06, Hernan Cunico [EMAIL PROTECTED] wrote:
Have you tried to deploy with the --inPlace option. It would be
some thing like this
java -jar deployer.jar --user system --password manager deploy --
inPlace app_home
and point
On 12/12/06, David Jencks [EMAIL PROTECTED] wrote:
I can think of 2 things to try:
1. try deploying offline
Hello David:
I deployed my-app using this as suggested:
deploy.bat --user system --password manager --offline deploy --inPlace
app path
It did seem to deploy correctly in Geronimo
Also you should make sure you're listing your JMS resources as a dependency
in your openejb-jar.xml ike this:
dep:dependency
dep:groupIdconsole.jms/dep:groupId
dep:artifactIdfabric-jms/dep:artifactId
dep:version1.0/dep:version
dep:typerar/dep:type
23 matches
Mail list logo
