WSAD WinCVS integration

I am working on forming some guidelines document, dealing with using WinCVS for configuration management from with in WSAD. Mainly to check out or check in code and to add new source to control. I would appreciate if some of you could put in some info which you came across or any interesting links. The idea is just to make the doc as comprehensive as possible.
thanx,
;-)

I don't know much about WSAD and WinCVS integration,
but searching in the Eclipse forums you can get a
taste of some problems that can appear while using the
Eclipse CVS plug-in and WinCVS.
Basically because the Eclipse CVS plug-in tries to be
compatible with the CVS command-line and WinCVS uses
the CVS database but it is more "user-friendly"
Notice: requires (free) registration.
http://dev.eclipse.org/newslists/news.eclipse.tools/msg
9321.html
http://dev.eclipse.org/newslists/news.eclipse.tools/msg
4825.html
and so on...
Just for keeping your thread alive, because we are
writing a big system using WebSphere and maybe we
would switch from MS SourceSafe to CVS.to get to this links it seems that I need some username/passcode, so let me see if I can register. Thanx anyway

Similar Messages

Kodo 2.4 integration with IBM WSAD (IBM)

I am using WSAD (IBM/eclipse) 4.0.3. with Kodo 2.4. I have kodo installed,
but whenever I
attempt to use it I get the following error.... I appears that KODO can't
find the workbenchSite,
I have checked the KODO install and it does list the org/eclipse/ui in its
needed files....and I have
verfiied that the ui directory is present and that workbenchsite is present
in the jar.
I get this error whenever I try to use any of the features on Kodo menu....
Log: Fri Dec 13 12:22:03 CST 2002
1 org.eclipse.core.resources 4 Unhandled exception caught in event loop.
Log: Fri Dec 13 12:22:03 CST 2002
4 org.eclipse.ui 0 org/eclipse/ui/IWorkbenchSite
java.lang.NoClassDefFoundError: org/eclipse/ui/IWorkbenchSite
at
com.solarmetric.modules.integration.eclipse.AbstractAction.getView(AbstractA
ction.java:31)
at
com.solarmetric.modules.integration.eclipse.AbstractMetadataAction.run(Abstr
actMetadataAction.java:44)
at org.eclipse.ui.internal.PluginAction.run(PluginAction.java:125)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at
org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled
Code))
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled
Code))
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled
Code))
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled
Code))
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled
Code))
at org.eclipse.ui.internal.Workbench.run(Workbench.java:656)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:815)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
at org.eclipse.core.launcher.Main.run(Main.java:442)
at org.eclipse.core.launcher.Main.main(Main.java:315)

It appears that in our released version, a different compiler broke our
Eclipse 1.0 support (and for apps based on Eclipse 1.0 such as WSAD 4).
We will get this resolved before the next patch release.
Sorry for any inconvenience this may have caused.
Brian Smith wrote:
Here is the list of files in the solarmetrics.... directory:
list of files in the com.solarmetric.kodo_0.9.0
xml-apis.jar
xercesImpl.jar
xalan.jar
serp_license.txt
serp.jar
plugin.xml
plugin.properties
log4j-1.2.6.jar
kodo-reverse-schema.jar
kodo-jdo-runtime.jar
kodoJDO.library
jta-spec1_0_1.jar
jndi.jar
jdo1_0.jar
jdbc-hsql-1_7_0.jar
jdbc2_0-stdext.jar
jca1.0.jar
jakarta-commons-logging-1.0.2.jar
hypersonic_license.txt
classes12.zip
icons folder
"Brian Smith" <[email protected]> wrote in message
news:[email protected]...
We are running NT 4 for the OS
Yes, this except is from the .log file, the screen just a message that Ihad
an error with the UI (subsystem) and I had to find the .log file to get
something meaningful.
I still don't have a great idea what the root cause of the problem is.
I will get a list of the files in kodo subdirectory when I get intomorrow,
I followed the
directions and copied all of the KODO-JDO-2.4.0 jar files there, but Iwill
get the exact
set for you.
Brian
"Steve Kim" <[email protected]> wrote in message
news:[email protected]...
What OS are you running on? Is this from the .log or from the screen?
If the latter, could you send us the applicable portion of the IDE log
(its $your_eclipse_directory/workspace/.metadata/.log)?
Could you also post a list of the files in your
$your_eclipse_dir/plugins/com.solarmetric.kodo_0.9.0 durectory?
Brian Smith wrote:
I am using WSAD (IBM/eclipse) 4.0.3. with Kodo 2.4. I have kodo
installed,
but whenever I
attempt to use it I get the following error.... I appears that KODOcan't
find the workbenchSite,
I have checked the KODO install and it does list the org/eclipse/ui inits
needed files....and I have
verfiied that the ui directory is present and that workbenchsite ispresent
in the jar.
I get this error whenever I try to use any of the features on Kodomenu....
Log: Fri Dec 13 12:22:03 CST 2002
1 org.eclipse.core.resources 4 Unhandled exception caught in event
loop.
Log: Fri Dec 13 12:22:03 CST 2002
4 org.eclipse.ui 0 org/eclipse/ui/IWorkbenchSite
java.lang.NoClassDefFoundError: org/eclipse/ui/IWorkbenchSite
at
com.solarmetric.modules.integration.eclipse.AbstractAction.getView(AbstractA
ction.java:31)
at
com.solarmetric.modules.integration.eclipse.AbstractMetadataAction.run(Abstr
actMetadataAction.java:44)
at org.eclipse.ui.internal.PluginAction.run(PluginAction.java:125)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at
org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled
Code))
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java(Compiled
Code))
atorg.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled
Code))
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled
Code))
atorg.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled
Code))
at org.eclipse.ui.internal.Workbench.run(Workbench.java:656)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:815)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
at org.eclipse.core.launcher.Main.run(Main.java:442)
at org.eclipse.core.launcher.Main.main(Main.java:315)

