marc fleury wrote:
> |Ok I see that. When I built it thats where they went. So do these
> |classes have to be present in order for jboss to load over the network?
> |If yes then should I change run.mf to ../lib/ext or do I remove them
> |from the jboss-service.xml classpath?
>
> The jaxp stuff is buggy with CL and it needs the local path stuff right now.
> I talked to their developer a couple of days ago (SUN kiddy, wouldn't cut it
> a day here ;) and they say the new version on apache fixes that. Same with
> log4j (grrrr!) same ol' sun... don't know jack!
>
> lib/ext libraries are those loaded over the network. The ones we are
> talking about need to be present (the ones in lib). I think we could rename
> it /lib/boot and lib/services to be more explicit, I think lib/ext is
> confusing to many people.
>
> The jboss-service.xml should not reference lib/ stuff and if you don't
> specify a codebase it points to http/file://yourinstall/lib/ext... we could
> move that to yourinstall/lib/services
> what do you say?
>
> marcf
>
So the upshot is ..for a network load you still need those three jars locally becuase
they do not want to play nice with the CL.
Go with the lib/boot and lib/services. I'm assuming once those jars are CL safe thenwe
can move the jars from boot to services and remove boot.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
