Using Cairo with Gtkmm

Okay we should be all familiar with the Cairo API. If this is the first time you've ever heard of Cairo outside of a reference to Egypt then let me give you a quick peek at Cairo.



Cairo is pretty much the main library used for drawing anything with vectors. It is used everywhere, sort of like SQLite. The website is http://cairographics.org/



In the GNOME trifecta of things, Cairo provides the 2D drawing API, whereas Pango provides the Text Rendering API, and Gtk-Glib provide the toolkit/glue for all the above.



The neat thing about Cairo is that output is not limited to the screen. Backends for Cairo can be written for anything, so things drawn in Cairo can be outputted to an SVG file, OpenGL commands, a printer, or to a Pixbuf for use in a very popular web browser (Firefox anyone).



So today I'm going to use Cairomm (C++ bindings for Cairo) to do some basic drawing. Here is our header file justin_draw.h that defines our DrawingArea.

#ifndef SAMPLE04_JUSTIN
#define SAMPLE04_JUSTIN

#include <gtkmm/drawingarea.h>

class JustinDraw : public Gtk::DrawingArea
{

public:
	JustinDraw();
	virtual ~JustinDraw();
	
protected:
	virtual bool on_expose_event(GdkEventExpose* event);

};

#endif

The only thing of note here is that we are going to define an on_expose_event. This is important because this is the method that is called when the window needs to draw itself. Either because the Window is new, or we've uncovered the window an exposed a part of it that was under another window.




Now let's implement our Gtk::DrawingArea with our justin_draw.cc file:

#include "justin_draw.h"
#include <cairomm/context.h>

JustinDraw::JustinDraw() {}

JustinDraw::~JustinDraw() {}

bool JustinDraw::on_expose_event(GdkEventExpose* event) 
{
	Glib::RefPtr<Gdk::Window> window = get_window();
	
	if (window)
	{
		Gtk::Allocation a = get_allocation();
		const int w = a.get_width();
		const int h = a.get_height();
		
		int xc, yc;
		xc = w/2;
		yc = h/2;
		
		Cairo::RefPtr<Cairo::Context> cr = window->create_cairo_context();
		cr->set_line_width(10.0);
		
		cr->rectangle(event->area.x, event->area.y, event->area.width, event->area.height);
		cr->clip();
		
		cr->set_source_rgb(0.8, 0.0, 0.0);
		cr->move_to(0,0);
		cr->line_to(xc,yc);
		cr->line_to(0,h);
		cr->move_to(xc,yc);
		cr->line_to(w,yc);
		cr->stroke();
	}
	
	return true;
}

Notice a couple of things here before we move on. Drawing an entire screen with Cairo should be done very rarely. Not to say Cairo is slow but there is no need to waste time on drawing. The cr->rectangle(...); cr->clip(); parts allow us to focus on only the part of the window that has changed. Pretty much all code that uses Cairo has something similar to this so it's a good idea to include something like this in you code before you actually do any drawing.




Also notice that we are using a Cairo::RefPtr. Yes Cairo has it's own type of RefPtr's that you must use to hold Cairo related things. You have no idea how much time you can waste using the wrong type of RefPtr.




Finally, our program that uses our new Gtk::DrawingArea. main.cc

#include "justin_draw.h"
#include <gtkmm/main.h>
#include <gtkmm/window.h>

int main(int argc, char** argv)
{
   Gtk::Main kit(argc, argv);

   Gtk::Window win;
   win.set_title("DrawingArea");

   JustinDraw area;
   win.add(area);
   area.show();

   Gtk::Main::run(win);

   return 0;
}

And that's all there is to it! You can hit up basically any manual on Cairo to find all the 2D API commands. It's basically a 1:1 translation between the C and C++ bindings so you shouldn't have any problems there.




Tomorrow I'm going to cover Making a throbbing image in Java, because I'm gotten two emails over the last four days asking how to do that. Till then, Cheers!

Trying out L2TPv3 in Linux 2.6.35.4

So I built me a 2.6.35.4 kernel to try out the new L2TPv3 support offered in this kernel.

L2TPv3 is pretty good and the newest kernel provides awesome RFC 3931 support, but I would advise some people to stick with L2TPv2. Not a lot of 3rd party vendors are there yet and the newest version has a lot of overhead over the wire.

