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
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> Sent: Saturday, May 27, 2000 4:13 AM
> To: JBoss
> Subject: [jBoss-User] Container Configurations
>
>
> I used EJX to create a jboss.xml file for my stateless session
> bean, and EJX included several container configurations (I only wanted
> one, but sadly, the rest appeared by default and refused to be removed).
> When I deployed the bean, though, it said "using default configuration",
> and ignored my container configuration (I removed the extras by hand in
> the XML file). It seems like the parameter "configurationName" is never
> set for the individual bean, so it doesn't know which of the specified
> container configurations to use, and hence doesn't use any of them. How
> can I link a bean to a particular jBoss container configuration?
>
> Thanks,
> Aaron
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
