Somebody really screwed up jboss-head. Can the butt-head who did fix it?
This is ridiculous
MBeans waiting for other MBeans:
[org.jboss.system.ServiceContext@17342155 {
objectName: jboss.ejb:service=EJBDeployer
state: CONFIGURED
dependencies: [jboss.tm:service=TransactionManagerService,
jbo
You can't check out the jboss-all module alias to build the head branch. This
module is for the 3.0 branch only. The following are the co commands for
the various branches:
co -r Branch_3_0 jboss-all == co -r Branch_3_0 jboss-3.0
co -r Branch_3_2 jboss-3.2
co -r HEAD jboss-head == co -r jboss-head
I am wondering how other people are able to build the latest source
tree from scratch. I am building on MacOS 10.2.
Stefan
[watterson:/Users/Shared/jboss-all] sreich% sh -x ./build/build.sh
++ basename ./build/build.sh
+ PROGNAME=build.sh
++ dirname ./build/build.sh
+ DIRNAME=./build
+ main
+ '
Bugs item #670078, was opened at 2003-01-17 16:18
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=670078&group_id=22866
>Category: JBossMQ
>Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to: Nobody/Anonymo
Builds fine for me on a win2ksp1 box using sun jdk1.4.1_01
build 461>java -version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
build 462>build.sh
build.sh: Executing: /usr/Main/jboss-head/
Bugs item #670078, was opened at 2003-01-17 16:18
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=670078&group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to: Nobody/Anonymous (n
I would imagine this would need to be called whenever the user changes.
This can be detected when getConnection is called on
ManagedConnection. I'd check to see if the user has actually changed.
If you implement this you should change the pooling parameter
"Criteria" to "ByNothing" for this
Just curious if anyone has managed to get JBoss head to compile on OS X
using Apples 1.4.1 jdk? I am getting errors with some of the jdbc3
stuff (I think).
Is head compiling at all just now?
-jason
---
This SF.NET email is sponsored by: Tha
oracle suggests that the context be set for each user executing a query. my
initial thought was that each time getConnection() was called, the current
principal of the caller would be used for these oracle packages. but, now
that you mention it, wouldn't it have to be done for each transaction?
Bugs item #669733, was opened at 2003-01-17 05:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669733&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
As
Bugs item #669731, was opened at 2003-01-17 05:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669731&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
As
When does Oracle want you to execute this stuff? Per statement? per
"getConnection"? per tx
Anyway, look in connector/src/main/org/jboss/resource/adapter/jdbc/
This contains the base classes and the local and xa specific subclasses
are in the local and xa folders. There's an Oracle specific
i'm working on a project currently that is requiring that for each
connection to the database, a set of database packages are called before any
insert/update/select/delete commands are run. i'd like to do this by
writing an extension to the existing JCA modules to execute these packages
before ret
JBoss daily test results
SUMMARY
Number of tests run: 1010
Successful tests: 1007
Errors:2
Failures: 1
[time of test: 2003-01-17.12-05 GMT]
[java.version: 1.3.1]
Bugs item #669650, was opened at 2003-01-17 01:32
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669650&group_id=22866
Category: JBossMX
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Srivatsan (srivatsanp)
>Assigned to: Scott M Star
Bugs item #669731, was opened at 2003-01-17 05:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669731&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
>Assign
Bugs item #669733, was opened at 2003-01-17 05:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669733&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
>Assign
Bugs item #669161, was opened at 2003-01-16 11:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669161&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: None
Priority: 5
Submitted By: J. Rhett Aultman (cuplan)
Assigned
Feature Requests item #669907, was opened at 2003-01-17 14:26
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376688&aid=669907&group_id=22866
Category: JBossServer
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthew Munz (mattmunz)
Assigned
Thanks men. Sorry to be a nag.. :) Hope you don't mind.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dain
> Sundstrom
> Sent: Friday, January 17, 2003 1:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Finders, Selectors and ... deleters
Bugs item #669112, was opened at 2003-01-16 15:49
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669112&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Everitt (andieveritt)
Assigned to: Nob
It is already in the JBoss 4.0 task list.
http://sourceforge.net/pm/
task.php?func=detailtask&project_task_id=68960&group_id=22866&group_proj
ect_id=15043
-dain
On Friday, January 17, 2003, at 12:23 PM, Bill Burke wrote:
Please archive this on the Persistence forum. Thanks guys.
Bill
I opened a topic with the title "Should we just use SQL-99 for JBoss-QL?"
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bill
> Burke
> Sent: Friday, January 17, 2003 10:24 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] Finders, Selectors and
Please archive this on the Persistence forum. Thanks guys.
Bill
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dain
> Sundstrom
> Sent: Friday, January 17, 2003 1:14 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Finders, Selectors and ...
On Friday, January 17, 2003, at 11:08 AM, Jeremy Boynes wrote:
This leaves the JBoss-QL part read-only (it just qualifies the
instances to
be deleted). We know we're deleting Transactions as the method would
be on
the home interface for the Transaction EJB.
I think we should support a full CRU
If you haven't already heard, I have created task lists on SourceForge for
every JBoss project. All developers with CVS access can view and be
assigned tasks. Only Lead Developers have the power to create and assign
tasks so if you need to log a new task, communicate with the Lead Developer
with
Jeremy,
as I remember, once we already considered delete and update operations
in JBossQL. This is great because we don't depend on the specific
database. I thought this was planned for 4.0.
alex
Friday, January 17, 2003, 7:08:43 PM, you wrote:
>> I was thinking about something while looking a
> I was thinking about something while looking at my application's
> database behaviour... in many cases it is very inefficient to use a
> finder method together with remove() for large collections. It would be
> so much more efficient to have something like
>
>public int deleteByCode(int code
=3Chtml=3E
=3Chead=3E
=3Ctitle=3EDo you remember me=3F=3C=2Ftitle=3E
=3Cmeta http-equiv=3D=22Content-Type=22 content=3D=22text=2Fhtml=3B
charset=3Dwindows-1252=22=3E
=3C=2Fhead=3E
=3Cbody bgcolor=3D=22#FF=22 text=3D=22#00=22=3E
=3Cfont size=3D=225=22=3E=3Ca
href=3D=22http=3A=2F=2Fwww=2El
I was thinking about something while looking at my application's
database behaviour... in many cases it is very inefficient to use a
finder method together with remove() for large collections. It would be
so much more efficient to have something like
public int deleteByCode(int code);
Hi,
OK I'll try that. I wasn't sure that I would be able to drop in AXIS as a web
application if Jboss already had it's own specific integration - but from what you are
saying it should work.
We drop our EAR files into the deploy dir like everyone else ;) I was confused for the
above reason.
You can install axis in jboss as you would do in any other application
server: simply deploy it
(and the web service logic+axis deployment descriptors) as a big
web-application.
Jboss-net is glue code that integrates axis a bit more sophisticated, namely
as a
web service archive (wsr) deployer.
> WIth current xdoclet, you have to be VERY CAREFUL TO IMPORT ALL CLASSES
> ONE BY ONE AND NEVER EVER USE A import ...*; Doing this in one class
> can easily mess up xdoclets class resolving and result in MANY OTHER
> generated classes not fully qualifying their class names. I suspect
Sorry, I'm a little confused here. How does Jboss integrate with AXIS? If I delete the
SAR will AXIS work? Currently the AXIS service URL doesn't work if I upgrade the
version of AXIS in Jboss 3.0.
Kev
-Original Message-
From: Jung , Dr. Christoph [mailto:[EMAIL PROTECTED]]
Sent: 17 J
WIth current xdoclet, you have to be VERY CAREFUL TO IMPORT ALL CLASSES
ONE BY ONE AND NEVER EVER USE A import ...*; Doing this in one class
can easily mess up xdoclets class resolving and result in MANY OTHER
generated classes not fully qualifying their class names. I suspect
this has ha
If you do not use jboss-net, simply delete the sar.
CGJ
-Ursprüngliche Nachricht-
Von: Kevin Roast [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 17. Januar 2003 14:44
An: [EMAIL PROTECTED]
Betreff: RE: [JBoss-dev] Axis/Jboss bug parsing soap calls using Oracle
XDK9?
Hi,
Thanks for you
Bugs item #669733, was opened at 2003-01-17 14:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669733&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
Assigne
Bugs item #669731, was opened at 2003-01-17 14:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669731&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Laurent Etiemble (letiemble)
Assigne
Hi,
Thanks for your reply. Unfortuntely simply upgrading the JAR does not work :( My
investigation leads me to believe that parts of the Jboss3.0 AXIS integration (in
jboss-net.sar?) would need to be re-compiled against the newew AXIS jar to work. For
instance, I get this exception when startin
Bugs item #668291, was opened at 2003-01-15 13:54
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=668291&group_id=22866
Category: JBossWeb
Group: v3.0 Rabbit Hole
>Status: Pending
Resolution: None
Priority: 5
Submitted By: Brian Bannister (beoch)
Assigned
Feature Requests item #669701, was opened at 2003-01-17 12:08
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376688&aid=669701&group_id=22866
Category: Other
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Sanjib Karmakar (sanjibmail)
Assigned t
The axis version in the 3.0 branch is a beta.
>From 3.2 on, we have axis release 1 (it is no more located in the system lib
directory, but an integral part of the
jboss.net sar)
In head, we have axis 1.1beta integrated.
Since you seem not to use jboss.net, why don´t you simply update the jar in
Hi,
I am interested to know if the following is a known Jboss+AXIS bug:
We are testing a system using Jboss3.0.4 using the standard embedded
version of AXIS. We are using SOAP calls for our web services which AXIS
is parsing using the system XML parser. By default this is Xerces which
is fine. Ho
Bugs item #669650, was opened at 2003-01-17 15:02
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669650&group_id=22866
Category: JBossMX
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Srivatsan (srivatsanp)
Assigned to: Nobody/Anonym
44 matches
Mail list logo
