Skip to main content
M
mark_stallard1-Visitor
1-Visitor
December 22, 2010
Question

Listing Windchill Workspace Models in JLink & Pro/Toolkit

  • December 22, 2010
  • 3 replies
  • 1240 views
Hi Everyone -

Does anyone know how a JLink method for listing models in the current
workspace? Failing that, does anyone know of a similar function in
the Pro/Toolkit library? It may be hard to believe, but I don't think
either API will help me find the names of .prt/.asm/.drw files in a
workspace, even though both APIs support Windchill checkin & checkout.

I have a JLink application which may require this functionality soon.
This application already uses a task-based Pro/Toolkit DLL, so I can
use either Java or C to do this.

I'm already contemplating a work-around for this, but I'd rather use
the API as designed.

I'm currently using Pro/Engineer Wildfire 3, by the way.

|+| M a r k |+|

Mark Stallard
Rapid Response Development
information Solutions
Integrated Defense Systems
Raytheon Company



(business)
+1.978.436.6016
(cell)
+1.617.331.5443
(tie line)
239.6016
-

880 Technology Drive
Billerica, MA 01821
www.raytheon.com


This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this
message in error, please so advise the sender by reply e-mail and delete
this message. Thank you for your cooperation.



This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

3 replies

J
jkent1-Visitor
1-Visitor
December 22, 2010
Take a look at ListFiles method. I know this works in WF 4 but not sure
about WF 3.



Here is what I use in one of my applications.

stringseq files = proSession.ListFiles(filter,
FileListOpt.FILE_LIST_LATEST_INST, "wtws://" + server.GetAlias() + "/" +
workSpaceName + "/");


P
pwilliams-313-Aquamarine
13-Aquamarine
December 22, 2010
If it was a Pro/INTRALINK workspace then I would of course advise you to
create a utility exe that performed the desired workspace operations. I
never understood why accessing the workspace was not implemented in the
Pro/E API since native Pro/E does it all the time. It just makes things
more difficult. Hmm....could be a good topic for a TC discussion.

PATRICK S WILLIAMS
Information Technology
Mechanical Engr Solutions
Missile Systems
Raytheon Company

+1 520.545.6995 (office)
+1 520.446.0244 (pager)
+1 520.545.6399 (fax)
-

6221 S Palo Verde Rd
Tucson, AZ 85706-5093 USA
www.raytheon.com

Follow Raytheon On




This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this
message in error, please so advise the sender by reply e-mail and delete
this message. Thank you for your cooperation.


B
bfrandsen10-Marble
10-Marble
December 23, 2010
How about ListModels method.
The API doc for WF4 explain this method as: Retrieves the list of objects
in the Pro/ENGINEER workspace.
I do not know if this is available in WF3.

/Bjarne



Joe Kent <jkent@rdleverage.com>
22-12-2010 18:04
Please respond to
Joe Kent <jkent@rdleverage.com>


To
Mark R Stallard <->
<->
cc

Subject
[proecus] - RE: Listing Windchill Workspace Models in JLink & Pro/Toolkit






Take a look at ListFiles method. I know this works in WF 4 but not sure
about WF 3.

Here is what I use in one of my applications.
stringseq files = proSession.ListFiles(filter,
FileListOpt.FILE_LIST_LATEST_INST, "wtws://" + server.GetAlias() + "/" +
workSpaceName + "/");
Terms & ConditionsAccessibility statement