I'm still on the fence about btrfs. I'll give it another six months before I actually change my LVM over.

Oh and by the by. The new kernel improves LVM response by about 5% - 10% depending on setup.

I hate Jennifer Aniston.

This is f'ing funny.


Jennifer Aniston Adopts 33-Year-Old Boyfriend From Africa

A Quick try of Gtkmm

Okay I figure I would give my hand a try at some Gtkmm. The API is pretty much like most curses and Java Windowing framework. So let's do a quick sample.

Let's start with our header file for the Window, we'll call it window1.h

#ifndef WINDOW_1_DEF_H
#define WINDOW_1_DEF_H

#include<gtkmm/window.h>
#include<gtkmm/button.h>
#include<gtkmm/entry.h>
#include<gtkmm/box.h>

class Window1 : public Gtk::Window {

public:

	Window1();
	virtual ~Window1();
	
protected:

	void on_button1_clicked();

private:

	Gtk::Button button1, button2;
	Gtk::Entry entry1;
	Gtk::VBox vbox1;

};

#endif

All of that should explain itself. Basically the object is a Gtk::Window, which is the top level container (widget, whatever you want to call it). We are adding two Gtk::Button, a Gtk::Entry (text entry widget), and a Gtk::VBox which is the layout container.

Now the fun thing about Gtkmm is that you don't have to "new" objects into existence. Instead Gtkmm will handle the memory allocation for you in most cases!! However, if you need to dynamically allocate objects or you need them outside of the class scope then your own your own, unless you use the Gtkmm smart pointer Glib::RefPtr<>, which is basically the same as the std::auto_ptr<> for those of you who have studied standard C++.

Okay let's implement the window, this will be in most logically window1.cc

#include "window1.h"
#include <iostream>
#include<gtkmm/main.h>

Window1::Window1() : button1("Print"), button2("Ouit") {

	set_size_request(200,100);
	set_title("Text Entry Demo");
	
	add(vbox1);

	entry1.set_max_length(25);
	entry1.set_text("Enter something");
	entry1.select_region(0,entry1.get_text_length());
	
	vbox1.add(entry1);

	button1.signal_clicked().connect(sigc::mem_fun(*this,&Window1::on_button1_clicked));
	button2.signal_clicked().connect(sigc::ptr_fun(&Gtk::Main::quit));

	vbox1.add(button1);
	vbox1.add(button2);
	
	show_all();
}

Window1::~Window1() {
	using namespace std;
	cout << "Say goodbye" << endl;
}

void Window1::on_button1_clicked() {
	std::cout << "You have entered: " << entry1.get_text() << std::endl;
}

Okay this one has a couple of things to cover. Like what the heck is the sigc namespace?!

sigc is the library that Gtkmm uses to implement callbacks. A callback is a function or method that is called from another function. Basically the on_click method of your buttons gets called when you click on them. The method basically says, when I'm clicked run ________(insert blank line)________. The callback fills in the blank line.

Now historically there is basically one way to do this in C, but in C++ there must be at least a dozen libraries that do this. I won't get into why this is because that's a much bigger topic.

At anyrate, sigc is the tool that Gtkmm has chosen to implement callbacks. sigc has two ways to add callbacks. mem_fun and ptr_fun, both used here. mem_fun, allows you to call a method and ptr_fun allows you to call a function. Pretty clear cut there. As you can see I've connected the button2's click to the Gtk::Main::quit, which of course does what it says. Quits.

The other button, button1, I've connected to the on_button1_clicked method. This method simply uses standard C++ cout to write information to standard out. You may notice that I use the entry1.get_text() method within the on_button1_clicked() method and that I don't cast it's result to std::string. That's the neatest part of Gtkmm is that it was made to work with the C++ STL so well. Gtkmm already implements the logic needed to cast Glib::ustring (which is what the get_text() wethod returns) to std::string.

The rest of the code is pretty simple to follow.

So now that we have implemented our window we need an application that actually uses it.

I present main.cc

#include<gtkmm/main.h>
#include"window1.h"

int main(int argc, char *argv[]){

	Gtk::Main kit(argc, argv);
	Window1 w;
	Gtk::Main::run(w);

	return 0;
}

This is as basic as you can make an application that uses our window.

The results are here.


