It helps much more if you already create a JUnit test that fails showing your problem. I have created such test in the intact-uniprot module and I cannot reproduce the problem. I cannot commit the test now because googlecode is under maintenance today. The test looks like:
@Test
public void retrieveByUniprotId2() throws Exception {
Collection<UniprotProtein> prots = getUniprotService().retrieve( "Q96EU7" );
final UniprotProtein uniprotProtein = prots.iterator().next();
assertEquals( "Q96EU7", uniprotProtein.getPrimaryAc() );
assertEquals( "C1GALT1-specific chaperone 1", uniprotProtein.getDescription());
assertEquals(4, uniprotProtein.getSynomyms().size());
}
You can try it in the UniprotRemoteServiceTest inside the intact-uniprot module (under bridges).
Can it be the case that you are using an outdated version of the intact-uniprot module? The latest is 2.1.4-SNAPSHOT, you may want to try this one if you are not using it.
You can run mvn dependency:tree in your project and see what versions of intact-uniprot and uniprotjapi you are using...
Hope this helps!
Bruno