Problems with Toplink integration with JTS and WSAD

We have a very strange problem.
Description:
 We are attempting to integrate with JTS, insuring that TopLink does its transactional activity within the scope of a JTS transaction, as described in the Foundation Library Guide.
 We have a stateless session bean, a method of which implements a simple "insert" on a database table registerObject() on a unit of work). This bean is configured to use bean-managed transactions, but with a default resolver of rollback.
 The bean is launched in the WSAD test environment.
 When the bean method is invoked from the WSAD Universal Test Client (web app that runs in the same app server allowing discovery and unit test of bean methods), the code works. A row is inserted into the table, etc.
 Same code, same method, same (stateless) bean, same instance of the WSAD test environment, if the bean method is invoked from outside the application server (via a JUnit test driver that discovers the session bean via JNDI), the code breaks. The final JTS commit catches a javax.transaction.RollbackException, apparently without any sort of stack trace tacked to the exception printStackTrace() doesn't result in anything). No row is inserted.
 We can call the bean alternately, via these two approaches, under the same instance of test environment, and get different behavior.
 We don't understand. All (hopefully) of the relevant details follow.
We are using:
 WSAD Version: 5.0.1 Build id: 20030423_1316
 TopLink - 9.0.3.3 (Build 430)
 Oracle 9i
From our sessions.xml:
 <login>
 <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
 <datasource>project</datasource>
 <platform-class>oracle.toplink.internal.databaseaccess.OraclePlatform</platform-class>
 <uses-external-connection-pool>true</uses-external-connection-pool>
 <uses-external-transaction-controller>true</uses-external-transaction-controller>
 </login>
 <external-transaction-controller-class>oracle.toplink.jts.was.JTSExternalTransactionController_5_0</external-transaction-controller-class>
From our project XML:
 <uses-external-connection-pooling>true</uses-external-connection-pooling>
 <uses-external-transaction-controller>true</uses-external-transaction-controller>
The code that breaks:
 SessionManager sm = SessionManager.getManager();
 Server ss = (Server) sm.getSession("project", TestBean.class.getClassLoader());
 ClientSession cs = ss.acquireClientSession();
 Context c = new InitialContext();
 UserTransaction t = (UserTransaction) c.lookup("java:comp/UserTransaction");
 t.begin();
 UnitOfWork u = ss.getActiveUnitOfWork();
 u.registerObject(value);
 u.commit();
 t.commit(); /* this throws javax.transaction.RollbackException */
Thanks.

Strange problem, could be a Websphere issue, or an issue with the JTSExternalTransactionController_5_0.
Try configuring TopLink to not use JTS and see if the same problem still occurs. Also turn on TopLink logging and exception logging and your Websphere server logging to see if you can get the real exception and stack that is causing the RollbackException.
This could be an issue with the JTSExternalTransactionController_5_0 as the original version of the controller did have a JTS issue. Make sure you are no the latest patch and check with support to see if they have a patch for this problem.

