Title: Message
I
don't think you need the "./" in the path. Just the JAR
names.
--
Danny Yates
-Original Message-From: Bill Milbratz
[mailto:[EMAIL PROTECTED] Sent: 22 September 2003
18:00To: '[EMAIL PROTECTED]'Subject:
[JBoss-user] "could not be found": jar in .ear
Title: Exception Sorter Information
Hi All,
I have implemented an ExceptionSorter for my AS400 connection.
The reconnect works, eventually, but only after it fails one time to recreate the connection.
In other words, when the connection is lost, I get an error when reusing the connection.
No,
Each and every ear file has a file called application.xml. This file contains
the modules to deploy
The order in which you specify the modules is the order in which they will be
deployed
Regards,
Stephane
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Hi all,
I'm really sitting with a huge issue here. The managers here(who have minimal IT
experience) have opted to do a code migration of their existing
legacy code written in PICK, a COBOL/QBASIC mix.
There's like hundreds of 100's of lines of code there, and a lot of business rules and
logic
[EMAIL PROTECTED] writes:
Hi all,
I have a sar file which depends on classes in my ejb jar file.
I would like to package them both in a single ear file. But, I have read
somewhere that the default deployment order is:
sar, jar, war
Is this true? Or can I modify this in the
On Tue, 2003-09-23 at 07:44, Muraly R wrote:
Hi Gurus,
The error I am facing on my web side is:
ERROR 17/Jul/2003 15:07:36 [Thread-32] (MonWizardData.java:416):
web.MonPolicyWizardServlet$1 - java.rmi.NoSuchObjectException: Could
not activate;
The problem is the web is having reference to
Yes, it is. There is only one log4j configuration available in JBoss as it is
a singleton (and thus global to the whole JVM that hosts JBoss).
This is a problem which is quite annoying, I don't know if there is a clear
solution to this
check $JBOSS_HOME/server/default/conf/log4j.xml and the
This has been fixed for 3.2.2
The connection close processing does not happen until
end of transaction.
You can turn it off by setting spec compliance to true
on the CachedConnectionManager in transaction-service.xml
Regards,
Adrian
On Tue, 2003-09-23 at 08:17, rajeshnn wrote:
Hi
I am trying
Can you allow me to include your sorter in the jboss distribution?
Regards,
Adrian
On Tue, 2003-09-23 at 10:30, Ricardo Coutinho wrote:
Hi All,
I have implemented an ExceptionSorter for my AS400 connection.
The reconnect works, eventually, but only after it fails one time to
recreate the
Title: error while trying to open a new connection
Hi All
While trying to create a new connection before closing an existing connection
the following error occured.
Can anyone pls help..
java.lang.IllegalStateException: Trying to return an unknown connection2!
Title: RE: [JBoss-user] Exception Sorter Information
No problem.
However I am not sure if it is functioning correctly. As I said I get an exception from the container on the first re-use of the connection after it was cut and after that it works okay.
For my client application this is
On Tue, 2003-09-23 at 16:05, Ricardo Coutinho wrote:
No problem.
However I am not sure if it is functioning correctly. As I said I get
an exception from the container on the first re-use of the connection
after it was cut and after that it works okay.
For my client application this is
Title: Message
Adrian is the best AS400 programmer in UK, so don't worry
;)
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ricardo
CoutinhoSent: mardi, 23. septembre 2003 17:06To:
[EMAIL PROTECTED]Subject: RE: [JBoss-user] Exception
You'll have to provide some more information.
It says you are closing a connection that it does not know about
were there previous errors?
There has been some cleanup of the error checking in the 3.2.2RC
releases can you check if you still have the problem with 3.2.2RC4?
This actual error
On Tue, 2003-09-23 at 17:18, Ricardo Coutinho wrote:
Hi Adrian,
It is likely there are other connections still in the pool that are
also
invalid if the problem is due a temporary outage.
I understand the underlying connection being closed when I return
true, it make sense. What I don't
Hi,
I am trying to get the generated wsdl to use the host name instead of
localhost.
?xml version=1.0 encoding=UTF-8 ?
- wsdl:definitions
targetNamespace=http://localhost:8080/jboss-net/services/reportserver;
xmlns=http://schemas.xmlsoap.org/wsdl/;
I've been unable to get the TrivalDavFilter to work. I copied netboot.war to
the deploy directory, but the org.mortbay.http.handler.ResourceHandler class
rejects the PROPFIND with a 405 error before the filter ever gets a chance
to handle the request.
How is Jetty configured to allow this filter
Hello list,
apparently LIMIT and OFFSET clauses in JBossQL only accepter parameters (?x)
and not fixed values. Can you confirm?
If not could you provide me an example where fixed values are used (Xdoclet
would be great)
Regards,
Stephane
winmail.dat
Could someone post a simple (complete) CMP example using Xdoclet
postgresql-fetch-seq where by the database auto-increments the PK? I've
been struggleing with this for a few hours and can't seem to get my EJBs
to behave properly using the correct combination of @ejb and @jboss tags.
JBoss
Maybe you could consider first processing your source files with Velocity
and then calling Xdoclet.
Joachim
- Original Message -
From: Matthew Hixson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 23, 2003 2:19 AM
Subject: [JBoss-user] specifying a variable in xdoclet
You'll want to put this at the top of your entity bean.
* @jboss.entity-command
* name=postgresql-fetch-seq
and then for your primary key getter:
/**
* @ejb.interface-method
* @ejb.pk-field
* @jboss.persistence
* auto-increment=true
*
Hi Stephane, that is correct. Hardcoded values are not allowed in
LIMIT or OFFSET clauses up to and including 3.2.2RC3, as far as I know.
-M@
On Tuesday, September 23, 2003, at 03:39 PM, Stephane Nicoll wrote:
Hello list,
apparently LIMIT and OFFSET clauses in JBossQL only accepter
22 matches
Mail list logo