Closed GoogleCodeExporter closed 8 years ago
Initially favored approach is multiple ClassLoaders to support multiple
connector
types with different third-party requirements, including multiple versions of
the
same connector type.
Original comment by jl1615@gmail.com
on 8 Dec 2008 at 11:32
This should probably depend on issue 107, to avoid really confusing log files.
Original comment by jl1615@gmail.com
on 9 Dec 2008 at 1:32
Should be able to edit the logging.properties without restarting the Tomcat.
Original comment by mgron...@gmail.com
on 28 Jan 2009 at 10:52
Dropping out of the next release. We will investigate the use of HttpClient in
the various connectors, and explore
running at least SharePoint, Documentum, and Livelink connectors together in
the same Tomcat instance. I've
been running Documentum and Livelink together with no ill effects (save that of
logging; see issue 107).
Original comment by jl1615@gmail.com
on 10 Mar 2009 at 7:29
The Issue 110 and 107 fixes should make it less painful to run multiple
connector instances. The jar conflicts
could be resolved for the common connectors so we don't need to sandbox them.
Few customers need this
right now, so I opt for clearing the small hurdles and leave it at that.
Original comment by Brett.Mi...@gmail.com
on 16 Apr 2009 at 11:18
[deleted comment]
Hi I am Currently working in a GE project for GSA connector development because
their
necessity of having many connectors for different databases and feeding on a
schedule. So I am currently doing some improvements to our connector for
logging each
instance of the same connector type. I saw that the connector manager creates a
folder and configuration files for each instance of the connectors. Would be
possible
to have a extra logging configuration file for separate logs? In order to not
getting
confused
Original comment by saul.rosalesb@gmail.com
on 25 Nov 2009 at 3:55
Original comment by mar...@google.com
on 4 Dec 2009 at 11:13
Original comment by jla...@google.com
on 24 Jun 2011 at 11:38
This issue is filed as Google issue #6513983
Original comment by tdnguyen@google.com
on 18 May 2012 at 9:48
Original issue reported on code.google.com by
jeffreyl...@gmail.com
on 21 Apr 2008 at 9:49