===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Bugs item #835596, was opened at 2003-11-04 11:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=835596&group_id=22866
Category: JBossCMP
Group: v3.2
Status: Open
Resolution: No
UPSIDE INTERNATIONAL - Searching Out Stocks with Big Upside Potential...that have gone
unnoticed until now.
UpSide International uncovers unusual trends and activity in stocks. We look for
signs of block trades and insider purchasing in order to uncover insight into uncommon
trends.
Seven we
Cut your debt in half!
ml lxzlosa fqppzgt wlec kaxykluoyr qio ygfuy
bozpu
cx dbhcn qqixwlz
pjo yzo exhemifq
Patches item #835671, was opened at 2003-11-04 13:39
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376687&aid=835671&group_id=22866
Category: JBossTX
Group: v3.2
Status: Open
Resolution:
neff epitaxy gully maggot bagley eleazar shari whomsoever
commissary aspirant mccall malta shrank spiro asceticism drench hamilton fiske cheap
peppermint anatomic policy rheumatic
The ultimate digital
cable filter
The filter will allow
you to receive all
the channels that you
order wit
Posting to jbosxs-dev. Let's keep it there please!
Bill
Bill Burke wrote:
LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
Yes, IMO, migration should be a separate distinct tool/step. We should
not be maintaining past versions of deployment descriptors in 4.0, 3.2,
or 3.0. Anybody know
Keep this discussion on jboss-dev please.
I think we should have separate deploy directories.
/deploy/system with all core stuff
/deploy/applications with all non-jboss configs.
A number of clients do this I found this much easier to manage myself in
other projects I've worked on.
You are right
Posting to jboss dev
Juha Lindfors wrote:
Getting the scripts done would be the first step and itself helpful for
most current admins, regardless of the language used in the script.
Once those exist, it should not be a huge step to integrate the scripts
with a new MigrationSubDeployer that regist
posting to jboss-dev
Sacha Labourey wrote:
This is because you consider the system services as dirt.
If you consider it
as the system, putting that in a system folder makes sense.
Remember 2.4.x?
the deploy was empty and that was great from a user point of view.
Why? You're just moving the fi
Posting to jboss-dev. Please CC jboss-dev on all design emails.
Thanks,
Bill
Jung , Dr. Christoph wrote:
-Ursprüngliche Nachricht-
Von: Scott M Stark [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 4. November 2003 01:13
An: Jung , Dr. Christoph
Cc: 'Thomas Diesler'; '[EMAIL PROTECTED]'
What are we talking about here?
Migration?
Scripting?
Management?
What?
Let's break it up into those categories and create separate discussions.
PLEASE CC JBOSS_DEV
Bill
Sacha Labourey wrote:
This is because you consider the system services as dirt.
If you consider it
as
It is checked in Branch_3_2.
org.jboss.varia.dsdelegator package.
After building (varia/build.bat), you should find dsdelegator.jar in
varia/output/lib. It should be copiied to server//lib.
In varia/src/resources/services/dsdelegator you can find a sample config
dsdelegator-service.xml
Sorry, fo
i think this is an excellent idea. if you did move in this direction,
would you also
extend this to the "conf" directory as well? it would be nice to treat
any application specific
config files in the same way.
-jae
-Original Message-
From: Bill Burke [mailto:[EMAIL PROTECTED]
Sent:
!?%zq&$wq!
Mozilla is eating all my spam, but why should a mailing list receive messages
from somebody not subscribed to the list?
To the person who manages the dev list: allow posting to subscribers only, please.
Thanks in advance,
Ricardo Argüello
Scripting is getting off of the original topic of not knowing how to
edit a component's config. Free form scripting as an admin tool
is a step backwards from an admin interface, and already exists via
the bsh deployer.
Categorization of the deployment directories is also not really addressing
the i
Looks like the CIA bot is not working right yet...
This is the message I get when I commit.
Ricardo Argüello
In C:\cvs\jboss\jboss-head\media: cvs -q commit -m "No constructor"
src/main/javax/emb/ProtocolConstraints.java
CVSROOT=:ext:[EMAIL P
Am 04.11.2003 um 17:22 schrieb Bill Burke:
Posting to jbosxs-dev. Let's keep it there please!
Bill
Bill Burke wrote:
LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
Yes, IMO, migration should be a separate distinct tool/step. We
should not be maintaining past versions of deployment descr
On Wed, 5 Nov 2003, Holger Baxmann - bitwind wrote:
> > Bill Burke wrote:
> >> LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
> >> Yes, IMO, migration should be a separate distinct tool/step. We
> >> should not be maintaining past versions of deployment descriptors in
> >> 4.0, 3.2, or 3.0.
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Am 05.11.2003 um 02:53 schrieb Juha Lindfors:
On Wed, 5 Nov 2003, Holger Baxmann - bitwind wrote:
Bill Burke wrote:
LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
Yes, IMO, migration should be a separate distinct tool/step. We
should not be maintaining past versions of deployment descriptors
On Wed, 2003-11-05 at 01:53, Juha Lindfors wrote:
> On Wed, 5 Nov 2003, Holger Baxmann - bitwind wrote:
> > > Bill Burke wrote:
> > >> LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
> > >> Yes, IMO, migration should be a separate distinct tool/step. We
> > >> should not be maintaining past v
On Wed, 2003-11-05 at 02:08, Holger Baxmann @ mac wrote:
> Am 05.11.2003 um 02:53 schrieb Juha Lindfors:
> > On Wed, 5 Nov 2003, Holger Baxmann - bitwind wrote:
> >>> Bill Burke wrote:
> LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
> Yes, IMO, migration should be a separate distin
Am 05.11.2003 um 02:53 schrieb Juha Lindfors:
On Wed, 5 Nov 2003, Holger Baxmann - bitwind wrote:
Bill Burke wrote:
LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
Yes, IMO, migration should be a separate distinct tool/step. We
should not be maintaining past versions of deployment descriptors
Am 05.11.2003 um 03:11 schrieb Adrian Brock:
On Wed, 2003-11-05 at 02:08, Holger Baxmann @ mac wrote:
When does JBoss.org have the meta-model of the whole stuff defined
in
XSD and throuw the ugly DTD's away?
Then one is able to appy XSLT on the XSD's and all migration things
belonging to the meta
On Wed, 2003-11-05 at 02:22, Holger Baxmann @ mac wrote:
> Am 05.11.2003 um 03:11 schrieb Adrian Brock:
>
> > On Wed, 2003-11-05 at 02:08, Holger Baxmann @ mac wrote:
> When does JBoss.org have the meta-model of the whole stuff defined
> in
> XSD and throuw the ugly DTD's away?
> >
On Wed, 5 Nov 2003, Adrian Brock wrote:
> > >> When does JBoss.org have the meta-model of the whole stuff defined in
> > >> XSD and throuw the ugly DTD's away?
> > >> Then one is able to appy XSLT on the XSD's and all migration things
> > >> belonging to the meta-level are handled by the meta-level
On Wed, 5 Nov 2003, Adrian Brock wrote:
> How does Joe hates-GUIs programmer (i.e. me) maintain that wizard
> and other management interfaces when I add configuration options
> to the jdbc rars or db specifc plugins?
You don't. That's the fundamental problem with a rich GUI ;-)
-- Juha
---
Am 05.11.2003 um 03:08 schrieb Adrian Brock:
On Wed, 2003-11-05 at 01:53, Juha Lindfors wrote:
On Wed, 5 Nov 2003, Holger Baxmann - bitwind wrote:
Bill Burke wrote:
LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
Yes, IMO, migration should be a separate distinct tool/step. We
should not be m
Am 05.11.2003 um 03:25 schrieb Adrian Brock:
On Wed, 2003-11-05 at 02:22, Holger Baxmann @ mac wrote:
Am 05.11.2003 um 03:11 schrieb Adrian Brock:
On Wed, 2003-11-05 at 02:08, Holger Baxmann @ mac wrote:
When does JBoss.org have the meta-model of the whole stuff defined
in
XSD and throuw the ugly
Alright, I have commented this script out as this is the second problem with
this change.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Ricardo Argüello wrote:
Looks like the CIA bot is not working right yet...
This is the message I get
Its required for j2ee1.4, but you don't need an xsd to use xsl
to transform and xml document.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Holger Baxmann - bitwind wrote:
When does JBoss.org have the meta-model of the whole stuff defi
Explain how xsd is actually the object model in terms of what
the metadata handling code is using. Its directly manipulating
xml instances that conform to the xsd or is there is a binding of
the xsd to a java object model? If there is a binding, then that
is the object model, not the xsd as that is
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Holger Baxmann - bitwind wrote:
Am 05.11.2003 um 02:53 schrieb Juha Lindfors:
On Wed, 5 Nov 2003, Holger Baxmann - bitwind wrote:
Bill Burke wrote:
LETS TAKE THESE DISCUSSIONS TO JBOSS-DEV PLEASE!
Yes, IMO, migration should be a separate distinct tool/step. We
should not be maintaining pas
37 matches
Mail list logo
