getting error while creating anypoint connector using MuleSoft's AnyPoint Devkit - apache

I am creating an anypoint connector for oracle's sales cloud using soap services but while creating the connector I am getting the error.
This is my wsdl file
https://cagc-test.crm.us1.oraclecloud.com/foundationParties/LocationService?WSDL
i did the following steps
1)creating the anypoint connector using anypoint studio.
2)choose the SOAP and provided the above wsdl url.
after clicking finish,followings error and warnings are displayed on console.
log4j:WARN No appenders could be found for logger
(org.apache.cxf.common.logging.LogUtils).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig
for more info.
org.apache.cxf.tools.common.ToolException: org.w3c.dom.DOMException:
NAMESPACE_ERR: An attempt is made to create or change an object in a
way which is incorrect with regard to namespaces.
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute
(WSDLToJavaContainer.java:294)
at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool
(ToolRunner.java:103)
at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
at org.mule.devkit.generation.wsdl.WsdlConnectorGenerator.
generateJavaCode(WsdlC onnectorGenerator.java:161)
at
org.mule.devkit.generation.wsdl.WsdlConnectorGenerator.initialize
(WsdlConnectorGenerator.java:84)
at org.mule.devkit.generation.core.ConnectorGenerator.execute
(ConnectorGenerator.java:119)
at org.mule.tools.devkit.ConnectorGeneratorMavenPlugin.execute
(ConnectorGeneratorMavenPlugin.java:108)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.
LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder
.buildProject
(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter
.singleThreadedBuild
(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:352)
Caused by: org.w3c.dom.DOMException: NAMESPACE_ERR:
An attempt is made to create or change an object in a way
which is incorrect with regard to namespaces.
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl
.checkDOMNSErr
(CoreDocumentImpl.java:2530)
at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName
(AttrNSImpl.java:117)
at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.
<init> (AttrNSImpl.java:78)
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl
.createAttributeNS(CoreDocumentImpl.java:2142)
at com.sun.org.apache.xerces.internal.dom.ElementImpl
.setAttributeNS
(ElementImpl.java:659)
at org.apache.ws.commons.schema.XmlSchemaSerializer.serializeAttribute
(XmlSchemaSerializer.java:470)
at org.apache.ws.commons.schema.XmlSchemaSerializer.setupAttr
(XmlSchemaSerializer.java:2201)
at org.apache.ws.commons.schema.XmlSchemaSerializer
.serializeComplexType
(XmlSchemaSerializer.java:938)
at org.apache.ws.commons.schema.XmlSchemaSerializer
.serializeSchemaChild
(XmlSchemaSerializer.java:2400)
at org.apache.ws.commons.schema.XmlSchemaSerializer
.serializeSchemaElement
(XmlSchemaSerializer.java:1659)
at org.apache.ws.commons.schema.XmlSchemaSerializer
.serializeSchema
(XmlSchemaSerializer.java:132)
at org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBDataBinding
.addSchemas
(JAXBDataBinding.java:639)
at org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBDataBinding
.initialize
(JAXBDataBinding.java:439)
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.generateTypes
(WSDLToJavaContainer.java:591)
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl
(WSDLToJavaContainer.java:243)
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute
(WSDLToJavaContainer.java:138)
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute
(WSDLToJavaContainer.java:286)
... 28 more
Jan 19, 2015 11:43:39 AM
org.mule.devkit.generation.core.ConnectorGenerator execute
WARNING: icons/temp-connector-24x16.png (Permission denied)
[INFO] ---------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ---------------------------------------------------------------
[INFO] Total time: 3:16.671s
[INFO] Finished at: Mon Jan 19 11:43:39 IST 2015
[INFO] Final Memory: 23M/156M
[INFO] ---------------------------------------------------------------
[ERROR] Failed to execute goal
org.mule.tools.devkit:connector- generator-wsdl2connector
-maven-plugin:1.0.3:connector-generator (default)
on project temp-connector:
Execution default of goal org.mule.tools.devkit
:connector-generator-wsdl2connector
-maven-plugin:1.0.3:connector-generator failed. NullPointerException - > [Help 1]

It seems that the issue here is that the wsdl is not compatible with the wsdl2java tool used in devkit. For a more detailed answer please check http://forum.mulesoft.org/mulesoft/topics/error-while-creating-oracle-sales-cloud-connector-using-mule-soft

Devkit 3.7.0 has now a new feature called SOAP Connect, you can create a fully functional connector directly from a WDSL file.
Take a look:
https://www.mulesoft.com/webinars/api/soap-connect

Related

Cannot deploy Java Adapter on IBM MobileFirst Platform 8.0

We have a java adapter that we are trying to deploy in IBM BFP 8.0. See error stack trace below:
[ERROR] logger.changeStateDeploymentException: FWLSE0321: State change failure. Caused by: java.lang.RuntimeException: User code thrown exception: java.lang.NoSuchMethodError: org/apache/http/impl/conn/CPool.setValidateAfterInactivity(I)V at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:181) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:163) at org.apache.http.impl.client.HttpClientBuilder.build(HttpClientBuilder.java:973) at org.apache.http.impl.client.HttpClients.createDefault(HttpClients.java:56) at com.mypackage.adapter.XYZJavaAdapterResource.init(XYZJavaAdapterResource.java:52) at com.mypackage.adapter.XYZJavaAdapterApplication.init(XYZJavaAdapterApplication.java:21) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.531 s
[INFO] Finished at: 2018-10-05T18:28:03+08:00
[INFO] Final Memory: 10M/204M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.ibm.mfp:adapter-maven-plugin:8.0.2018082311:deploy (default-cli) on project com.mypackage.XYZJavaAdapter: Unexpected response from http://somehost:9080/mfpadmin/management-apis/2.0/runtimes/mfp/adapters -> [Help 1]
MFP version:
Name: IBM MobileFirst Platform Server
Installation directory: /opt/IBM/MFPDEVENV/MobileFirst_Platform_Server
Translations: English (en)
Architecture: 64-bit
[Package]
Name: IBM® MobileFirst Platform Server (com.ibm.mobilefirst.foundation.server)
Version: 8.0.0.20170220_1811 (8.0.0.20170220_1811)
CLI VERSION:
MobileFirst Platform Foundation Command Line Interface (CLI): 8.0.0-2018040312
MFP console log: see below
Caused by: java.lang.RuntimeException: User code thrown exception: java.lang.NoSuchMethodError: org/apache/http/impl/conn/CPool.setValidateAfterInactivity(I)V
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:181)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:163)
at org.apache.http.impl.client.HttpClientBuilder.build(HttpClientBuilder.java:973)
at org.apache.http.impl.client.HttpClients.createDefault(HttpClients.java:56)
[10/26/18 8:36:24:686 HKT] 00013f2d .worklight.admin.configservice.datastore.ConfigServiceClient E Unable to delete configuration with id ADAPTER_CONTENT due to exception FWLSE3208E: An invalid status code "404" was returned. The response content is "{"reason":"configuration_not_found","details":"CNFSRVE115: configuration with id 'ADAPTER_CONTENT' for schema 'mfp_default_schema' with version '1.0' not found"}"
Can anyone help us on how to solve this issue?
Thanks in advance

