Hi, I noticed that XWiki does case sensitive search, e.g. if I search for "available", available will be found, but not "Available." How can I make searches case insensitive? Speaking of searching, it not clear to me what happens if I turn on Lucene. Does this replace searching back-end for regular search box, or I have to add new page for searching? Regards, v Zeljko
On 3/26/07, Zeljko Trogrlic <[email protected]> wrote:
Hi,
I noticed that XWiki does case sensitive search, e.g. if I search for "available", available will be found, but not "Available."
How can I make searches case insensitive?
The search page should be case insensitive. If it is not, then it might be a bug. Are you sure there isn't a typo in the "Available" word, as it is in the document? Or, is it in a page named like the one where "available" is, because page names are compared case-insensitive and only one hit is returned. Speaking of searching, it not clear to me what happens if I turn on
Lucene. Does this replace searching back-end for regular search box, or I have to add new page for searching?
No, it does not replace normal search. You will have to write a search page that uses Lucene. Maybe we should have this page in the Code area on xwiki.org. Sergiu -- http://purl.org/net/sergiu
On Mar 26, 2007, at 9:19 AM, Sergiu Dumitriu wrote:
On 3/26/07, Zeljko Trogrlic <[email protected]> wrote: Hi,
I noticed that XWiki does case sensitive search, e.g. if I search for "available", available will be found, but not "Available."
How can I make searches case insensitive?
The search page should be case insensitive. If it is not, then it might be a bug.
it's a bug... I don't know if we have a jira issue. I heard this issue from another user 2 days ago and I remember seeing it myself.
Are you sure there isn't a typo in the "Available" word, as it is in the document? Or, is it in a page named like the one where "available" is, because page names are compared case-insensitive and only one hit is returned.
Speaking of searching, it not clear to me what happens if I turn on Lucene. Does this replace searching back-end for regular search box, or I have to add new page for searching?
No, it does not replace normal search. You will have to write a search page that uses Lucene. Maybe we should have this page in the Code area on xwiki.org.
We already have it :-) http://www.xwiki.org/xwiki/bin/view/Code/LucenePlugin Thanks -Vincent
Vincent Massol wrote:
On Mar 26, 2007, at 9:19 AM, Sergiu Dumitriu wrote:
On 3/26/07, *Zeljko Trogrlic* <[email protected] <mailto:[email protected]>> wrote:
Hi,
I noticed that XWiki does case sensitive search, e.g. if I search for "available", available will be found, but not "Available."
How can I make searches case insensitive?
The search page should be case insensitive. If it is not, then it might be a bug.
it's a bug... I don't know if we have a jira issue. I heard this issue from another user 2 days ago and I remember seeing it myself.
I'm using PostgreSQL as backend, could that be the source of the problem? How actually searching works? Using database functions? If you give me a hint where is it done (in code) I can investigate the problem.
Speaking of searching, it not clear to me what happens if I turn on Lucene. Does this replace searching back-end for regular search box, or I have to add new page for searching?
No, it does not replace normal search. You will have to write a search page that uses Lucene. Maybe we should have this page in the Code area on xwiki.org <http://xwiki.org>.
We already have it :-)
It was not clear to me does it replace regular search, thanks for the answer. I will add search box integration to JIRA for future reference, and I think that this should be stated on plugin page, because description is a bit misleading: "It can be used in place of the default search implementation..."
On 3/27/07, Zeljko Trogrlic <[email protected]> wrote:
Hi,
I noticed that XWiki does case sensitive search, e.g. if I search
for
"available", available will be found, but not "Available."
How can I make searches case insensitive?
The search page should be case insensitive. If it is not, then it might be a bug.
it's a bug... I don't know if we have a jira issue. I heard this issue from another user 2 days ago and I remember seeing it myself.
I'm using PostgreSQL as backend, could that be the source of the problem? How actually searching works? Using database functions? If you give me a hint where is it done (in code) I can investigate the problem.
Check the code for Main.WebSearch , its a series of hibernate hql queries. The string is searched with "where field LIKE '$keyword'", so if LIKE is not case insensitive, this is the cause.
Speaking of searching, it not clear to me what happens if I turn on
Lucene. Does this replace searching back-end for regular search box, or I have to add new page for searching?
No, it does not replace normal search. You will have to write a search page that uses Lucene. Maybe we should have this page in the Code area on xwiki.org <http://xwiki.org>.
We already have it :-)
It was not clear to me does it replace regular search, thanks for the answer. I will add search box integration to JIRA for future reference, and I think that this should be stated on plugin page, because description is a bit misleading: "It can be used in place of the default search implementation..."
Sergiu -- http://purl.org/net/sergiu
Vincent:
No, it does not replace normal search. You will have to write a search page that uses Lucene. Maybe we should have this page in the Code area on xwiki.org <http://xwiki.org>.
We already have it :-)
This is very timely for me, as I was next looking into how to do this, so I am grateful. But it's very puzzling to me that I can't find the actual plugin; I had thought for all this time that it was in the distribution I have (0.9.840), but it isn't. I had been hearing about it for over a year and assumed, like someone earlier in this thread, that it was just an option that needed to be turned on. Furthermore, I haven't been able to download it from the SVN site because (apparently) of firewall issues here - I can see the code, and could probably download it all via the web interface, but that's incredibly tedious, and we also have the 1.0b5 code, so I can get it from there - if indeed it is there - or have I made another incorrect assumption? brain[sic]
Sergiu Dumitriu <sergiu.dumitriu@...> writes:
On 3/27/07, Zeljko Trogrlic <[email protected]> wrote:
Hi,>>>> I noticed that XWiki does case sensitive search, e.g. if
I search for>> "available", available will be found, but not "Available."
How can I make searches case insensitive?>>>>>> The search page
should be case insensitive. If it is not, then it>> might be a bug.>> it's a bug... I don't know if we have a jira issue. I heard this issue
Check the code for Main.WebSearch , its a series of hibernate hql queries. The string is searched with "where field LIKE '$keyword'", so if LIKE is not case insensitive, this is the cause.
You were right, problem solved, JIRA issue created: http://jira.xwiki.org/jira/browse/XWIKI-1031
Hmm, my origional reply got rejected/did not send for some reason.. Problem is that MySQL is default case-insensitive; so LIKE is working fine for MySQL queries. eg: select doc.name from XWikiDocument doc where doc.fullName like '%thistest' above will be case-insensitive on MySQL. PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive. eg: select doc.name from XWikiDocument doc where doc.fullName ilike '%thistest' above (should, far as I can recall) be case-insensitive on PostgreSQL, but again may not work with MySQL. I would have thought Hibernate fixes this kind of discrepency though? ________________________________ From: Sergiu Dumitriu [mailto:[email protected]] Sent: 27 March 2007 08:50 To: [email protected] Subject: Re: [xwiki-users] Re: Case insensitive search On 3/27/07, Zeljko Trogrlic <[email protected]> wrote: >> >> Hi, >> >> I noticed that XWiki does case sensitive search, e.g. if I search for >> "available", available will be found, but not "Available." >> >> How can I make searches case insensitive? >> >> >> The search page should be case insensitive. If it is not, then it >> might be a bug. > > it's a bug... I don't know if we have a jira issue. I heard this issue > from another user 2 days ago and I remember seeing it myself. I'm using PostgreSQL as backend, could that be the source of the problem? How actually searching works? Using database functions? If you give me a hint where is it done (in code) I can investigate the problem. Check the code for Main.WebSearch , its a series of hibernate hql queries. The string is searched with "where field LIKE '$keyword'", so if LIKE is not case insensitive, this is the cause. >> Speaking of searching, it not clear to me what happens if I turn on >> Lucene. Does this replace searching back-end for regular search >> box, or >> I have to add new page for searching? >> >> >> No, it does not replace normal search. You will have to write a search >> page that uses Lucene. Maybe we should have this page in the Code area >> on xwiki.org <http://xwiki.org>. > > We already have it :-) > > http://www.xwiki.org/xwiki/bin/view/Code/LucenePlugin It was not clear to me does it replace regular search, thanks for the answer. I will add search box integration to JIRA for future reference, and I think that this should be stated on plugin page, because description is a bit misleading: "It can be used in place of the default search implementation..." Sergiu -- http://purl.org/net/sergiu
On Mar 27, 2007, at 4:19 PM, Zeljko Trogrlic wrote:
Esbach, Brandon <Esbachb@...> writes:
PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive.
ILIKE is PostgreSQL specific. Two UPPERCASE will work on any database.
Are you sure there isn't any hibernate-specific solution to the problem? (which IMO might be better) What about using something like the ilike in http://www.hibernate.org/ hib_docs/v3/api/org/hibernate/criterion/Restrictions.html? Does anyone know how to use this Expression class in Hibernate? Thanks -Vincent
Vincent Massol wrote:
On Mar 27, 2007, at 4:19 PM, Zeljko Trogrlic wrote:
Esbach, Brandon <Esbachb@...> writes:
PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive.
ILIKE is PostgreSQL specific. Two UPPERCASE will work on any database.
Are you sure there isn't any hibernate-specific solution to the problem? (which IMO might be better)
What about using something like the ilike in http://www.hibernate.org/hib_docs/v3/api/org/hibernate/criterion/Restriction... Does anyone know how to use this Expression class in Hibernate?
Thanks -Vincent
ILIKE is not in HQL reference. Can somebody running something else than PostgreSQL test is it working on his system? If ILIKE doesn't work on other databases, I'll rather keep UPPERs because fiddling with Hibernate API in Velocity is both impossible and, to my standards, over-engineered.
On Mar 27, 2007, at 9:33 PM, Zeljko Trogrlic wrote:
Vincent Massol wrote:
On Mar 27, 2007, at 4:19 PM, Zeljko Trogrlic wrote:
Esbach, Brandon <Esbachb@...> writes:
PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive.
ILIKE is PostgreSQL specific. Two UPPERCASE will work on any database. Are you sure there isn't any hibernate-specific solution to the problem? (which IMO might be better) What about using something like the ilike in http:// www.hibernate.org/hib_docs/v3/api/org/hibernate/criterion/ Restrictions.html? Does anyone know how to use this Expression class in Hibernate? Thanks -Vincent
ILIKE is not in HQL reference. Can somebody running something else than PostgreSQL test is it working on his system?
If ILIKE doesn't work on other databases, I'll rather keep UPPERs because fiddling with Hibernate API in Velocity is both impossible and, to my standards, over-engineered.
I don't think it should be done in Velocity at all. We could do it in Java, in the search implementations. Again, I don't know how this works (or doesn't work) in Hibernate. I'm just making sure we've covered all angles before deciding. Thanks -Vincent
Well, I can confirm it's an issue for me on MySQL. It raises an Xwiki exception, though it's not clear if the exception is bubbling up from hibernate, or from xwiki itself. According to the v3 hibernate docs (not sure what vers of hib xwiki uses), it is supposed to be supported - search for "insensitive" on the hibernate docs site; returns three results, first one covers ilike. One would think the hibernate.cfg.xml allows you to remap key things like the ilike/like, etc; but failing that, perhaps instead of "fixing" this as a hardcoded change,: How about a new config set for the xwiki.cfg file? So then if someone uses an odd database, supporting it should not require added effort (just checking keywords). For example, replacing like and % (memory scratchy, but iirc postgresql supports _ as well as % for single wildcards?). hibernate.replace.list=like,%,' <the list is used so that you're not constantly scanning the whole config file for replacements> hibernate.replace.like=ilike hibernate.replace.%=_ hibernate.replace.'='' The last one there would be a godsend as you often get users that stick in a ' that needs to be escaped, though you can use .replace(), it's still tacky that way. -----Original Message----- From: Vincent Massol [mailto:[email protected]] Sent: 27 March 2007 20:42 To: [email protected] Subject: Re: [xwiki-users] Re: Case insensitive search On Mar 27, 2007, at 9:33 PM, Zeljko Trogrlic wrote:
Vincent Massol wrote:
On Mar 27, 2007, at 4:19 PM, Zeljko Trogrlic wrote:
Esbach, Brandon <Esbachb@...> writes:
PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive.
ILIKE is PostgreSQL specific. Two UPPERCASE will work on any database. Are you sure there isn't any hibernate-specific solution to the problem? (which IMO might be better) What about using something like the ilike in http:// www.hibernate.org/hib_docs/v3/api/org/hibernate/criterion/ Restrictions.html? Does anyone know how to use this Expression class in Hibernate? Thanks -Vincent
ILIKE is not in HQL reference. Can somebody running something else than PostgreSQL test is it working on his system?
If ILIKE doesn't work on other databases, I'll rather keep UPPERs because fiddling with Hibernate API in Velocity is both impossible and, to my standards, over-engineered.
I don't think it should be done in Velocity at all. We could do it in Java, in the search implementations. Again, I don't know how this works (or doesn't work) in Hibernate. I'm just making sure we've covered all angles before deciding. Thanks -Vincent
On Mar 28, 2007, at 10:52 AM, Esbach, Brandon wrote:
Well, I can confirm it's an issue for me on MySQL. It raises an Xwiki exception, though it's not clear if the exception is bubbling up from hibernate, or from xwiki itself. According to the v3 hibernate docs (not sure what vers of hib xwiki uses)
3.1.2 (check your WEB-INF/lib :-))
, it is supposed to be supported - search for "insensitive" on the hibernate docs site; returns three results, first one covers ilike.
Exactly my point. We should investigate this first rather than trying to implement it ourselves and only if it doesn't work then we should think of alternative solutions.
One would think the hibernate.cfg.xml allows you to remap key things like the ilike/like, etc; but failing that, perhaps instead of "fixing" this as a hardcoded change,: How about a new config set for the xwiki.cfg file? So then if someone uses an odd database, supporting it should not require added effort (just checking keywords). For example, replacing like and % (memory scratchy, but iirc postgresql supports _ as well as % for single wildcards?). hibernate.replace.list=like,%,' <the list is used so that you're not constantly scanning the whole config file for replacements> hibernate.replace.like=ilike hibernate.replace.%=_ hibernate.replace.'=''
Isn't this one purpose of Hibernate (to isolate yourself from the DB)? Thanks -Vincent
The last one there would be a godsend as you often get users that stick in a ' that needs to be escaped, though you can use .replace(), it's still tacky that way.
-----Original Message----- From: Vincent Massol [mailto:[email protected]] Sent: 27 March 2007 20:42 To: [email protected] Subject: Re: [xwiki-users] Re: Case insensitive search
On Mar 27, 2007, at 9:33 PM, Zeljko Trogrlic wrote:
Vincent Massol wrote:
On Mar 27, 2007, at 4:19 PM, Zeljko Trogrlic wrote:
Esbach, Brandon <Esbachb@...> writes:
PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive.
ILIKE is PostgreSQL specific. Two UPPERCASE will work on any database. Are you sure there isn't any hibernate-specific solution to the problem? (which IMO might be better) What about using something like the ilike in http:// www.hibernate.org/hib_docs/v3/api/org/hibernate/criterion/ Restrictions.html? Does anyone know how to use this Expression class in Hibernate? Thanks -Vincent
ILIKE is not in HQL reference. Can somebody running something else than PostgreSQL test is it working on his system?
If ILIKE doesn't work on other databases, I'll rather keep UPPERs because fiddling with Hibernate API in Velocity is both impossible and, to my standards, over-engineered.
I don't think it should be done in Velocity at all. We could do it in Java, in the search implementations.
Again, I don't know how this works (or doesn't work) in Hibernate. I'm just making sure we've covered all angles before deciding.
Thanks -Vincent
Well, given that we're therefore on the requisite version of Hibernate; it's more a bug for the hibernate folks than xwiki then. -----Original Message----- From: Vincent Massol [mailto:[email protected]] Sent: 28 March 2007 10:03 To: [email protected] Subject: Re: [xwiki-users] Re: Case insensitive search On Mar 28, 2007, at 10:52 AM, Esbach, Brandon wrote:
Well, I can confirm it's an issue for me on MySQL. It raises an Xwiki
exception, though it's not clear if the exception is bubbling up from hibernate, or from xwiki itself. According to the v3 hibernate docs (not sure what vers of hib xwiki uses)
3.1.2 (check your WEB-INF/lib :-))
, it is supposed to be supported - search for "insensitive" on the hibernate docs site; returns three results, first one covers ilike.
Exactly my point. We should investigate this first rather than trying to implement it ourselves and only if it doesn't work then we should think of alternative solutions.
One would think the hibernate.cfg.xml allows you to remap key things like the ilike/like, etc; but failing that, perhaps instead of "fixing" this as a hardcoded change,: How about a new config set for the xwiki.cfg file? So then if someone
uses an odd database, supporting it should not require added effort (just checking keywords). For example, replacing like and % (memory scratchy, but iirc postgresql supports _ as well as % for single wildcards?). hibernate.replace.list=like,%,' <the list is used so that you're not constantly scanning the whole config file for replacements> hibernate.replace.like=ilike hibernate.replace.%=_ hibernate.replace.'=''
Isn't this one purpose of Hibernate (to isolate yourself from the DB)? Thanks -Vincent
The last one there would be a godsend as you often get users that stick in a ' that needs to be escaped, though you can use .replace(), it's still tacky that way.
-----Original Message----- From: Vincent Massol [mailto:[email protected]] Sent: 27 March 2007 20:42 To: [email protected] Subject: Re: [xwiki-users] Re: Case insensitive search
On Mar 27, 2007, at 9:33 PM, Zeljko Trogrlic wrote:
Vincent Massol wrote:
On Mar 27, 2007, at 4:19 PM, Zeljko Trogrlic wrote:
Esbach, Brandon <Esbachb@...> writes:
PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive.
ILIKE is PostgreSQL specific. Two UPPERCASE will work on any database. Are you sure there isn't any hibernate-specific solution to the problem? (which IMO might be better) What about using something like
the ilike in http:// www.hibernate.org/hib_docs/v3/api/org/hibernate/criterion/ Restrictions.html? Does anyone know how to use this Expression class
in Hibernate? Thanks -Vincent
ILIKE is not in HQL reference. Can somebody running something else than PostgreSQL test is it working on his system?
If ILIKE doesn't work on other databases, I'll rather keep UPPERs because fiddling with Hibernate API in Velocity is both impossible and, to my standards, over-engineered.
I don't think it should be done in Velocity at all. We could do it in Java, in the search implementations.
Again, I don't know how this works (or doesn't work) in Hibernate. I'm just making sure we've covered all angles before deciding.
Thanks -Vincent
Guys: The docs have a problem when installing on postgres, since the manual says to use the xwiki Xar AFTER a configured Postgres DB, but no script to create the DB in postgres is given. Is this an error in the doc or have I not understood properly. Regards, Mauricio Hernández Durán Director de Proyectos Ingenian Software LTDA. PBX + 57 (1) 6233606/17 ext 106 Kra 14 #90-31 Ofi 403 Bogotá -----Mensaje original----- De: news [mailto:[email protected]] En nombre de Zeljko Trogrlic Enviado el: Martes, 27 de Marzo de 2007 02:33 p.m. Para: [email protected] Asunto: [xwiki-users] Re: Case insensitive search Vincent Massol wrote:
On Mar 27, 2007, at 4:19 PM, Zeljko Trogrlic wrote:
Esbach, Brandon <Esbachb@...> writes:
PostgreSQL treats LIKE queries as case-sensitive; so to make it case-insensitive you would have to use ilike (extra i in front of like) to make it case-insensitive.
ILIKE is PostgreSQL specific. Two UPPERCASE will work on any database.
Are you sure there isn't any hibernate-specific solution to the problem? (which IMO might be better)
What about using something like the ilike in
http://www.hibernate.org/hib_docs/v3/api/org/hibernate/criterion/Restriction s.html?
Does anyone know how to use this Expression class in Hibernate?
Thanks -Vincent
ILIKE is not in HQL reference. Can somebody running something else than PostgreSQL test is it working on his system? If ILIKE doesn't work on other databases, I'll rather keep UPPERs because fiddling with Hibernate API in Velocity is both impossible and, to my standards, over-engineered.
Mauricio Hernández wrote:
Guys:
The docs have a problem when installing on postgres, since the manual says to use the xwiki Xar AFTER a configured Postgres DB, but no script to create the DB in postgres is given.
Is this an error in the doc or have I not understood properly.
Regards,
Mauricio Hernández Durán
You can create it with few clicks in pgAdmin. You don't have to create tables; just create database (as empty container for tables) and user and XAR will take care of the rest.
In case anyone has this problem, we fixed it using a level 3 JDBC driver for postgres and the proper version of the driver (in our case we were using a 7.3 driver with a 7.4 pg server). Aparently xwiki could not populate the initial schemmas and everything went broke from then on. After we changed the driver we could populate a XAR file just like you mention. Thankyou for your help!! On 3/28/07, Zeljko Trogrlic <[email protected]> wrote:
Mauricio Hernández wrote:
Guys:
The docs have a problem when installing on postgres, since the manual says to use the xwiki Xar AFTER a configured Postgres DB, but no script to create the DB in postgres is given.
Is this an error in the doc or have I not understood properly.
Regards,
Mauricio Hernández Durán
You can create it with few clicks in pgAdmin. You don't have to create tables; just create database (as empty container for tables) and user and XAR will take care of the rest.
-- You receive this message as a subscriber of the [email protected] list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- Mauricio Hernández Durán PBX 6233606/17 ext 106 Kra 14 # 90-31oficina 403 http://www.ingenian.com
On Mar 27, 2007, at 9:50 AM, Sergiu Dumitriu wrote:
On 3/27/07, Zeljko Trogrlic <[email protected]> wrote:
Hi,
I noticed that XWiki does case sensitive search, e.g. if I
search for
"available", available will be found, but not "Available."
How can I make searches case insensitive?
The search page should be case insensitive. If it is not, then it might be a bug.
it's a bug... I don't know if we have a jira issue. I heard this issue from another user 2 days ago and I remember seeing it myself.
I'm using PostgreSQL as backend, could that be the source of the problem? How actually searching works? Using database functions? If you give me a hint where is it done (in code) I can investigate the problem.
Check the code for Main.WebSearch , its a series of hibernate hql queries. The string is searched with "where field LIKE '$keyword'", so if LIKE is not case insensitive, this is the cause.
Sergiu, I think this also happens with HSQL. We should check if it happens on xwiki.org too (what is it running on BTW? MySQL?)
Speaking of searching, it not clear to me what happens if I
turn on
Lucene. Does this replace searching back-end for regular search box, or I have to add new page for searching?
No, it does not replace normal search. You will have to write a
search
page that uses Lucene. Maybe we should have this page in the Code area on xwiki.org <http://xwiki.org>.
We already have it :-)
It was not clear to me does it replace regular search, thanks for the answer. I will add search box integration to JIRA for future reference, and I think that this should be stated on plugin page, because description is a bit misleading: "It can be used in place of the default search implementation..."
Feel free to edit and improve the LucenePlugin documentation on the wiki :-) Thanks -Vincent
Vincent Massol wrote:
On Mar 27, 2007, at 9:50 AM, Sergiu Dumitriu wrote:
>> I noticed that XWiki does case sensitive search, e.g. if I search for >> "available", available will be found, but not "Available." >> >> How can I make searches case insensitive?
Sergiu, I think this also happens with HSQL. We should check if it happens on xwiki.org too (what is it running on BTW? MySQL?)
No, it works fine. I checked it to clarify is problem on my side or in general.
It was not clear to me does it replace regular search, thanks for the answer. I will add search box integration to JIRA for future reference, and I think that this should be stated on plugin page, because description is a bit misleading: "It can be used in place of the default search implementation..."
Feel free to edit and improve the LucenePlugin documentation on the wiki :-)
I will play with it first. It seems to me that search panel just calls search page. If I put Lucene code there, it should be executed for every search, even from panel.
participants (7)
-
Esbach, Brandon -
Mauricio Hernández -
Mauricio Hernández Durán
-
Sergiu Dumitriu -
THOMAS, BRIAN M (ATTSI) -
Vincent Massol -
Zeljko Trogrlic