Maffeo, check that your category elements precede the root element.
---
A different problem I have been experiencing with 3.2.2RC3
(yes, I know I should upgrade) is log4j logging intermittently
failing to log after initial boot. There is output in the log
up to the point where my own
Maffeo, check that your category elements precede the root element.
---
A different problem I have been experiencing with 3.2.2RC3
(yes, I know I should upgrade) is log4j logging intermittently
failing to log after initial boot. There is output in the log
up to the point where my own
Hi, Thaer, welcome to the list. Here is my attempt at the simplest possible
explanation of how to create a JBoss web application.
1.) Download JBoss 3.0.x and unzip or untar it.
2.) Go to the bin directory and run JBoss (run.bat or run.sh file). Just
type ./run on the command line. This will
In each EJB jar file, add the following line to your manifest.mf file:
Class-Path: ./ext/MyServerLib.jar
You can then put the classes that are shared by the EJBs into
this MyServerLib.jar file, which you deploy to JBOSS_HOME\deploy\ext.
--- Original Message -
Message: 3
Hi Dimitri,
In my opinion, you will end up with too many classes
using a class per query approach. I would recommend
instead the following approach:
1.) Define an interface for all queries
(e.g., ProjectManagementSQL_IF).
Each query would be a function in this interface
(e.g.,
We are using JBoss with Oracle 9i RAC. To get transparent failover and load
balancing between the RAC servers, we probably need to use the OCI JDBC
driver. Up to now, we have only been using the thin JDBC driver. Does
anyone have experience with this driver? Does it perform as well as the
Instructions to create the J2eeRiServices for Sun J2EE CAS COM-bridge may be
found at:
http://laurent.etiemble.free.fr/combridge/index.html
There is a binary as well that one can download:
http://laurent.etiemble.free.fr/combridge/combridge_30.html
This includes the source files.
Haven't tried
An Active Server Page can make a SOAP RPC call using the new .NET stuff,
which calls a network service. JBoss can expose EJBs as network services
using JBoss.net (see http://www.jboss.org/developers/jboss-net.jsp). It is
still alpha code, so you might not want to use it in production status
See the story of the badly translated Japanese video game
All Your Base Are Belong to Us at
http://www.planettribes.com/allyourbase/story.shtml
-Original Message-
From: Sacha Labourey [EMAIL PROTECTED]
To: Dain Sundstrom [EMAIL PROTECTED],
marc fleury [EMAIL PROTECTED]
Cc:
I forgot to mention to be sure to see the video:
http://www.planettribes.com/allyourbase/AYB2.swf
Maybe only after seeing this video can one
understand the cult phenomenon of All Your Base.
___
JBoss-user mailing list
[EMAIL PROTECTED]
Hi Eric,
Um, the answer is probably not, but you can reference another jar file by
adding something like the following to your manifest.mf file:
Class-Path: ./ext/MyCustSpecific.jar
In this case, one puts the MyCustSpecific.jar file in deploy/lib to indicate
it is not one of the normal ejb jar
The idea of prepared statements is to be able to use the same prepared
statement over and over again many times. However, the convention in
bean-managed entity beans is to get a connection (presumeably from the
connection pool), use it, and then close it in each method, which means the
prepared
The idea of prepared statements is to be able to use the same prepared
statement over and over again many times. However, the convention in
bean-managed entity beans is to get a connection (presumeably from the
connection pool), use it, and then close it in each method, which means the
prepared
If you really and truly need them, the runtime exceptions can be caught in
your session bean. When you catch a runtime or system exception, then
translate it to an application exception (i.e., just throw a type of
exception you have defined yourself). That type of exception should be
passed
Some advantages of session beans:
1.) Access via RMI. No need for a web server. You can use a Java
thin-client approach. The client is mainly user-interface code. The
session beans contain
some business logic and make use of data access objects that interface to
your legacy application.
Check out the free utility from IBM (Websphere/DB2-specific, but possibly
useful elsewhere; no source code for the tool is provided):
http://www-106.ibm.com/developerworks/java/library/co-ejbmkr/index.html?dwzo
ne=java
http://www.alphaworks.ibm.com/tech/ejbmaker
- Original Message -
I need some advice on how to deploy Jive in the Jboss-Jetty combo. I can
see from previous emails that Lionel built a jive.war file and put it in
jboss\deploy. But he is using Tomcat with Jboss. Is that also the best way
to do it with Jboss-Jetty?
I'm a total beginner with respect to
17 matches
Mail list logo
