Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Spring JIRA by Matej Spiller-Muys, 2 years ago
expected:<...faultMetadataService[:] validGets = 0, recu...> but was:<...faultMetadataService[@9664a1] validGets = 0, recu...>
via Spring JIRA by Matej Spiller-Muys, 1 year ago
expected:<...faultMetadataService[:] validGets = 0, recu...> but was:<...faultMetadataService[@9664a1] validGets = 0, recu...>
via GitHub by RedAdder
, 3 days ago
expected:<[]ext> but was:<[t]ext>
via GitHub by wildfly-ci
, 2 years ago
expected:<[1]> but was:<[0]>
via GitHub by wildfly-ci
, 2 years ago
expected:<[1]> but was:<[0]>
via GitHub by wildfly-ci
, 2 years ago
expected:<[1]> but was:<[0]>
org.junit.ComparisonFailure: expected:<...faultMetadataService[:] validGets = 0, recu...> but was:<...faultMetadataService[@9664a1] validGets = 0, recu...> at org.junit.Assert.assertEquals(Assert.java:125) at org.junit.Assert.assertEquals(Assert.java:147) at org.springframework.roo.metadata.DefaultMetadataServiceTest.testToStringOfNewInstance(DefaultMetadataServiceTest.java:22) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)