JBoss daily test results
SUMMARY
Number of tests run: 63
Successful tests: 61
Errors:1
Failures: 1
[time of test: 19 October 2001 4:35 GMT]
[java.version: 1.3.1
JBoss daily test results
SUMMARY
Number of tests run: 63
Successful tests: 61
Errors:1
Failures: 1
[time of test: 19 October 2001 3:58 GMT]
[java.version: 1.3.1
JBoss daily test results
SUMMARY
Number of tests run: 63
Successful tests: 61
Errors:1
Failures: 1
[time of test: 19 October 2001 3:22 GMT]
[java.version: 1.3.1
JBoss daily test results
SUMMARY
Number of tests run: 63
Successful tests: 59
Errors:2
Failures: 2
[time of test: 19 October 2001 2:54 GMT]
[java.version: 1.3.0
User: starksm
Date: 01/10/18 18:20:26
Modified:src/main/org/jboss/configuration ConfigurationService.java
Log:
Only use the property editor if it is not null
Revision ChangesPath
1.40 +7 -3 jboss/src/main/org/jboss/configuration/ConfigurationService.java
Excellent, that was the sort of reply I was hoping for.
thanks again,
dim
On Thu, 18 Oct 2001, Scott M Stark wrote:
> The problem is that JMS has no real notion of security. You can provide
> a username and password when obtaining a connection but this is
> the extent of JMS security. There i
confirm 694441
_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listin
Fixed in 2.4.4 and mainline. That is, the cache insertion problem.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ole
> Husgaard
> Sent: Thursday, October 18, 2001 12:49 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] Bug in cache
>
>
> Hi,
>
Change Notes item #472557, was opened at 2001-10-18 13:50
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=472557&group_id=22866
Category: None
Group: v2.4.4
Status: Open
Priority: 5
Submitted By: Bill Burke (patriot1burke)
Assigned to: Nobody/Anonymous (n
User: patriot1burke
Date: 01/10/18 13:46:30
Modified:src/main/org/jboss/ejb/plugins
EntitySynchronizationInterceptor.java
EntityInstanceInterceptor.java
Log:
code was incorrectly locking bean and inserting bean in invokeHome even if th
User: patriot1burke
Date: 01/10/18 13:32:39
Modified:src/main/org/jboss/ejb/plugins Tag: Branch_2_4
EntitySynchronizationInterceptor.java
EntityInstanceInterceptor.java
Log:
code was incorrectly locking bean and inserting bean in invok
I was going to write a detailed email on Monday detailing how to use this
stuff. I'll send you info offline Anatoly if you can't wait until then. I
wanted to massage the code a little before Monday.
This stuff will not work with 2.4.x.
Bill
> -Original Message-
> From: [EMAIL PROTECTE
Hi,
This message is to Sacha and Bill, primarily. Some people in my research
group are starting to look into issues that tie into clustering somewhat
and they want to start playing with the HA stuff. Can you, please, provide
some sort of pointers on how to get your current HA implementation up a
User: vharcq
Date: 01/10/18 13:03:42
Modified:src/etc/conf/default standardjboss.xml
Log:
locking-policy tag is only for entity beans
Revision ChangesPath
1.21 +1 -2 jboss/src/etc/conf/default/standardjboss.xml
Index: standardjboss.xml
> Thanks, I realize it has always been like this... glad to see
> it is the
> default in ejb2.0
Actually you can't turn it off. This is a side affect of the eager/lazy
loading feature where we may not have all the data to do a complete update.
-dain
___
Hi,
org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock
is present for stateful beans on standardjboss.xml for 3.0 but not for
2.4.
>From the sources it is not used for stateful session beans.
Can we remove this line from 3.0 ?
Regards.
___
Jboss-devel
User: mnf999
Date: 01/10/18 11:40:43
Modified:src/docs/common doco.jsp
Log:
Revision ChangesPath
1.2 +3 -3 newsite/src/docs/common/doco.jsp
Index: doco.jsp
===
RCS file: /cvsroot/jboss
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Thursday, October 18, 2001 1:09 PM
|To: Jboss-Development@Lists. Sourceforge. Net
|Subject: Re: [JBoss-dev] Tuned-updates OFF?
|
|
|tuned-updates has been false since this file was
User: mnf999
Date: 01/10/18 11:40:43
Modified:src/docs/jbossgroup services.jsp
Log:
Revision ChangesPath
1.7 +10 -0 newsite/src/docs/jbossgroup/services.jsp
Index: services.jsp
===
RCS
User: mnf999
Date: 01/10/18 11:40:42
Modified:src/docs binary.jsp
Log:
Revision ChangesPath
1.11 +10 -0 newsite/src/docs/binary.jsp
Index: binary.jsp
===
RCS file: /cvsroot/jboss/newsite
http://www3.flashline.com/components/View.jsp?sid=1003424992671-1091351083-5
0&prodid=4252
JBoss documentation available at Flashline
We included ALL THE AVAILABLE DOCUMENTATION in one convenient
download bundle. The bundle contains ALL the file formats you can use:
- Full JBoss documentation in
-Ursprüngliche Nachricht-
>Von: David Jencks [mailto:[EMAIL PROTECTED]]
>Gesendet: Donnerstag, 18. Oktober 2001 17:36
>An: [EMAIL PROTECTED]
>Betreff: Re: [JBoss-dev] JMX detaching of invokers (RH/3.0)
>There is always a balance to be struck between on the one hand greater
>generality and
User: starksm
Date: 01/10/18 10:09:33
Modified:src/etc/conf/default standardjaws.xml
Log:
Enabled tuned-updates by default
Revision ChangesPath
1.22 +2 -2 jboss/src/etc/conf/default/standardjaws.xml
Index: standardjaws.xml
==
User: starksm
Date: 01/10/18 10:07:53
Modified:src/etc/conf/default Tag: Branch_2_4 standardjaws.xml
Log:
Enabled tuned-updates by default
Revision ChangesPath
No revision
No revision
1.15.4.1 +1 -1 jboss/src/etc
On Thu, 18 Oct 2001, jp Morgan wrote:
> I have a set of jars my ejb whose classes my ejb
> calls. Where do I put these jars in the jboss
> directory tree.
> Should they go in lib or lib/ext or deploy/lib. I put
> the jdbc driver jar jconn2.jar in lib/ext but for any
> other jars created from e
tuned-updates has been false since this file was checked into sourcefourge
as the
1.1 release has this:
Hypersonic
Hypersonic SQL
true
false
false
false
300
...
I'll set the default to true.
Scott Stark
Chief Techn
The fix is in EntityInstanceInterceptor.invokeHome. It is inserting the
bean in the cache in a finally block. It should check to see if an
exception was thrown before inserting the bean into the cache. I'll fix
this on 2.4.4 and 3.0.
Bill
> -Original Message-
> From: [EMAIL PROTECTED
CMP just shouldn't update primary keys.
- Original Message -
From: "Bill Burke" <[EMAIL PROTECTED]>
To: "Jboss-Development@Lists. Sourceforge. Net"
<[EMAIL PROTECTED]>
Cc: "Jaws@Kpi. Com. Au" <[EMAIL PROTECTED]>
Sent: Thursday, October 18, 2001 11:17 AM
Subject: [JBossCMP] RE: [JBoss-dev]
I have a set of jars my ejb whose classes my ejb
calls. Where do I put these jars in the jboss
directory tree.
Should they go in lib or lib/ext or deploy/lib. I put
the jdbc driver jar jconn2.jar in lib/ext but for any
other jars created from existing application I do not
know. The documentation i
Hi,
Seems that we have a entity bean cache bug in both the
stable and development series that affects both BMP and
CMP entity beans.
This was originally reported as bug #463548 for the stable
series, and I have created a test for it with BMP in the
development series. (Please note that if the ca
More than thatBecause of our ignorance on DB schema design back in
March, we almost didn't use JBoss because tuned-updates were OFF by default
which caused updates of PrimaryKeys which caused DB deadlock all over the
place in our application.
For CMP 2.0, I'm remember that tuned-updates are a
I am looking at the new configuration files in 2.4.1 and it seems that the
CMP engines come with tuned-updates turned OFF by default.
Why is this? I suspect there is a reason but can't think of it off the top
of my head.
I strongly recommend turning this on as people will see a sharp drop in
pe
There is always a balance to be struck between on the one hand greater
generality and flexibility with less compile-time type checking and less
speed, and on the other hand a more specific solution that can be checked
more by the compiler and includes scenario-specific optimizations. We have
some
It is
not in cvs but afaik Scott and juha did some work on it.
We
will discuss in Las Vegas and do a clean integration don't
worry.
By
x-mass we will be done
marcf
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bill
BurkeSent: Thur
Jiri Luzny wrote:
> They don't call the Transaction stuff directly.
> They
> a) register a listener to TransactionManager to be notified about
> the events
> b) use a connection from a connection pool
> (org.jboss.jdbc.XADataSourceLoader) for commit/rollback/close...
>
> So Toplink just call
Is this in CVS
yet? I have a strong feeling that this affects the clustering work Sacha
and I have done. If it is in CVS, can somebody point me to the relevant
code? If not, can somebody email me some code so that I can develop an
understanding of it?
Thanks,
Bill
User: mnf999
Date: 01/10/18 07:14:05
Modified:src/docs index.jsp
Log:
Revision ChangesPath
1.21 +1 -1 newsite/src/docs/index.jsp
Index: index.jsp
===
RCS file: /cvsroot/jboss/newsite/sr
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jung
|, Dr. Christoph
|Sent: Thursday, October 18, 2001 4:25 AM
|To: Jboss-Development (E-Mail)
|Subject: AW: [JBoss-dev] JMX detaching of invokers (RH/3.0)
|
|
|Hello Marc & others,
|
|I would like to p
User: mnf999
Date: 01/10/18 06:51:22
Modified:src/docs index.jsp
Log:
Revision ChangesPath
1.20 +10 -1 newsite/src/docs/index.jsp
Index: index.jsp
===
RCS file: /cvsroot/jboss/newsite/sr
User: cgjung
Date: 01/10/18 05:08:34
Modified:jetty/src/main/org/jboss/jetty JettyService.java
Log:
switched jetty.properties syntax back to *nix
JettyService now accepts and translates both *nix and WinX path
syntax for Jasper.
Revision ChangesPath
1.25 +3
User: cgjung
Date: 01/10/18 05:08:33
Modified:jetty/src/etc jetty.properties
Log:
switched jetty.properties syntax back to *nix
JettyService now accepts and translates both *nix and WinX path
syntax for Jasper.
Revision ChangesPath
1.5 +1 -1 contrib/j
Ok, then I´ll implement a tiny adaptor for that. What would be the right
default
format in the tc_path_add property ... Unix or WinX?
It´s Jasper that uses the tc_path_add property to extend its classpath just
for compilation
purposes (calls the embedded compiler with explicit, string-based argum
On Thursday 18 October 2001 09:57, Jung , Dr. Christoph wrote:
> I fixed this in jetty.properties, although I´m not sure whether exchanging
> the ":" with ";" in the
> compiler-classpath specification is platform-neutral?
>
> CGJ
>
It appears that it isn't. Windows might use ";". On Linux I had t
On 18 Okt, Scott M Stark wrote:
> My source tell me that these two standard intitiatives will for the basis
> for J2EE
> security in the future. Take a look at them and see how that affects your
> design.
>
> http://www.oasis-open.org/committees/security/
At least S2ML was integrated with an LDA
On 18 Okt, Scott M Stark wrote:
> The problem is that JMS has no real notion of security. You can provide
> a username and password when obtaining a connection but this is
> the extent of JMS security. There is no defined mechanism for propagating
> the user identity as part of the message.
>
> I
It ended up being a bug in Jetty. For form based auth, jetty doesn't
call user.authenticate() (except on the first login post) and so it
doesn't associat a subject with activeSubject in the security manager.
So when it tries to authorize the user in the role, the subject is null
and so it fails.
My source tell me that these two standard intitiatives will for the basis
for J2EE
security in the future. Take a look at them and see how that affects your
design.
http://www.oasis-open.org/committees/security/
http://www.oasis-open.org/committees/xacml/
As for where to the DirContext naming st
The problem is that JMS has no real notion of security. You can provide
a username and password when obtaining a connection but this is
the extent of JMS security. There is no defined mechanism for propagating
the user identity as part of the message.
I think its rather poor myself. I would be in
On 17 Okt, Scott M Stark wrote:
> We do need a centralized notion of user, authentication and authorization
> and profiles. Our current fragmented notion does not make any sense
> administratively.
Nod.
>
> Basically we want a single API and administrative interface for the
> following
> 1. Who
User: kimptoc
Date: 01/10/18 01:27:42
Modified:src/etc/conf/default log4j.properties
Log:
added date/time to the default log output for the server
Revision ChangesPath
1.13 +3 -3 jboss/src/etc/conf/default/log4j.properties
Index: log4j.properties
==
Hello Marc & others,
I would like to pose another issue in revisiting the invocation-handler
chain to public discussion, that is the
separation of "Invoker" into "Invoker" and "ArgumentDeserializer".
That is, we use sometimes very particular (de-)serialisation routines
(XML<->Java as well as RM
There are many testcases for security in the jbosstest unit tests and 2.4.3
works fine. Look at those and if you think you really have a bug post
an example to sourceforge.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Messa
I fixed this in jetty.properties, although I´m not sure whether exchanging
the ":" with ";" in the
compiler-classpath specification is platform-neutral?
CGJ
-Ursprüngliche Nachricht-
Von: Andreas Schaefer [mailto:[EMAIL PROTECTED]]
Gesendet: Samstag, 13. Oktober 2001 18:26
An: [EMAIL
On 17 Okt, Scott M Stark wrote:
> - Original Message -
> From: "Peter Antman" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, October 17, 2001 7:42 AM
> Subject: [JBoss-dev] Tomcat security/LdapLoginModule
>
>
>> Hi (mostly Scott I guess),
>>
>> I have been experimenting
54 matches
Mail list logo