Clicking on the Print button outputs the text box on standard out and clicking quit, well quits. As you can see Gtkmm is very much like most other Toolkits, semantics are a little different here and there and you'll use some of the core tools of Gtkmm a little differently but overall you'll easily see how Gtkmm compares to things like SWT, Swing, and QT.

And since I said something about QT, it's worth saying something about it. If you have ever used QT then you know about it's signal/slot system and moc. Well Gtkmm takes the "high road" on this one and uses sigc to implement callbacks in a C++ standard-ish kind of way. The downfall of this, however, is that every callback must be statically typed. This amounts to a lot of double work. If you implement a signal connection in Glade, you must also implement that connection in Gtkmm by importing the widget and then using sigc.

I know this is one of the downfalls of C++'s strong type safety system and name mangling system. QT gets around this with moc but then using moc makes your code non-C++ standard compliant, which I don't think anybody really has a problem with except the people behind Gtkmm.

At anyrate, at risk for getting way off topic, Gtkmm is a neat little wrapper around Gtk+ and you should give it a whirl. You'll be making Gtk+ applications in no time, and best of all is the Gtkmm library works on Windows, Mac, Linux, BSD, and other Unix systems.
Link to Gtkmm

Is it just me?

Does it seem that Colbie Caillat has incredibly "wide" eyes? Is that even a thing? Maybe, I'm just mental?



Oh her song on the radio is a nifty little tune, and she was on the the Next Food Network Star show too. Before that I would have sworn that you were talking about a type of cheese.

Working on a neat project

Usually I have the most fun with design and coding. Rarely do I go back and play with the UI in the sense of having fun with it.

It's just mostly checking if the UI is okay and if there are any bugs/misspellings.

Well I've just got a project that I'm having fun with the UI as well because the interface is a Text based User Interface (TUI, if you are so inclined to use that).

It's cool using JCurses. JCurses is a very loose JNI for the Curses environment, nCurses on Linux. Since it does use JNI that means that you do loose the cross platform compatibility, but JCurses comes with sources and Win32 and Linux x86 binary libraries.

I've been able to compile JCurses for Linux amd64, Mac OSX, and PPA systems. So you should be covered for systems that you may want to run this on.(Note: I don't have access to an ARM chip so I don't know if you can use JCurses there).

The setup at work is to provide a SSH session via RF scanner to our warehouse users, noting new there we've been serving TN-5250 sessions via wireless for the past fifteen years (longer than I've been there).

However, this is the first time that I've actually been calling EJBs from a text based interface. The principal is basically the same, call the remote endpoint from the Java code, present results bark to user.

The fun part is with a text based interface, you really have to concentrate on features and how you present them. A screen full of text is impossible to use effectively, and the more options you present at once the more cluttered the screen appears.

I've found that the best way to break up things is not present all the needed input at once, but instead to take an ask on need approach. So when the next step is to get an EAN or UCC128 code that's what you ask and only that and the options that might effect that.

Also, keyboard functions are limited to basically, TAB, ENTER, F1 through F4, the numbers 0 through 9, and BACKSPACE. Obviously there are no mouse functions.

All of this, limited input, limited screen size, and limited ways of getting the user's attention (Curses can only ring the system bell) really forces you to really think out the UI in a manner that end users usually can't help with.

That's not to say that I never think of the UI for GUIs, but usually we have a company layout and guideline on how our GUIs are created. You simply follow that, get end user feedback, and modify as needed without breaking something.

I'll have to post some examples of JCurses and EJBs soon.

Heading on the road, again.

Well.  I'm heading on the road again.  Travel sucks and double much when it is business travel.  The hope is that this round is my last round for a good bit of time, until next year.

At any rate, I've really got to get back to blogging because I enjoyed it so much.

I've had time in the air to think of some little projects that I'd like to do personally on my system.  I'll have to share them when I'm not in the air.  Also, trains suck.  It never fails that I am delayed twenty minutes going to anywhere by a train crossing.  Just yesterday while going from one building to another I wasted forty-five minutes, the break down is as follows:

1. Rail construction, the construction train was at the crossing on Highway 11.  Wasted 23 minutes.
2. Slow moving train coming back via different route.  Wasted 17 minutes.
3. What the heck! A mostly unused train track is being used to move cargo into a rail-yard. Wasted 9 minutes.

