Robert,
Thanks very much for this information.
T
On 2/14/2014 6:34 PM, robertlazarski . wrote:
On Fri, Feb 14, 2014 at 8:14 PM, T. Allen wrote:
I did not receive any replies about this problem but was able to get past
it. Changing the regex from:
to:
fixed the problem. It seems XML Be
On Fri, Feb 14, 2014 at 8:14 PM, T. Allen wrote:
> I did not receive any replies about this problem but was able to get past
> it. Changing the regex from:
>
>
> to:
>
>
> fixed the problem. It seems XML Beans does not interpret the leading ^
> symbol correctly. Is this by design or should I
I did not receive any replies about this problem but was able to get
past it. Changing the regex from:
to:
fixed the problem. It seems XML Beans does not interpret the leading ^
symbol correctly. Is this by design or should I create a JIRA?
Thanks,
T
On 2/12/2014 9:01 AM, T. Allen wro
Has anyone had problems with regex using XML Beans binding (see message
below)? I have used the following regex and it worked fine:
This regex gives an error every time:
Have I done something wrong or is this a bug with XML Beans?
Thanks,
T
On 2/10/2014 12:40 PM, T. Allen wrote:
I have an
I have an Axis2 1.6.1 web service that has 1 regex in the WSDL schema.
The WSDL/schema snippet is below.
type="tns:hazmatCode"/>
type="tns:hazmatFlag"/>
I know the regex pattern of ^(NA|UN).* is valid as I have tested it.
However, each time I send a request with a string that matc
