Hello,
For the laziest around here, I have compiled a ready-to-run version (based
on 2.2.1 of the 17th of April 2001). You can read info on the web page or
download it directly (you'll find a HADoc folder in it):
- http://194.38.95.241/jboss/
- http://194.38.95.241/jboss/JBossHA2.
Hi all!
Is there a possibilty to let the finder defined in jaws.xml interpret
a given PK-class (lets say PersonPK)?
Overwriting toString() has no effect!
example:
public class PersonPK impl java.io.Ser {
public String personID
}
AccountHom
Hello,
we can't work with super-interfaces of the home interfaces instead the home
interfaces itselfs. Is this a jBoss bug or is what we try to do against the
EJB 1.1 spec?
we have a group of EB's which have a set of equal business methods. We tried
to define a interface as super-interface for
Hi,
On Mon, 16 Apr 2001, Jason Dillon wrote:
> Any preferences on how to continue? My bias would be to commit these
> changes soon, so I can move on to other bits. This will effect OpenJMS
> users, so we should probably add that to a release note also.
yeah I think you can commit it.. if peop
Hi!
Problems occurred when using feature automatically creating
findBy...-Methods with nested fields!
JDBCFindByCommand-constructor could not recognize cmp-fields which are
nested in data objects.
Following small JDBCFindByCommand-constructor patch works fine:
public JDBCFindByCommand(JDBCCo
Question:
Currently it looks like every remote call is load balanced with a round
robin algorithm.
What if the user initiates a transaction (user transaction) and the
transaction lasts over three method invokations.
If I have three servers clustered, this means that the invokation will
happen on
User: alborini
Date: 01/04/17 09:46:22
Modified:src/docs howtombeans.xml
Log:
typo
Revision ChangesPath
1.5 +3 -3 manual/src/docs/howtombeans.xml
Index: howtombeans.xml
===
RCS file: /cvs
Hey,
Good catch. Should encourage other people to do the same. Any typos
or incorrect information, just go in and correct it.
On Tue, 17 Apr 2001 [EMAIL PROTECTED] wrote:
> User: alborini
> Date: 01/04/17 09:46:22
>
> Modified:src/docs howtombeans.xml
> Log:
> typo
>
> Re
Hi Dan...
--On Monday, April 16, 2001 6:49 PM -0700 [EMAIL PROTECTED] wrote:
> Group: v2.2.1
Does this mean that this fix will be released with the 2.2.1 bug fix
release this week?
Thanks!
Jim
___
Jboss-development mailing list
[EMAIL PROTECTED]
User: starksm
Date: 01/04/17 10:24:42
Modified:src/docs howtombeans.xml
Log:
Update the non-ServiceMBeanSupport version to use System.out rather
than the ServiceMBeanSupport log.
Revision ChangesPath
1.6 +1 -1 manual/src/docs/howtombeans.xml
Index: how
Yes. Scott was planning on packaging that up tommorrow or so.
Jim Archer wrote:
>
> Hi Dan...
>
> --On Monday, April 16, 2001 6:49 PM -0700 [EMAIL PROTECTED] wrote:
>
> > Group: v2.2.1
>
> Does this mean that this fix will be released with the 2.2.1 bug fix
> release this week?
>
> Thanks!
>
Please submit patches here:
https://sourceforge.net/tracker/?func=add&group_id=22866&atid=376687
Thanks,
-- Juha
At 17:52 17.4.2001 +0200, you wrote:
>Hi!
>
>Problems occurred when using feature automatically creating
>findBy...-Methods with nested fields!
>JDBCFindByCommand-constructor could
User: starksm
Date: 01/04/17 12:33:09
Modified:src/main/org/jboss/metadata ApplicationMetaData.java
Log:
Remove the requirement that the res-jndi-name be prefixed with java:
Revision ChangesPath
1.14 +1 -5 jboss/src/main/org/jboss/metadata/ApplicationMetaData.
User: starksm
Date: 01/04/17 12:36:37
Modified:src/main/org/jboss/metadata Tag: Branch_2_2
ApplicationMetaData.java
Log:
Remove the requirement that the res-jndi-name be prefixed with java:
Revision ChangesPath
No revision
Change Notes item #416812, was updated on 2001-04-17 12:47
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416812&group_id=22866
Category: None
Group: v2.2.1
Status: Open
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Nobody/Anonymous (nob
User: starksm
Date: 01/04/17 12:52:21
Modified:src/main/org/jboss/metadata ApplicationMetaData.java
Log:
Add an author tag for me
Revision ChangesPath
1.15 +2 -1 jboss/src/main/org/jboss/metadata/ApplicationMetaData.java
Index: ApplicationMetaData.java
Bugs item #416817, was updated on 2001-04-17 12:57
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=416817&group_id=22866
Category: JBossServer
Group: v2.3 (unstable)
Status: Open
Resolution: None
Priority: 3
Submitted By: Scott M Stark (starksm)
Assigned
User: user57
Date: 01/04/17 13:10:10
Modified:.cvswrappers
Log:
o Added some more binary file extentions:
Archives - .rar, .ear, .war, .tar, .tgz, .gz
Documents - .pdf
Revision ChangesPath
1.3 +9 -0 CVSROOT/cvswrappers
Index: cvswrapp
Is it possible that people upgrading will need to put the 'java:' back
into their res-jndi-names where appropriate?
[EMAIL PROTECTED] wrote:
>
> Change Notes item #416812, was updated on 2001-04-17 12:47
> You can respond by visiting:
> http://sourceforge.net/tracker/?func=detail&atid=381174&aid
On Tue, Apr 17, 2001 at 12:36:38PM -0700, [EMAIL PROTECTED] wrote:
> User: starksm
> Date: 01/04/17 12:36:37
>
> Modified:src/main/org/jboss/metadata Tag: Branch_2_2
> ApplicationMetaData.java
> Log:
> Remove the requirement that the res-jndi-name be prefixe
User: user57
Date: 01/04/17 13:27:09
contrib/openjms/src/build - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:27:42
contrib/openjms/src/main/org/jboss - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:27:10
contrib/openjms/src/lib - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:27:42
contrib/openjms/src/main/org/jboss/jms/openjms - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:27:42
contrib/openjms/src/main/org - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:27:42
contrib/openjms/src/main/org/jboss/jms - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:26:45
contrib/openjms/src - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:27:10
contrib/openjms/src/main - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:26:22
contrib/openjms - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/04/17 13:33:43
Added: openjms/src/lib exolabcore-0.1.jar
openjms-client-patched-0.5.1.jar
openjms-patched-0.5.1.jar openjms-pool.jar
openjms-rmi-patched-0.5.1.jar
Log:
o Migration of O
User: user57
Date: 01/04/17 13:33:42
Added: openjms/src/build build.sh build.xml
Log:
o Migration of OpenJMS specific JBoss JMS provider classes from the
main 'jboss'.
NOTE: The migrated classes have been consolidated into one package.
Revision ChangesPath
User: user57
Date: 01/04/17 13:33:42
Added: openjms README
Log:
o Migration of OpenJMS specific JBoss JMS provider classes from the
main 'jboss'.
NOTE: The migrated classes have been consolidated into one package.
Revision ChangesPath
1.1
User: user57
Date: 01/04/17 13:33:43
Added: openjms/src/main/org/jboss/jms/openjms OpenJMSProvider.java
OpenJMSServerSessionPoolFactory.java package.html
Log:
o Migration of OpenJMS specific JBoss JMS provider classes from the
main 'jboss'.
NO
Yup,
Especially those of us that are using direct SQL calls using the connection
pools. Am I correct here?
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of danch
Sent: Tuesday, April 17, 2001 4:09 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] [
Yes if names without a java: are being used they will have to be added.
- Original Message -
From: "danch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 17, 2001 1:08 PM
Subject: Re: [JBoss-dev] [ jboss-Change Notes-416812 ] Removed res-jndi-name java:
prefix need
>
I think it is a bug for 2.2 as I cannot run the current ENC naming tests that
need to access the JMS queue/topic factories because of this issue. I'll
update the change note to include more details.
- Original Message -
From: "Toby Allsopp" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sen
Can this change be postponed? Some of us are using code generators and it
would be more than a simple search/replace exercise to accomadate this.
Or, is it possible to set the code such that it works with or without the
java: prefix?
Jim
--On Wednesday, April 18, 2001 8:14 AM +1200 Toby Allso
On Tue, Apr 17, 2001 at 01:50:16PM -0700, Scott M Stark wrote:
> I think it is a bug for 2.2 as I cannot run the current ENC naming tests that
> need to access the JMS queue/topic factories because of this issue. I'll
> update the change note to include more details.
Ah, that makes sense. I just
Your code itself shouldn't change. I believe that it will just be places
where you're mapping resource references in jboss.xml that would change,
or have I misinterpreted, Scott?
Jim Archer wrote:
>
> Can this change be postponed? Some of us are using code generators and it
> would be more than
I don't have a strong opinion on its inclusion so if in general this is going to
cause more problems then it solves it can be left out of the 2.2.1 release.
An ApplicationMetaData level compatability flag could be added to indicate
whether the java:/ prefix should be assumed and this could be made
Does anyone know if exolabcore-0.1.jar is used by anything other than
OpenJMS?
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
A change will be required if you have a res-jndi-name element in your jboss.xml
descriptor that is relying on the implied java:/ prefix being added. For example if
your using:
DefaultDS
DefaultDS
rather than:
DefaultDS
User: user57
Date: 01/04/17 14:27:14
Removed: src/lib openjms-client-patched-0.5.1.jar
openjms-patched-0.5.1.jar openjms-pool.jar
openjms-rmi-patched-0.5.1.jar
Log:
o Removing files OpenJMS specific files that have been migrated to
User: user57
Date: 01/04/17 14:27:14
Modified:src/main/org/jboss/ejb/plugins/jms JMSContainerInvoker.java
Log:
o Removing files OpenJMS specific files that have been migrated to the
contrib/openjms CVS module.
o Added AbstractJMSProviderAdapter, which provides most of the
User: user57
Date: 01/04/17 14:27:14
Modified:src/main/org/jboss/jms/jndi JBossMQProvider.java
Added: src/main/org/jboss/jms/jndi AbstractJMSProviderAdapter.java
Removed: src/main/org/jboss/jms/jndi OpenJMSProvider.java
Log:
o Removing files OpenJMS specific files t
User: user57
Date: 01/04/17 14:27:14
Removed: src/main/org/jboss/jms/asf
OpenJMSServerSessionPoolFactory.java
Log:
o Removing files OpenJMS specific files that have been migrated to the
contrib/openjms CVS module.
o Added AbstractJMSProviderAdapter
Maybe support the java:/ defaulting in 2.2.1 but issue a deprecation
warning?
Scott M Stark wrote:
>
> I don't have a strong opinion on its inclusion so if in general this is going to
> cause more problems then it solves it can be left out of the 2.2.1 release.
> An ApplicationMetaData level com
That is correct. There will be no code changes required. Only certain undocumented
usage of the jboss.xml descriptor res-jndi-name element will require changes to the
res-jndi-name element.
- Original Message -
From: "danch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, Apri
Change Notes item #416846, was updated on 2001-04-17 14:47
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416846&group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Jason Dillon (user57)
Assigned to: Nobody/Anonymous (nobody)
There seems to be a bit of confusion as to exactly what the ApplicationMetaData
change that I committed is and what its impact will be. I'll describe the current
problem and then suggest an integration of the patch into the 2.2.1 release that
won't break any code or jboss.xml descriptors but will
It looks like log4j-old.jar (which contains classes in org.log4j) is not
being referenced by any files in the jboss or contrib/log4j modules (except
log4j-old.jar).
So, it is *probably* safe to remove this file.
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
> Wanna take a look at the Ope
> I would like to make it possible to access any resource using the suggested ENC
> naming convention in the 2.2.1 release, but since its not clear how many people
> are using broken jboss.xml descriptors I'm proposing the following change.
> The ApplicationMetaData will look for a
>org.jboss.met
User: starksm
Date: 01/04/17 19:09:46
Modified:src/bin Tag: Branch_2_2 run.bat run.sh
Log:
Don't include the system CLASSPATH as this results in too many conflicts
in general. Change CLASSPATH to JBOSS_CLASSPATH to make it clear that
the CLASSPATH variable is not used.
Re
Change Notes item #416920, was updated on 2001-04-17 19:19
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416920&group_id=22866
Category: None
Group: v2.2.1
Status: Open
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Nobody/Anonymous (nob
User: starksm
Date: 01/04/17 19:21:10
Modified:src/bin run.bat run.sh
Log:
Don't include the system CLASSPATH as this results in too many conflicts
in general. Change CLASSPATH to JBOSS_CLASSPATH to make it clear that
the CLASSPATH variable is not used.
Revision Changes
Change Notes item #416922, was updated on 2001-04-17 19:22
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416922&group_id=22866
Category: None
Group: v2.4
Status: Open
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Nobody/Anonymous (nobod
User: starksm
Date: 01/04/17 19:39:21
contrib/tomcat/src/etc/conf - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: starksm
Date: 01/04/17 19:39:09
contrib/tomcat/src/etc - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: starksm
Date: 01/04/17 19:39:35
contrib/tomcat/src/etc/conf/tomcat - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: starksm
Date: 01/04/17 19:40:41
Added: tomcat/src/etc/conf/tomcat jboss.conf.patch jboss.jcml.patch
server.xml.patch
Log:
Patch files that transform the default dist config files into those
required for the JBoss/EmbededTomcat bundle
Revision
User: starksm
Date: 01/04/17 19:43:21
Modified:tomcat README
Log:
Update the Ant build file to support building the JBoss/Tomcat prepackaged
bundle given jboss.dist and tomcat.dist locations.
Revision ChangesPath
1.3 +19 -16contrib/tomcat/README
Index
User: starksm
Date: 01/04/17 19:43:21
Modified:tomcat/src/build build.xml
Log:
Update the Ant build file to support building the JBoss/Tomcat prepackaged
bundle given jboss.dist and tomcat.dist locations.
Revision ChangesPath
1.9 +77 -39contrib/tomcat/src/bu
Change Notes item #416928, was updated on 2001-04-17 19:51
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416928&group_id=22866
Category: None
Group: v2.4
Status: Open
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Nobody/Anonymous (nobod
User: starksm
Date: 01/04/17 20:18:08
Modified:tomcat/src/build build.bat build.sh build.xml
Log:
Change jboss.home & tomcat.home to jboss.dist & tomcat.dist
Add fixcrlf task for the *.bat files
Revision ChangesPath
1.4 +1 -1 contrib/tomcat/src/build/build.
User: starksm
Date: 01/04/17 21:30:51
Modified:tomcat/src/etc/conf/tomcat server.xml.patch
Log:
Change JBOSS_HOME to JBOSS_DIST
Change TOMCAT_HOME to TOMCAT_DIST
Update server.xml.patch to be against the shipped 3.2.1 server.xml file
Revision ChangesPath
1.2 +
User: starksm
Date: 01/04/17 21:30:51
Modified:tomcat/src/build build.bat build.sh
Log:
Change JBOSS_HOME to JBOSS_DIST
Change TOMCAT_HOME to TOMCAT_DIST
Update server.xml.patch to be against the shipped 3.2.1 server.xml file
Revision ChangesPath
1.5 +9 -9
User: starksm
Date: 01/04/17 21:30:51
Modified:tomcat README
Log:
Change JBOSS_HOME to JBOSS_DIST
Change TOMCAT_HOME to TOMCAT_DIST
Update server.xml.patch to be against the shipped 3.2.1 server.xml file
Revision ChangesPath
1.4 +5 -5 contrib/tomcat/REA
User: starksm
Date: 01/04/17 23:04:28
Modified:src/main/org/jboss/metadata Tag: Branch_2_2
ApplicationMetaData.java
Log:
Add a org.jboss.metadata.ApplicationMetaData.assumeJavaPrefix property that
defaults to true which restores the 2.2 behavior requiring
68 matches
Mail list logo
