Quoting Alex Loubyansky <[EMAIL PROTECTED]>:
> But why don't you contribute it to jboss.org? It would be even better
> to have all the material in one place.
> Of course, it's your work, you are owners and it's your choice.
By sending it to the mailing list, we are contributing it to jBoss.
It's
Hello Steve,
have you read Scott's article on javaworld.com? If not read it first
and then ask your questions if you have.
good luck!
Friday, July 05, 2002, 7:26:34 AM, you wrote:
SK> Hello,
SK> I have a simple security requirement...I need to restrict access to a set of jsps
in my war. But
Thank you, guys, for populating the stuff. It's certainly useful,
helpful and pricelessly (if it's up to date, of course ;))
But why don't you contribute it to jboss.org? It would be even better
to have all the material in one place.
Of course, it's your work, you are owners and it's your choice.
Thanks for pointing that out - I do indeed have a downlevel version of log4j
source code. However, the JBoss source is NOT using
org.apache.log4j.Logger, which as you point out extends Category. Instead
the source is using org.jboss.logging.Logger, which does not extend
Category, but instead wra
> How can JBoss deprecate an interface in a separate package?
Category has been deprecated by the log4j project:
"This class has been deprecated and replaced by the Logger subclass. It will
be kept around to preserve backward compatibility until mid 2003.
Logger is a subclass of Category, i.e.
How can JBoss deprecate an interface in a separate package? I see what you
are referring to - jboss-all\common\src\main\org\jboss\logging\Logger.java
wraps Category so it can introduce Trace level logging. I wasn't aware of
this - thanks for pointing it out. I don't necessarily agree with it (s
He *is* using log4j. Your suggestion below is a "deprecated" interface.
I suspect that he is not looking in the right place for the debug
messages.
Debug messages only appear in the log/server.log file, not on the
console.
This works for us btw.
On Monday, July 8, 2002, at 11:34 AM, Guy Ro
Use log4j, e.g.,
private final Category log = Category.getInstance(getClass().getName());
- Original Message -
From: "Dimitri PISSARENKO" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 07, 2002 6:42 PM
Subject: [JBoss-user] Logging from within EJBs
Hello!
I want so
Hi David,
I would think that RedHat 7.2's kernel is probably fully modular. I
simply put the following into my /etc/modules file:
ipt_MASQUERADE
ipt_REJECT
ipt_REDIRECT
ipt_TCPMSS
ip_conntrack
And then you should be able to use your redirect statements, as
below. Unfortunately it will only wo
I'm obviously a newbie to JBoss/Jetty. Excuse me
if this post
would be better posted elsewhere but I would greatly
appreciate
any thoughts on the following
problem:
I'm running Redhat 7.2 which has IPCHAINS enabled by
default. I'vetried the suggestions for redirecting traffic
(http://
Hello!
I want some of the events in the life of my EJBs to be logged at debug
level. The usual way to get an instance of Logger
class ProjectBean ...
{
...
private Logger logger = Logger.getLogger(ProjectBean.class);
}
and invokation of
if (logger.isDebugEnabled())
{
logger.deb
Hi!
Thanks for your tip, but I've already done so. The server log does not
show any stack trace. I have the feeling that the error occurs
somewhere between the client application and the EJB within the
server.
Also, in the ejbCreate method of the affected EJB, I have a logging
statement as the f
Look in the server.log file on the server for the server side
stacktrace; it may help.
-dain
Dimitri PISSARENKO wrote:
> Hello!
>
> I've a BMP entity bean, and when I try to create a new instance of
> this bean (that is, a new record in the database by calling the create
> method of the home i
Hello!
I've a BMP entity bean, and when I try to create a new instance of
this bean (that is, a new record in the database by calling the create
method of the home interface), I get the following exception:
javax.ejb.CreateException: General error
at
sun.rmi.transport.StreamRemoteCall.ex
Yep, I noticed as well that the forums availability has not been optimal
lately ;-)
Regards,
Cor.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Stephen J.
Thompson (CaSS)
Sent: Sunday, July 07, 2002 17:58
To: [EMAIL PROTECTED]
Subject: [JBoss-user]
Hello all,
Is anyone else having problems accessing the forums on the jboss home
site?
Regards,
Stephen.
signature.asc
Description: This is a digitally signed message part
That was the problem: the jboss-transaction-client.jar file was not in the class path.
I added it in the build.xml file and now it works.
Pablo.
On Sunday 07 July 2002 12:48, David Jencks wrote:
> The tm is in a separate module in 3.1. Do you have it? If this is a client,
> is jboss-transact
On Sat, 6 Jul 2002, Bill Burke wrote:
> This may or may not work never tried it.
>
> http://www.jboss.org/demos/netboot.jsp
actually i'd only need to have a "centralized" installation within one
machine using only the local filesystem.
--
aspa
-
The tm is in a separate module in 3.1. Do you have it? If this is a client,
is jboss-transaction-client.jar on the classpath?
david jencks
On 2002.07.07 09:58:20 -0400 Pablo Pita Leira wrote:
>
> Again, another problem with the CD collection example from CVS.
>
> I removed the element in jbo
Again, another problem with the CD collection example from CVS.
I removed the element in jboss.xml. The ejbs in cd.jar deployed
successfully.
When runing the upload client, it failed in JBoss 3.1.alpha. The upload is fine with
JBoss-3.0.0.
[java] Exception in thread "main" java.lang.
Hi
-
I have just completed the next generation of the Resin plugin. This new Resin plugin
integrates JBoss 3.0.0 with Resin 2.1.2 (meaning same
VM). There is a version of the Resin plugin for Resin 2.0.5 and JBoss 3.0.0. Also, there is an existing Resin plugin that integrates JBoss
2
21 matches
Mail list logo
