Perhaps the useful utility object from the web package should be moved to a utilitypackage so that other packages can utilize it without inviting an unwanted dependency.
The utilitypackage contains the XML parser and transaction builder classes used to construct a transaction manager based on the SOA transaction Definition file (Figure 2).
As Figure 1 illustrates, the classes that comprise the TCS prototype are bundled into four packages: the transaction package, the service package, the utilitypackage, and the exception package.