I posted instructions in the forum topic. The API is very simple (one
line of code to get a file from a deployment). Also, the whole reason
for it is so that support for arbitrary deployment types (jar,
filesystem directory, network location, etc) can be added and maintained
in one location (the mc).
-----Original Message-----
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Wednesday, December 13, 2006 8:45 AM
To: Jason T. Greene
Cc: Thomas Diesler; jbossws-dev(a)lists.jboss.org
Subject: Using VFS for locating wsdl resources
Jason,
please see
Using the VFS to read a resource from nested jars
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993404#...
Why should I waste my time with a project that is so poorly documented
if I don't absolutely have to?
Yes, in future we should use the VFS.
Then I update
public void EarTestCase.testResourceURL() throws Exception
{
File earFile = new File("libs/jaxws-eardeployment.ear");
assertTrue(earFile.exists());
URL warURL = new URL("jar:" + earFile.toURL() +
"!/jaxws-eardeployment.war!/");
URL wsdlURL = new URL(warURL, "WEB-INF/wsdl/TestEndpoint.wsdl");
Element root = DOMUtils.parse(new
ResourceURL(wsdlURL).openStream());
assertNotNull(root);
}
cheers
-thomas
Jason T. Greene wrote:
> Thomas,
>
> I took a look at your solution to JBCTS-422. Why didn't you use the
VFS
> as mentioned in the jira issue? With JBoss 5 all deployment
resource
> access is support to go through the VFS.
>
> I have created a new issue for this:
>
http://jira.jboss.com/jira/browse/JBWS-1421
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Jason T. Greene
> Senior Software Engineer
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx