On Tue, 26 Jun 2001, Jay Walters wrote:
You guys wouldn't want to hear my stories... suffice it to say I agree that
if you can't understand to edit the properties files by hand you probably
shouldn't be editing them with a GUI...
That's a much different assertion than there
On Tue, 26 Jun 2001, Jay Walters wrote:
I don't edit my xml by hand or by tool, I generate it!
That's not always realistic. It works great if you're writing new
code for JBoss only, but if you have a pile of existing WebLogic JARs, or
you're not free to add arbitrary JavaDoc tags or
-
From: Peter Fagerlund [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 26, 2001 10:29 AM
To: [EMAIL PROTECTED]
Subject: Re: The next generation GUI (was : Re: [JBoss-dev] EJX and XML)
on 1-06-26 15.13, Jay Walters at [EMAIL PROTECTED] wrote:
You guys wouldn't want to hear my stories... suffice
:35 AM
To: '[EMAIL PROTECTED]'
Subject: RE: The next generation GUI (was : Re: [JBoss-dev] EJX and XML)
On Tue, 26 Jun 2001, Jay Walters wrote:
I don't edit my xml by hand or by tool, I generate it!
That's not always realistic. It works great if you're writing new
code for JBoss only
on 1-06-26 16.23, Jay Walters at [EMAIL PROTECTED] wrote:
I don't edit my xml by hand or by tool, I generate it!
Cool - that rules ... and can be utilised by many if it has a userfriendly
UI in front ... I would say a generator is a tool - together with a facade -
it is the future ...
/peter
Is anyone working to update the EJX and related code to use JAXP1.1?
This is the only dependency that requires the outdated xml.jar parser to
be included and prevents doing builds using ant alone(without the
build.sh/build.bat scripts).
___
|Subject: [JBoss-dev] EJX and XML
|
|
|Is anyone working to update the EJX and related code to use JAXP1.1?
|This is the only dependency that requires the outdated xml.jar parser to
|be included and prevents doing builds using ant alone(without the
|build.sh/build.bat scripts
Even better.
- Original Message -
From: marc fleury [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 25, 2001 9:44 AM
Subject: RE: [JBoss-dev] EJX and XML
Actually I have remove EJX from JBoss 3.0 for a whole variety of reasons...
it will need to be an addon or a new
of JBoss and really have the commitment to do it
free? do it!
marcf
|
|- Original Message -
|From: marc fleury [EMAIL PROTECTED]
|To: [EMAIL PROTECTED]
|Sent: Monday, June 25, 2001 9:44 AM
|Subject: RE: [JBoss-dev] EJX and XML
|
|
| Actually I have remove EJX from JBoss 3.0 for a whole variety
on JB3.0?
there I said it, it pisses me off, get off your butt and produce something
real ;-)
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Rickard Öberg
|Sent: Monday, June 25, 2001 2:02 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] EJX
On Mon, 25 Jun 2001, Rickard Öberg wrote:
Well, the mgmt yadda yadda is nice 'n all, but the big problem is still
there: it'll run piss-poor with Tomcat. It doesn't really matter what fancy
stuff you can think up with that crap hanging around.
There, I said it, it pisses me off. The J2EE
Rickard Öberg wrote:
yep, also for those that really want I believe the for pay add-on will be a
killer...
look who is still lurking :)
hey kiddo, when you pull your head out of your arse and your coma, you can
come and help us again, it is a shame to see so much talent go to waste...
do you
| AFAICT the only problem in integrating with Tomcat is the whole
|ClassLoader architecture. If you can nail that in an intelligent way, I
|think JBoss will run fine with Tomcat. IMHO, the only way to solve this
|is for a 3rd party service to create the ClassLoaders and then tell both
On Mon, 25 Jun 2001, Rickard Öberg wrote:
AFAICT the only problem in integrating with Tomcat is the whole
ClassLoader architecture.
AFAIK no it isn't. That was nailed ages ago. Works great.
What doesn't work great is Tomcat. It's dead slow. Do some benchmarks and be
disturbed.
/R
There, I said it, it pisses me off. The J2EE stack is a dream but nothing
more unless Tomcat is fixed.
Which is why Jules has been busy getting Jetty working.
Let me be more specific then: unless Jasper is fixed (which Jetty uses too).
There is work underway to correct this, but it'll take
On Mon, 25 Jun 2001, marc fleury wrote:
what do you mean we already integrate the CL stuff... for the past year or
so...
I thought it still didn't work with reloading (if you change a
servlet class or EJB class). If I'm wrong, great!
Aaron
you are not wrong, you are just a bit rusty...
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron
|Mulder
|Sent: Monday, June 25, 2001 2:59 PM
|To: [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] EJX and XML
|
|
|On Mon, 25 Jun 2001, marc fleury
Rickard Öberg wrote:
On Mon, 25 Jun 2001, Rickard Öberg wrote:
AFAICT the only problem in integrating with Tomcat is the whole
ClassLoader architecture.
AFAIK no it isn't. That was nailed ages ago. Works great.
Except that Jasper has different behavior when it compiles JSPs than
when
on 1-06-25 19.30, marc fleury at [EMAIL PROTECTED] wrote:
The next generation GUI
Could be built using a set of extension to a freeware shell like the
Together Community Edition 5.0
http://www.togethercommunity.com/community-edition.shtml
or some other free tool with easy yet powerfull plugin
netbeans is another possibility...
-Original Message-
From: Peter Fagerlund [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 3:36 PM
To: [EMAIL PROTECTED]
Subject: The next generation GUI (was : Re: [JBoss-dev] EJX and XML)
on 1-06-25 19.30, marc fleury at [EMAIL PROTECTED] wrote
GUI (was : Re: [JBoss-dev] EJX and XML)
netbeans is another possibility...
-Original Message-
From: Peter Fagerlund [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 3:36 PM
To: [EMAIL PROTECTED]
Subject: The next generation GUI (was : Re: [JBoss-dev] EJX and XML)
on 1-06-25
On Mon, 25 Jun 2001, Rickard Öberg wrote:
AFAICT the only problem in integrating with Tomcat is the whole
ClassLoader architecture.
AFAIK no it isn't. That was nailed ages ago. Works great.
Except that Jasper has different behavior when it compiles JSPs than
when they're run. (the classes
generation GUI (was : Re: [JBoss-dev]
EJX and XML)
Dude, GUI tools suck. Just edit the xml by hand. IMO if a
person can't edit
xml they shouldn't be configuring the server or ejb-jar.
-dain
___
Jboss-development mailing list
[EMAIL PROTECTED
on 1-06-25 22.26, Dain Sundstrom at [EMAIL PROTECTED] wrote:
Dude, GUI tools suck. Just edit the xml by hand. IMO if a person can't edit
xml they shouldn't be configuring the server or ejb-jar.
Yes exactly - throw out Gnome and the like alltogether - U are using Lynx
reading this and the
generation GUI (was : Re: [JBoss-dev]
EJX and XML)
Oh man
How short sighted you are. I aggree when you are a J2EE
programmer then you don't need a GUI but the most future
administrator of JBoss don't know J2EE well enough to do
so.
And also a management GUI is not only to configure a server
Dain Sundstrom wrote:
I was just picking a fight :)
OK, I just discarded my rant-mail.
-danch
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Hi Geeks
- Original Message -
From: Rickard Öberg [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 25, 2001 11:01 AM
Subject: Re: [JBoss-dev] EJX and XML
So that will mark the end of its life in JBoss, it is free to come back
as
an add-on to JBOSS.
It won't come back
We are beating a dead horse...
We are all aware of the importance of GUIs (for better or worse)
|BEA Weblogic (I can only speak for 5) has a poor GUI moslty only
|showing values but with no administration.
|
|IBM Websphere (I can only speak for 3) has a relatively good GUI with
|administration
28 matches
Mail list logo