That last one was just to spite me.  I think CSX personally has a vendetta out on me.

Well I'm off.  Cheers!

Where I work trains are a big problem. they can take up to fifteen minutes some times like this guy.
From my phone.

Yeah I know. I've been on the road for company related stuff.

So I've shown how to add security annotations to a pretty vanilla EJB. When you develop EJBs remember to keep them limited in scope. For example, if you have an EJB that handles Inbound orders (placeOrder, reviewOrder, cancelOrder, addToOrder, removeFromOrder, etc...) do not feature creep by having that same EJB handle Outbound orders or worst yet schedule orders in a calendar app.

I cannot tell you the number of times that I've run across an EJB where 30% of the code really belongs in its own EJB unit. For example the calendar app should view Inbound orders as a Collection not as a derived member called SchdOrd (PS use freaking descriptive names! The next guy will not understand that OrdTckChcExc is short for Order Ticket Cache Exchange; nor will that name mean anything to them.) A calendar *HAS A* Collection of Inbound orders makes more sense than A Scheduled Order *IS AN* Inbound Order.

The reason it makes more sense? Just because something is a something else does not mean that the logic for the unit is clarified by the statement. The statement only implies a date an doesn't do a very good job of telling anyone what that date means to anybody. A calendar (thus we get the date concept) has a (okay that tells us something about storage) collection (alrighty this tells us that we are going to be looking at a lot of similar things at once) of Inbound orders.

As you can see the HAS A statement tell more about the underlying logic than the IS A statement. So, more than likely by Justin's 23rd rule of programming, the logic will be easier to implement.

I'm getting off on a tangent here, sorry.

Next post I'll cover using a JAAS callback to implement acustom login dialog and how to handle a failed login, yes you do have to handle those Glassfish will not do it for you.

Cheers!

Had my first in and out burger. awesome.

teenage girl won't stop fighting

teenage girl won't stop fighting mom on aa flight1959. So we're landing in Phoenix. She was hand cuffed! Flight delay!

Posting from my phone!

