Number of tests run: 883
Successful tests: 877
Errors:2
Failures: 4
[time of test: 14 August 2002 0:53 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
Jetty makes an effort to avoid flushing the buffer - as this is not
very network efficient.
For example, if the includer has called getWriter and the includee also calls
getWriter, then their is no need to flush before the include.
cheers
Alex Sumner wrote:
Seems to be a Jasper thing,
Already in CVS.
cheers
PS. don't blow away Marc's jasper hack in JBoss
Jules Gosnell wrote:
Guys,
I reproduced the problem on JBoss-3.0.1 easily, added Greg's fixes to
the Jetty component and could not then reproduce the Exception.
Greg, If you stick this into Mort Bay Jetty cvs (or
Bugs item #594978, was opened at 2002-08-14 11:39
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=594978group_id=22866
Category: JBossCMP
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andreas Billmann (frosch95)
Assigned to:
These two changes have made my example work without the interrupts.
What's the procedure for changing Jetty? Should I check these in? Jules?
Wait for a new Jetty?
thanks
david jencks
On 2002.08.13 04:57:18 -0400 Greg Wilkins wrote:
David,
thanks for the detailed analysis of this.I
Bugs item #594596, was opened at 2002-08-13 15:44
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=594596group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Deleted
Resolution: Rejected
Priority: 1
Submitted By: Nir Oren (jhudsy)
Assigned to:
Greg,
Already in CVS.
cheers
PS. don't blow away Marc's jasper hack in JBoss
You wrote it :) Hey the other day I was at this Sabre division and one
of the things they were asking about is precompiled JSP, I didn't know
you had commited the fix for live deployment, it is really useful.
I meant the hack I did for Marc.
I have raised a bug against the jasper people for it - but I have
seen no action from them yet.In fact they have 290+ open bugs
against tomcat/jasper and not much action on any of them!
The hack is in the jboss jetty tree, but not in the main jetty tree.
Which Branch[es] do you think that I should update? I'm getting confused
about how many there are.
I figure :
HEAD
Branch_3_2
JBoss_3_0_1
any more ?
Let me know and I will merge an up-to-date Jetty into all of them today.
Jules
David Jencks wrote:
These two changes have made my example
I've pretty much given up on working on anything but head.
I think your list of branches is complete.
david
On 2002.08.14 10:36:11 -0400 Jules Gosnell wrote:
Which Branch[es] do you think that I should update? I'm getting confused
about how many there are.
I figure :
HEAD
Branch_3_2
Are you using custom primary key classes? If so, make sure you have equals
and hashCode implemented correctly and that your PK class serializes
correctly as well.
What exactly is the JBoss 2.4 version you're converting from?
Thanks,
Bill
-Original Message-
From: [EMAIL PROTECTED]
I'm committing the latest Jetty onto HEAD as we speak.It includes the patch.
Jules
David Jencks wrote:
I've pretty much given up on working on anything but head.
I think your list of branches is complete.
david
On 2002.08.14 10:36:11 -0400 Jules Gosnell wrote:
Which Branch[es] do
Is the testsuite out of sync with the container, or the container broken ?
Or is xdoclet generating stuff which is no longer valid ?
Jules
running the WebIntegrationTestSuite :
17:19:18,041 INFO [MainDeployer] Starting deployment of package:
Someone just made the verifier stop deployments whenever it found an error.
Most of our ejb test packages have at least one error, so many tests fail.
Try setting
!--
StrictVerifier: Setting this to 'true' will cause all deployments
to fail when the Verifier detected a
JBoss_3_0_1 is a tag, the branch tag is Branch_3_0 and I think this
fix needs to be included there as there will be a 3.0.2 release.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Jules Gosnell [EMAIL
Patches item #595176, was opened at 2002-08-14 20:22
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376687aid=595176group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Bartmann (bartmann)
Assigned to:
the most important thing we can do now is recruit the next generation of
talent in JBoss. New versions (in this case 3.0) have always been the
way to recruit new developers.
To do so I have put the TODO-DEVELOPMENT forum list high up in the
forums listing. Please use it to post your ideas and
I've replaced the jdbc xa wrapper for jboss 4 (cvs HEAD) with an entirely
new version that is
--lgpl
--jca compliant
--easily extensible to counteract the quirks of vendor drivers.
However, I don't have any XADataSources to find out if it works. If you
have an XADataSource based driver,
Bugs item #595258, was opened at 2002-08-14 14:41
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=595258group_id=22866
Category: JBossCX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Bruce Schuchardt (bruceschuchardt)
OK.
I have a few other fixes to make to HEAD, then I will roll them all into
Branch_3_0.
What is your schedule for 3.0.2 ?
What about Branch_3_2 ?
Jules
Scott M Stark wrote:
JBoss_3_0_1 is a tag, the branch tag is Branch_3_0 and I think this
fix needs to be included there as there will
Jetty is used to implement JBossWeb.
Look in jbossweb.sar/META-INF/jboss-service.xml
Jules
Emerson Cargnin - SICREDI Serviços wrote:
We used to have many instances of jboss3.0.0 with tomcat in the same
machine (for developers). Now i'm trying to update to 3.0.1, but there's
no version
3.0.2 will be released Aug 24. A 3.2 beta will follow that in
a day or so.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Jules Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 14,
Another (additional) way would be to provide snappy and easy to read
introductions to the basic code layout in JBoss. I am a Java Certified
Programmer, so I know a little about Java, and I have coded many large
sites, but know little about JBoss. I came here to learn about a year ago
but
sites, but know little about JBoss. I came here to learn
about a year ago
but left, not feeling welcome. Not crying, just letting you
know. I have
you *are* crying. Look there are really 3 ways to get seriously into
the codebase.
1- Go dig bugs. You can't imagine the number that
Bugs item #595258, was opened at 2002-08-14 21:41
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=595258group_id=22866
Category: JBossCX
Group: v3.0 Rabbit Hole
Status: Pending
Resolution: None
Priority: 5
Submitted By: Bruce Schuchardt (bruceschuchardt)
Number of tests run: 891
Successful tests: 760
Errors:124
Failures: 7
[time of test: 15 August 2002 2:20 GMT]
[java.version: 1.3.1_03]
[java.vendor: Sun Microsystems
...cache from the EJB containers should be exposed as MBeans (name to
be discussed)
and the entries in the cache must be invalidated manually. It
requires removing the CacheKey
as a wrapping structure to the primarykey
Questions:
I noticed that CacheKey implements a safety measure of
I think that sometimes people do not see the effort a newbie has put into
something, because putting yourself into their place is also difficult, and
is not so urgent, i.e. their pain is not your pain. I paid to get
documentation that turned out to be a work in progress and have never
really
28 matches
Mail list logo
