The ra was updated last week and is included in 2.0.2 as well as trunk
On Oct 4, 2007, at 1:32 PM, David Jencks wrote:
After more investigation I discovered that you can set these
particular properties on the ActivationSpec in the mdb
configuration as well, and I've updated the amq docs to
I wonder if it would be appropriate to replace the expired context
with something representing the "no one" identity? then the ACE
might occur naturally when "no one" can't do something but stuff that
is actually allowed for an unauthenticated user would still work...
so I think this woul
Hello,
I am trying to deploy an MDB that worked fine in Geronimo 1.1 on 2.0. It
deploys just fine, but doesn't get triggered when a message comes to the
queue.
Here's how my MDB looks like (snippet):
=
@MessageDriven(mappedName = "CallFinishMDB
Sorry -- forgot the code...
Replace
assert context != null : "No registered context";
with
if (context == null)
throw new AccessControlException("No registered context (may have
expired)");
Scott Stanchfield wrote:
>
> Suggested Fix
>
> Change getCurrentContext() to throw and Acce
We had the same issue, and didn't see much about it online (except this note
and bug GERONIMO-2100)
I debugged through the Geronimo code for a while today, and I think I've
found the solution (which I also think is the proper solution to
GERONIMO-2100 as well...)
The problem
[In this descriptio
On Oct 8, 2007, at 1:10 PM, Ashish Jain wrote:
Hi,
I am trying to start Geronimo as a windows service. I am following
this link for the same. http://cwiki.apache.org/GMOxDOC20/
configuring-geronimo-as-a-windows-service.html
Server start is fine but when I try to stop the server. I get th
On Oct 9, 2007, at 5:20 PM, Zakharov, Vasily M wrote:
Hi, all,
After I deploy a JMS connector (named SPECJMS) and an application
(SPECjAppServer2004) using this connector, the following messages
appear in the console after each 30 seconds or so:
03:06:18,619 ERROR [ActiveMQEndpointWorker] End
On Oct 10, 2007, at 9:29 AM, Oleg Nitz wrote:
Hi!
I am trying to move our app from Geronimo 1.1.1 to Geronimo 2.0 and
I am getting a strange error during deployment:
16:15:55,569 ERROR [GBeanInstanceState] Error while starting; GBean
is now in the FAILED state: abstractName="irbis/irbis/1.
On Oct 10, 2007, at 12:46 PM, [EMAIL PROTECTED] wrote:
From: Kevan Miller [mailto:[EMAIL PROTECTED]
You can find JNDI naming documentation for 2.0.2 here -- http://
cwiki.apache.org/GMOxDev/client-jndi-names.html Supposedly this doc
got moved to a better location, but I don't see it... Perhap
Quoting "Zakharov, Vasily M" <[EMAIL PROTECTED]>:
> Kevan,
>
> Thanks for your help! Your solution worked.
Thanks as well, Kevan!
>
> However, in my case the proper JNDI name for the bean turned out to be
> as follows:
> "orders.jar/OrderAuditSes/org.spec.jappserver.orders.orderauditses.ejb.O
>
On Oct 9, 2007, at 1:10 PM, Zakharov, Vasily M wrote:
Kevan,
Thanks for your help! Your solution worked.
However, in my case the proper JNDI name for the bean turned out to be
as follows:
"orders.jar/OrderAuditSes/
org.spec.jappserver.orders.orderauditses.ejb.O
rderAuditSes"
and I had to pa
On 10/10/07, Tomasz Mazan <[EMAIL PROTECTED]> wrote:
>
> OK. it's working. I have to add to my classpath: openjpa spec and jar with
> classes that are used in webservice, but error message was not clear.
>
> Thanks
> Beniamin
Ok, great. Yeah, the exception does not really help but I don't think
we
Jarek Gawor-2 wrote:
>
> Ok. I'm still unable to replicate. Here's what I'm doing:
>
> jaxws-tools.bat wsgen -verbose -r wsdl -s src -d target -keep
> -wsdl:Xsoap1.2 -extension -cp
> ..\geronimo-jpa_3.0_spec-1.1.jar;..\test.jar
> org.apache.greeter_control.Foo
>
> and my Foo.java looks like:
Well - indeed I was reading the ejb docs from ejb 2.x point of view: having
ejb EntityBeans.
The big difference I did not notice before is, creating an Entity ejb using
deployment descriptors or using the @Entity annotation does not result in
the same behaviour of the container...
Finally I just
14 matches
Mail list logo
