Request of Publish of Plugin Searchable - Multi Tenant Bridge (SMTB)

[archanaa.karun]

Hi,

I have created the Plugin to overcome the struggle to the problems that exist when the two essential Grails Plugins Searchable and Multi Tenant (Core) for an application come together. 

Please review it and give the permission to publish the Plugin as this will be useful for others to overcome the issue.

Grails.org Username: archanaa-karun
Name of the Plugin: searchable-multi-tenant-bridge
Link to Source Code: https://github.com/archanaa-karun/searchable-multi-tenant-bridge

Thanks,
Archanaa.

[Graeme Rocher-2]

The drawbacks of the plugin seem quite severe, have you discussed this with the multi-tenant plugin devs to see if there is a way around those drawbacks?

-- 

Graeme Rocher

On Monday, July 16, 2012 at 3:30 PM, Archanaa Karun wrote:

Hi,

I have created the Plugin to overcome the struggle to the problems that exist when the two essential Grails Plugins Searchable and Multi Tenant (Core) for an application come together. 

Please review it and give the permission to publish the Plugin as this will be useful for others to overcome the issue.

Grails.org Username: archanaa-karun
Name of the Plugin: searchable-multi-tenant-bridge
Link to Source Code: https://github.com/archanaa-karun/searchable-multi-tenant-bridge

Thanks,
Archanaa.

[archanaa.karun]

The drawbacks has to be taken up for both the Plugins to co-exist. I tried my level best to overcome these. But there seems to be no way out, unless and until both the Owners of the Plugins come together.

There were many posts on this:
http://grails.1312388.n4.nabble.com/Plugin-Incompatibility-Multi-Tenant-Searchable-td1354534.html
http://grails.1312388.n4.nabble.com/Compilation-failed-after-installing-falcone-util-plugin-td1754560.html

But nothing seemed to work for me. So I wrote my own plugin to overcome the issue.

I did not speak to the Multi-Tenant team regarding this.

Luckily I always had the workaround of whatever issues I faced with the Multi Tenant features.

I thought it will be useful if I can share the plugin with others who can live with the workarounds.

Thanks,
Archanaa.

On Mon, Jul 16, 2012 at 9:20 PM, Graeme Rocher <[hidden email]> wrote:

The drawbacks of the plugin seem quite severe, have you discussed this with the multi-tenant plugin devs to see if there is a way around those drawbacks?

-- 

Graeme Rocher

On Monday, July 16, 2012 at 3:30 PM, Archanaa Karun wrote:

Hi,

I have created the Plugin to overcome the struggle to the problems that exist when the two essential Grails Plugins Searchable and Multi Tenant (Core) for an application come together. 

Please review it and give the permission to publish the Plugin as this will be useful for others to overcome the issue.

Grails.org Username: archanaa-karun
Name of the Plugin: searchable-multi-tenant-bridge
Link to Source Code: https://github.com/archanaa-karun/searchable-multi-tenant-bridge

Thanks,
Archanaa.

[pledbrook]

> The drawbacks has to be taken up for both the Plugins to co-exist. I tried
> my level best to overcome these. But there seems to be no way out, unless
> and until both the Owners of the Plugins come together.
>
> There were many posts on this:
> http://grails.1312388.n4.nabble.com/Plugin-Incompatibility-Multi-Tenant-Searchable-td1354534.html
> http://grails.1312388.n4.nabble.com/Compilation-failed-after-installing-falcone-util-plugin-td1754560.html
>
> But nothing seemed to work for me. So I wrote my own plugin to overcome the
> issue.

Are there any changes to the Searchable plugin that would help?

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Matt Sheehan]

We had the same issues and were able to get around them using the methods described in the first thread. Specifically

1. Fork compass. Modify to use reflection instead of casting to SessionFactoryImpl.
2. Fork multitenant plugin. Comment out "context.entityClass == null" in the if statement within the criteriaCreated block.

Matt

On Tue, Jul 17, 2012 at 8:44 AM, Peter Ledbrook <[hidden email]> wrote:

> The drawbacks has to be taken up for both the Plugins to co-exist. I tried
> my level best to overcome these. But there seems to be no way out, unless
> and until both the Owners of the Plugins come together.
>
> There were many posts on this:
> http://grails.1312388.n4.nabble.com/Plugin-Incompatibility-Multi-Tenant-Searchable-td1354534.html
> http://grails.1312388.n4.nabble.com/Compilation-failed-after-installing-falcone-util-plugin-td1754560.html
>
> But nothing seemed to work for me. So I wrote my own plugin to overcome the
> issue.

Are there any changes to the Searchable plugin that would help?

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

> We had the same issues and were able to get around them using the methods
> described in the first thread. Specifically
>
> 1. Fork compass. Modify to use reflection instead of casting to
> SessionFactoryImpl.

This can be added to the repository:

    https://github.com/gpc/compass

That's the source from which we build Compass for the Searchable plugin.

> 2. Fork multitenant plugin. Comment out "context.entityClass == null" in the
> if statement within the criteriaCreated block.

Are the maintainers of the plugin averse to including this in the plugin?

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[basejump (Josh)]

What I believe should happen is that these plugins that need to "hijack" the sessionFactory should be using the
http://multi-tenant.github.com/grails-hibernate-hijacker/docs/v0.6/guide/index.html
If they were using this then no one would be stepping on each other.
the multi-tenant-single-db uses this and it works well.

I think this capability should really be in grails-core

> Are the maintainers of the plugin averse to including this in the plugin?
>
> Peter
>
> --
> Peter Ledbrook
> Grails Advocate
> SpringSource - A Division of VMware
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email