Calling a class not included in your application package

Hi all,

I hope I can explain this clearly and that someone can assist me with this issue.

I have an application that needs to call a class from a dependant application.   However, I need to alleviate the need of having the dependant code included in the applications release package, yet still compile as though it were there.

I was instructed to create an interface for the class that I will be dependant on, and have that class implement the interface of my application.  Then store the class name in a property file and use that property to instantiate the class name in my code and call the necessary methods at that time.

So, there are two problems I have.  One, is the interface design.  The dependant package has relatively simple public methods, but there is one method that is dependant on another class in that package. i.e., the dependant classes are similar to this:

class Test1 {
 public void addMethod() {
  // they have code here
 }

 public void testMethod () {
  //they have code here
 }

 public void exampleMethod () {
   //again code here
 }

 public Test2 createMethod () {
  //code here that uses another class
}
}

class Test2 {
 Test2 () { //constructor which I call }
 //additional code
}

Now I'm supposed to create an interface for Test1 for the exampleMethod and the createMethod...but like I said the createMethod references another class.  Do I need to create an interface for the Test2 class?  How do I do that, if you can't put constructors in interfaces?

Then in my code, I need to reference my interfaces and instantiate the Test1 class via the classname defined in the properties file, then call the methods defined in the interface:

//get property value
//instantiate the object
Test1 test1 = new Test1();
test1.exampleMethod();
Test2 test2 = test1.createMethod();

Hopefully that made sense!  Can anyone help me using the example above to show me how the code would look and work correctly?

Thanks
sapientconceptionsAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
objectsConnect With a Mentor Commented:
you'll need to change the Test1 classes createMethod signature then

public Test2Interface createMethod () {

and your interfaces will look like:

class Test1Interface {
 public void addMethod();

 public void testMethod ();

 public void exampleMethod ();

 public Test2Interface createMethod ();
}

interface Test2Interface {
 //additional methods
}
0
 
objectsCommented:
what class (referring to your example) do you not have access to?
0
 
girionisCommented:
You do not have to create an interface for the Test2 class. You can simple do:

public interface Test1Interface
{
    public void addMethod();
    public void testMethod();
    public void exampleMethod();
    // You could also declare the following but it is not necessary
    public Test2 createMethod();
}

0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
objectsCommented:

public interface A
{
   public void method();
}

public class AImpl implements A
{
   public void method()
   {
   }
}


then to create instance use:

String classname = "AImpl";
A instance = (A) Class.forName(classname).newInstance();
0
 
sapientconceptionsAuthor Commented:
Thanks all.  

Objects,
Test1 and Test2 are the two dependant classes that I must call in my code, that I will not be included in my application at deployment (they will be made available later).  So I need to make sure it builds fine prior to the code being included -- hence the declarations of the interface and my use of it.

Girionis, you say I don't have to create an interface for Test2, but if Test2 isn't a part of my application and I reference it in the interface, wouldn't the compiler throw an error because it can't find the class?
0
 
girionisConnect With a Mentor Commented:
> but if Test2 isn't a part of my application and I reference it in the interface, wouldn't the
> compiler throw an error because it can't find the class?

You will have to import it in order to use it.

import mypackage.package.Test2;

public interface Test1Interface
{
    // method declaration here.
}

public class Test1 implement Test1Interface
{
...
...
}
0
 
girionisCommented:
:)
0
 
sapientconceptionsAuthor Commented:
Thanks guys, sorry for the delay in passing out the points, I forgot the question was still open.  I've split the points between the two of you.  Enjoy.
0
 
objectsCommented:
Thats ok, thanks for closing :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.