<div dir="ltr"><div><div>This sounds like a perfect valid case for new subsystem<br>that would handle hibernate-search related stuff.<br><br></div>and could based on some deployment markers enable / add dependent modules to deployment.<br>
<br></div>it could also help configure search / ogm via server config :)<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 1, 2014 at 12:58 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@hibernate.org" target="_blank">sanne@hibernate.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Currently users wishing for Search super-powers in their Hibernate<br>
applications need to enable the module explicitly.<br>
<br>
This seems to be rather annoying, and we have questions like this one:<br>
- <a href="https://community.jboss.org/thread/243346" target="_blank">https://community.jboss.org/thread/243346</a><br>
<br>
I see no reasons to not enable it by default, following the same<br>
activation rules of other Hibernate dependencies: it's very<br>
conservative about not auto-enabling itself when not needed.<br>
<br>
May I open such a feature request? Happy to try the patching myself.<br>
<br>
Sanne<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>