Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DTP » Logging utility classes have (annoying) dependency on org.eclipse.core.runtime.Plugin
Logging utility classes have (annoying) dependency on org.eclipse.core.runtime.Plugin [message #52098] Thu, 08 January 2009 15:53 Go to next message
Eclipse User
Originally posted by: chris.enterprise-elements.com

First let me say that I couldn't have solved my problem without DTP, so
thanks to everyone involved. Now onto my question.

We are using ModelBase and the SQL Parser to provide some functionality of a
commercial product. Our product is not based on the Eclipse platform, so we
are using the DTP jar files standalone. Since our application is launched
by Java WebStart we are sensitive to the size of the jar files that get
downloaded at startup.

Specifically we are disappointed that the logging utility classes in the DTP
SQL Parser and ModelBase have a dependency on
org.eclipse.core.runtime.Plugin, which in turn has a dependency on
org.osgi.framework.BundleActivator. The BundleActivator class comes from
org.eclipse.osgi_<version>.jar, which is nearly one MB in size.

Unfortunately SQLLogUtil, SQLParserLogger, SQLQueryLogger,
SQLQueryParserLogger are all concrete classes that do not implement any
interfaces and they all depend on the Plugin class. I don't see how a
consumer of DTP SQL Parser and ModelBase can break this dependency in a good
way.

Is it possible to do what I want?

If it is not possible, then should I submit a bugzilla report?

Thanks,
Chris Hines
Re: Logging utility classes have (annoying) dependency on org.eclipse.core.runtime.Plugin [message #52207 is a reply to message #52098] Mon, 12 January 2009 16:45 Go to previous messageGo to next message
Brian Payton is currently offline Brian Payton
Messages: 152
Registered: July 2009
Senior Member
Chris,

Yes, please open a Bugzilla request to refactor those plugins to not
have a hard dependency on o.e.core.runtime.Plugin.

Brian Payton
SQL and XQuery Tools Development
IBM Information Management

Chris Hines wrote:
> First let me say that I couldn't have solved my problem without DTP, so
> thanks to everyone involved. Now onto my question.
>
> We are using ModelBase and the SQL Parser to provide some functionality of a
> commercial product. Our product is not based on the Eclipse platform, so we
> are using the DTP jar files standalone. Since our application is launched
> by Java WebStart we are sensitive to the size of the jar files that get
> downloaded at startup.
>
> Specifically we are disappointed that the logging utility classes in the DTP
> SQL Parser and ModelBase have a dependency on
> org.eclipse.core.runtime.Plugin, which in turn has a dependency on
> org.osgi.framework.BundleActivator. The BundleActivator class comes from
> org.eclipse.osgi_<version>.jar, which is nearly one MB in size.
>
> Unfortunately SQLLogUtil, SQLParserLogger, SQLQueryLogger,
> SQLQueryParserLogger are all concrete classes that do not implement any
> interfaces and they all depend on the Plugin class. I don't see how a
> consumer of DTP SQL Parser and ModelBase can break this dependency in a good
> way.
>
> Is it possible to do what I want?
>
> If it is not possible, then should I submit a bugzilla report?
>
> Thanks,
> Chris Hines
>
>
Re: Logging utility classes have (annoying) dependency on org.eclipse.core.runtime.Plugin [message #52367 is a reply to message #52207] Thu, 15 January 2009 12:13 Go to previous message
Eclipse User
Originally posted by: chris.enterprise-elements.com

Thanks, Brian.

Bugzilla submitted.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=261221

Chris


"Brian Payton" <bpayton@us.ibm.com> wrote in message
news:gkgdlq$q4m$1@build.eclipse.org...
> Chris,
>
> Yes, please open a Bugzilla request to refactor those plugins to not have
> a hard dependency on o.e.core.runtime.Plugin.
>
> Brian Payton
> SQL and XQuery Tools Development
> IBM Information Management
>
> Chris Hines wrote:
>> First let me say that I couldn't have solved my problem without DTP, so
>> thanks to everyone involved. Now onto my question.
>>
>> We are using ModelBase and the SQL Parser to provide some functionality
>> of a commercial product. Our product is not based on the Eclipse
>> platform, so we are using the DTP jar files standalone. Since our
>> application is launched by Java WebStart we are sensitive to the size of
>> the jar files that get downloaded at startup.
>>
>> Specifically we are disappointed that the logging utility classes in the
>> DTP SQL Parser and ModelBase have a dependency on
>> org.eclipse.core.runtime.Plugin, which in turn has a dependency on
>> org.osgi.framework.BundleActivator. The BundleActivator class comes from
>> org.eclipse.osgi_<version>.jar, which is nearly one MB in size.
>>
>> Unfortunately SQLLogUtil, SQLParserLogger, SQLQueryLogger,
>> SQLQueryParserLogger are all concrete classes that do not implement any
>> interfaces and they all depend on the Plugin class. I don't see how a
>> consumer of DTP SQL Parser and ModelBase can break this dependency in a
>> good way.
>>
>> Is it possible to do what I want?
>>
>> If it is not possible, then should I submit a bugzilla report?
>>
>> Thanks,
>> Chris Hines
Re: Logging utility classes have (annoying) dependency on org.eclipse.core.runtime.Plugin [message #594191 is a reply to message #52098] Mon, 12 January 2009 16:45 Go to previous message
Brian Payton is currently offline Brian Payton
Messages: 152
Registered: July 2009
Senior Member
Chris,

Yes, please open a Bugzilla request to refactor those plugins to not
have a hard dependency on o.e.core.runtime.Plugin.

Brian Payton
SQL and XQuery Tools Development
IBM Information Management

Chris Hines wrote:
> First let me say that I couldn't have solved my problem without DTP, so
> thanks to everyone involved. Now onto my question.
>
> We are using ModelBase and the SQL Parser to provide some functionality of a
> commercial product. Our product is not based on the Eclipse platform, so we
> are using the DTP jar files standalone. Since our application is launched
> by Java WebStart we are sensitive to the size of the jar files that get
> downloaded at startup.
>
> Specifically we are disappointed that the logging utility classes in the DTP
> SQL Parser and ModelBase have a dependency on
> org.eclipse.core.runtime.Plugin, which in turn has a dependency on
> org.osgi.framework.BundleActivator. The BundleActivator class comes from
> org.eclipse.osgi_<version>.jar, which is nearly one MB in size.
>
> Unfortunately SQLLogUtil, SQLParserLogger, SQLQueryLogger,
> SQLQueryParserLogger are all concrete classes that do not implement any
> interfaces and they all depend on the Plugin class. I don't see how a
> consumer of DTP SQL Parser and ModelBase can break this dependency in a good
> way.
>
> Is it possible to do what I want?
>
> If it is not possible, then should I submit a bugzilla report?
>
> Thanks,
> Chris Hines
>
>
Re: Logging utility classes have (annoying) dependency on org.eclipse.core.runtime.Plugin [message #594255 is a reply to message #52207] Thu, 15 January 2009 12:13 Go to previous message
Chris Hines is currently offline Chris Hines
Messages: 15
Registered: July 2009
Junior Member
Thanks, Brian.

Bugzilla submitted.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=261221

Chris


"Brian Payton" <bpayton@us.ibm.com> wrote in message
news:gkgdlq$q4m$1@build.eclipse.org...
> Chris,
>
> Yes, please open a Bugzilla request to refactor those plugins to not have
> a hard dependency on o.e.core.runtime.Plugin.
>
> Brian Payton
> SQL and XQuery Tools Development
> IBM Information Management
>
> Chris Hines wrote:
>> First let me say that I couldn't have solved my problem without DTP, so
>> thanks to everyone involved. Now onto my question.
>>
>> We are using ModelBase and the SQL Parser to provide some functionality
>> of a commercial product. Our product is not based on the Eclipse
>> platform, so we are using the DTP jar files standalone. Since our
>> application is launched by Java WebStart we are sensitive to the size of
>> the jar files that get downloaded at startup.
>>
>> Specifically we are disappointed that the logging utility classes in the
>> DTP SQL Parser and ModelBase have a dependency on
>> org.eclipse.core.runtime.Plugin, which in turn has a dependency on
>> org.osgi.framework.BundleActivator. The BundleActivator class comes from
>> org.eclipse.osgi_<version>.jar, which is nearly one MB in size.
>>
>> Unfortunately SQLLogUtil, SQLParserLogger, SQLQueryLogger,
>> SQLQueryParserLogger are all concrete classes that do not implement any
>> interfaces and they all depend on the Plugin class. I don't see how a
>> consumer of DTP SQL Parser and ModelBase can break this dependency in a
>> good way.
>>
>> Is it possible to do what I want?
>>
>> If it is not possible, then should I submit a bugzilla report?
>>
>> Thanks,
>> Chris Hines
Previous Topic:Using DTP to analyze data flow
Next Topic:Using DTP to analyze data flow
Goto Forum:
  


Current Time: Wed Jul 30 03:22:43 EDT 2014

Powered by FUDForum. Page generated in 0.02632 seconds