No, neither client jars or ejb interfaces need be included in the war.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Michael Angelo Libio [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, November
Hello all,
Using jboss-3.0.0_tomcat-4.0.3, I am
trying to access a Session bean called Registration from within a servlet, both
of which are part of an application called pc, deployed as pc.ear. I can access the bean with no problem
from a stand-alone client, with the following code:
ECPERF is in CVS under the ecperf module. For testing with 3.0 series,
you'll need to checkout:
ecperf -r Branch_3_0
3.2 and higher, just check out ecperf regulary.
at jboss's CVS server? sorry for asking, but me cvs aren't that close so
that I fully understand all you said ;-)
Also
Joao Pedro Clemente wrote:
ECPERF is in CVS under the ecperf module. For testing with 3.0 series,
you'll need to checkout:
ecperf -r Branch_3_0
3.2 and higher, just check out ecperf regulary.
at jboss's CVS server? sorry for asking, but me cvs aren't that close so
that I fully understand all
Hello:
I'm trying to configure the DatabaseServerLoginModule to use as an
authentication mechanism for a simple JSP with simple FORM based
security. I'm sure I am missing something, but have not been able to
find my error(s) in the documentation or other related posts. This is
with JBoss 3.0.0
There is no jboss-web.xml descriptor describing the security domain
under which authentication should occur. See the getting started guide
where a WEB-INF/jboss-web.xml file is described as being required
to enable security:
jboss-web
security-domainjava:/jaas/other/security-domain
/jboss-web
This happens when the stateful session has been removed due to
inactivity. The default timeout is 30 minutes. jboss-3.0.0 is now getting
to be a rather out of date version so lookup into updating to 3.0.4.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Hello
all,Using jboss-3.0.0_tomcat-4.0.3, I am trying to access a Session bean
called Registration from within a servlet, both of which are part of an
application called pc, deployed as pc.ear.
Here is the code Im using to do it:
Context
jndiContext = getInitialContext();Object ref =
Bug in 3.0.0. Upgrade to 3.0.4.
Scott StarkChief Technology
OfficerJBoss Group, LLC
- Original Message -
From:
John Snyder
To: [EMAIL PROTECTED]
Sent: Sunday, November 03, 2002 9:31
AM
Subject: [JBoss-user]
Hi,
someone of you run Jboss successfully on a IBM AS 400?
Thanks
Stefan
---
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF.
That makes sense -- thanks.
Are there any configuration changes I have to make to deployment or service
descriptors when I move from 3.0 to 3.0.4, or should what I have for 3.0
work in the upgraded version, too? If there are modifications, is there any
documentation listing the needed changes?
Thanks for the info and by the way, I have been working straight from
the Quick Start Guide draft 3.
I've modified by jboss-web.xml to be exactly as you listed below with no
apparent impact on the behavior.I'm still getting the behavior as
described below. Any help at all will be greatly
At various times there have been various class cast problems, and many of
them have been fixed. Please be sure you are using an up to date jboss
version (such as 3.0.4) before complaining too loudly.
thanks
david jencks
On 2002.11.03 14:26:08 -0500 John Snyder wrote:
My problem looks very
Scott,
I upgraded to jboss-3.0.4_tomcat-4.0.6, but I still have the exact same
problem. Everything works fine when I first start JBoss and deploy the
.ear, but as soon as I re-deploy the .ear, I get the ClassCastException.
This happens even when I remove the .jar and .ear files from the deploy
If my client for some reason goes down and I have to restart it, I'd get the
following exception ...
---
MBeanException: Exception in MBean operation
'createQueue(,java.lang.String,java.lang.String)'
Cause: javax.management.InstanceAlreadyExistsException:
Hi Guys,I have a JMS implementation for my project using
JBoss 3.0.2, JDK 1.4.1When an external client closes the connection to a
particular Queue hosted by JBoss, you can see the following exception being
thrown in the Jboss console. I am wondering if there is any way to capture this
Hi,
How do I tell jboss that my JMS provider does not support XA. I am
trying to use Fiorano with JBOSS and Fiorano does not support XA.My
problem is that the JBOSS JMS plugin gets a class cast exception because
it thinks that the ConnectionFactory it got from the Fiorano JNDI is an
forum people,
I have updated forums with security concerns.
If you are using 3.0.4 :
It are using a login-config that you have to set up
before running it. The snippet is in the class
forum_home/src/main/org/jboss/forums/security/SecurityService.java.
If you are using HEAD :
1.You can use
thanks, scott...one last thing:
I'm really confused as to where my third-party-web.jar files should be.
They're the files that drive my web application. Should they sit on the
WEB-INF/lib of the war file? Or should they be in the root of the my
ejb-app.jar file? Do I need to include
19 matches
Mail list logo
