I've been asked to install filera into WSADS 6.0 and am having trouble. The problem is that WSADS 6.0 does not support a GUI based installation of a J2C 1.5 level connector like filera.
From the WSADS 6.0 documentation:
"...Prerequisite steps:
Create an enterprise application and target the server to WebSphere Application Server v6.0.
Create or import a connector project set at J2C (formerly known as JCA) v1.0 in your workspace.
Restriction: You can not add connector projects set at J2C v1.5 using the Deployment page of the WebSphere Enhanced EAR editor...."
I would appreciate any suggestions.
tx,
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While waiting for an inspiration as to how to install filera into WSADS 6.0, I discovered that Spring (www.Springframeworks.org) 1.2 has added support for J2C. ( http://www.springframework.org/search/node/j2c )
I would be ecstatic if somebody had an example of how to use Spring to connect to filera.
It is surely a very easy process.... Unfortuately I don't know how to write that simple code.
tx,
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
(I must really sound like a newbie). Well on the bright side I'll help with a FAQ after I get all my ducks in a row.
Anyway, I'm making great progress on the JNDI/WSADS 6 end of things.
I wrote a little servlet that has been a big help.
Here's the relevant method:
Hi, it's me again. Okay, Filera works fine in WSADS 6.0. For what it's worth, here's the output of my servlet that proved it worked:
================================
Hello World. param1='eis/filera'
obj is an instance of FileResourceAdapterConnectionFactory
obj class=net.sourceforge.filera.api.DefaultFileResourceAdapterConnectionFactory
got an instance of FileResourceAdapterConnection okay
frac.createTemporaryFile() created: C:\Documents and Settings\GloverR\Local Settings\Temp\filera7151.tmp
frac.existsFile("C:\Documents and Settings\GloverR\Local Settings\Temp\filera7151.tmp")='true'
obj.toString()='net.sourceforge.filera.api.DefaultFileResourceAdapterConnectionFactory@eeb7952'
Goodbye... Fri Sep 23 19:39:29 EDT 2005
=============================
Now there are two things left to do.
Enhance filera to support ftp, and get filera
to work with Spring Frameworks.
The latter task (Spring) is the one I'm uncertain of.
Does using Spring mean I can run filera from a java batch job? That would be ideal. Comments very, very much appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been asked to install filera into WSADS 6.0 and am having trouble. The problem is that WSADS 6.0 does not support a GUI based installation of a J2C 1.5 level connector like filera.
From the WSADS 6.0 documentation:
"...Prerequisite steps:
Create an enterprise application and target the server to WebSphere Application Server v6.0.
Create or import a connector project set at J2C (formerly known as JCA) v1.0 in your workspace.
Restriction: You can not add connector projects set at J2C v1.5 using the Deployment page of the WebSphere Enhanced EAR editor...."
I would appreciate any suggestions.
tx,
Robert
While waiting for an inspiration as to how to install filera into WSADS 6.0, I discovered that Spring (www.Springframeworks.org) 1.2 has added support for J2C. ( http://www.springframework.org/search/node/j2c )
I would be ecstatic if somebody had an example of how to use Spring to connect to filera.
It is surely a very easy process.... Unfortuately I don't know how to write that simple code.
tx,
Robert
(I must really sound like a newbie). Well on the bright side I'll help with a FAQ after I get all my ducks in a row.
Anyway, I'm making great progress on the JNDI/WSADS 6 end of things.
I wrote a little servlet that has been a big help.
Here's the relevant method:
====================
protected void doWork(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
ServletOutputStream sos = response.getOutputStream();
String sContextToLookup =
(null==request.getParameter("param1")) ? "null" : request.getParameter("param1");
sos.println("<html><head><title>FileraNyseMwPocServ</title></head>");
sos.println("<body>");
sos.println("<h1>Hello World. param1='" + sContextToLookup + "'</h1>");
InitialContext context = null;
Object obj = null;
FileResourceAdapterConnectionFactory cxFactory = null;
try {
context = new InitialContext();
/*
cxFactory = (FileResourceAdapterConnectionFactory)
context.lookup(sContextToLookup);
*/
obj = context.lookup(sContextToLookup);
} catch (NamingException e) {
sos.println("<h1>" + e.getMessage() + "</h1>");
sos.println("</body></html>");
return;
}
if (obj instanceof FileResourceAdapterConnectionFactory) {
sos.println("<h1>obj is an instance of FileResourceAdapterConnectionFactory</h1>");
sos.println("<h1>obj class=" + obj.getClass().getName() + "</h1>");
} else {
sos.println("<h1>obj.toString()='" + obj.toString() + "'</h1>");
sos.println("<h1>Nothing left to do, so: Goodbye... " + (new Date()).toString() + "</h1>");
sos.println("</body></html>");
return;
}
try {
cxFactory = (FileResourceAdapterConnectionFactory) obj;
FileResourceAdapterConnection frac = cxFactory.getConnection();
sos.println("<h1>got an instance of FileResourceAdapterConnection okay</h1>");
} catch (FileResourceAdapterException e) {
sos.println("<h1>FileResourceAdapterException!!!!!!!!!!!!!1</h1>");
sos.println("<h1>" + e.getMessage() + "</h1>");
sos.println("</body></html>");
return;
}
sos.println("<h1>obj.toString()='" + obj.toString() + "'</h1>");
sos.println("<h1>Goodbye... " + (new Date()).toString() + "</h1>");
sos.println("</body></html>");
}
====================
And the results I get, which are extremely encouraging are:
================================
Hello World. param1='eis/filera'
obj is an instance of FileResourceAdapterConnectionFactory
obj class=net.sourceforge.filera.api.DefaultFileResourceAdapterConnectionFactory
got an instance of FileResourceAdapterConnection okay
obj.toString()='net.sourceforge.filera.api.DefaultFileResourceAdapterConnectionFactory@7cab92b'
Goodbye... Fri Sep 23 19:19:46 EDT 2005
=================================
Looking ahead, my boss wants me to enhance filera to add support for using ftp to read/write remote files. Suggestions appreciated.
R.
Hi, it's me again. Okay, Filera works fine in WSADS 6.0. For what it's worth, here's the output of my servlet that proved it worked:
================================
Hello World. param1='eis/filera'
obj is an instance of FileResourceAdapterConnectionFactory
obj class=net.sourceforge.filera.api.DefaultFileResourceAdapterConnectionFactory
got an instance of FileResourceAdapterConnection okay
frac.createTemporaryFile() created: C:\Documents and Settings\GloverR\Local Settings\Temp\filera7151.tmp
frac.existsFile("C:\Documents and Settings\GloverR\Local Settings\Temp\filera7151.tmp")='true'
obj.toString()='net.sourceforge.filera.api.DefaultFileResourceAdapterConnectionFactory@eeb7952'
Goodbye... Fri Sep 23 19:39:29 EDT 2005
=============================
Now there are two things left to do.
Enhance filera to support ftp, and get filera
to work with Spring Frameworks.
The latter task (Spring) is the one I'm uncertain of.
Does using Spring mean I can run filera from a java batch job? That would be ideal. Comments very, very much appreciated.