=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard
I think there is still a problem with the recently re-enabled foe deployer
tests. I can't build the testsuite on a clean checkout:
[ejbdoclet] Generating weblogic-cmp-rdbms-jar.xml.
[ejbdoclet] org.xml.sax.SAXParseException: Element weblogic-rdbms-bean
does not allow field-map here.
[ejbdoclet]
Hello David,
I'm working on it. Probably, I'll disable it again.
Sorry for troubles.
alex
Sunday, December 15, 2002, 3:53:02 PM, you wrote:
DJ I think there is still a problem with the recently re-enabled foe deployer
DJ tests. I can't build the testsuite on a clean checkout:
DJ [ejbdoclet]
David Jencks wrote:
Hi Anatoly,
I think your discussion has 2 parts that are to me pretty much completely
unrelated:
1. you want to be able to write deployment scripts using jelly
2. you want to be able to deploy bits of security stuff with your
packages.
You are correct, the two pieces are
I ended up with disabling WebLogic DDs validation, thus relying on
XDoclet to generate correct DDs.
If someone knows the reason why it happens on first run. Please, let
me know.
Thanks,
alex
Sunday, December 15, 2002, 4:12:39 PM, you wrote:
AL Hello David,
AL I'm working on it. Probably, I'll
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard
I have requested a clean checkout several times and these are still being generate.
It appears the 1.4.1_01 compile is still checking out the old jboss-all alias rather
than jboss-head.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-
Well, the use case driving this is simply a problem with how JBossMQ integrates
with the security framework. Its a hardcoded property of its security manager
rather than an attribute of the service. If the latter was the case then you could
reference a unique configuration.
The security config
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard
Title: READ THIS
SIMPLE
SYSTEMTM
BEST
SERVICE, BEST PRICES, GUARANTEED RESULTS!
DIAL
1-512-497-4718
I
make $1000's or more everyday What's the secret you ask...? It's
simple, SIMPLE
SYSTEM!
All you need to do is
reach the
masses
Scott M Stark wrote:
Well, the use case driving this is simply a problem with how JBossMQ integrates
with the security framework. Its a hardcoded property of its security manager
rather than an attribute of the service. If the latter was the case then you could
reference a unique configuration.
Bugs item #654181, was opened at 2002-12-15 20:27
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=654181group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Jarl Petter Kvalsvik (ttjarl)
Assigned
- Original Message -
From: Anatoly Akkerman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, December 15, 2002 10:57 AM
Subject: Re: [JBoss-dev] deployment scripts + extending Configuration of JBossSX on
the fly
I've taken a look at the SecurityConfig. All it does is create an
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard
Hi,
This crap code is definitely from jboss-head (not jboss-all).
It compiles fine with jdk1.3 - but fails with jdk1.4.
Regards,
Chris
--- [EMAIL PROTECTED] wrote:
=
==THIS IS AN AUTOMATED EMAIL - SEE
A clean checkout of jboss-head is compiling for me under JDK1.4.1_01 on win2k
and RedHat 8.0 and RedHat 7.3. The issue has to be a conflict with the way the
JDK/Ant are running in your environment. Neither environment has ANT_HOME
set. What does a build with the -verbose flag passed in show
Hi guys,
I run in a problem with RMIConnectorImpl in the jmx/connector/rmi package.
When I use the RMIConnetor in project I get a exception:
javax.naming.NoInitialContextException: Cannot instantiate class:
org.jnp.interfaces.NamingContextFactory. Root exception is
JBoss daily test results
SUMMARY
Number of tests run: 1001
Successful tests: 991
Errors:9
Failures: 1
[time of test: 2002-12-15.15-31 GMT]
[java.version: 1.3.1]
Chris,
I will dedicate time to do a grep and peplace your .sh
/peter
PS: and also dub U as the first to get Rewarded ! ;
söndagen den 15 december 2002 kl 19.33 skrev [EMAIL PROTECTED]:
=
==THIS IS AN AUTOMATED EMAIL - SEE
I had this same error on winxp, jdk1.4.1. Manually creating the
directory allowed the build to finish.
I thought it had something to do with an empty directory in the cache
project -- is there supposed to be code in the cache/src/main directory?
There are only other empty directories on the
Hi Stefan
You just have to add the appropriate JAR file from the /client directory
to you classpath that contains org.jnp.interfaces.NamingContextFactory
which is left to the reader.
Andy
- Original Message -
From: Stefan Groschupf [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday,
Bugs item #654332, was opened at 2002-12-15 19:20
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=654332group_id=22866
Category: JBossWeb
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: jeff dickenson (dickensonj)
Assigned to:
Bugs item #575966, was opened at 2002-07-01 13:59
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=575966group_id=22866
Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Paul Adams (padams)
Assigned to: David
Bugs item #651476, was opened at 2002-12-10 15:30
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=651476group_id=22866
Category: JBossCX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernd Zeitler (frito)
Assigned to: David Jencks
Bugs item #648631, was opened at 2002-12-04 21:25
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=648631group_id=22866
Category: JBossCX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Patrick Murphy (murphyp1)
Assigned to: David Jencks
Bugs item #618908, was opened at 2002-10-05 12:21
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=618908group_id=22866
Category: JBossServer
Group: v4.0
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Frank Langelage (lafr)
Assigned to: David
Sorry if I messed up the JBossMQ JAAS stuf; I could no figure out a
generic way to specify what MBean to invoke from a loginmodule.
The on-the-fly-security configuration you are asking for is however
possible to solve in more that one way. I tried the aproach of Scott a
while ago, but did not
29 matches
Mail list logo