Apache usergrid tomcat error

I am trying to deploy apache usergrid stack on my localhost. I placed ROOT.war in to /vat/lib/tomcat7/webapps. After restart tomcat when I access http://localhost:8080 then I get nothing in response. When I checked the logs of tomcat, I get following error in localhost log.
Mar 19, 2016 5:51:10 AM org.apache.catalina.core.ApplicationContext log
INFO: No Spring WebApplicationInitializer types detected on classpath
Mar 19, 2016 5:51:10 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class org.apache.usergrid.rest.ShutdownListener
java.lang.UnsupportedClassVersionError: org/apache/usergrid/rest/ShutdownListener : Unsupported major.minor version 52.0 (unable to load class org.apache.usergrid.rest.ShutdownListener)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2948)
at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1208)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1688)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:529)
at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:511)
at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:139)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4888)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5467)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
Mar 19, 2016 5:51:10 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
If anyone has the solution please help.
The UnsupportedClassVersionError exception usually means that you are trying to run some Java code that is compiled for a newer version of Java, on an older version of Java.
Usergrid 2 requires Java 8 so make sure that you are using a Java 8 JDK.
See the Usergrid Deployment Guide for requirements and instructions:
https://usergrid.apache.org/docs/installation/deployment-guide.html

ClassNotFoundException when using the Mule Amazon SQS connector

