I agree with you completely with you. These hacks are only made locally in
my system only for testing the great Francisco's work. When we go in
production phase we need to resolve the remaining issues.
Claudio
> -----Original Message-----
> From: Jason Dillon [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 12, 2002 10:45 AM
> To: Vesco Claudio
> Cc: 'David Jencks'; [EMAIL PROTECTED]; 'Francisco
> Reverbel'
> Subject: RE: [JBoss-dev] Test Suite broken?
>
> Yes, I understand this is a JacORB issue... but I suggest that there is a
> better way to handle the problem which they are trying to solve otherthan
> adding the the jvm boot classpath.
>
> I asked Francisco to look into the details further and am still waiting
> for
> information about the problem.
>
> We want to use JBoss for classloading & not force users to start managing
> hacked archives on there boot classpath. For example, if the classes are
> remote (using NetBoot), we then have a problem adding the jar to the boot
> classpath.
>
> I think it is a REALLY BAD IDEA to special case this or any other archive
> just
> to make the system work.
>
> For example, imagine if JBoss insisted that the java.lang.String impl was
> broken (which it might be) and forced you to use a patched version of the
> VM
> classes for the system to work correctly... what a pain in the ass. It
> would
> have been better to handle the buggy String impl in a different fashion.
>
> Since I do not know the full details of the JacORB hack, I can not say
> that
> the case is the same, but I can say that there is a high chance that an
> alternative aproache could be used to solve the same problem.
>
> I think that until this is solved, we can not ship with iiop support in
> the
> default config, as there is no easy way to determie and setup this boot
> classpath hack.
>
> --jason
>
>
> Quoting Vesco Claudio <[EMAIL PROTECTED]>:
>
> > Hi!
> >
> > I think that this is a jacorb problem and for now we cannot remove the
> > -Xbootclasspath :-(
> >
> > If I remember well the problem is when the iiop container invoker tries
> to
> > bind the ejb home into the corba naming space, it cannot create a
> > subcontext.
> >
> > Claudio
> >
> > PS to Francisco: I have tested iiop in jdk 1.4 in my test bed with
> jython,
> > it works! (deploy in jboss and calling ejb over iiop) :-)
> > but the testsuite is still falling, today I'll try to figure why.
> >
> > > -----Original Message-----
> > > From: Jason Dillon [SMTP:[EMAIL PROTECTED]]
> > > Sent: Thursday, April 11, 2002 11:07 PM
> > > To: Vesco Claudio
> > > Cc: 'David Jencks'; [EMAIL PROTECTED]
> > > Subject: Re: [JBoss-dev] Test Suite broken?
> > >
> > > >
> > > >
> > > >
> > > >export JAVA_OPT=-Dpolicy.expandProperties=false
> > > >-Xbootclasspath/p:$JBOSS_HOME/lib/jacorb.jar
> > > >
> > >
> > > We need to fix this... having to rely on non-standard -X flags to the
> > > JVM is going to be a pain in the ass... There must be a better way to
>
> > > get around this issue with JacORB.
> > >
> > > --jason
> > >
> >
>
>
>
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