Issue in converting Struts view to JSF view using struts-faces integration

Hi All,
I am facing a issue in my Sruts to JSF conversion application using struts-faces.jar integration library.
Need expert's help desperately as I am not able to use <s:form> tag in my new jsf page to call a struts action.
I want to call a struts action from my web page designed using JSF,
but it seems impossible without using <s:form> tag from struts-faces integration library.
Please suggest how to resolve this...
I am using WSAD 5.1 IDE with inbuilt Test environment WebSphere server
JSF Version: Sun's RI 1.1
Struts framework: 1.2.6
Struts-Faces Integration Library version: 1.0
I have configured a controller element in struts-config.xml file as has been suggested by different online
documents I studied:
<controller>
<set-property property="processorClass"
value="org.apache.struts.faces.application.FacesRequestProcessor"/>
</controller>
But configuring a controller does not allow my test server to start up properly and due to errors the ActionServlet also becomes unavailable.
If I comment the controller and start the test server it starts fine but then I cannot access the converted jsf page which contains the <s:form action="/xxxxx.do"> tag.
If now I get back to <h:form> tag instead of <s:form> tag with a <h:commandButton action="xxxx.do"/> for form submission in my jsf page, I see the html page generated with all components but now checking the html source generated I see
<form action="/contextName/jspFolder/sameDisplayedPage.jsf"> which is not valid and never gets called successfully.
I think someways I need to use the <s:form> tag with the controller configured properly to use the struts-faces integration library's request processor, to get things working. But HOW???
Following is the error I get if I use the <controller> tag element in struts-config.xml file and start the server.
This error appears on starting the server without accessing any application's jsp web page
[6/12/06 15:31:14:109 IST] 3e311815 ActionServlet E org.apache.struts.action.ActionServlet Unable to initialize Struts ActionServlet due to an unexpected exception or error thrown, so marking the servlet as unavailable. Most likely, this is due to an incorrect or missing library dependency.
[6/12/06 15:31:14:109 IST] 3e311815 ActionServlet E org.apache.struts.action.ActionServlet TRAS0014I: The following exception was logged java.lang.IllegalAccessError: org.apache.commons.digester.SetPropertyRule tried to access method org/apache/commons/beanutils/BeanUtils.setProperty(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/Object;)V
at org.apache.commons.digester.SetPropertyRule.begin(SetPropertyRule.java:198)
at org.apache.commons.digester.Rule.begin(Rule.java:200)
at org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:736)
at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:685)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:331)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:82)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)
at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java:113)
at com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.java:189)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java:870)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:542)
at com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java:1277)
at com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java:283)
at com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java:387)
at com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java:209)
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:987)
at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:136)
at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:356)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:418)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:787)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:354)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:575)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:271)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:249)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:125)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
[6/12/06 15:31:14:188 IST] 3e311815 WebGroup E SRVE0020E: [Servlet Error]-[ActionServlet]: Failed to load servlet: javax.servlet.UnavailableException: org.apache.commons.digester.SetPropertyRule tried to access method org/apache/commons/beanutils/BeanUtils.setProperty(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/Object;)V
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:366)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:82)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)
at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java:113)
at com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.java:189)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java:870)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:542)
at com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java:1277)
at com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java:283)
at com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java:387)
at com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java:209)
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:987)
at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:136)
at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:356)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:418)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:787)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:354)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:575)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:271)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:249)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:125)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
(same error message re-iterates/repeats itself... and finally -
Error 503: Failed to load target servlet [ActionServlet] comes in web-browser
Following is the error which I get if I comment the <controller> element in the struts-config.xml file
and use a <s:form action="xxxxx.do"> in the struts converted jsf page. The web-server starts fine, but
accessing the jsf page givers error as:
[6/12/06 15:38:00:781 IST] 696f19de WebGroup I SRVE0180I: [Sample Struts-JSF integration application] [training2] [Servlet.LOG]: /jsp/welcomeF.jsp: init
[6/12/06 15:38:01:219 IST] 696f19de WebGroup E SRVE0026E: [Servlet Error]-[]: java.lang.NullPointerException
at org.apache.struts.faces.renderer.FormRenderer.encodeBegin(FormRenderer.java:114)
at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:683)
at javax.faces.webapp.UIComponentTag.encodeBegin(UIComponentTag.java:591)
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:478)
at org.apache.jsp._welcomeF._jspService(_welcomeF.java:207)
at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:344)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:662)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
at org.apache.struts.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1054)
at org.apache.struts.action.RequestProcessor.internalModuleRelativeForward(RequestProcessor.java:992)
at org.apache.struts.action.RequestProcessor.processForward(RequestProcessor.java:551)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:209)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1192)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:412)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Finally if I change my <s:form action="xxxxx.do"> tag to
<h:form>
<h:commandButton id="submit" action="xxxx.do" value="Submit" />
I see the webpage coming up in the browser (no controller element used in struts-config.xml file this time)
But in the html source of this html created from jsf I see
<form id="_id2" method="post" action="/training2/jsp/welcomeF.faces" enctype="application/x-www-form-urlencoded">
here form's action attribute is pointing to the same displayed page with the context name prefixed. I
assume it is because jsf could not resolve the "xxxx.do" action to anything so set it to the same displayed page.
May be I am wrong as usual...
Below is the simple struts jsp page which I need to convert to jsf page as I am converting only the View part of application.
I want to use the same struts beans and application logic at the back-end. At front-end I need UIComponents from JSF to be used.
Following is the struts jsp page
<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1" %>
<%@ taglib prefix="html" uri="/WEB-INF/lib/struts-html.tld" %>
<%@ taglib prefix="bean" uri="/WEB-INF/lib/struts-bean.tld" %>
<html:html>
<html:base/>
<html:messages id="messages" />

