Hi Dave , Francis , laird, CC
Thank you all for your insight. I understand what you are saying. But do you
have anything to say about CC's Point of view???
And CC said this
"""" 5} Can a supporting class access a synchronized method of another class
in the system??
No. Restrictions apply to beans and the transitive closure of all non
system classes they access. System classes defined here as classses that
are not packaged with the bean and that are written with respect to the
server implementation (i.e. same thread management concept).
This would mean that a bean could never call a Vector, since all the
methods on a Vector are synchronized. I think you are being too strict.
cc """""""""
Thank you
arava
> Arava,
>
> I understand that the spec does not mention other classes used by the bean
> but I strongly argue and have in this forum repeatidly that it is
> irrelevant. The requirements are there to allow for portability of your
> beans in a true WORA fashion and whether the bean violates the requirement
> directly or the bean has an accomplice violate the specification is
> irrelevant. The rule has been broken.
>
> So my feeling is that all of your questions are illgeal no matter who does
> the work. Again, killing another person is illegal whether you pull the
> trigger or convince someone else to do it for you. Conspiricy is sometimes
> more nefarious then the actual violation.
>
> I beleive the only proper way to violate the terms of 18.1.2 is through a
> J2EE based API like a JDBC driver or the Connector architecture etc. So, if
> a JDBC driver uses a synchronized method or does I/O that is not a violation
> of 18.1.2 as it is the job of the deployer to choose an appropriate
> implementation of that J2EE API for their platform and hence there is no
> WORA issue.
>
> Dave Wolf
> Internet Applications Division
>
> ----- Original Message -----
> From: "arava" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, November 17, 2000 12:25 AM
> Subject: Re: EJB Questions!
>
> > Hi Dave
> >
> > The restrictions have been listed...sure in the ejb spec. But Please
> permit me
> > to point out a thought. All the restrictions listed there are clearly only
> for
> > the BEANS. Nothing is mentioned for the supporting classes and all of my
> > questions pertain to that.
> >
> > If you have deleted my previous mail here are the questions again
> >
> > Questions
> > ---------------------------------------------------
> > Hi
> >
> > I have a some Questions . Could somebody kiindly clarify?
> >
> > To begin with let me define the terms used in the questions.
> >
> > A} Supporting class --- A Utility class in the same package as the BEAN
> > class
> >
> > B} "class in the system"--A Utility class in the same package as the
> > BEAN class and the supporting class
> >
> > The Questions are:
> >
> > 1} Can you call a static method of a supporting class from your Bean
> > class ?
> >
> > 2} can your supporting class call a static method another class in the
> > System??
> >
> > 3} Should the methods of the supporting class be PUBLIC ONLY or can
> > they have PACKAGE visibility??
> >
> > 4} can your bean access a synchronized method of a supporting class?
> >
> > 5} Can a supporting class access a synchronized method of another class
> > in the system??
> >
> > could you kindly clarify these !
> > thank you
> > arava
> >
> >
> > Dave Wolf wrote:
> >
> > > Arava,
> > >
> > > I dont plan to re-open the can of worms about what you can and cannot do
> in
> > > relation to restrictions placed in section 18.1.2 of the EJB 1.1
> > > specification. I will only say that these restrictions exist to allow
> for
> > > portability of your EJB's across multiple vendors containers and if this
> is
> > > a requirement or need, you should avoid these restrictions completely.
> If
> > > it is not a need, proceed at your own discretion.
> > >
> > > As for the IllegalAccessError this is likely caused by a ClassLoader
> > > conflict where one class is being loaded by a custom ClassLoader and
> another
> > > by the system ClassLoader. You will have to ask your container vendor
> how
> > > they handle this.
> > >
> > > <vendor>
> > >
> > > For instance in Sybase EAServer we allow you to list for each bean which
> > > classes, packages or JARs should be loaded by which the system or custom
> > > ClassLoader.
> > >
> > > </vendor>
> > >
> > > The issue is that two classes loaded by differing ClassLoaders are
> > > incompatable.
> > >
> > > Dave Wolf
> > > Internet Applications Division
> > >
> > > ----- Original Message -----
> > > From: "arava" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Thursday, November 16, 2000 5:58 AM
> > > Subject: EJB Questions!
> > >
> > > > Hi
> > > >
> > > > I have a some Questions . Could somebody kiindly clarify?
> > > >
> > > > To begin with let me define the terms used in the questions.
> > > >
> > > > A} Supporting class --- A Utility class in the same package as the
> BEAN
> > > > class
> > > >
> > > > B} "class in the system"--A Utility class in the same package as the
> > > > BEAN class and the supporting class
> > > >
> > > > The Questions are:
> > > >
> > > > 1} Can you call a static method of a supporting class from your Bean
> > > > class ?
> > > >
> > > > 2} can your supporting class call a static method another class in the
> > > > System??
> > > >
> > > > 3} Should the methods of the supporting class be PUBLIC ONLY or can
> > > > they have PACKAGE visibility??
> > > >
> > > > 4} can your bean access a synchronized method of a supporting class?
> > > >
> > > > 5} Can a supporting class access a synchronized method of another
> class
> > > > in the system??
> > > >
> > > > For some of the above problems I am getting IllegaAccessError.
> > > >
> > > > could you kindly clarify these !
> > > >
> > > > I thank you in anticipation
> > > >
> > > > Thank you
> > > > Arava
> > > >
> > > >
> > >
> ===========================================================================
> > > > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> > > body
> > > > of the message "signoff EJB-INTEREST". For general help, send email
> to
> > > > [EMAIL PROTECTED] and include in the body of the message "help".
> > > >
> > > >
> > >
> > >
> ===========================================================================
> > > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > > of the message "signoff EJB-INTEREST". For general help, send email to
> > > [EMAIL PROTECTED] and include in the body of the message "help".
> >
> >
> ===========================================================================
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > of the message "signoff EJB-INTEREST". For general help, send email to
> > [EMAIL PROTECTED] and include in the body of the message "help".
> >
> >
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
