Aaron
You are right. I found that working through EJX in one order would work,
while another order would fail.
But don't worry - it's early days. Report all your problems, and they
will go away (in the fullness of time).
Aaron Mulder <[EMAIL PROTECTED]> wrote:
> Ahhh, you're right. For some reason I had skipped one of the
>fields in the enterprise bean configuration in EJX. I'm finding EJX a
>little difficult to work with - it's not always clear which sequence of
>load operations (with different file types) should be performed. So I
>guess I should take a look at the new GUI proposal.
>
>Aaron
>
>On Sat, 27 May 2000, marc fleury wrote:
>> I think there are 2 problems
>> 1- the "using default configuration" triggers if you "conf == null"
>> indicating that there is a EJX misconfiguration
>> 2- The container uses a default configuration based on the type of bean
>> (container Factory), he knows which one to use
>>
>> Get the EJX configuration right and this should not happen.
>>
>> marc
>
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Problems?: [EMAIL PROTECTED]
>
--
Justin Forder
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
