I am getting the below error while accessing the project :
Unable to create new element for " path"
ccweb: Error: Config spec indicates that checkouts are not allowed for element "path"
Provided you did solve your Database timed-out issue in Clearcase UCM, that error message is not surprising.
The technote "About non-UCM and UCM views" mentions:
Working in a UCM view will return an error if accessing a VOB or component that is not associated with its project:
cleartool: Error: Config spec indicates that checkouts are not allowed for element "<some element>".
Views can only be used to work on a single stream, under a specific project and in modifiable components that are associated with that project.
New versions created by a checkin are catalogued in an activity
Metadata is applied automatically to checked in versions
Operations, such as cleartool mkactivity, are recorded at the project level
If you are trying to add to source control a file in a path which is not part of a writable UCM component declared on the stream which is referenced by your UCM views, you would get that message.
Related
I am trying to move a newly uploaded file in sharepoint using power automate. I have used two connectors 1) When a file is created in a folder 2) Move File. I have used file identifier as dynamic content in the move file connector. When i tried i got this error.
Error Message - Missing or mismatched field definition on the destination list for source field 'RequestType' type 'Text'. Source site template id 'GroupWebTemplateID', target site template id 'GroupWebTemplateID'. Total blocked root objects in this operation is 1.
Am i using a wrong connector or wrong dynamic content
I'm trying to do a simple Proxy Service using the Developer Studio tool from the open-source SOA middleware provider WSO2.
When I drag into the flow a Switch Mediator in the graphical view there is no problem but when I changed to the text view, I'm facing the following error:
Cannot update source view. The following error(s) have been detected
Reason: XPathFactoty#newInstance() failed to create an XPathFactoty for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactotyConfigurationException: javax.xml.xpath.XPathFactotyConfigurationException: java.util.ServiceConfigurationError javax.xml.xpath.XPathFactoty: bundleresource://1013.fwk317983781:21/META-INF/services/javax.xml.xpath.XPathFa ctory:2: Illegal configuration-file syntax
And the XML is empty, so I can't to add any Switch Mediator and get it working with the WSO2 DS.
This is happening with the 3.5.0 and 3.6.0 version of the tool, and I even try one of the sample in the website but with the same result.
Anyone have any reason why this error is happening?
Thank you!
Each switch element needs to have an attribute called 'source'. This is the Xpath attribute that is checked against the criteria in each case. To add the 'source' attribute, type the Xpath and then click 'update' or 'save'. With that required attribute, a valid xml configuration file may be created and viewed as text.
Here is more documentation on the switch mediator: https://docs.wso2.org/display/ESB481/Switch+Mediator
So I've added a custom field to a Salesforce Object and need to update the Web Reference and proxy classes created from said web reference. What I'm doing is replacing the existing WSDL file in the Web Reference folder with the new Enterprise WSDL file. I then right-click the Web Reference instance (in this case, SFDC) and select "Update Web Reference" however nothing happens. In fact, the updated WSDL file reverts back to its original state and the proxy class file does change at all.
Am I missing a step here?
I actually accomplished this by deleting the web reference, than creating a new one, which added the new field.
I am using DotCMIS with no problem to connect to Alfresco and FileNet.
I registered for an IBM Connections account, added a few files via the web interface, and tried to connect to its CMIS endpoint https://greenhouse.lotus.com/files/basic/cmis/my/servicedoc
GetRepositories on this URL gives one repository, which in turn contain the two folders below:
My Files
My Folders
But when I run GetObjectByPath("/My Files") in the same repository, I get:
DotCMIS.Exceptions.CmisObjectNotFoundException was unhandled
Message=Not Found
Source=DotCMIS
ErrorContent=<?xml version="1.0" encoding="UTF-8"?><lcmis:error xmlns:lcmis="http://www.ibm.com/xmlns/prod/sn/cmis"><lcmis:code>objectNotFound</lcmis:code><lcmis:message>EJPVJ9023E: Unable to find object at path /My Files</lcmis:message><lcmis:userAction></lcmis:userAction></lcmis:error>
What does IBM Connections say Unable to find object at path /My Files despite My Files being a folder at the root of the repository?
The cmis:name property ("My Files", "My Folers") is localized. A non-English user would get different cmis:name property values for these two objects.
To fetch children from these resources, you need to build the path using the cmis:path property returned on each object or construct the path relative to its parent using the cmisra:pathSegment.
For example, the cmis:object for the resource labeled "My Files" in your scenario has the following:
<cmis:propertyString propertyDefinitionId="cmis:path"
localName="cmis_path" displayName="Path" queryName="cmis:path">
<cmis:value>/files</cmis:value>
</cmis:propertyString>
So to actually fetch the user's files, the path to call is the following:
GetObjectByPath("/files")
And to fetch the user's folders, the path to call is the following:
GetObjectByPath("/collections")
The net is to ensure you build paths using the cmisra:pathSegment or the cmis:path property, and not the cmis:name as this may not be valid in all scenarios (i.e. if the repository has same name siblings, etc.).
I have configured ClearCase plugin in Hudson .
I created a project , by giving new hudson_view_name as view name for the Hudson project and provided config spec.
I identified in my view storage directory it is creating multiple folders related to the view. like ,
hudson_view_name.vws
hudson_view_name.1.vws
hudson_view_name.2.vws
, but when I see my "cleartool lsview" command only hudson_view_name.vws is visible not the hudson_view_name.x.vws.
When I do the following command:
cleartool rmview -force -tag hudson_view_name
hudson_view_name.2.vws is being removed but hudson_view_name.vws and
hudson_view_name.1.vws remains , How can I remove those two as well.
Another question is why Hudson created many view storage locations like viewname.x.vws?
viewname.x.vws is the naming convention for view storage for views whose tag is reused.
That is the case when the view is not deleted on the client side, but only on the view server side (i.e "cleartool unregister", followed by a "cleartool rmtag"):
The view is essentially gone for ClearCase, but its client-side view storage (which is now useless) remains.
(That is what Trent Fisher says in his comment of the Hudson ClearCase Plugin page)
In this scenario, you can re-create a view by reusing the former view tag, but, since a corresponding view storage still exists, a new storage.x.vws is created.
I would really-really recommend selecting the option "use existing dynamic view" to avoid that:
(but contrary to this picture, I would not select the "Do not reset the config spec").