Details
-
- Environment:
-
Actually, I'm using the version 4.0.4.
Windows XP, Petals 3.1.1.
Activity
| Fix Version/s | 4.1_4.0 [ 10269 ] | |
| Fix Version/s | 4.1 [ 10186 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Assignee | Nicolas Oddoux [ noddoux ] | Christophe DENEUX [ cdeneux ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 4.0.8 [ 10263 ] | |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 4.1 [ 10186 ] | |
| Fix Version/s | 4.1_4.0 [ 10269 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Under our environement, the bc-soap doesn't have this issue (it seems). The first invocation works, and the first time we read the wsdl (adding '?wsdl' at the end of the url) or vists the bc soap web page (under 8084 port by default), we can consult the wsdl page.
We're under RHEL5, not windows, under esb 3.1.1.
So, curious, and hard to reproduce : keep preciously your dev PC