There are various shading tools that could help rather than manually
mucking about with byte code.
On Jun 24, 2015 5:45 AM, "Li Li" <[email protected]> wrote:

> I have to use another package name other than the original one because
> the original package is loaded and not controlled by my code.
>
>
> On Wed, Jun 24, 2015 at 5:37 PM, Benedikt Ritter <[email protected]>
> wrote:
> > Hello Li Li
> >
> > 2015-06-24 11:21 GMT+02:00 Li Li <[email protected]>:
> >
> >> Hi all,
> >>      I have a jar file and without the source code, I want to replace
> >> a package and all classes of this package with my own.
> >>      e.g.  There is a package
> >>       com.abc.tool
> >>       com.abc.tool.A.class
> >>       com.abc.tool.B.class
> >>     The com.abc.tool.A.class and com.abc.tool.B.class are used in many
> >> other classes.
> >>     I want to use my own implementation, So I can create my
> >> package(com.def.tool) and my A.java B.java which has exactly the same
> >> method as  com.abc.tool.A.class and  com.abc.tool.B.class
> >>        com.def.tool
> >>        com.def.tool.A.class
> >>        com.def.tool.B.class
> >>     But other classes in this jar still use com.abc.tool.A.class and
> >> com.abc.tool.B.class. I want to use a byte code library to modify the
> >> jar so it can run and use my implementation.
> >>     Is BCEL suitable for this? Thank you
> >>
> >
> > This sounds like a pretty complicated solution to your problem. Why don't
> > you just replace the class files in the jar at build time?
> >
> > Regards,
> > Benedikt
> >
> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
> >
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to