I think you forgot the namespace on the plan, so geronimo didn't recognize it as something it could deploy (an error that comes from Deployer rather than a specific builder usually means that geronimo couldn't find a builder that could interpret your plan. How about:http://geronimo.apache.org/xml/
Hello,
I have been trying to get G 1.0 w/Jetty to use sticky sessions by
appending a JVM route to the session. I found a page about using G 1.0
with WADI, but the instructions do not seem to be current
The page in question indicated simply adding :
org.codehaus.wadi.jetty5.JettyManager
to your
Hi Aaron,
I commented out the addOperation calls and re-jared and tried to deploy again. Still the same error. The command that I used to deply is
"java -jar bin\deployer.jar --user system --password manager --verbose deploy GBean1-plan.xml". There is no error message on the server side and th
Well, you certainly don't need the addOperation declarations -- the
getter and setter there are already configuration when you add the
attribute.
Can you post the specific command you're running and error message
you're getting with stack trace if any?
Thanks,
Aaron
On 4/7/06, Ye Lu <[EMAIL
Hi Aaron,
I just tried deploying with your modified deployment plan and still got the same error. Could there be something wrong with the gbean itself? Here is the source code for my test gbean. Any ideas?
Thanks.
Ye
---
package com.businessobjects.geronimo;
import javax.man
How about:
yelu/GBean1/1/jar
test1
(assuming your JAR is at repository/yelu/jars/GBean1-1.jar
Thanks,
Aaron
On 4/7/06, Ye Lu <[EMAIL PROTECTED]> wrote:
>
> Hi Aaron,
>
> Sorry about the confusion. Perhaps my previous message wasn't clear enough.
> I meant to say tha
Hi Aaron,
Sorry about the confusion. Perhaps my previous message wasn't clear enough. I meant to say that I had been using the deploy tool all along in the way that you have suggested but still got the deployment error. I also tried the hot deploy method, but that didn't work either for the re
Sorry, there's a bug in the hot deployer in 1.0 and it can't deploy
service plans (that is, anything except a J2EE application or module).
If you use the deploy tool it should work. The fix for this bug is
already in, but you won't see it until the 1.1 release unless you
build from SVN HEAD. The
HI Aaron,
I did exactly as you suggested below, but I am still getting the following error message:
Error: Unable to distribute GBean1-plan.xml: Cannot deploy therequested application module(planFile=D:\geronimo-1.0\GBean1-plan.xml)
I took care to ensure that the gbean is compiled and jared w
Yeah, I've seen this issue before, and I can't remember what was done
to work around it. But the hidden classes is a good place to start.
Thanks,
Aaron
On 4/7/06, Pablo <[EMAIL PROTECTED]> wrote:
> Paul McMahan wrote:
>
> >Pablo, I think the problem is that your app includes a copy of the
>
Paul McMahan wrote:
Pablo, I think the problem is that your app includes a copy of the
commons logging and the server's classloader (which is visible to your
app) does too. Try adding this to your deployment plan:
org.apache.commons.logging
I'm not sure why deployment didn't fa
Pablo, I think the problem is that your app includes a copy of the
commons logging and the server's classloader (which is visible to your
app) does too. Try adding this to your deployment plan:
org.apache.commons.logging
I'm not sure why deployment didn't fail in jetty, perhaps
I'll do go ahead and make sure we're in sync and update the SNAPSHOT.
Gianny Damour wrote:
Yeap.
Do you want to upgrade yourself or do you need a hand to do it? I am
happy to make the relevant updates to move to TranQL 1.3 over the
week-end.
Thanks,
Gianny
Matt Hogstrom wrote:
I would li
Hi guys.
When I deploy my webapp in geronimo-1.0-jetty everything works fine but
when I do it in geronimo-1.0-tomcat I get the following error:
You have more than one version of 'org.apache.commons.logging.Log'
visible, which is not allowed.
Is this issue known? Will it be fixed in the near
I'm not able to recreate the error and since you don't see the error
using geronimo+tomcat on a different machine there must be something
specific with that machine's configuration. Since the tomcat log
shows that a request was received ("GET / HTTP/1.1") I don't think
it's a problem with your bro
the gbean sample on wiki is outdated, you should follow Aaron advice.
and after that, maybe you have to change your gbean name too
2006/4/7, Aaron Mulder <[EMAIL PROTECTED]>:
> You should put your JAR at, say, repository/yelu/jars/gbean-1.jar --
> note that it has the form repository//jars/-.jar
>
You should put your JAR at, say, repository/yelu/jars/gbean-1.jar --
note that it has the form repository//jars/-.jar
where group, file, and version can be anything you like, but need to
be present and with a dash before the version.
Then set your dependency URI to group///jar (like
yelu/gbean/1/j
On 4/7/06, Rohit Rai <[EMAIL PROTECTED]> wrote:
> Thanks Aaron for the reply.
>
> By your reply I understand that I'll have to modify the server code itself.
> But that is not possible.
No, not in the server code really. You need to make a custom JAAS
LoginModule, which is part of a security real
Yeap.
Do you want to upgrade yourself or do you need a hand to do it? I am
happy to make the relevant updates to move to TranQL 1.3 over the week-end.
Thanks,
Gianny
Matt Hogstrom wrote:
I would like to move to TranQL 1.3 and the Connector 1.2 for Geronimo
1.1. Are you ok with this?
Hi, I am now working with some application based on Avalon/Merlin.
Merlin is dead now, and it also needs jetty to run its web gui, so I
would like to intergate the application in Geronimo, maybe by writing
a GBean for merlin.
I have found some post talking about running merlin or spring
components
20 matches
Mail list logo
