> Someone else has reported this issue. Apparently the 1.3.0 version is
> not picking up editors that are not on the system classpath.
> I have not
> seen this issue with the IBM 1.3.1 version of the jdk.
I sent the following to jboss-users on the 8th.
Kev
> org.jboss.deployment.DeploymentException: No property editor for
attribute: ConfigurationURL; type=class java.net.URL
I've just come across this one a few days ago, moving jboss onto solaris.
I tracked the problem down to the version of the JDK being run on the
machine, 1.3.0_04.
The ServiceConfigurator uses java.beans.PropertyEditorManager to load
the PropertyEditor. This uses the java.beans.Introspector to instantiate
the editor, however it was ignoring the context class loader for the
current thread. This has changed in JDK1.3.1 and JDK1.4.0.
I have commented out the ConfigurationURL attribute of the Log4jService in
jboss-service.xml for now as it defaults to the same value. I wouldn't
advise
it in a production environment as I don't know the implications of this
problem.
I don't mind because we are only using the solaris box as the netboot server
for our development machines (NT/2000 + JDK1.3.1/JDK1.4.0).
We will eventually use the solaris box to host some of our test environments
but
not until we have some JDKs on at least 1.3.1 :-).
Kev
Kevin Conner
Orchard Information Systems Limited
Newcastle Technopole, Kings Manor
Newcastle Upon Tyne, NE1 6PA. United Kingdom
Registered in England, Number 1900078
Tel: +44 (0) 191-2032536 Fax: +44 (0) 191 2302515
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