<html:errors/>

<BODY>
Sample Struts and JSF integration example
This one is being displayed via Struts specific tags
<html:form action="validateUser.do">
<bean:message key="label.name" /> : <html:text property="name" />
<bean:message key="label.password" /> : <html:password property="password" />
<bean:message key="label.age" /> : <html:text property="age" />
<bean:message key="label.city" /> : <html:text property="city" />
<bean:message key="label.address" /> : <html:text property="address" />
<html:submit property="submit" value="Show info via Struts" />
</html:form>
</BODY>
</html:html>
I have converted it into the following jsf page
<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://struts.apache.org/tags-faces" prefix="s" %>
<f:view>
<HTML><BODY>
<f:verbatim>Sample Struts and JSF integration example</f:verbatim>
<f:verbatim>This one is being displayed via JSF tags</f:verbatim>
<h:form> 
<h:inputText id="name" value="#{userForm.name}" /><f:verbatim>
</f:verbatim>
<h:inputSecret id="password" value="#{userForm.password}" /><f:verbatim>
</f:verbatim>
<h:inputText id="age" value="#{userForm.age}" /><f:verbatim>
</f:verbatim>
<h:inputText id="city" value="#{userForm.city}" /><f:verbatim>
</f:verbatim>
<h:inputText id="address" value="#{userForm.address}" /><f:verbatim>
</f:verbatim>
<h:commandButton id="submit" action="#{user.facesAction}" value="Show info via Struts" />
</h:form>
</BODY></HTML>
</f:view>
I am very hopeful of some answer from respected group experts, please help me.
I am in urgency of course but would not push for immed. response like other, just want some help for sure that is going to
be extremely valuable to me. Anticipating a helping hand...
Thanks and Regards
Vishal Sharm
Time's fun when you're having flies � Kermit, the Frog
-------------------------------------------------------------------------

I've managed to get this working Ok from JDeveloper:
See:
http://www.groundside.com/blog/content/DuncanMills/J2EE+Development/?permalink=573FDB6F8D918B9704907899635CABB1.txt
http://www.groundside.com/blog/content/DuncanMills/J2EE+Development/?permalink=2B04ACE99A6437EDED775F15553D1DED.txt
Basically you just have to fiddle around with Library settings to get this working OK.
As to how useful this is, well that's up to you - I'd not regard Faces + Struts as a must use combination, rather it's a can mix if you really need to. Look at Faces and Faces navigation first and see if that actually gives you enough before you start to look at mixing.

Integration with Websphere 5.0 (EJB 2.0) problems

