Adrian Brock wrote:
> I managed to reproduce the problem of double deployment caused by an
> entry in MANIFEST.MF using a previous snapshot of CVS HEAD.
> My fix from last weekend solves it, at least for the problem I saw.
>
> Regards,
> Adrian
>
Hi Adrian,
although the system having the above
I managed to reproduce the problem of double deployment caused by an
entry in MANIFEST.MF using a previous snapshot of CVS HEAD.
My fix from last weekend solves it, at least for the problem I saw.
Regards,
Adrian
>From: "Adrian Brock" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL
Title: Message
HI
Edward,
I am
giving the RELEVANT code snippet here:
package com.cadmus.rpm.server.util;
import
org.apache.xerces.parsers.DOMParser;import org.w3c.dom.Document;import
org.w3c.dom.NamedNodeMap;import org.w3c.dom.Node;import
org.w3c.dom.NodeList;import org.w3c.dom.Attr;
Hi Saroj,
Thanks a million, you have set me on the right path my man.
my work includes parsing an xml file, read the settings within it, and then configure an object based on the entries in the xml file, as u may have noticed I am new to xml, but I love it and everything it represents, I just have
Jon Haugsand wrote:
> ERROR at line 1: ORA-01830: date format picture ends before
> converting entire input string
>
> (Because the stupid Oracle system does not like to get date strings
> in any other format than is defined in the initora8.ora file:
> nls_date_format = "-MM-DD")
This a
I fixed a similar problem last weekend, where it was possible for
a sub-deployment to get deployed twice.
The problem I saw wasn't due to manifest entries, but these are
sub-deployments. I'll try this exact case.
Regards,
Adrian
>From: Michael Bartmann <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROT
This I'll have to try to reproduce.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: "Michael Bartmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 31, 2002 6:31 AM
Subject: Re: [JBo
* Jon Haugsand
> With JBoss 3.0.1, CMP 2.0 and oracle.jdbc.driver.OracleDriver (Oracle DB
> 8.1.7) we try to map Timestamp-attributes to Oracle Date. We have no
> problems with Timestamp and the Borland server.
>
>
> The error message is as follows:
>
> 15:00:08,254 ERROR [Pant] Could not crea
David Jencks wrote:
> On 2002.08.31 08:12:17 -0400 Michael Bartmann wrote:
>
>>David Jencks wrote:
>>
>>
>>>The message warns you that if your transaction fails your data may be
>>
>>left
>>
>>>in an inconsistent state. You have more than one participant in a jta
>>>transaction, but one of them
want to add this:
Each class of the package for which package private access failed
was in the same single jar.
Michael
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.in
With JBoss 3.0.1, CMP 2.0 and oracle.jdbc.driver.OracleDriver (Oracle DB
8.1.7) we try to map Timestamp-attributes to Oracle Date. We have no
problems with Timestamp and the Borland server.
The error message is as follows:
15:00:08,254 ERROR [Pant] Could not create entity
java.sql.SQLException
Scott M Stark wrote:
> Yes, the only way you can guarentee package private access is to
> include the classes from the package in the same jar. See bug #602828.
>
They *were* in one jar, but this jar was references from more than
one MANIFESTs -> booom.
I think the problem is that not the per-ja
Hi everybody,
no bugs this time; I have bothered you with many problems,
I think now its time for a JBoss success story.
The technology vision I had (and of which I knew it could
only become true with JBoss 3) finally succeded. What
my co-workers and I got working at 4Production is:
A fully mod
On 2002.08.31 08:54:02 -0400 Marius Kotsbak wrote:
> David Jencks wrote:
>
> >The message warns you that if your transaction fails your data may be
> left
> >in an inconsistent state. You have more than one participant in a jta
> >transaction, but one of them only supports local transactions wit
David Jencks wrote:
>The message warns you that if your transaction fails your data may be left
>in an inconsistent state. You have more than one participant in a jta
>transaction, but one of them only supports local transactions without two
>phase commit.
>
Is two phase commit needed when JMS i
Yes, the only way you can guarentee package private access is to
include the classes from the package in the same jar. See bug #602828.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: "Michael Bartmann" <[
On 2002.08.31 08:12:17 -0400 Michael Bartmann wrote:
> David Jencks wrote:
>
> > The message warns you that if your transaction fails your data may be
> left
> > in an inconsistent state. You have more than one participant in a jta
> > transaction, but one of them only supports local transaction
Scott M Stark wrote:
> Its not an issue of visibility, its that two classes from the same package
> can be loaded by different class loaders and package private access
> fails. I have seen this and the easiest way to cause it is to split the package
> classes across two jars. An ear should use a c
David Jencks wrote:
> This is on a jboss 3 version, right?
This is on a two weeks old version of Branch_3_2 (after
the arrayclass-fix)
>
> I'm very surprised. Everything in your .ear should be visible to
> everything else: it should all be loaded by classloaders in one loader
> repository.
Ever
Its not an issue of visibility, its that two classes from the same package
can be loaded by different class loaders and package private access
fails. I have seen this and the easiest way to cause it is to split the package
classes across two jars. An ear should use a common class loader across
all
David Jencks wrote:
> The message warns you that if your transaction fails your data may be left
> in an inconsistent state. You have more than one participant in a jta
> transaction, but one of them only supports local transactions without two
> phase commit.
It does not warn when both partici
This is on a jboss 3 version, right?
I'm very surprised. Everything in your .ear should be visible to
everything else: it should all be loaded by classloaders in one loader
repository.
Can you supply a minimal example, preferably as a testcase in the
org.jboss.test.classloader.test package?
Th
[EMAIL PROTECTED] wrote:
>>When I got back form XA-tx-JMS to local-tx-JMS these messages went away.
>
> But what is the consequece of doing that? I think you then miss the transactions
>involving both JMS and DB. A better solution is to use a XA-enabled datasoure.
Ok, I should have made this c
The message warns you that if your transaction fails your data may be left
in an inconsistent state. You have more than one participant in a jta
transaction, but one of them only supports local transactions without two
phase commit.
The warning might be excessive at this point since in order to
Title: Message
Hi
Edward,
I am
having my xml in jar and need to read this once the bean is invoked in a
DOM Tree.
Code
is :
InputStream fi =
this.getClass().getClassLoader().getResourceAsStream(xmlFile) ; // xmlfile
is name of
file
InputStreamReader isr = new
I
hello,
could you pls tell me more about your xml file like its location and any more info , I would be very grateful , I am working on something similar too,
thanks in advance
Edward.
Saroj Kumar <[EMAIL PROTECTED]>wrote:
Hi All,I have fixed this. Just made the method an instance method from sta
Hi All,
I have fixed this.
Just made the method an instance method from static method and used.
InputStream fi =
this.getClass().getClassLoader().getResourceAsStream(xmlFile) ;
Then, I removed the DOCTYPE from the XML File and it works.
-Saroj
-Original Message-
From: [EMAIL PROTECT
On Sat, Aug 31, 2002 at 08:16:28AM +0200, Michael Bartmann wrote:
> G.L. Grobe wrote:
> > Anyone know what this warning means? It doesn't seem to be affecting my
> > app and the update actually works. This update is done within a MDB.
> >
> > 23:09:29,546 WARN
> > [LocalTxConnectionManager$L
On Fri, Aug 30, 2002 at 01:22:26PM -0300, Emerson Cargnin - SICREDI Serviços wrote:
> ok, people, but expose your context,
boostcom.no
> number of clients,
about 1-3 at the same time
> hardware and
Pentium 3 800
> software configuration,
SuSE linux
it could be helpful for all of us.
>
> San
×ð¾´µÄÁìµ¼£º
ÄúºÃ£¡ÎÒÊÇÒ»ÃûÍøÂçÓªÏú¹¤³Ìʦ£¬Ö÷ҪΪ¹¤ÒµºÍÉÌÒµÆóÒµ¿ª·¢µç×ÓÉÌÎñ¡¢ÍøÂçÓªÏúϵͳ£¬²¢ÔÚÕâÁìÓòСÓн¨Ê÷¡£Äú¿ÉÄÜÒѾ½¨ÉèÁË×Ô¼ºµÄÆóÒµÍøÕ¾£¬²¢Ï£Íû¼®´Ë×÷ΪÆóÒµÐÎÏóÐû´«¡¢²úƷչʾºÍÏúÊÛµÄÒ»¸ö´°¿Ú£¬ÎªÁËÕâ¸öÄ¿±êÄú¿ÉÄÜÒѾͶÈëºÜ¶à£¬µ«²¢²»¼ûʵÖÊÐÔµÄЧÒ棬Èç¹ûÄúÓÐÕâ·½ÃæµÄÀ§ÈÄ£¬ÄÇôÎÒ¼°ÎÒËù¿ª·¢EC-SYST
AFAIK, Jetty is compliant.
Is your webapp ? - this would cause it to use my new
distributable session manager, which may be the problem.
As a workaround increase the session-timeout.
If, after testing you are convinced that Jetty is at fault, take your
problem to [EMAIL PROTECTED] - I'm away
Hello,
Can you please provide us with:
- the version (3.0.2, 3.2beta, HEAD, etc.)
- the client code and any config file
- the stack trace
Cheers,
Sacha
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De
32 matches
Mail list logo