I'm using the Amazon SQS connector in my Mule project. When I updated it from the 2.5.5 to the 3.0.0 version according to the user guide and set the DEBUG logging level for the com.amazonaws package I noticed the following error right after project starts:
DEBUG 2015-07-20 15:15:56,927 [Receiving Thread] com.amazonaws.1.9.39.shade.jmx.spi.SdkMBeanRegistry: Failed to load the JMX implementation module - JMX is disabled
java.lang.ClassNotFoundException: com.amazonaws.1.9.39.shade.jmx.SdkMBeanRegistrySupport
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at org.mule.module.launcher.FineGrainedControlClassLoader.findClass(FineGrainedControlClassLoader.java:175)
at org.mule.module.launcher.MuleApplicationClassLoader.findClass(MuleApplicationClassLoader.java:134)
at org.mule.module.launcher.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:119)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at com.amazonaws.1.9.39.shade.jmx.spi.SdkMBeanRegistry$Factory.<clinit>(SdkMBeanRegistry.java:46)
at com.amazonaws.1.9.39.shade.metrics.AwsSdkMetrics.registerMetricAdminMBean(AwsSdkMetrics.java:351)
at com.amazonaws.1.9.39.shade.metrics.AwsSdkMetrics.<clinit>(AwsSdkMetrics.java:316)
at com.amazonaws.1.9.39.shade.AmazonWebServiceClient.requestMetricCollector(AmazonWebServiceClient.java:629)
at com.amazonaws.1.9.39.shade.AmazonWebServiceClient.isRMCEnabledAtClientOrSdkLevel(AmazonWebServiceClient.java:570)
at com.amazonaws.1.9.39.shade.AmazonWebServiceClient.isRequestMetricsEnabled(AmazonWebServiceClient.java:562)
at com.amazonaws.1.9.39.shade.AmazonWebServiceClient.createExecutionContext(AmazonWebServiceClient.java:523)
at com.amazonaws.1.9.39.shade.services.sqs.AmazonSQSClient.listQueues(AmazonSQSClient.java:1163)
at com.amazonaws.1.9.39.shade.services.sqs.AmazonSQSClient.listQueues(AmazonSQSClient.java:1501)
at org.mule.modules.sqs.connection.strategy.SQSConnectionManagement.connect(SQSConnectionManagement.java:173)
at org.mule.modules.sqs.connectivity.SQSConnectionManagementSQSConnectorAdapter.connect(SQSConnectionManagementSQSConnectorAdapter.java:21)
at org.mule.modules.sqs.connectivity.SQSConnectionManagementSQSConnectorAdapter.connect(SQSConnectionManagementSQSConnectorAdapter.java:9)
at org.mule.devkit.3.6.1.shade.connection.management.ConnectionManagementConnectorFactory.makeObject(ConnectionManagementConnectorFactory.java:47)
at org.mule.devkit.3.6.1.shade.connection.management.ConnectionManagementConnectorFactory.makeObject(ConnectionManagementConnectorFactory.java:15)
at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220)
at org.mule.modules.sqs.connectivity.SQSConnectorConfigConnectionManagementConnectionManager.acquireConnection(SQSConnectorConfigConnectionManagementConnectionManager.java:407)
at org.mule.modules.sqs.connectivity.SQSConnectorConfigConnectionManagementConnectionManager.acquireConnection(SQSConnectorConfigConnectionManagementConnectionManager.java:55)
at org.mule.devkit.3.6.1.shade.connection.management.ConnectionManagementProcessInterceptor.execute(ConnectionManagementProcessInterceptor.java:47)
at org.mule.devkit.3.6.1.shade.connection.management.ConnectionManagementProcessInterceptor.execute(ConnectionManagementProcessInterceptor.java:19)
at org.mule.security.oauth.process.RetryProcessInterceptor.execute(RetryProcessInterceptor.java:84)
at org.mule.devkit.3.6.1.shade.connection.management.ConnectionManagementProcessTemplate.execute(ConnectionManagementProcessTemplate.java:33)
at org.mule.modules.sqs.sources.ReceiveMessagesMessageSource.run(ReceiveMessagesMessageSource.java:134)
at java.lang.Thread.run(Thread.java:662)
It's true, the mule-module-sqs-3.0.0.jar downloaded by Maven doesn't contain such class. I rebuild the Amazon SQS connector's source code with little changes in the pom.xml: set <minimizeJar>false</minimizeJar> for the maven-shade-plugin. Then the missing class appeared in the jar and I managed to run the project without errors.
Not sure is it a bug or not but don't like the idea to build the connector manually. Will really appreciate if you help me to sort it out. Thanks.

Impossible to generate metamodel in spagoBI studio with hive(CDH5|CDH4)