Hello all,
Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
Websphere 5.0 (using EJB 2.0).
I have been basically binding a PersistenceManagerFactory into JNDI via
start-up servlet, however got the exception bellow when I tried to create
PersistenceManagerFactory (in setSessionContext of the EJB).
JDOFatalInternalException: Could not perform automatic lookup of EJB
container's javax.transaction.TransactionManager implementation. Please ensure
that you are running the application from within an EJB 1.1 compliant
EJB container, and then set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
value to obtain the TransactionManager.
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
5.0?
Thank you,
Petr

Petr-
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
Websphere. However, it should be noted that it is not as rigorously
tested internally at SolarMetric as some other application servers (E.g.,
JBoss and WebLogic). In short, integration is known to work, but it
might be a little more rough around the edges than for other application
servers (as shown in our misspelling of Websphere's TransactionManager
implementation name).
How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
javax.jdo.option.ConnectionFactoryName property (see
http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
This is often more appropriate for applications server usage, since it
allows you to configure pooling and other information from within the
application server's centralized configuration.
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
configuration we use for testing with IBM's drivers is:
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
They shouldn't behave differently (I am guessing that the app driver is
a type 2 driver or something), but it might be worth a shot to try using
the net driver. If this fixes the problem, please let us know, because
it will indicate that Kodo has a deficiency with one of IBM's drivers
that we should look into resolving.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
PM and start persistence operations. Note that you should also be able
to deploy Kodo as a Resource Adapter (which allows Kodo configuration
through the centralized Websphere configuration interface). However, I
doubt this is part of the issue.
So, in short, I recommend trying the following things:
1. Using the ConnectionFactoryName to use the DataSource defined for the
appserver, on the off chance this will fix it.
2. Using the net driver instead of the app driver.
3. Seeing if it will work with javax.jdo.option.Optimistic set to false
If none of these work, please let us know, and we will continue to
investigate other possible solutions.
In article <[email protected]>, Petr Bulanek wrote:
Hello Marc,
Very good guess. Pretty much the same code worked well without App server.
In that case, there obviously was no magic related to
TransactionManagerFactory initialization (see bellow).
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?
How do I tell Kodo to use existing Datasource managed by app server?
Here is the basic configuration (URL, class, etc):
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snet
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.
The new EESimpleConfiguration(true) construct seems to (by default) read
the kodo.properties file that is part of the project.
EEConfiguration conf = new EESimpleConfiguration(true);
conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
EEPersistenceManagerFactory pmf =
 new EEPersistenceManagerFactory(conf);
