You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ak...@apache.org> on 2007/05/21 20:35:27 UTC
Let's stay on the subject - (Re: [ApacheDS] Embedded http service part2)
Can we keep this thread focused on the technical issues of embedding
an HTTP service into ApacheDS. All this noise is obscuring this thread and
will
make people puke when they troll our archives. Relevant discussions in
accordance
with thread titles are critical if we want our archives to remain an asset.
If you want to deviate from the thread please just start another one with a
new
subject.
Alex
On 5/21/07, Ole Ersoy <ol...@gmail.com> wrote:
>
> SNIP
>
> > If the webapps are as modular and independent from ApacheDS as
> possible,
> > it would maximize developer interest and momentum.
> >
> >
> > If you are talking about having a webapp which does not embed ADS, then
> > this is not the good ML to talk about it : try Geronimo ML or tomcat ML
> ;)
> > If you are thinking about communication between a webapp and a
> > LdapServer outside the container, then JNDI is the key.
>
> What I'm really talking about are use cases and how they can be satisfied.
>
> We know we can embed ApacheDS in a webapp.
> The question is what use case does this satisfy?
>
> Then if embedding ApacheDS is the only way to go
> by all means do it.
>
> If the webapp can be made independent of apacheds, this can
> turn on other contributors that are not
> currently ApacheDS core contributors, but really like the functionality
> in the webapp and want to help make it better.
>
> So it just depends on what the use cases for the webapp are.
>
> See what I mean?
>
> Cheers,
> - Ole
>
>
> >
> > --
> > Regards,
> > Cordialement,
> > Emmanuel Lécharny
> > www.iktek.com <http://www.iktek.com>
>
Re: Let's stay on the subject - (Re: [ApacheDS] Embedded http service
part2)
Posted by Ole Ersoy <ol...@gmail.com>.
Sure - I'm totally digging it now.
Thanks for all the elaboration.
Cheers,
- Ole
Alex Karasulu wrote:
> Just consider this the embedded Jetty service is merely there for the
> standalone server
> configuration. In most cases you won't even turn it on and if you do
> you can have another
> simple instance there just for running some dumb web apps for simple
> tasks like serving
> out DSML.
>
> Alex
>
> On 5/21/07, *Ole Ersoy* <ole.ersoy@gmail.com
> <ma...@gmail.com>> wrote:
>
>
> Alex Karasulu wrote:
> >
> >
> > On 5/21/07, *Ole Ersoy* <ole.ersoy@gmail.com
> <ma...@gmail.com>
> > <mailto:ole.ersoy@gmail.com <ma...@gmail.com>>> wrote:
> >
> > Good Idea :-)
> >
> >
> > Thanks for understanding Ole.
>
> Sure - Thanks for the nudge.
> I'll be more careful to stay
> focused on the thread in the future,
> or change the subject line accordingly.
>
> SNIP
>
> >
> > Oh great thanks.
> >
> > Did we leave anything else out?
> >
> > Oh - I did mention /var/lib/webapps as a FHS home
> > for the webapps. Since it is the FHS home
> > other webapps live there too, so when using
> > this directory care should be taken to ensure that
> > they do not trip up in other servers.
> >
> >
> > Yes this is a good idea. If this is done then we need to add an
> > additional field to
> > tell ApacheDS not to serve out certain webapps in that
> directory. I'll
> > incorporate
> > this into the config as well.
>
> Also, we may want to consider the flip side.
> What if Geronimo or Tomcat try to load an ApacheDS
> App?
>
> I'm just anticipating users going "OK - I installed ApacheDS
> with the webapps and stuff, and now Geronimo is barking..."
>
> I'm sure there's a simple way to handle it,
> and if there's juicy stuff in the webapps for Geronimo
> guys, then they'll probably help ensure that such scenarios are covered.
>
> Cheers,
> - Ole
>
>
Re: Let's stay on the subject - (Re: [ApacheDS] Embedded http service part2)
Posted by Alex Karasulu <ak...@apache.org>.
Just consider this the embedded Jetty service is merely there for the
standalone server
configuration. In most cases you won't even turn it on and if you do you
can have another
simple instance there just for running some dumb web apps for simple tasks
like serving
out DSML.
Alex
On 5/21/07, Ole Ersoy <ol...@gmail.com> wrote:
>
>
> Alex Karasulu wrote:
> >
> >
> > On 5/21/07, *Ole Ersoy* <ole.ersoy@gmail.com
> > <ma...@gmail.com>> wrote:
> >
> > Good Idea :-)
> >
> >
> > Thanks for understanding Ole.
>
> Sure - Thanks for the nudge.
> I'll be more careful to stay
> focused on the thread in the future,
> or change the subject line accordingly.
>
> SNIP
>
> >
> > Oh great thanks.
> >
> > Did we leave anything else out?
> >
> > Oh - I did mention /var/lib/webapps as a FHS home
> > for the webapps. Since it is the FHS home
> > other webapps live there too, so when using
> > this directory care should be taken to ensure that
> > they do not trip up in other servers.
> >
> >
> > Yes this is a good idea. If this is done then we need to add an
> > additional field to
> > tell ApacheDS not to serve out certain webapps in that directory. I'll
> > incorporate
> > this into the config as well.
>
> Also, we may want to consider the flip side.
> What if Geronimo or Tomcat try to load an ApacheDS
> App?
>
> I'm just anticipating users going "OK - I installed ApacheDS
> with the webapps and stuff, and now Geronimo is barking..."
>
> I'm sure there's a simple way to handle it,
> and if there's juicy stuff in the webapps for Geronimo
> guys, then they'll probably help ensure that such scenarios are covered.
>
> Cheers,
> - Ole
>
>
Re: Let's stay on the subject - (Re: [ApacheDS] Embedded http service
part2)
Posted by Ole Ersoy <ol...@gmail.com>.
Alex Karasulu wrote:
>
>
> On 5/21/07, *Ole Ersoy* <ole.ersoy@gmail.com
> <ma...@gmail.com>> wrote:
>
> Good Idea :-)
>
>
> Thanks for understanding Ole.
Sure - Thanks for the nudge.
I'll be more careful to stay
focused on the thread in the future,
or change the subject line accordingly.
SNIP
>
> Oh great thanks.
>
> Did we leave anything else out?
>
> Oh - I did mention /var/lib/webapps as a FHS home
> for the webapps. Since it is the FHS home
> other webapps live there too, so when using
> this directory care should be taken to ensure that
> they do not trip up in other servers.
>
>
> Yes this is a good idea. If this is done then we need to add an
> additional field to
> tell ApacheDS not to serve out certain webapps in that directory. I'll
> incorporate
> this into the config as well.
Also, we may want to consider the flip side.
What if Geronimo or Tomcat try to load an ApacheDS
App?
I'm just anticipating users going "OK - I installed ApacheDS
with the webapps and stuff, and now Geronimo is barking..."
I'm sure there's a simple way to handle it,
and if there's juicy stuff in the webapps for Geronimo
guys, then they'll probably help ensure that such scenarios are covered.
Cheers,
- Ole
Re: Let's stay on the subject - (Re: [ApacheDS] Embedded http service part2)
Posted by Alex Karasulu <ak...@apache.org>.
On 5/21/07, Ole Ersoy <ol...@gmail.com> wrote:
>
> Good Idea :-)
Thanks for understanding Ole.
> OH - I think for the download
> of XSD Instances that some webapps
> attempt we can just use:
>
> xsi:noNamespaceSchemaLocation="/path/to/xml/schema/xmlschemeforwebapp.xsd"
>
> inside the xml documents of the webapp.
>
> In other words package the schema with the webapp,
> and point to it through usage of the
> xsi:noNamespaceSchemaLocation attribute.
Oh great thanks.
Did we leave anything else out?
>
> Oh - I did mention /var/lib/webapps as a FHS home
> for the webapps. Since it is the FHS home
> other webapps live there too, so when using
> this directory care should be taken to ensure that
> they do not trip up in other servers.
Yes this is a good idea. If this is done then we need to add an additional
field to
tell ApacheDS not to serve out certain webapps in that directory. I'll
incorporate
this into the config as well.
Thanks,
Alex
Re: Let's stay on the subject - (Re: [ApacheDS] Embedded http service
part2)
Posted by Ole Ersoy <ol...@gmail.com>.
Good Idea :-)
I think all my concerns regarding
memory footprint etc. were answered.
OH - I think for the download
of XSD Instances that some webapps
attempt we can just use:
xsi:noNamespaceSchemaLocation="/path/to/xml/schema/xmlschemeforwebapp.xsd"
inside the xml documents of the webapp.
In other words package the schema with the webapp,
and point to it through usage of the
xsi:noNamespaceSchemaLocation attribute.
Did we leave anything else out?
Oh - I did mention /var/lib/webapps as a FHS home
for the webapps. Since it is the FHS home
other webapps live there too, so when using
this directory care should be taken to ensure that
they do not trip up in other servers.
Cheers,
- Ole
Alex Karasulu wrote:
> Can we keep this thread focused on the technical issues of embedding
> an HTTP service into ApacheDS. All this noise is obscuring this thread
> and will
> make people puke when they troll our archives. Relevant discussions in
> accordance
> with thread titles are critical if we want our archives to remain an asset.
>
> If you want to deviate from the thread please just start another one
> with a new
> subject.
>
> Alex
>
> On 5/21/07, *Ole Ersoy* <ole.ersoy@gmail.com
> <ma...@gmail.com>> wrote:
>
> SNIP
>
> > If the webapps are as modular and independent from ApacheDS
> as possible,
> > it would maximize developer interest and momentum.
> >
> >
> > If you are talking about having a webapp which does not embed
> ADS, then
> > this is not the good ML to talk about it : try Geronimo ML or
> tomcat ML ;)
> > If you are thinking about communication between a webapp and a
> > LdapServer outside the container, then JNDI is the key.
>
> What I'm really talking about are use cases and how they can be
> satisfied.
>
> We know we can embed ApacheDS in a webapp.
> The question is what use case does this satisfy?
>
> Then if embedding ApacheDS is the only way to go
> by all means do it.
>
> If the webapp can be made independent of apacheds, this can
> turn on other contributors that are not
> currently ApacheDS core contributors, but really like the functionality
> in the webapp and want to help make it better.
>
> So it just depends on what the use cases for the webapp are.
>
> See what I mean?
>
> Cheers,
> - Ole
>
>
> >
> > --
> > Regards,
> > Cordialement,
> > Emmanuel Lécharny
> > www.iktek.com <http://www.iktek.com> <http://www.iktek.com>
>
>