While creating a JDBC connection between spagoBI studio and hive(CDH5/CDH4),This is my log :-
eclipse.buildId=unknown
java.version=1.7.0_45
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64 -consoleLog
This is a continuation of log file /home/cloudera/SpagoBIStudio_4.2.0_linux64/workspace/.metadata/.bak_0.log
Created Time: 2014-06-30 01:38:31.422
Error
Mon Jun 30 02:51:46 PDT 2014
Impossible to generate metamodel
java.lang.RuntimeException: Impossible to initialize the model
at it.eng.spagobi.meta.editor.multi.wizards.SpagoBIModelEditorWizard.createModel(SpagoBIModelEditorWizard.java:241)
at it.eng.spagobi.meta.editor.multi.wizards.SpagoBIModelEditorWizard.performFinish(SpagoBIModelEditorWizard.java:217)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at it.eng.spagobi.studio.core.views.actionProvider.ResourceNavigatorActionProvider$13.run(ResourceNavigatorActionProvider.java:411)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: java.lang.RuntimeException: Impossible to initialize the physical model
at it.eng.spagobi.meta.editor.multi.wizards.SpagoBIModelEditorWizard.createPhysicalModel(SpagoBIModelEditorWizard.java:340)
at it.eng.spagobi.meta.editor.multi.wizards.SpagoBIModelEditorWizard.createModel(SpagoBIModelEditorWizard.java:237)
... 41 more
Caused by: java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at it.eng.spagobi.meta.editor.multi.wizards.SpagoBIModelEditorWizard.createPhysicalModel(SpagoBIModelEditorWizard.java:295)
... 42 more
Caused by: java.lang.RuntimeException: Impossible to initialize physical model
at it.eng.spagobi.meta.initializer.PhysicalModelInitializer.initialize(PhysicalModelInitializer.java:121)
at it.eng.spagobi.meta.editor.multi.wizards.SpagoBIModelEditorWizard$1.run(SpagoBIModelEditorWizard.java:321)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.sql.SQLException: Method not supported
at org.apache.hive.jdbc.HiveDatabaseMetaData.getIdentifierQuoteString(HiveDatabaseMetaData.java:342)
at it.eng.spagobi.meta.initializer.PhysicalModelInitializer.initialize(PhysicalModelInitializer.java:112)
... 2 more
some of the related questions hive methos not supported ,"java.sql.SQLException: Method not supported which says
Your original error results from using Cloudera's Hive driver which does not implement many JDBC API methods that PDI needs to function properly. That's why we have our own version of the hive driver in the cdh4 folder (called hive-0.7.0-pentaho-1.0.2 or something like that). Simply put, there should be no JARs copied from your cluster to your PDI client, the cdh4 folder already contains the correct versions of all necessary JARs.
but I didnt find any spagoBI hive driver for CDH5/CDH4.I am able to connect to hive but while accessing table getting above error in studio ,I am able to access the table on spagoBI server.any help,thanks.
You have to use Cloudera's .jar files in order to be able to connect to CDH. Have a look here and put all of the .jar files in the CLASSPATH. If running SpagoBI put it in /lib folder of the SpagoBI (Tomcat) server.

Enunciate not able to assemble a jersey based REST API to upload a file: No more than one JAX-RS entity parameter is allowed

I have a resource like this. Enunciate has problem documenting this resource: "No more than one JAX-RS entity parameter is allowed (all other parameters must be annotated with one of the JAX-RS resource parameter annotations)".
#POST
#Path("{appId}/versions/{id}/upload")
#Consumes(MediaType.MULTIPART_FORM_DATA)
public Response upload(#PathParam("appId") Long appId,
#PathParam("id") Long id,
#FormDataParam("file") InputStream uploadedInputStream,
#FormDataParam("file") FormDataContentDisposition fileDetail)
throws Exception;
I found a similar issue reported
http://markmail.org/message/vgvi3cljo3a2f6eh
http://jira.codehaus.org/browse/ENUNCIATE-537
and this was fixed in version 1.23.
I'm using the latest version 1.26.2 but still seeing this error.
When I annotate with org.codehaus.enunciate.XmlTransient I'm able to avoid this error, but this removes documentation for the whole resource (all methods).
Any help would be great.
Maven Error stack:
[WARNING] Validation result has errors.
error: [core] AppResource.upload: No more than one JAX-RS entity parameter is allowed (all other parameters must be annotated with one of the JAX-RS resource parameter annotations).
1 error
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.640s
[INFO] Finished at: Tue May 28 14:48:18 IST 2013
[INFO] Final Memory: 20M/50M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.enunciate:maven-enunciate-plugin:1.26.2:assemble (default) on project crashreport-ws: Problem assembling the enunciate app. org.codehaus.enunciate.apt.ModelValidationException: There were validation errors -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.enunciate:maven-enunciate-plugin:1.26.2:assemble (default) on project crashreport-ws: Problem assembling the enunciate app.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Problem assembling the enunciate app.
at org.codehaus.enunciate.AssembleMojo.execute(AssembleMojo.java:75)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
I'm not getting the same error. Maybe you could try using Enunciate 1.27?
Updating...
New schema location is: http://enunciate.webcohesion.com/schemas/enunciate-1.27.xsd
Regards.