Borland Customer Service
Thomas Miller
from the web site.
Thanks.
--
Thomas Miller
Chrome Portal Project Manager
CPCUG Programmers SIG Chairperson (formally Delphi)
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork
http://www.bss-software.com
http://programmers.cpcug.org/
http://sourceforge.net/projects/chromeportal/
http://sourceforge.net/projects/uopl/
http://sourceforge.net/projects/dbexpressplus
Thomas Miller
Craig Stuntz [TeamB] wrote:
> Thomas Miller wrote:
>
>> How do I get a hold of someone in customer service?
>
> Depends what sort of service you require. Can you be more specific?
Craig Stuntz [TeamB]
> How do I get a hold of someone in customer service?
Depends what sort of service you require. Can you be more specific?
--
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
Everything You Need to Know About InterBase Character Sets:
http://blogs.teamb.com/craigstuntz/articles/403.aspx
Nick Hodges (Borland/DevCo)
> How do I get a hold of someone in customer service? It wasn't
> obvious from the web site.
>
> Thanks.
http://support.borland.com/index.jspa
--
Nick Hodges
Delphi Product Manager - Borland/DevCo
Read my Blog -- http://blogs.borland.com/nickhodges
Thomas Miller
related to sales, please.
Thanks.
Nick Hodges (Borland/DevCo) wrote:
> Thomas Miller wrote:
>
>> How do I get a hold of someone in customer service? It wasn't
>> obvious from the web site.
>>
>> Thanks.
>
> http://support.borland.com/index.jspa
>
--
Craig Stuntz [TeamB]
> Need to return just purchased BDS 2006
If you haven't opened it, you can return it to the vendor you bought
it from, whoever that is.
If you've opened it, I doubt it's returnable. The license agreement
doesn't list any kind of satisfaction warranty, although there is of
course the trial version for people who aren't sure if they want the
product or not.
TObject
"Thomas Miller" <tmi...@bss-software.com> wrote in message news:4499a8db$1...@newsgroups.borland.com...
> That doesn't seem to have what I am looking for. Customer service
> related to sales, please.
If you paid by credit card the transaction description
often includes a phone number, you could try that.
Just an idea
Thomas Miller
and fight it out. I was so excited to finally get my hands on D2006 and
then the utter disappointment of it unable to handle the web service I
need to consume.
If I can't use THTTPRIO, then D5 will do fine. No need to upgrade.
--
Craig Stuntz [TeamB]
similarly expressed complaints then I don't think returning Delphi will
fix that problem for you. Blaming your tools doesn't solve programming
problems; it only avoids them.
Hint: When you create a web app you have three choices. Examine them
carefully.
--
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
IB 6 versions prior to 6.0.1.6 are pre-release and may corrupt
your DBs! Open Edition users, get 6.0.1.6 from http://mers.com
Tom Corey
> I was so excited to finally get my hands on D2006
> and then the utter disappointment of it unable to handle the web
> service I need to consume.
> If I can't use THTTPRIO, then D5 will do fine. No need to upgrade.
I'm certainly not an expert, but using D2006 Pro I did write two
Windows services using the THTTPRIO component. Both are able to
successfully and automatically query two different web services.
Thomas Miller
services stuff. I am doing it initial as a win app as it is easy to
debug and see what is going on. Once the class is complete, it will be
trivial to implement it in the CGI app.
The problem is that D2006 creates an invalid soap envelope for the
service. I know what a valid one looks like as I use SOAP Scope to test
the web service and see what is going on at a raw level before trying to
program against it. So I can cut a paste a valid envelope from SOAP
Scope. The envelope that Delphi creates if very, very different.
I am not the only user having this problem, so it isn't me.
Any suggestion on how to figure this out so I can use Delphi for this
would be greatly appreciated.
Being able to replace the SOAP envelope with my own would solve the
problem short term so I can work with people with more knowledge of the
inter-workings of HTTPRIO then I. I am on a dead line. The other guy
decided to do it in VS 2005 and call an assembly from Delphi. Then he
plans on porting the whole thing to VS2005 and dumbing Delphi. Not an
option for me, unfortunately. I have to do this in Delphi as part of a
current project.
Suggestions?
Craig Stuntz [TeamB] wrote:
> If this is the thing about CGIs being "almost impossible to debug" and
> similarly expressed complaints then I don't think returning Delphi will
> fix that problem for you. Blaming your tools doesn't solve programming
> problems; it only avoids them.
>
> Hint: When you create a web app you have three choices. Examine them
> carefully.
>
--
Thomas Miller
it as well. But obviously something isn't write as I can use the
service from other products and I am not the only one with the problem.
There are at least two of us having the exact same problem.
We send multiple parameters to the Web Service and it thinks they are
NULL.
--
David Clegg
> The problem is that D2006 creates an invalid soap envelope for the
> service.
Dumb question, but are you ensuring that you're using the correct
encoding for your web service calls? IIRC, by default Delphi Win32 SOAP
clients use RPC encoding, but .NET web services use document/literal
encoding.
You can specify in your client code to explicitly use doc/lit encoding
by using the following line :-
InvRegistry.RegisterInvokeOptions(TypeInfo(IGatewayResultSoap),
ioDocument);
HTH, and apologies if you've already investigated this :-)
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"You've tried and failed. The lesson here is, never try again." - Homer
Simpson
David Clegg
> We send multiple parameters to the Web Service and it thinks they are
> NULL.
That sounds like a symptom I'd expect to see if you had an encoding
mismatch between the web service and client. Check my earlier reply to
you to see if it helps.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"You never know when an old calendar might come in handy! Sure, it's
not 1985 right now, but who knows what tomorrow will bring?" - Homer
Simpson
David Clegg
> I have seen this, but no one really explained what it was doing.
> Should I put this at the top, bottom, last InvRegistry item, doesn't
> matter.
I put it in the initialization section of the unit consuming the web
service.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Trying is the first step towards failure." - Homer Simpson
Thomas Miller
I put this at the top, bottom, last InvRegistry item, doesn't matter.
Thanks!!!!
David Clegg wrote:
> Thomas Miller wrote:
>
>> The problem is that D2006 creates an invalid soap envelope for the
>> service.
>
> Dumb question, but are you ensuring that you're using the correct
> encoding for your web service calls? IIRC, by default Delphi Win32 SOAP
> clients use RPC encoding, but .NET web services use document/literal
> encoding.
>
> You can specify in your client code to explicitly use doc/lit encoding
> by using the following line :-
>
> InvRegistry.RegisterInvokeOptions(TypeInfo(IGatewayResultSoap),
> ioDocument);
>
> HTH, and apologies if you've already investigated this :-)
>
--
Thomas Miller
David Clegg wrote:
> Thomas Miller wrote:
>
>> I have seen this, but no one really explained what it was doing.
>> Should I put this at the top, bottom, last InvRegistry item, doesn't
>> matter.
>
> I put it in the initialization section of the unit consuming the web
> service.
>
--
Thomas Miller
David Clegg wrote:
> Thomas Miller wrote:
>
>> The problem is that D2006 creates an invalid soap envelope for the
>> service.
>
> Dumb question, but are you ensuring that you're using the correct
> encoding for your web service calls? IIRC, by default Delphi Win32 SOAP
> clients use RPC encoding, but .NET web services use document/literal
> encoding.
>
> You can specify in your client code to explicitly use doc/lit encoding
> by using the following line :-
>
> InvRegistry.RegisterInvokeOptions(TypeInfo(IGatewayResultSoap),
> ioDocument);
>
> HTH, and apologies if you've already investigated this :-)
>
--
David Clegg
> Right, just wondering if the order mattered.
As long as you do it before you consume the web service, you should be
OK.
Researching into this a bit further reveals that you may want to change
the registration to the following :-
InvRegistry.RegisterInvokeOptions(TypeInfo(IMySOAPInterface),
ioDocument);
InvRegistry.RegisterInvokeOptions(TypeInfo(IMySOAPInterface),
ioLiteral);
There is an overload which is supposed to let you specify multiple
invoke options (as shown below), but my initial testing using Delphi 6
revealed problems invoking the web service when doing so. Registering
the options in separate calls to RegisterInvokeOptions didn't exhibit
this behavior.
InvRegistry.RegisterInvokeOptions(TypeInfo(IYourWebService),
[ioDocument, ioLiteral]);
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Where's the 'Any' Key?" - Homer Simpson
Thomas Miller
My interface is IAssesementManagement so I want to do
InvRegistry.RegisterInvokeOptions(TypeInfo(IAssesementManagement),
[ioDocument, ioLiteral]);
David Clegg wrote:
> Thomas Miller wrote:
>
>> Right, just wondering if the order mattered.
>
> As long as you do it before you consume the web service, you should be
> OK.
>
> Researching into this a bit further reveals that you may want to change
> the registration to the following :-
>
> InvRegistry.RegisterInvokeOptions(TypeInfo(IMySOAPInterface),
> ioDocument);
> InvRegistry.RegisterInvokeOptions(TypeInfo(IMySOAPInterface),
> ioLiteral);
>
> There is an overload which is supposed to let you specify multiple
> invoke options (as shown below), but my initial testing using Delphi 6
> revealed problems invoking the web service when doing so. Registering
> the options in separate calls to RegisterInvokeOptions didn't exhibit
> this behavior.
>
> InvRegistry.RegisterInvokeOptions(TypeInfo(IYourWebService),
> [ioDocument, ioLiteral]);
>
--
David Clegg
> What unit is IGatewayResultSoap in? Thanks
That's in one of our units (the one that the wsdl importer generated,
in fact). You could put the initialization code in there, but you'd
have to remember to update it when/if you re-imported the wsdl.
Putting the call in the initialization section of any unit (or even in
the .dpr) should suffice. I personally like to group this sort of
stuff together with the code that consumes it, but it shouldn't make a
difference where you do it.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Oh, well, of course, everything looks bad if you remember it." - Homer
Simpson
Thomas Miller
you have suggested. As you suggest the Interface is specific to your
import. Is there a white paper out there on this so I can figure out
what to do?
> What unit is IGatewayResultSoap in.
That's in one of our units (the one that the wsdl importer generated,
in fact). You could put the initialization code in there, but you'd
have to remember to update it when/if you re-imported the wsdl.
Putting the call in the initialization section of any unit (or even in
the .dpr) should suffice. I personally like to group this sort of
stuff together with the code that consumes it, but it shouldn't make a
difference where you do it.
David Clegg
> I think you are right about my problem, but I don't see the solution
> as you have suggested. As you suggest the Interface is specific to
> your import.
You will need to replace IGatewayResultSoap with the interface stub the
wsdl importer generated for the web service you are consuming. If this
web service is publically accessible, send me the URL for the wsdl, and
I should be able to come up with an example for you.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Do I know what rhetorical means?" - Homer Simpson
David Clegg
> My interface is IAssesementManagement so I want to do
>
> InvRegistry.RegisterInvokeOptions(TypeInfo(IAssesementManagement),
> [ioDocument, ioLiteral]);
Maybe, maybe not :-)
When I do that using D6, I get an ERemotableException thrown when
registering the invoke options that way. If I register ioDocument and
ioLiteral separately, I don't see this problem. I suspect this is a
bug, and one which may have been fixed between D6 and D2006 (I've not
tested that yet).
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Homer no function beer well without." - Homer Simpson
Tom Corey
> We send multiple parameters to the Web Service and it thinks they are
> NULL.
Questions:
1) Is the web service under your control, or is it some third party
system?
2) Were you able to get this function working in any previous version
of Delphi?
What I'm aiming at here is the possibility that the problem is actually
somewhere else - like on the web service side. As I said before, I'm no
expert, but in the whopping two programs I've done with this component,
the two different services I was interacting with were configured much
differently. For that matter, the XML one of them generated was so
resistant to the library I was using (TurboPower XMLPartner) that I
ended up having to parse the strings myself. As you might imagine, I
have a someone reserved opinion about the technical skills of some of
the service providers out there :)
David Clegg
> I get an ERemotableException thrown when
> registering the invoke options that way.
I should clarify. The exception is not thrown when registering, but
when I attempt to invoke any of the web service methods.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"You never know when an old calendar might come in handy! Sure, it's
Thomas Miller
The code seems to format the three variables that I have 3 different
ways. I don't want to repost it here as it is already posted in the Web
service soap group. But the one thing that really sticks out as
different is this
<NS1:GetTestGroupID xmlns:NS1="http://tempuri.org">
and in the one that works
<tns:GetTestGroupID xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
The line wrapped, but the difference is very very significant.
There is no real documentation. If anyone knows of some, please point
me to it.
Since I know exactly what the envelope is suppose to look like, is there
a component that I can use to just send and receive the SOAP and do the
envelopes on my own?
Setting followup to borland.public.delphi.webservices.soap
But now that I start looking at the WSDL file, some of this makes more
sense, but not sure why SOAP Scope does it one way and Delphi the other way
tns => TargetNameSpace
NS1 => Probably NameSpace1
There are 10 name spaces in the WDSL file and non of them are mapped
into the soap envelope in Delphi.
xmlns:s is for the XMLSchema and Delphi makes it xmlns:xsd
The only on that is close is soapenc vs Delphi SOAP-ENC. No wonder the
web service can't understand the envelope. These seems to be a major
bug, or I hope there is some magic encoding flag that I can set and it
will properly encode this stuff.
Thanks David for trying to help.
David Clegg wrote:
> Thomas Miller wrote:
>
>> What unit is IGatewayResultSoap in? Thanks
>
> That's in one of our units (the one that the wsdl importer generated,
> in fact). You could put the initialization code in there, but you'd
> have to remember to update it when/if you re-imported the wsdl.
>
> Putting the call in the initialization section of any unit (or even in
> the .dpr) should suffice. I personally like to group this sort of
> stuff together with the code that consumes it, but it shouldn't make a
> difference where you do it.
>
--
David Clegg
> Thanks David for trying to help.
No worries, and good luck with finding a solution.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"I didn't need that fact...now I forgot who won Bud Bowl 8." - Homer
Simpson
Dave Nottage [TeamB]
> There is an overload which is supposed to let you specify multiple
> invoke options (as shown below), but my initial testing using Delphi 6
> revealed problems invoking the web service when doing so.
That's because when calling using the overload with the parameter as a
set, you're replacing *all* the options, which means if there were any
options present because of another call (such as
RegisterDefaultSOAPAction) beforehand, they will disappear.
--
Dave Nottage [TeamB]
Dave Nottage [TeamB]
> I suspect this is a bug..
It's not a bug, but the cause could possibly be modified. See my other
post.
--
Dave Nottage [TeamB]
Dave Nottage [TeamB]
> What I'm aiming at here is the possibility that the problem is
> actually somewhere else - like on the web service side
AFAICT, the webservice is written for .NET (ie possibly in C#). Since a
lot of it is handled by the .NET framework, that's probably not the
problem.
I suspect the solution will be making sure the invoke options are
correct. It's difficult to sort out when the webservice needs some kind
of HTTP authorization, unless Thomas can come up with a test
username/password.
--
Dave Nottage [TeamB]
David Clegg
> That's because when calling using the overload with the parameter as a
> set, you're replacing all the options, which means if there were any
> options present because of another call (such as
> RegisterDefaultSOAPAction) beforehand, they will disappear.
That makes sense. And yeah, I agree that the cause *could* be modified,
but that may well break existing code which relies on the current
behaviour. At least I know what caused it, so I don't stumble into the
same trap again. Thanks for the explanation.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Oh, people can come up with statistics to prove anything, Kent. 14% of
people know that." - Homer Simpson
Thomas Miller
> Thomas Miller wrote:
>
>> I think you are right about my problem, but I don't see the solution
>> as you have suggested. As you suggest the Interface is specific to
>> your import.
>
> You will need to replace IGatewayResultSoap with the interface stub the
> wsdl importer generated for the web service you are consuming. If this
> web service is publically accessible, send me the URL for the wsdl, and
> I should be able to come up with an example for you.
>
Thanks for the offer, but it is not. I am getting a response from the
server, it just thinks the parameters are null or empty. It is
definitely an encoding problem no that I dig deeper into the WSDL and
actually try to read what it is communicating.
Brian Moelk
> Any suggestion on how to figure this out so I can use Delphi for this
> would be greatly appreciated.
RemObjects. ;)
--
Brian Moelk
Brain Endeavor LLC
bmo...@NObrainSPAMendeavorFOR.MEcom
Thomas Miller
> Thomas Miller wrote:
>
>> We send multiple parameters to the Web Service and it thinks they are
>> NULL.
>
> Questions:
>
> 1) Is the web service under your control, or is it some third party
> system?
Third party
> 2) Were you able to get this function working in any previous version
> of Delphi?
No. I upgraded the client form D5 to D2006 just for this purpose.
>
> What I'm aiming at here is the possibility that the problem is actually
> somewhere else - like on the web service side. As I said before, I'm no
> expert, but in the whopping two programs I've done with this component,
> the two different services I was interacting with were configured much
> differently. For that matter, the XML one of them generated was so
> resistant to the library I was using (TurboPower XMLPartner) that I
> ended up having to parse the strings myself. As you might imagine, I
> have a someone reserved opinion about the technical skills of some of
> the service providers out there :)
We are using SOAP Scope. By the way, an invaluable tool. Using it to
poke around the service uncovered a bug that the provider has sense fixed.
http://www.mindreef.com/products/soapscope/index.php
So I know that the service works as expected. And I even have a valid
envelope. So how would you send this manually? I would still love to
see this work the right way, but I need to get something working by
Monday at the latest. The piece I am working on is due tomorrow, but
that isn't going to happen.
I also was sending one statements and saw Dave's message about
separating them. I will try that tomorrow.
The encoding is really messed up.
Thomas Miller
I am more then happy to do that on a private basis. Please contact me
by email and I will provide you with what ever you need to help me out,
even a beer if I can get it through the line :-)
I also will try separating the statement as to not replace the existing
settings as you eluded to in another message.
--
Thomas Miller
Brian Moelk wrote:
> Thomas Miller wrote:
>> Any suggestion on how to figure this out so I can use Delphi for this
>> would be greatly appreciated.
>
> RemObjects. ;)
>
--
Thomas Miller
it is now working!!!!! the ioDocument was the fix.
Thomas Miller wrote:
> How do I get a hold of someone in customer service? It wasn't obvious
> from the web site.
>
> Thanks.
Tom Corey
> So I know that the service works as expected. And I even have a
> valid envelope. So how would you send this manually?
Sorry, can't help. Like I said, I'm certainly no expert, and I'm afraid
you've just exceeded the limits of my knowledge :)
David Clegg
> Great news!!!! After looking at a suggestion from both David and
> Dave it is now working!!!!! the ioDocument was the fix.
Yay! I'll have a beer on your behalf tonight to celebrate. :-)
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Marge, you being a cop makes you the man! Which makes me the woman --
and I have no interest in that, besides occasionally wearing the
underwear, which as we discussed, is strictly a comfort thing." - Homer
Simpson
Graham
where to buy additional copies? :-)
John Kaster (Borland)
> No worries, and good luck with finding a solution.
Further discussion should be on the technical newsgroup rather than
non-tech
--
John Kaster http://blogs.borland.com/johnk
Features and bugs: http://qc.borland.com
Get source: http://cc.borland.com
If it's not here, it's not happening: http://ec.borland.com
David Clegg
> Further discussion should be on the technical newsgroup rather than
> non-tech
Yeah, sorry about the thread drift. On the bright side, it seems that
Thomas found a solution to his problem.
--
Cheers,
David Clegg
dcl...@gmail.com
http://cc.borland.com/Author.aspx?ID=72299
QualityCentral. The best way to bug Borland about bugs.
http://qc.borland.com
"Vampires are make believe, just like elves and gremlins and eskimos."
- Homer Simpson
Thomas Miller
--
John Kaster (Borland)
> On the bright side, it seems that
> Thomas found a solution to his problem.
Agreed. Hopefully next time the default response will be trying to
figure out the solution rather than returning the product.