Problem when trying to publish after adding webreference

Problem when trying to publish after adding webreference

  
Hi,

I'm having a problem when trying to use a webreference. The problem occurs only when im trying to publish the oml. I can add the reference successfuly and use it on the service studio, i verify the oml and when im trying to publish it i get this:

Invalid Web Reference: The WSLesadoInfo web reference could not be imported because it is not supported.
[Exception Details:
[1] Invalid Web Reference: The WSLesadoInfo web reference could not be imported because it is not supported.
at #Xk.#Op.Dump(#rl code)
at OutSystems.HubEdition.Compiler.Espace.#yy(ArrayList webreferences)
at OutSystems.HubEdition.Compiler.Espace.Dump()
at #Xk.#Yc.#Nt()
at #Xk.#Yc.#Pt(String[] args)
at #Xk.#Yc.#nf(String[] args)
[2] Id : WSDLFieldNotFound
Type : Error
Message : Invalid Web Reference
Detail : Could not find 'DADOS_XML_BODY_SUBCLAIMDATA_ESTIMATION_BUDGETS_DAT' field.
HelpRef : 2050
ExtraInfo : Exception Details:
[1] Invalid Web Reference: Could not find 'DADOS_XML_BODY_SUBCLAIMDATA_ESTIMATION_BUDGETS_DAT' field.
at #Xk.#Up.#zQ(#rl writer, #5m type, String typeName, String fieldName)
at #Xk.#Sp.#RP(#rl writer)
at #Xk.#Pp.#YP(#rl code)
at #Xk.#Op.Dump(#rl code)
at OutSystems.HubEdition.Compiler.Espace.#yy(ArrayList webreferences)
at OutSystems.HubEdition.Compiler.Espace.Dump()
at #Xk.#Yc.#Nt()
at #Xk.#Yc.#Pt(String[] args)
at #Xk.#Yc.#nf(String[] args)
Submitable : Yes]

I think this is probably a bug because it says:
Detail : Could not find 'DADOS_XML_BODY_SUBCLAIMDATA_ESTIMATION_BUDGETS_DAT' field.

The compiler is only considering the first 50 chars. The name of the field is DADOS_XML_BODY_SUBCLAIMDATA_ESTIMATION_BUDGETS_DATA

Is there a fixed limit of 50 chars on any field name in a given webreference?

Thanks in advance.

Hi João,

 

I suggest you to report this situation to OutSystems support (support@outsystems.com).

 

Also (if possible):

 

 - send the OML file,

 - indicate Service Studio & Platform Server versions you're using.

 

 

Regards,

 

João Portela


weird. I have it now also.

Is there a problem with it, when you create an oml on the community version than trying to publsih it on a "normal" version?
version that works: 5.0.2.6, version it fails: 5.0.2.7

I already posted to support, but any help appreciated.

full error:
Invalid Web Reference

The IAUT1_PROXY_WEBSERVICE web reference could not be imported because it is not supported.

Exception Details:
[1] Invalid Web Reference: The IAUT1_PROXY_WEBSERVICE web reference could not be imported because it is not supported.
at #JL.#IL.DumpRecordType(#KM recordType, TextWriter code)
   at OutSystems.HubEdition.Compiler.ESpace.DumpStructuresCSharp()
   at OutSystems.HubEdition.Compiler.ESpace.DumpStructures()
   at OutSystems.HubEdition.Compiler.ESpace.Dump()
   at OutSystems.HubEdition.Compiler.Compiler.MainExec(Byte[] fullOmlBytes, Byte[] partialOmlBytes)
   at OutSystems.HubEdition.Compiler.Compiler.RealMain(Byte[] fullOmlBytes, Byte[] partialOmlBytes, String targetDirectory, String[] args)
   at OutSystems.HubEdition.Compiler.CompilerWrapper.#ebb(Byte[] fullOml, Byte[] partialOml, String outputPath, String[] args, Dictionary`2& extraCompilerOutputs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
   at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Lifetime.LeaseSink.SyncProcessMessage(IMessage msg)
   at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(Object[] args)
   at System.Threading.Thread.CompleteCrossContextCallback(InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Channels.ChannelServices.SyncDispatchMessage(IMessage msg)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatchCallback(Object[] args)
   at System.Threading.Thread.CompleteCrossContextCallback(InternalCrossContextDelegate ftnToCall, Object[] args)
[2] Id : ClassNotFound
Type : Error
Message : Internal Error
Detail : Could not find Class 'Iaut1ProxyWebserviceExportRowOutSubmenuIaut1Authorization'.
HelpRef : 2063
ExtraInfo : Exception Details:
[1] Internal Error: Could not find Class 'Iaut1ProxyWebserviceExportRowOutSubmenuIaut1Authorization'.
at #JL.#OL.#sAb(TextWriter writer)
   at #JL.#KL.#AAb(TextWriter code)
   at #JL.#IL.DumpRecordType(#KM recordType, TextWriter code)
   at OutSystems.HubEdition.Compiler.ESpace.DumpStructuresCSharp()
   at OutSystems.HubEdition.Compiler.ESpace.DumpStructures()
   at OutSystems.HubEdition.Compiler.ESpace.Dump()
   at OutSystems.HubEdition.Compiler.Compiler.MainExec(Byte[] fullOmlBytes, Byte[] partialOmlBytes)
   at OutSystems.HubEdition.Compiler.Compiler.RealMain(Byte[] fullOmlBytes, Byte[] partialOmlBytes, String targetDirectory, String[] args)
   at OutSystems.HubEdition.Compiler.CompilerWrapper.#ebb(Byte[] fullOml, Byte[] partialOml, String outputPath, String[] args, Dictionary`2& extraCompilerOutputs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
   at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Lifetime.LeaseSink.SyncProcessMessage(IMessage msg)
   at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(Object[] args)
   at System.Threading.Thread.CompleteCrossContextCallback(InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Channels.ChannelServices.SyncDispatchMessage(IMessage msg)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatchCallback(Object[] args)
   at System.Threading.Thread.CompleteCrossContextCallback(InternalCrossContextDelegate ftnToCall, Object[] args)
Submitable : Yes



Hi Joost,

Could you try the following: clone your espace and pbulish it. If the error is gone then it's probably a compilation problem that was already solved in Platform Version 5.0.2.17, otherwise you really neeed support help.


Regards,
João Portela