Forum Replies Created
-
AuthorPosts
-
I notice IWObjektImport is the class name, what is the method name you wish to call?
Also does IWObjektImport have a default constructor?
You class library should look something like this:
namespace IWImportAssembly
{
public class IWObjektImport
{
public static string SomeMethod(string p1, string p2, string p3, string p4)
{
}
}
}And Your xpath should be:
<xsl:variable name=”var:v1″ select=”ScriptNS3:SomeMethod($objektart_nr, $grundst_typ, $sonstige_typ, $isWAZ)” />August 19, 2010 at 4:53 AM in reply to: Sending Html mail with embedded image via the smtp adapter #25678Hi, thank you for your reply,
I have already found this link, but unfortunately, it doesn’t help me because here the picture to embed is a second message part.
In my case, pictures are in the html body (referenced by url), so I think that “multipart/related” is not helpful for me.but I’m maybe mistaken
Hi Greg!
I am referencing this assembly in my BizTalk project. (it is in the GAC). Now My Extension XML looks like this:
<ExtensionObjects>
<ExtensionObject Namespace=”http://schemas.microsoft.com/BizTalk/2003/ScriptNS0” AssemblyName=”IWImportAssembly, Version=1.0.3883.17877, Culture=neutral, PublicKeyToken=351babac2ee00600″ ClassName=”IWImportAssembly.Objektart” />
<ExtensionObject Namespace=”http://schemas.microsoft.com/BizTalk/2003/ScriptNS1” AssemblyName=”IWImportAssembly, Version=1.0.3883.17877, Culture=neutral, PublicKeyToken=351babac2ee00600″ ClassName=”IWImportAssembly.ISO_LAND” />
<ExtensionObject Namespace=”http://schemas.microsoft.com/BizTalk/2003/ScriptNS2” AssemblyName=”IWImportAssembly, Version=1.0.3883.17877, Culture=neutral, PublicKeyToken=351babac2ee00600″ ClassName=”IWImportAssembly.GeoDaten” />
<ExtensionObject Namespace=”http://schemas.microsoft.com/BizTalk/2003/ScriptNS3” AssemblyName=”IWImportAssembly, Version=1.0.3883.17877, Culture=neutral, PublicKeyToken=351babac2ee00600″ ClassName=”IWImportAssembly.IWObjektImport” />
</ExtensionObjects>My Call Template script functoid:
<xsl:template name=”Immo_Art” xmlns:ScriptNS3=http://schemas.microsoft.com/BizTalk/2003/ScriptNS3>
<xsl:param name=”isWAZ” select=”WAZ”/>
<xsl:param name=”grundst_typ” select=”grundst_Typ”/>
<xsl:param name=”sonstige_typ” select=”sonstige_Typ”/>
<xsl:variable name=”objektart_nr” select=”/Immobilie/objektkategorie/objektart/child::node()[1]”/>
<xsl:element name=”Immobilienart”>
<xsl:variable name=”var:v1″ select=”ScriptNS3:IWImportObjekt($objektart_nr, $grundst_typ, $sonstige_typ, $isWAZ)” />
<xsl:value-of select=”$var:v1″ />
</xsl:element>
</xsl:template>And this is the new error message I get:
‘IWImportObjekt()’ is an unknown XSLT function.
I feel it. I am coming closer to the solution 😉
P.S.: When I remove the referenced assembly in my biztalk project I get this:
Cannot find the script or external object that implements prefix ‘ScriptNS3’.
August 18, 2010 at 12:23 PM in reply to: Consume one WCF service for multiple Biztalk application #25674Hi,
Create port with different name. You can’t have two ports with same name.
August 18, 2010 at 12:21 PM in reply to: Use "add generated items" error – WCF Service Consuming Wizard #25673Hi,
1. I would check at first – if I can consume that WCF from regular code (Console Application is easiest).
2. If good – than something is wrong with generating objects in BizTalk.
3. Try not consuming mex, but the second option (the upper radio button – don”t recall it’s name). If good – this would generate schemas + bindings for you.
If you get error on the beginning, even trying to consume from console application – something is wrong in your WCF., Else – something wrong in your BTS.
Is WCF written? Or it’s some kind of published orchestration/schema?
If written – check that your methods and all stuff you need access to, is public.
🙂
August 18, 2010 at 12:16 PM in reply to: Sending Html mail with embedded image via the smtp adapter #25672Hi,
Have a look a the following blog and see if the steps taken to embed images in an email sent through SMTP adapter in BizTalk help you achieve what you need:
http://blogdoc.biztalk247.com/article.aspx?page=ca1cf68a-ab23-4a1d-ad4c-61011bba83cb
Daniel.
August 18, 2010 at 9:25 AM in reply to: Use "add generated items" error – WCF Service Consuming Wizard #25670Hi Wolfgang,
Check your <xsd:schema> nodes in the WSDL file of your WCF service and make sure that the attribute targetNamespace is defined for them.
Best,
Daniel.
Hi Yonathan.
You’re right I call a assembly within an orchestration now. I tried to programm it in Expression Shaps, Looping shapes and so on and then I have to use Atomic ….
Just call a assembly is by far much more easier – at least for me.
cheers
Wolfgang
Sorry my last post was completely wrong. You only need to specify the assembly name:
<ExtensionObject Namespace=”http://immowelt.de/Import/ObjektImport” AssemblyName=”XSLT_External_Assembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c5b7d5a4522ce583″ ClassName=”IWImportAssembly.IWObjektImport”/>
Is your XSLT_External_Assembly in the GAC?
Are you referencing this assembly in your BizTalk project – you should not. If you are remove the reference, add the assmbly to the GAC and restart Visual Studio.all exception handling can be done in the scope!! even schema exception handling also!!
Hey Greg, thanks for your help!!
But I still get the same error message:
Cannot find the script or external object that implements prefix ‘IWObjektImport’.
It`s like he doesnt recognize the custoum extension xml file:
<ExtensionObjects>
<ExtensionObject Namespace=”http://immowelt.de/Import/ObjektImport” AssemblyName=”IWImportAssembly, XSLT_External_Assembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c5b7d5a4522ce583″ ClassName=”IWImportAssembly.IWObjektImport”/>
</ExtensionObjects>I tried everything you guys told me to do. I`m stuck.
You are missing the a bit of the assembly name:
It should look something like this:: IWImportAssembly, XSLT_External_Assembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c5b7d5a4522ce583Note: the namespace used in the previous post was just an example, each assembly in the extensions xml file needs to have it’s own namespace. I would suggest using a better namespace that reflects your environment. The urn style is just a personal preference, the namespace can be any unique string e.g. urn:yourcompany.com:utilities:objektimport or http://yourcompany.com/Utilities/ObjektImport
Now my xslt call template scripting functoid looks like this:
<xsl:template name=”Immo_Art” xmlns:IWObjektImport=”urn:external:assembly:functions”>
<xsl:param name=”isWAZ” select=”WAZ”/>
<xsl:param name=”grundst_typ” select=”grundst_Typ”/>
<xsl:param name=”sonstige_typ” select=”sonstige_Typ”/>
<xsl:variable name=”objektart_nr” select=”/Immobilie/objektkategorie/objektart/child::node()[1]”/>
<xsl:element name=”Immobilienart”>
<xsl:variable name=”var:v1″ select=”IWObjektImport:IWImportObjekt($objektart_nr, $grundst_typ, $sonstige_typ, $isWAZ)” />
<xsl:value-of select=”$var:v1″ />
</xsl:element>
</xsl:template>And my Custom Extension XML file like this:
<ExtensionObjects>
<ExtensionObject Namespace=”urn:external:assembly:functions” AssemblyName=”XSLT_External_Assembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c5b7d5a4522ce583″ ClassName=”IWImportAssembly.IWObjektImport”/>
</ExtensionObjects>But the compiler still cant find the prefix:
Cannot find the script or external object that implements prefix ‘IWObjektImport’.
Argh!!!
And I dont use an external custom xslt file.
Can you explain what you wish to do in more detail?
Any one with better solution??
-
AuthorPosts