So I can post during those long drives (If I was to type at say four letters a minute, I'd fill more than one text message).  Just to give you some scope of how long my drive to work is.  Cheers!

The switch to v2 over v3.

We had to downgrade to Glassfish v2.1.1 at work and I've been busy making sure everything is running smoothly. Our biggest issue (since I don't want to go on a rant about glassfish I'll just leave it at this issue) was the Java Web Start snafu. I know that the real problem lies with the JRE but we can keeping making workarounds on our Apache server and making custom JNPL's.

At any rate our requirement of JSF 2.0 was easily assuaged and I'd like to share that with you.

You can get all the information to install Mojarra v2.0.2 on Glassfish v2.1.1 form here.

Just follow those and you'll be able to deploy JSF 2.0 pages in no time!

UPDATE ON 7/21/2010:
Just so you know we're sticking with Glassfish v2.1.1 but the Glassfish 3.0.1 server has the issue pretty much fixed for most cases.

The upshoot with v2 is that we can actual take our three glassfish servers and have them talk to each other to keep everyone up to date!  Our v3 system had a cron, shell script, and NFS mount to do that but the v2 way is much better.

Apple will destroy you! Try not to be happy about how shiny your death will be.

Apple is the anti-Christ of computers. For years we all hated on Microsoft because they we're big bullies who try to take over everything. Now, don't get me wrong MS is evil, they will want you to use whatever they sell, but that have come to the conclusion that they can't control everything.

Enter Apple, they do believe that they can control everything, they will control how you get books on your iPad, they will control which book you have access to, they will control which apps you can buy, they will control how and when you can use said apps you just bought, they control what you can and can not do on the Internet, they control how you will use the Internet, they control how you have access to content, they control the content that you access...

I could go on forever, in short, it will be Apple's way or no way. It will be Apple's software or no software. In no way is Apple equal to a free market of any sorts and in every single way possible is Apple total vendor lock-in. Once you go Apple it is over, you no longer have *your* documents, you have access to *Apple's* documents.

This all come in the wake of Apple's latest move to destroy Google's platform, increase the operating cost of YouTube, lock out any Microsoft tools, destroy any sharing between KHTML devs and WebKit devs, and now their move to remove Adobe and Ogg from the Internet.

I know what most people would say, just don't buy Apple, good luck on getting that to work. I'm currently on the campaign (since I'm tired of Apple treating open source like a little redheaded bitch) to ensure that people I know don't buy Apple ever again. I ask anyone and everyone who believes in a open world of software to get the word out that Apple is the largest private company threat to everyone's freedom on the Internet. Apple, don't buy into it!

Where was I?

So sorry. Lost track of what I was doing here. I'll try to keep that to a minimum.

At any rate. If you are using Glassfish v3 to serve up application clients via Java Web Start, then check your client's (the people who will be running your crap) JVM. JRE 1.6 u 18 has a nasty bug that prevents Glassfish v3 JWS from working correctly.

I've got to get back on this horse. I'll see you all soon!

What's going on? I know it has been awhile since my last post. Been a bit busy, also workplace has banned blogger from the network. So I'm posting this from my Wii. Fun stuff! Gnome 2.30 is released if you are into that kind of thing. happy April fools day!

Adding Security to EJB

Alright let's take a quick look at the HelloBean.java file with security annotations:

package com.blogger.ramen;

import javax.ejb.Stateless;
import javax.annotation.security.RolesAllowed;
import javax.annotation.security.DeclareRoles;

@Stateless(name="HelloBean")
@DeclareRoles("SecureUser")
public class HelloBean implements HelloRemote {

        @RolesAllowed("SecureUser")
        public String sayHello() {
                return "Hello from EJB!";
        }

}

As you can see I've added the DeclareRoles and RolesAllowed annotations. The EJB container will read the meta-data in the class see the annotations and enforce the security described in them. This happens each time you call the method since it is Stateless.

So the next question is how does the container know you belong to the SecureUser role? Because the security mappings in your sun-ejb-jar.xml file. Here's what you need to add:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
<sun-ejb-jar>
  <enterprise-beans>
    <ejb>
      <ejb-name>HelloBean</ejb-name>
      <jndi-name>ejb/Helloness/HelloThere</jndi-name>
      <ior-security-config>
          <as-context>
             <auth-method>USERNAME_PASSWORD</auth-method>
             <realm>OurDBRealm</realm>
             <required>true</required>
          </as-context>
        </ior-security-config>
    </ejb>
  </enterprise-beans>
</sun-ejb-jar>

As you can see the <ior-security-config> and all of it's friends to add a realm to our EJB. Our realm being OurDBRealm that we already setup using the JDBCRealm method that was given earlier. We need to add one more thing to that file, our security mapping, this will map something that will match an entry in the JDBCRealm with the annotation we've giving here. We add this snippit right after the <sun-ejb-jar> element.

<security-role-mapping>
    <role-name>SecureUser</role-name>
    <group-name>SUSER</group-name>
</security-role-mapping>

Deploy your EJB and rerun your client. You should get the default login prompt that's built into Glassfish. Login with the information you've stored in the database and you should see results. Viola! Secure EJB. Of course, if you give bad login information then you will get an exception. At any rate this is a pretty cut and dry use of secure EJBs. We'll look at how to provide your own login dialog and how to catch exceptions on login.

Cheers!

Just so we can get on with it. Go here to see how to add a realm to your Glassfish server. Once you've added the realm you'll need to create some groups. For the best method, give each group a specific task as it is easier to focus on a limit set of permissions than code for roles.

You may have a task like add a product, review a shopping cart, delete an account, or add a bank transaction. Roles are more like Super users, accountants, managers, etc.

Focus on task in your groups and then add triggers or EJB beans that focus on roles, which in turn aggregate your tasks.

Where have I been? Sorry I've just not had the time to post code samples here. Car had some issues, got them fixed, house had issues, cot those fixed, work has issues, not a damn thing I can do about those.

Okay, so here is a quick example of using the FedEx WSDL to build a simple tracking application. To get the FedEx WSDL you just go over to their developer website at http://www.fedex.com/us/developer. You will need to sign up to get a key and password to use their service. When you do sign up give it a couple of days for the key and password to be activated. If it takes longer than two days for the key and password to come online, just give the FedEx number a call.

So download the WSDL and add it to your web services on the services tab of NetBeans. Start a new Java Project and drag the track service from the services tab into the main method in your project.

You should now see some code that looks like this:

package javaapplication34;

/**
 *
 * @author Me
 */
public class Main {

    /**
     * @param args the command line arguments
     */
    public static void main(String[] args) {

        try {
            com.fedex.ws.track.v4.TrackRequest trackRequest = null;
            com.fedex.ws.track.v4.TrackService service = new com.fedex.ws.track.v4.TrackService();
            com.fedex.ws.track.v4.TrackPortType port = service.getTrackServicePort();
            // TODO process result here
            com.fedex.ws.track.v4.TrackReply result = port.track(trackRequest);
            System.out.println("Result = " + result);
        } catch (Exception ex) {
            ex.printStackTrace();
        }
    }
}

We are going to change that code to look like this:

package javaapplication34;

import com.fedex.ws.track.v4.ClientDetail;
import com.fedex.ws.track.v4.Notification;
import com.fedex.ws.track.v4.NotificationSeverityType;
import com.fedex.ws.track.v4.TrackDetail;
import com.fedex.ws.track.v4.TrackIdentifierType;
import com.fedex.ws.track.v4.TrackPackageIdentifier;
import com.fedex.ws.track.v4.TrackRequest;
import com.fedex.ws.track.v4.TransactionDetail;
import com.fedex.ws.track.v4.VersionId;
import com.fedex.ws.track.v4.WebAuthenticationCredential;
import com.fedex.ws.track.v4.WebAuthenticationDetail;
import com.fedex.ws.track.v4.TrackService;
import com.fedex.ws.track.v4.TrackPortType;
import com.fedex.ws.track.v4.TrackReply;

/**
 *
 * @author me
 */
public class Main {

    /**
     * @param args the command line arguments
     */
    public static void main(String[] args) {

        try {
            TrackRequest trackRequest = new TrackRequest();
            VersionId verId = new VersionId();
            verId.setServiceId("trck");
            verId.setMajor(4);
            verId.setIntermediate(0);
            verId.setMinor(0);
            //The WSDL does not say that this is required but it is.
            trackRequest.setVersion(verId);

            WebAuthenticationDetail auth = new WebAuthenticationDetail();
            WebAuthenticationCredential cred = new WebAuthenticationCredential();
            //This is the key.
            cred.setKey("XXXX");
            //This is the password
            cred.setPassword("XXXX");
            auth.setUserCredential(cred);

            ClientDetail detail = new ClientDetail();
            //This is the test account number
            detail.setAccountNumber("XXXX");
            //This is the test meter number
            detail.setMeterNumber("XXXX");

            TransactionDetail trans_detail = new TransactionDetail();
            trans_detail.setCustomerTransactionId("Tracking with Java");

            TrackPackageIdentifier packId = new TrackPackageIdentifier();
            packId.setType(TrackIdentifierType.TRACKING_NUMBER_OR_DOORTAG);
            //This is some tracking number that you already have.
            packId.setValue("XXXX");

            trackRequest.setWebAuthenticationDetail(auth);
            trackRequest.setClientDetail(detail);
            trackRequest.setTransactionDetail(trans_detail);
            trackRequest.setPackageIdentifier(packId);
            trackRequest.setIncludeDetailedScans(Boolean.TRUE);

            TrackService service = new TrackService();
            TrackPortType port = service.getTrackServicePort();

            TrackReply result = port.track(trackRequest);
            if (result.getHighestSeverity() != NotificationSeverityType.FAILURE && result.getHighestSeverity() != NotificationSeverityType.ERROR) {
                System.out.println("----RESULTS----");
                if (!result.getTrackDetails().isEmpty()) {
                    for (TrackDetail d : result.getTrackDetails()) {
                        System.out.println("Tracking Number " + d.getTrackingNumber());
                        System.out.println("Tracking Description " + d.getStatusDescription());
                    }
                }
            } else {
                for (Notification n : result.getNotifications()) {
                    System.err.println(n.getMessage());
                }
            }
        } catch (Exception ex) {
            ex.printStackTrace();
        }

    }
}

Ta-da! Simple example of the FedEx tracking Web-Service in action. If your account has not been enabled yet you will receive an "Authentication Failed" message. Otherwise you should start seeing some detail about the package. I suggest that you give the TrackDetail class a quick glance since that will be where most of the information you need to access will be. Remember to read those pesky annotations in the WSDL for more information and the PDF on the FedEx developer's website.