Mac OS X. My main workstation is a Mac Book Pro. When I would build
and deploy locally, everything worked perfectly. However, when I try
FileNotFoundException. So, perhaps it is looking for the wsdl and
referencing a path that is unique to Mac OS X. Why would that be,
though? I'm not hand editing these WSDL files by any means. I'm
organization. Does that suggest that something is create components
I'll take a look at my files and see if that is the case. If so, how
> in regard of wsdl parsing, databasebc and ftpbc and filebc are using
> the same wsdl parser, so they should behave the same way.
>
> you said it deploys ok locally and failed when deployed remotely,
> could it be that there are some platform specific absolute path
> being generated as the import url, do a text search within your comp
> app, and see if that is the case.
>
> may be I should not call the importing wsdl 'master wsdl', you asked
> about a work around, I suggest that you can put the imported wsdl
> inline in the importing wsdl so that avoid the import resolution
> issue you ran into, as I said in previous e-mail, we always use
> wsdls with imports and they work well with filebc and other bcs...,
> so it could also be a issue with the way the app is constructed -
> just a possibility;-)
>
> your latest attached project has missing references - JSON - 2.2.5?
> I'll find it and may be find some time to attempt a deploy..
>
> BTW, you said deploy locally ok, the failure only happens when the
> comp app built on one machine being deployed on the app server on
> another machine?
>
> regards
> Jim
>
> Andrew McLaughlin wrote:
>> Okay, I stil don't know what the master wsdl is. So that still
>> doesn't make sense. Since this WSDL is the one that is generated by
>> the POJO wizard, how would that work?
>>
>> The difference between failure and success is if the project is
>> deployed locally or remotely. How are you guys using FILEBC? Are
>> all your projects deployed on your local workstation? Does remote
>> deploys only work on Sun Solaris? I've tested this against
>> GlassFish v2.1 running both on Ubuntu 9.04 and CentOS 5.
>>
>> I used to have this exact same error when trying to use the
>> DatabaseBC and FTPBC. These both seem to work, but FILEBC now seems
>> to be exhibiting the same error (specifically
>> FileNotFoundException, in reference to a POJO wsdl file).
>>
>> Andrew
>>
>>
>> On Sep 30, 2009, at 5:01 PM, Jim Fu wrote:
>>
>>> I was saying, as a temp work around, is it possible to put the
>>> imported wsdl inline in the master wsdl so that the project can be
>>> deployed and run without running into the import resolution issue
>>> - which we need to verify here, the experience is that it should
>>> work well since most of our projects using binding wsdls that
>>> imports another wsdl...
>>>
>>> I remember you mentioned that it works on some platform and fails
>>> on other?
>>>
>>> --Jim
>>>
>>> Andrew McLaughlin wrote:
>>>> Otherwise, how can I roll my WSDL in to this master wsdl, since
>>>> the app is not properly handling the deploy manifest.
>>>>
>>>> Andrew
>>>>
>>>>
>>>> On Sep 30, 2009, at 12:33 PM, Jim Fu wrote:
>>>>
>>>>> since it is caused by wsdl parser somehow failed to resolve
>>>>> imports, can you put the imports into the master wsdl directly
>>>>> for now?
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail:
[hidden email]
>>>> For additional commands, e-mail:
[hidden email]
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
[hidden email]
>>> For additional commands, e-mail:
[hidden email]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
[hidden email]
>> For additional commands, e-mail:
[hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
[hidden email]
> For additional commands, e-mail:
[hidden email]
>
