I have an application developed in 8.5 using a few elements from the extension library.
The server has been upgraded with the extension library applied each upgrade.
With the extension library now part of the code base there is no need to have it installed on top of the Domino installation, however the application cannot be edited unless it is applied.
How do we remove the extension library from the application?
That said, can I install the extension library on a Domino v10 server?
I have checked the extension library website and there is no reference to ND10 and using the extension library. This is not really downloaded much anymore which is why I feel I should remove this dependency my application has.
I am currently getting the error 'Could not load the page /cc_input.xsp because the corresponding class xsp.Cc_005finput was not a com.ibm.xsp.page.compiled.CompiledPageDispatcher.' This error points to the issue being with the missing extension library.
I have checked what is installed, and this is the output:
tell http osgi ss com.ibm.xsp.extlib
[16F8:0002-21FC] 19/04/2019 05:18:34 PM osgi "Framework is launched."
[16F8:0002-21FC] 19/04/2019 05:18:34 PM id State Bundle
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 171 ACTIVE com.ibm.xsp.extlib.controls_10.0.1.v00_00_20181128-2143
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 172 ACTIVE com.ibm.xsp.extlib.core_10.0.1.v00_00_20181128-2143
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 173 ACTIVE com.ibm.xsp.extlib.domino_10.0.1.v00_00_20181128-2143
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 174 ACTIVE com.ibm.xsp.extlib.mobile_10.0.1.v00_00_20181128-2143
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 175 ACTIVE com.ibm.xsp.extlib.oneui_10.0.1.v00_00_20181128-2143
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 176 ACTIVE com.ibm.xsp.extlib.relational_10.0.1.v00_00_20181128-2143
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 177 STARTING com.ibm.xsp.extlib.sample_10.0.1.v00_00_20181128-2143
[16F8:0002-21FC] 19/04/2019 05:18:34 PM 178 ACTIVE com.ibm.xsp.extlib_10.0.1.v00_00_20181128-2143
Extension Library is part of Domino since 9.0.1 FP10. From the error message, it seems like you're misunderstanding what needs installing where for what purpose.
tell http osgi ss and tell http osgi diag issued on a server console show what's running on the server. They're required for a successfully compiled application to run on the server.
Looking at the error message, the likelihood is that the application is not successfully compiled and the errors you're seeing are in Domino Designer as well as / instead of the Domino server.
I suspect it's also a high likelihood that the application has been opened in DDE with Build Automatically enabled. If that happens and the plugins it's dependent on are missing, the application gets recompiled and the result is an unsuccessfully compiled application, which means it no longer runs anywhere until successfully compiled.
The error message is almost certainly nothing to do with Extension Library, it's core plugins missing from DDE that last compiled the application. See https://openntf.org/main.nsf/blog.xsp?permaLink=JGAR-B9QL8B.
Under the strongest terms I would advise against developing without the XPages Extension Library. You'll also have a sub-optimal user experience and are likely to hit problems developers haven't encountered for over five years. And if you remove it from an existing application, you'll likely have to do significant redevelopment.
Related
I'm having some trouble deploying my .sppkg file to Sharepoint 2019. I've developed it using the SPFx framework version v1.4.1 to ensure it is compatible, and the webpart works fine when deployed in development mode against the Sharepoint environment's workbench (https://your-sharepoint-site/_layouts/workbench.aspx).
However, after uploading the webpart to the app catalog, it displays the general error message :
Error in client-side code
and is unable to deploy. In the logs for the Sharepoint environment, after uploading the package this error appears:
Caught an exception while updating the properties of SharePoint App package AppCatalog/my-webpart-app.sppkg. Error: There were errors when validating the App package: Error in the application. Stack Trace:
at Microsoft.SharePoint.Marketplace.CorporateCuratedGallery.SPCorporateCatalogEventReceiver.PromoteProperties(SPListItem listItem, Stream packageStream, Boolean addingPackage)
at Microsoft.SharePoint.Marketplace.CorporateCuratedGallery.SPCorporateCatalogEventReceiver.HandleItemAddedOrUpdated(SPListItem listItem, Boolean categoryChanged, Boolean addingPackage, Boolean isDeploying, Boolean beforeIsDeployed, Boolean beforeIsCurrentVersionDeployed)
The same package deploys fine in a Sharepoint Online environment. I don't have another 2019 environment to test in.
I'm a bit at a loss of how to debug. A test .sppkg file built from the starter SPFx project using version 1.4.1 deploys just fine, so my only thought is to slowly add functionality to the base package and deploy new versions until it breaks, but that feels a bit like madness.
Does anyone have any insight into what part of the packaging process might cause the .sppkg file to be unable to run when uploaded? Could it be permissioning issues in the environment?
Metadata of you .sppkg has errors:
There were errors when validating the App package: Error in the application.
I think, main error - you not create clean project. Create clean project, by using this info
yo #microsoft/sharepoint
Don't mistake, answer this question:
Which baseline packages do you want to target for your component(s)?
There are 2016, 2019, SharePoint Online only (latest)
If your package was created for sharepoint online - it not be added to sharepoint 2019 On Premis.
Permissions errors you will see in app catalog, and uls logs. Your error - incorrect metadata of package.
Sharepoint starter kit has this info
Starter Kit Version 1 includes a comprenshive strategy for only SharePoint Online, as well as a single SPFx solution that encapsulates all webparts and extensions into a single package. Version 1 may be accessed via the v1 branch for legacy purposes and will not be maintained beyond April 2020. link
so, don't modify it:) it's alredy legacy.
For developer own packages on premises - you can create single server farm. If you work in sharepoint online - you can use Office 356 developer programm
I want to use bootstrap in an application, but when I set the bootstrap theme via the xsp properties the framework is not loaded.
if I check the version of the extension library it says: 9.0.1.v00_00_20151122-0905
how can I check if the framework is available on this server?
That is the core 9.0.1 Extension Library. I believe it wasn't added until version 10 from OpenNTF (9.0.1.v00_10...). It will also be in FP8, which will be 9.0.1.v08_00.... The number before the "_" will be the feature pack version, the number after will be the OpenNTF release updating that release's Extension Library.
a good way to check it can be via the server console: tell http osgi ss com.ibm.xsp.theme
you should get a list of available themes returned e.g.:
tell http osgi ss com.ibm.xsp.theme
2017-02-28 11:44:14 Framework is launched.
2017-02-28 11:44:14 id State Bundle
2017-02-28 11:44:14 27 ACTIVE com.ibm.xsp.theme.bootstrap_9.0.1.v00_17_20160428-0214
2017-02-28 11:44:14 262 ACTIVE com.ibm.xsp.theme.oneui.idx_9.0.1.20151122-0905
2017-02-28 11:44:14 263 ACTIVE com.ibm.xsp.theme.oneuiv302_9.0.1.20151122-0905
In case this might help I have the following resources available on my local dev environment:
Dojo
http://dev1/xsp/.ibmxspres/dojoroot-1.9.7/dojo/dojo.js
Bootstrap
http://dev1/xsp/.ibmxspres/.extlib/responsive/bootstrap3/js/bootstrap.min.js
Try to reach these resources on your server (mine is dev1).
If the lather one fails you presumably do not have bootstrap available.
But then I am on 9.0.1.v00_17_20160428-0214.
Shouldn't DDE have the panels 'Bootstrap' and 'Responsive'?
Try to have the Bootstrap4Xpages extension installed if you can: https://bootstrap4xpages.openntf.org/
I've managed to deploy a simple Web application to Websphere 8.5, but unable to start it. It throws an ArrayIndexOutofBoundsException while starting my application.
We have been using Tomcat7 so far for our web app. It's a simple web-app with JSPs, JSs and Servlets.
I've tried a lot of options to deploy the application on Websphere, but the latest hurdle i'm facing is the ArrayIndexOutofBoundsException.
I tried to deploy the same application (a mini version) which contained only one servlet, and it was successful. But when I have multiple servlets, I get this exception. Below is my stack trace
[8/12/14 12:15:55:463 IST] 00000046 BeansDeployer E BeansDeployer deploy
java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException
at org.apache.webbeans.portable.AnnotatedElementFactory.newAnnotatedType(AnnotatedElementFactory.java:150)
at org.apache.webbeans.config.BeansDeployer.deployFromClassPath(BeansDeployer.java:484)
at org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:171)
at org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:124)
at org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:78)
at com.ibm.ws.webbeans.common.CommonLifeCycle.startApplication(CommonLifeCycle.java:106)
at com.ibm.ws.webbeans.services.JCDIServletContainerInitializer.onStartup(JCDIServletContainerInitializer.java:85)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initializeServletContainerInitializers(WebAppImpl.java:613)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:409)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:426)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:718)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1175)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1370)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:968)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:774)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2182)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:116)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:994)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:502)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862)
Caused by: java.lang.ArrayIndexOutOfBoundsException
at org.apache.webbeans.portable.AbstractAnnotatedCallable.setAnnotatedParameters(AbstractAnnotatedCallable.java:66)
at org.apache.webbeans.portable.AnnotatedConstructorImpl.<init>(AnnotatedConstructorImpl.java:56)
at org.apache.webbeans.portable.AnnotatedElementFactory.newAnnotatedType(AnnotatedElementFactory.java:117)
... 27 more
I read a couple of other posts from people who faced more or less the same problem, but they were talking about Spring or Guava, none of which I use here. As a result, the solutions I read there did not solve my problem.
Can any one throw light on a solution? It would be helpful to a very great extent.
Additional Info:
I'm developing my project on Eclipse Kepler and using the Webshpere 8.5 plugin to deploy on Websphere application server.
Thanks,
Sriram
Actually it turns out my project was indeed referencing to guava. It was using guava version 15.0. I changed the version to 16.0 and included then in my shared library.. and it solves the issue. Apologies for overlooking guava.. old have saved a lot of time !!
Many sources noted that in Domino 8.5.4/9 should be clean way of starting OSGi bundles on HTTP startup as noted for example here http://lekkimworld.com/2011/07/08/dots_and_automatic_startup_of_bundles.html
Currently I'm still not able to find any documentation about it. Is there some extension point or other configuration that can be used for that?
In Domino 8.5.3 we did ugly hack when bundles pretend to be Dojo libraries and so they started automatically. On one of our Domino 9 test machines this probably causes troubles (every other restart server complains that No Dojo library could be found), so I wanted to cleanup our code.
Bundle is our workflow engine and since it can do some automatic processing we need to start it even when no request comes to server.
The webdav plug-in on OpenNTF has an autostart option. In this case it was linked to the Servlet extension point. That might help. Are you extending Activiti?
I have been working on building a DNN module in VS 2010 under DNN 7.0.3. My module has a few controls, a web service, and some jQuery/Ajax calls to the web service. I am working in Windows 7 with IIS 7. Everything was fine until I upgraded to VS 2012. After that, I was getting 500 errors for all the files I am loading into my control, i.e. javascript files, css files, and even images (never saw a 500 error on an image before!). I tried rolling back my project to before I loaded it into VS 2012, but that didn't help. I found this article: Setting up separate ASP.NET app with DotNetNuke
and implemented the suggestion in answer 2 (adding location... to the web config file). That fixed most of the problems, but I am still getting 500 errors for 2 HttpHandlers I built (which just spit out some javascript) and for any calls to my web service. The error I am getting now is:
Parser Error. An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
It kind of looks like it can't find the codebehind for these files. That makes some sense, since that was basically the problem it was having with all the files before I added the tag to the web.config.
I tried a clean install of DNN 7.0.6 and just installed my module from the package that was created earlier, but still the same errors. Since I haven't made any change to my code since it was last working, I am pretty sure the problem has something to do with changes the VS 2012 install made to my machine but I have no idea what. Please help!!!
Thank you :-)
Check to see if you have a VIRTUAL DIRECTORY or Application on the DesktopModules folder, or on the Module's folder in there, sometimes that happens in VS.
Also make sure there is NOT a web.config file in the MODULE folder.