Fixes are available
APAR status
Closed as fixed if next.
Error description
If a WSDL file in a monitor model project, or a project referenced by a monitor model project, contains an incorrect import statement (for example, the path specified in the "location" attribute is incorrect), J2EE project generation for the monitor model fails. An exception similar to the following is displayed: Generation failed Path must include project and resource name: /MyWSDLFile.wsdl java.lang.IllegalArgumentException Path must include project and resource name: /MyWSDLFile.wsdl org.eclipse.core.runtime.Assert.isLegal(null:-1) org.eclipse.core.internal.resources.Workspace.newResource(null:- 1) org.eclipse.core.internal.resources.Container.getFile(null:-1) org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandlerIm pl$Workb enchHelper.createPlatformResourceInputStream(null:-1) org.eclipse.emf.ecore.resource.impl.PlatformResourceURIHandlerIm pl.creat eInputStream(null:-1) org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.c reateInp utStream(null:-1) org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.c reateInp utStream(null:-1) org.eclipse.wst.wsdl.internal.impl.ImportImpl.resolve(null:-1) org.eclipse.wst.wsdl.internal.impl.ImportImpl.importDefinitionOr Schema(n ull:-1) org.eclipse.wst.wsdl.internal.impl.DefinitionImpl.getImportedDef initions (null:-1) org.eclipse.wst.wsdl.internal.impl.DefinitionImpl.resolveWSDLEle ment(nul l:-1) org.eclipse.wst.wsdl.internal.impl.DefinitionImpl.resolveWSDLEle ment(nul l:-1) org.eclipse.wst.wsdl.internal.impl.DefinitionImpl.getPortType(nu ll:-1) com.ibm.wbit.bpel.services.partnerlinktype.impl.RolePortTypeImpl .reconci leReferences(null:-1) org.eclipse.wst.wsdl.internal.impl.WSDLElementImpl.reconcileRefe rences(n ull:-1) com.ibm.wbit.bpel.services.partnerlinktype.impl.RoleImpl.reconci leRefere nces(null:-1) org.eclipse.wst.wsdl.internal.impl.WSDLElementImpl.reconcileRefe rences(n ull:-1) com.ibm.wbit.bpel.services.partnerlinktype.impl.PartnerLinkTypeI mpl.reco ncileReferences(null:-1) org.eclipse.wst.wsdl.internal.impl.WSDLElementImpl.reconcileRefe rences(n ull:-1) org.eclipse.wst.wsdl.util.WSDLResourceImpl.handleDefinitionEleme nt(null: -1) org.eclipse.wst.wsdl.util.WSDLResourceImpl.findDefinition(null:- 1) org.eclipse.wst.wsdl.util.WSDLResourceImpl.doLoad(null:-1) org.eclipse.wst.wsdl.util.WSDLResourceImpl.doLoad(null:-1) org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(null:-1) org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(null:-1) org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(n ull:-1) org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHe lper(nul l:-1) org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource( null:-1) com.ibm.wbimonitor.xml.core.indexing.IndexRecorderFactory$WSDLIn dexRecor der.run(null:-1) com.ibm.wbimonitor.xml.core.indexing.IndexResourcesJob.run(null: -1) com.ibm.wbimonitor.xml.core.indexing.IndexAllJob.run(null:-1) com.ibm.wbimonitor.xml.core.search.SearchResourceDependenciesJob .run(nul l:-1) com.ibm.wbimonitor.xml.server.gen.ServerGenerator.copyModelFiles ToEAR(nu ll:-1) com.ibm.wbimonitor.xml.server.gen.ServerGenerator.generateContri bution(n ull:-1) com.ibm.wbimonitor.deploy.base.EarProjectGenerator.callGenerator (null:-1 ) com.ibm.wbimonitor.deploy.base.EarProjectGenerator.access$4(null :-1) com.ibm.wbimonitor.deploy.base.EarProjectGenerator$5.run(null:-1 ) org.eclipse.core.internal.resources.Workspace.run(null:-1) org.eclipse.core.internal.resources.Workspace.run(null:-1) com.ibm.wbimonitor.deploy.base.EarProjectGenerator.callGenerator s(null:- 1) com.ibm.wbimonitor.deploy.base.EarProjectGenerator.run(null:-1) com.ibm.wbimonitor.deploy.editor.wizard.GenerateWizard$GenerateJ ob.run(n ull:-1) org.eclipse.core.internal.jobs.Worker.run(null:-1)
Local fix
Ensure that all import statements in all WSDL files included in the monitor model project or referenced projects are correct.
Problem summary
This problem exists in WebSphere Business Monitor development Version 6.2 and Version 7.0. For Version 6.2 customers, this problem will be resolved in WebSphere Business Monitor development toolkit V6.2 Fix Pack 3 (6.2.0.3). For Version 7.0 customers, this problem will be resolved in WebSphere Business Monitor development toolkit V7.0 Fix Pack 2 (7.0.0.2).
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR35437
Reported component name
WEB BUS MONITOR
Reported component ID
5724M2400
Reported release
620
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-21
Closed date
2010-03-29
Last modified date
2010-03-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R620 PSY
UP
R700 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSRR3","label":"WebSphere Business Monitor"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 March 2010