InitialContext ic = new InitialContext();
ic.rebind(\"KodoPMF\", pmf);
Thank you,
Petr
Marc Prud\'hommeaux wrote:
Petr-
It looks like DB2 doesn\'t like our attempt to close the connection
without a rollback or commit. This is odd, since we have never
seen this happen in our stand-alone DB2 tests. Can you let us know
the connection details (driver, connectionURL, etc)?
In the meantime, one possible workaround may be to turn off
optimistic transactions (since this will cause the PM to
only use a single Connection); can you try to specify:
javax.jdo.option.Optimistic=false
Also, have you tried to run this code in a non-managed environment
(e.g., outside the application server)? I would be interested
to know if it is related to running within an appserver.
In article <[email protected]>, Petr Bulanek wrote:
Hi Abe,
Thank you for a speedo reply. You guys really are on the ball!!!
As you suggested, the
\\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
did the job (for others, please note that the proper package name should
contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
Unfortunately, I got another problem. When running a method containing
query (code bellow),
I get SQLException complaining about \\\'Invalid transaction state\\\'.
The method that executes the query is a stateless transactional Session
bean.
Thank you for your help,
Petr
--------------------------- DB2 - transaction state description
CLI0116E Invalid transaction state.
Explanation: There was a transaction in progress when SQLDisconnect was
called.
User Response: Call SQLTransact before calling SQLDisconnect.
--------------------------- Exception ------------------------------------
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
PARENTX.JDOCLASSX FROM PARENTX
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] executing statement <369367952>: [reused=1;params={}]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close:
com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close connection
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
exception when closing connection
[2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
Invalid transaction state. SQLSTATE=25000
atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
--------------------------- Failing code sample
try {
 PersistenceManager pm = factory.getPersistenceManager();
 Extent ex = pm.getExtent(Parent.class, false);
 Query q = pm.newQuery(ex, \\\"name==parName\\\");
 q.declareParameters(\\\"String parName\\\");
 Collection col = (Collection) q.execute(\\\"James\\\");
 Iterator iter = col.iterator();
 Parent pp;
 Collection ch;
 while (iter.hasNext()) {
 pp = (Parent) iter.next();
 System.out.println(pp);
 ch = pp.getChildren();
 Iterator it= ch.iterator();
 while (it.hasNext()) {
 System.out.println(it.next());
 q.closeAll();
 pm.close();
 } catch (Exception e) {
 System.out.println(e);
 throw new EJBException(e);
Abe White wrote:
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
EJB 2.0 is also supported. Sorry for the confusing error message.
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
WSAD
5.0?
Try these settings:
com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
 com.solarmetric.kodo.ee.InvocationManagedRuntime
com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
 TransactionManagerMethod=\\\\
 com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
Marc Prud\'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Eclipse or WSAD plugins for Weblogic?

Dear BEA people,
An integration kit for VisualAge for Java and Weblogic is available, but
what about plugins for the successor of VAJ, namely Websphere Studio
Application Developer (WSAD)? Are you looking into this, and if so, when may
we expect a first trial version?
Yours sincerely,
Ringo
P.S. MediaGeniX is a BEA partner.
Ringo De Smet MediaGeniX NV
Access Forty - Gossetlaan 54 1702 Groot-Bijgaarden - Belgium
Phone: +32-(0)2-467.34.30 Fax: +32-(0)2-467.34.39
mailto:[email protected] http://www.mediagenix.com

Plugins for both Eclipse and WSAD for Weblogic are available from Genuitec
at http://www.genuitec.com/products.htm
Regards,
Todd
"Ringo De Smet" <[email protected]> wrote in message
news:[email protected]..
Dear BEA people,
An integration kit for VisualAge for Java and Weblogic is available, but
what about plugins for the successor of VAJ, namely Websphere Studio
Application Developer (WSAD)? Are you looking into this, and if so, whenmay
we expect a first trial version?
Yours sincerely,
Ringo
P.S. MediaGeniX is a BEA partner.
Ringo De Smet MediaGeniX NV
Access Forty - Gossetlaan 54 1702 Groot-Bijgaarden - Belgium
Phone: +32-(0)2-467.34.30 Fax: +32-(0)2-467.34.39
mailto:[email protected] http://www.mediagenix.com

RC1 and WSAD 5.1

I am getting the following error when trying to generate the mapping file
and build schema into the database.
kodo.util.DataStoreException: java.lang.SecurityException: Package name not
allowed -'java.sql'
NestedThrowables
kodo.util.FatalDataStoreException: java.lang.SecurityException: Package name
not allowed -'java.sql'
NestedThrowables
java.sql.SQLException: java.lang.SecurityException: Package name not
allowed -'java.sql'
I cannot seem to get around it. I am not using or referring to the java.sql
package anywhere in my application code. Prior to this error, I was getting
an error ...ClassNotFound ...java.sql.Savepoint when trying to generate the
mapping. So I explicitly set a reference to the JDK1.4\JRE\rt.jar in the
plugin.xml file for the eclipse integration and dropped the rt.jar into the
plugin directory. This solved the ClassNotFound problem, but then I ended
up with the above.
BTW - the exact same progam and the enhance/map/schema functions work fine
through the JBuilder integration to the same database configuration. I am
using WSAD 5.1 (jdk1.4) with RC1. The Kodo configuration in WSAD is
considerably simpler than JBuilder, but I am using the sames values in each
config where appropriate.
Has anyone else seen this?
Any suggestions?
Thanks,
-Robert

Robert-
My first guess is that you are using JDK 1.4 and you are including the
jdbc2_0-stdext.jar in your CLASSPATH. If this is the case, can you
remove it (since it contains JDBC extensions that are included by
default with JDK 1.4), and see if it fixes the problem.
Otherwise, can you provide us with some more details: complete stack
trace, platform and JVM information, the setting of your CLASSPATH
variable, and kodo.properties file.
In article <blnevg$j86$[email protected]>, Robert Greene wrote:
I am getting the following error when trying to generate the mapping file
and build schema into the database.
kodo.util.DataStoreException: java.lang.SecurityException: Package name not
allowed -'java.sql'
NestedThrowables
kodo.util.FatalDataStoreException: java.lang.SecurityException: Package name
not allowed -'java.sql'
NestedThrowables
java.sql.SQLException: java.lang.SecurityException: Package name not
allowed -'java.sql'
I cannot seem to get around it. I am not using or referring to the java.sql
package anywhere in my application code. Prior to this error, I was getting
an error ...ClassNotFound ...java.sql.Savepoint when trying to generate the
mapping. So I explicitly set a reference to the JDK1.4\JRE\rt.jar in the
plugin.xml file for the eclipse integration and dropped the rt.jar into the
plugin directory. This solved the ClassNotFound problem, but then I ended
up with the above.
BTW - the exact same progam and the enhance/map/schema functions work fine
through the JBuilder integration to the same database configuration. I am
using WSAD 5.1 (jdk1.4) with RC1. The Kodo configuration in WSAD is
considerably simpler than JBuilder, but I am using the sames values in each
config where appropriate.
Has anyone else seen this?
Any suggestions?
Thanks,
-Robert
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

CVS Integration with JDeveloper 10.1.2

I have upgraded to JDeveloper 10.1.2 from the previous version and CVS integration appears to be partially broken.
All my source files are checked in and I can confirm this with WinCVS which allows me to 'cvs edit' my source for update. In JDeveloper however the 'Edit' option is grayed out and I cannot edit the file as it is read only. All the source icons have a * symbol against them.
CVS integration worked OK in the previous version and the only environment change is the upgrade to JDeveloper 10.1.2
I wondered if anyone else had experienced any similar problems.
Thanks,
Kim

We have also experienced this problem. The pattern seems to stem from a Module Checkout (We use the connections tab to a remote pserver repository).
Expanding a project will mark all files with the * (modified) symbol. Even though we only just checked out the module.
If we try and Update (or Update with deletion) the item remains on the uncommitted files list, however the background cvs command worked without error (at this point there is no way of removing files from the uncommitted file list).
Additionally if we use ANT and create a new task like follows;
<target name="CVS fake update MyProject quiet">
<cvs command="-n update -R"
cvsRoot="${cvsroot}"
package="MyProject"
/>
</target>
Then this reports all workfiles up to date with the repository (i.e. only a problem in what JDeveloper thinks is uncommited).
What I have noticed....
When the Module Checkout works I noticed the file named JDev under the CVS working folder looks as follows;
#Fri Apr 01 06:33:52 GMT 2005
universal_time_calibration=0
When it fails the content looks like this;
#Fri Apr 15 06:33:52 GMT 2005
universal_time_calibration=-3600000
(I suspect at some point it is getting this offset from my Windows settings - Australia GMT + 10hrs).
By fail I mean
Hope this information is of use to someone at Oracle.

Can NitroX be pluged into IBm WSAD 5.1.1 ?

empty

We are still working on the WSAD integration. The current build does not
support it yet..
M7 Support
"Alex" <[email protected]> wrote in message
news:40720c34$[email protected]..
Hi,I am using IBM WSAD 5.1.1 as my main developing tool.
How can I use NittoX in IBM WSAD 5.1.1 ?
Thank you

URGENT: Cvs Integration

Hi,
I am currently struggling with the CVS integration within JDeveloper 9.0.3. Maybe anyone can help ;-)
My configuration:
JDeveloper is installed on a W2k worstation, the cvs server resists on a linux server. We currently use the cvs client "Concurrent Versions System (CVSNT) 1.11.1.3 (Build 57j) (client/server)" provided by cvsnt.org, those folder path is listed in the environment variable PATH.
We must use SSH for the connect to the CVS server on the linux machine. Therefore, we configured an external locator which is ssh2.
We successfully established a connection via WinCVS and SSH to our CVS server.
We have been working on integration of JDeveloper with CVS since a few days - with little success. When JDeveloper starts we receive the typical CVS message pane, and the source control entry within the context menu is also available - by this means JDeveloper could successfully access the CVS client. When we try to create a CVS connection we run into some issues. We set the external locator to ssh2.exe with the remote server program cvs.
We also set the configuration parameters properly for our connection, so that our CVSROOT variable seems to be ok (real names replaced by placeholders):
:ext:<<username>>@<<ourCVSServer>>:/usr/local/cvs.
But when we try to make a test connection then the following issue occurs:
1. The external shell pops up where we enter the password
2. one or two seconds delay
3. Error message in wizard: Connection test failed: unable to connect.
I don't have any clue how to solve this.
My questions:
- Did anyone get connected to a CVS on linux machine via SSH within JDeveloper?
- if yes, how did you do this?
- what am I doing wrong?
I appreciate every hint or installation step procedure.
Regards,
Stefan

I posted a reply on your other thread on this.
Rob
Team JDev

Project folders and WinCVS sandbox

I have installed WinCVS 1.3.14.1 Beta and JDeveloper 9.0.3.4. I have sandbox with different folders and subfolders. How can I use this sandbox from within JDeveloper?
Should I copy all folders from sandbox to JDev or should I leave them there and work directly on them from JDev?
If I should copy them, how should I do that? (when I copy it seems I do not get subfolder structure copied over). What is the best practice in this WinCVS/JDev setup?
many thanks,
Sale

I agree with Shay, if you can move up to a later version of JDev do so. The integration with CVS has moved on massively over the releases of JDev.
The simple answer to your question is that you should create a project in JDev that uses the files under the sandbox you already have.
Then create a CVS connection in JDeveloper the same as the one you used in WinCVS to create the sandbox.
Something like
:pserver:myuser@myserver:/myrepos
JDeveloper will then recognise the sandbox as belonging to that connection and allow source control operations.
Hope this helps,
Geoff

Refresh System Data in Integration Directory PI 7.11

Hey,
I have setup a new technical system and a business system in SLD, but now I still can't find it in Integration Directory.
I knew from the later PI Version, that there was an option to transfer SLD data to integration directory, but now I can't find it
anymore.
Can anybody help?
Thanks!
Michael

I have setup a new technical system and a business system in SLD, but now I still can't find it in Integration Directory.
I knew from the later PI Version, that there was an option to transfer SLD data to integration directory, but now I can't find it
Tools (or right-click in ID) --> Assign Business System --> follow the wizard...it will assign the business system from SLD to ID

What is new AT&T iPhone MMS date? I see integrated messaging feature

Okay, I heard that this was to happen at then end of Summer, then end of July.
So what is the new date? I see Integrated Messaging counters in my AT&T profile as of this week.
Should we expect another update to sync with iTunes to get it working?

Funny. I'm going to mark this question as answered -and this last post as funny.
I hope it isn't sarcasm, cause my sarcasm detector runs on Windows 7 and I currently have my VMware Fusion session powered off.
The heart of my question was really the "integrated message" counter in my AT&T profile. I was hoping to hear others just got it, or don't have it, or when they got it, and they I could magically extrapolate a new MMS rumor date.
Anyway, I don't have to go to UK (although a good choice), cause Rogers in Canada has MMS already.
One Mac. One World.

How to print Integrity sql in the preparedstatement?

How to print Integrity sql in the preparedstatement?
Connection conn = null;
String sql = "select * from person where name=?";
PreparedStatement ps = conn.prepareStatement(sql);
ps.setObject(1, "robin");
ps.executeQuery();
i'm wants print Integrity sql.
For example:select * from person where name='robin'
How should I do?
thanks a lot!

PreparedStatement doesn't offer methods for that. You can write your own implementation of PreparedStatement which wraps the originating PreparedStatement and saves the set* values and writes it to the toString().
If needed, myself I just print the sql as well as the values-being-set to the debug statement.Logger.debug(query + " " + values);

Can i use OER to store the data from a excel sheet that pertains to the entire integrations ?

hi ,
i know that the OER can be used to view the entire landscape for the SOA composites and how they are related with each other. However we have a requirement wherein we need to store the data for the entire integration end systems e.g. ebiz, mfgpro, siebel etc ( that is we need to store data one level up).
Also, we want a customized form in OER wherein user can manually add data regarding the integrations.
So is it possible to do so ? If yes, how ?

ok, let me put it this way,
I tried using the import/export utility available under OER admin tab.
When i export my existing assets it generates the .xml file for each asset. Now as i have hundreds on new assets to be created for each asset type i want to be able to create a new .xml file and want it to create the new asset once i import it using import utility. I tried creating a new .xml file giving it a new UUID but it does not seem to work. Has anyone tried this earlier who can give the steps to do this ?

WSAD WinCVS integration

Similar Messages

Maybe you are looking for