You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Sepand M <se...@gmail.com> on 2006/09/05 21:18:57 UTC
Core-Jaas dependencies ... again
Hi guys,
I brought this up before and I thought it was solved, but it isn't.
The basic problem is that JaasAuthenticationBroker,
JaasCertificationAuthenticationBroker (that's a new class), and their
supporting classes need Broker, BrokerFilter, etc. and also need
JaasCertificateCallback (also new), etc.
Broker, BrokerFilter are in the core module (for obvious reasons) and
JaasCertificateCallback, etc. are in Jaas module.
This forces a non-optional dependency between core and jaas, which from what
I understand we are trying to avoid.
Moving JaasAuthenticationBroker and JaasCertificationAuthenticationBroker to
jaas is not an option (as far as I know) since mvn doesn't allow a circular
dependency (from core to jaas and back to core).
Obviously moving everything into core is dumb.
So... any suggestions?
Regards,
Sepand
Re: Core-Jaas dependencies ... again
Posted by Sepand M <se...@gmail.com>.
Oh. That makes more sense (and works well).
Thanks,
Sepand
On 9/5/06, Hiram Chirino <hi...@hiramchirino.com> wrote:
>
> Sepand,
>
> It's ok if it's compile time required... as long as it's not runtime
> required. To me that means it's optional. Since by default the
> broker is not configured with JAAS, you could run the borker without
> the jaas jars.
>
> On 9/5/06, Sepand M <se...@gmail.com> wrote:
> > Responses below
> >
> > On 9/5/06, Guillaume Nodet <gn...@gmail.com> wrote:
> > >
> > > What do you mean by non optional dependency ?
> > > A dependency can always be set as optional, and
> > > actually is until you use it.
> >
> >
> > The way things are, core always needs jaas, so it's not really optional.
> >
> > I guess the other solution is to create a module
> > > for these classes only, but i' m not sure it' s worth it.
> >
> >
> > I highly doubt it's worth the effort.
> >
> > On 9/5/06, Sepand M <se...@gmail.com> wrote:
> > > >
> > > > Hi guys,
> > > >
> > > > I brought this up before and I thought it was solved, but it isn't.
> > > > The basic problem is that JaasAuthenticationBroker,
> > > > JaasCertificationAuthenticationBroker (that's a new class), and
> their
> > > > supporting classes need Broker, BrokerFilter, etc. and also need
> > > > JaasCertificateCallback (also new), etc.
> > > > Broker, BrokerFilter are in the core module (for obvious reasons)
> and
> > > > JaasCertificateCallback, etc. are in Jaas module.
> > > > This forces a non-optional dependency between core and jaas, which
> from
> > > > what
> > > > I understand we are trying to avoid.
> > > > Moving JaasAuthenticationBroker and
> > > JaasCertificationAuthenticationBroker
> > > > to
> > > > jaas is not an option (as far as I know) since mvn doesn't allow a
> > > > circular
> > > > dependency (from core to jaas and back to core).
> > > > Obviously moving everything into core is dumb.
> > > >
> > > > So... any suggestions?
> > > >
> > > > Regards,
> > > > Sepand
> > > >
> > > >
> > >
> > >
> > > --
> > > Cheers,
> > > Guillaume Nodet
> > >
> > >
> >
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
Re: Core-Jaas dependencies ... again
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Sepand,
It's ok if it's compile time required... as long as it's not runtime
required. To me that means it's optional. Since by default the
broker is not configured with JAAS, you could run the borker without
the jaas jars.
On 9/5/06, Sepand M <se...@gmail.com> wrote:
> Responses below
>
> On 9/5/06, Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > What do you mean by non optional dependency ?
> > A dependency can always be set as optional, and
> > actually is until you use it.
>
>
> The way things are, core always needs jaas, so it's not really optional.
>
> I guess the other solution is to create a module
> > for these classes only, but i' m not sure it' s worth it.
>
>
> I highly doubt it's worth the effort.
>
> On 9/5/06, Sepand M <se...@gmail.com> wrote:
> > >
> > > Hi guys,
> > >
> > > I brought this up before and I thought it was solved, but it isn't.
> > > The basic problem is that JaasAuthenticationBroker,
> > > JaasCertificationAuthenticationBroker (that's a new class), and their
> > > supporting classes need Broker, BrokerFilter, etc. and also need
> > > JaasCertificateCallback (also new), etc.
> > > Broker, BrokerFilter are in the core module (for obvious reasons) and
> > > JaasCertificateCallback, etc. are in Jaas module.
> > > This forces a non-optional dependency between core and jaas, which from
> > > what
> > > I understand we are trying to avoid.
> > > Moving JaasAuthenticationBroker and
> > JaasCertificationAuthenticationBroker
> > > to
> > > jaas is not an option (as far as I know) since mvn doesn't allow a
> > > circular
> > > dependency (from core to jaas and back to core).
> > > Obviously moving everything into core is dumb.
> > >
> > > So... any suggestions?
> > >
> > > Regards,
> > > Sepand
> > >
> > >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> >
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: Core-Jaas dependencies ... again
Posted by Sepand M <se...@gmail.com>.
Responses below
On 9/5/06, Guillaume Nodet <gn...@gmail.com> wrote:
>
> What do you mean by non optional dependency ?
> A dependency can always be set as optional, and
> actually is until you use it.
The way things are, core always needs jaas, so it's not really optional.
I guess the other solution is to create a module
> for these classes only, but i' m not sure it' s worth it.
I highly doubt it's worth the effort.
On 9/5/06, Sepand M <se...@gmail.com> wrote:
> >
> > Hi guys,
> >
> > I brought this up before and I thought it was solved, but it isn't.
> > The basic problem is that JaasAuthenticationBroker,
> > JaasCertificationAuthenticationBroker (that's a new class), and their
> > supporting classes need Broker, BrokerFilter, etc. and also need
> > JaasCertificateCallback (also new), etc.
> > Broker, BrokerFilter are in the core module (for obvious reasons) and
> > JaasCertificateCallback, etc. are in Jaas module.
> > This forces a non-optional dependency between core and jaas, which from
> > what
> > I understand we are trying to avoid.
> > Moving JaasAuthenticationBroker and
> JaasCertificationAuthenticationBroker
> > to
> > jaas is not an option (as far as I know) since mvn doesn't allow a
> > circular
> > dependency (from core to jaas and back to core).
> > Obviously moving everything into core is dumb.
> >
> > So... any suggestions?
> >
> > Regards,
> > Sepand
> >
> >
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
Re: Core-Jaas dependencies ... again
Posted by Guillaume Nodet <gn...@gmail.com>.
What do you mean by non optional dependency ?
A dependency can always be set as optional, and
actually is until you use it.
I guess the other solution is to create a module
for these classes only, but i' m not sure it' s worth it.
On 9/5/06, Sepand M <se...@gmail.com> wrote:
>
> Hi guys,
>
> I brought this up before and I thought it was solved, but it isn't.
> The basic problem is that JaasAuthenticationBroker,
> JaasCertificationAuthenticationBroker (that's a new class), and their
> supporting classes need Broker, BrokerFilter, etc. and also need
> JaasCertificateCallback (also new), etc.
> Broker, BrokerFilter are in the core module (for obvious reasons) and
> JaasCertificateCallback, etc. are in Jaas module.
> This forces a non-optional dependency between core and jaas, which from
> what
> I understand we are trying to avoid.
> Moving JaasAuthenticationBroker and JaasCertificationAuthenticationBroker
> to
> jaas is not an option (as far as I know) since mvn doesn't allow a
> circular
> dependency (from core to jaas and back to core).
> Obviously moving everything into core is dumb.
>
> So... any suggestions?
>
> Regards,
> Sepand
>
>
--
Cheers,
Guillaume Nodet