Bugs item #601049, was opened at 2002-08-27 23:26
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=601049group_id=22866
Category: JBossServer
Group: v3.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Yan Pujante (madonnax)
Assigned to:
Patches item #614291, was opened at 2002-09-25 11:27
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376687aid=614291group_id=22866
Category: JbossSOAP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Infogest (infogest)
Assigned to:
Bugs item #614313, was opened at 2002-09-25 12:31
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866
Category: JBossTX
Group: v3.2
Status: Open
Resolution: None
Priority: 6
Submitted By: Michael Bartmann (bartmann)
Assigned to:
Bugs item #614313, was opened at 2002-09-25 12:31
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=614313group_id=22866
Category: JBossTX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Bartmann (bartmann)
Assigned to:
Bugs item #597216, was opened at 2002-08-19 16:34
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=597216group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Georg Schmid (giorgio42)
Assigned
Hi everyone,
I'm currently working on resolving Bug #613360 (see
https://sourceforge.net/tracker/?func=detailatid=376685aid=613360group_id=22866 ).
I have an implementation issue with the EJB Spec Section 10.6.14:
The Bean Provider should not use reserved identifiers as ejb-names or
Hello,
I am new in JBoss-Jetty users. I have downloaded
JBoss-all 3.0. It has build-in Jetty server.
Now I have to add a simple JSP project to the Jetty
server. So that, when I will run server and give
'http://Localhost/Myapp/index.jsp'
it should show index.jsp file in
browser.
Can
[x ] ejb-name should be restricted as above ONLY for CMP 2.0 Entity Beans
There really is no point to restricting the names in other contexts that I can see
as it will only introduce compatibility problems.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Bugs item #614116, was opened at 2002-09-24 19:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=614116group_id=22866
Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to:
I find the hsqldb.jar under thirdparty.
But it contains classes not in the release I obtained from the orig.
HSQLDB-Project.
I need the sources to find the reason for a thread leak, especially
org.hsqldb.Embedded_Server
which I find in the jboss's version of hsqldb.jar.
Thanks,
Michael Bartmann
CGJ JBoss.Net developers,
After working with wsdl2Java, I have come to the conclusion that the wsdl
being generated by org.jboss.net.jmx.server.MBeanProvider is not accurate.
I have included both the WSDL and the interface generated by wsdl2Java. Any
ideas? It seems to me that the method
Hello,
I am using JBoss3.0.
I have a small project developed and
deployedin war file. The project contains some JSPs.
When I start server and open JSP using url as
follows 'http://localhost:8080/test/test/index.jsp', then I get error
as...
HTTP ERROR: 500 Unable to compile class for JSP
I has to be restricted for CMP 2.0 beans as the code assumes that the
name is a valid java identifier.
-dain
Scott M Stark wrote:
[x ] ejb-name should be restricted as above ONLY for CMP 2.0 Entity Beans
There really is no point to restricting the names in other contexts that I can see
as
I am using the 3.2.0beta2 CVS version of JBoss and have run into a problem
with the JMS DestinationManager. It appears that the JMS DestinationManager
stores in a hashmap the actual queue/topic JNDI names that are then looked
up at deployment time by the MDB deployment logic in JBoss. This
Matt,
MBeanProvider should normally reflect over the JMX-Metadata (hence also the
mbean methods) to
Build the wsdl. But I havn´t looked at the code for a while. Let met check
this.
CGJ
-Ursprüngliche Nachricht-
Von: Matt Munz [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 25.
Bugs item #600474, was opened at 2002-08-26 14:31
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=600474group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Marcus Redeker (mredeker)
Bugs item #601049, was opened at 2002-08-27 16:26
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=601049group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Yan Pujante (madonnax)
Assigned
onsdagen den 25 september 2002 kl 14.53 skrev Michael Bartmann:
I find the hsqldb.jar under thirdparty.
But it contains classes not in the release I obtained from the orig.
HSQLDB-Project.
I need the sources to find the reason for a thread leak, especially
org.hsqldb.Embedded_Server
which
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.0_01
Java(TM) 2 Runtime Environment, Standard
Bugs item #608807, was opened at 2002-09-13 01:47
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=608807group_id=22866
Category: JBossSX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Michael Christen (tgdchmi2)
viktor wrote:
onsdagen den 25 september 2002 kl 14.53 skrev Michael Bartmann:
I find the hsqldb.jar under thirdparty.
But it contains classes not in the release I obtained from the orig.
HSQLDB-Project.
I need the sources to find the reason for a thread leak, especially
Bugs item #603959, was opened at 2002-09-03 05:16
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=603959group_id=22866
Category: Clustering
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 8
Submitted By: Dirk Vleugels (vleugels)
Bugs item #614116, was opened at 2002-09-24 16:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=614116group_id=22866
Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to:
Wow, now i see the leak!
Embedded_ServerConnection extends Thread
==
but you do:
Socket s = serverSocket.accept();
Embedded_ServerConnection c = new Embedded_ServerConnection(s, this);
Bugs item #594978, was opened at 2002-08-14 04:39
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=594978group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Andreas Billmann (frosch95)
Bugs item #614116, was opened at 2002-09-24 19:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=614116group_id=22866
Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to:
David Jencks wrote:
On 2002.09.24 21:11:36 -0400 Emerson Cargnin - SICREDI Serviços wrote:
David Jencks wrote:
Yes.
is there any reason for that? this question is becouse that this kind of
change generates a lot of trouble (and questions to jboss-user list)
when upgrading the server.
onsdagen den 25 september 2002 kl 20.43 skrev Michael Bartmann:
What is the best way to change the codebase? Another
patch for hsqldb?
Commit something that works optimised ... is the best way...
After running the testsuit that is ...
:-) ...
/peter_f
PS: test and debug hsqldb 1.7.0
Bugs item #607213, was opened at 2002-09-10 04:11
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=607213group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: vishal (attachvishal)
Assigned to:
Sorry to post to this list but I'm currently dealing with this issue in
my own project and thought it would be appropriate to comment. Also,
I'm not sure where to post any buildmagic related questions or if there
is such a place to do so.
We've recently switched to buildmagic. I've more
viktor wrote:
onsdagen den 25 september 2002 kl 20.43 skrev Michael Bartmann:
What is the best way to change the codebase? Another
patch for hsqldb?
Commit something that works optimised ... is the best way...
After running the testsuit that is ...
:-) ...
/peter_f
PS: test
Number of tests run: 934
Successful tests: 928
Errors:2
Failures: 4
[time of test: 25 September 2002 13:9 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer,
onsdagen den 25 september 2002 kl 22.17 skrev Michael Bartmann:
A possible answer might be:
0) test...
1) post patch to hsqldb (as source)
2) build the modified jar in your garage (as binary)
3) commit the jar to Branch_X of jboss cvs
Just Do IT(TM) comes to mind ...
Do we still need the hacked version with the latest release of HSQLDB?
If not lets drop the hacked version and just integrate what they
release.
If not, then lets get a fix into the HSQLDB sources so they are more
embeddable.
--jason
-Original Message-
From: [EMAIL PROTECTED]
onsdagen den 25 september 2002 kl 23.02 skrev Jason Dillon:
Do we still need the hacked version with the latest release of HSQLDB?
If not lets drop the hacked version and just integrate what they
release.
If not, then lets get a fix into the HSQLDB sources so they are more
embeddable.
Bugs item #608202, was opened at 2002-09-12 00:30
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=608202group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Cory Prowse (cosmic)
Assigned to:
Guys,
first of all sorry for the lack of input in the last days, NYC took a
lot of time and I have been out most of the week. JBoss Group grows
fast and I need to be everywhere at once, if only I could clone myself
:)
OK here is the point:
we need to be sure our free and for-pay
I've put together a working version of JBoss3.0.2-Tomcat4.1.12 (using
the Digester class instead of XmlMapper). Everything works fine (a new
tomcat4-service.jar gets built), except that I'm having trouble with
deployment. When a war contains a jar file, I get the following
exception:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_03
Java(TM) 2 Runtime Environment, Standard
Bugs item #526696, was opened at 2002-03-06 15:18
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=526696group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Kelly McTiernan (kellymct)
Assigned
I want to change that once and for all, I will ask that as
you submit new code you also submit the JUnit tests if you
have them as the documentation. The documentation can come
This doesn't make sense. I mean, just like you have you junit test,
submit doco Doco is not the junit obviously
Whom should I send it?
alex
I want to change that once and for all, I will ask that as
you submit new code you also submit the JUnit tests if you
have them as the documentation. The documentation can come
mf This doesn't make sense. I mean, just like you have you junit test,
mf submit
42 matches
Mail list logo