topic Re: 1.1 STILL has problems with remoting and same error in Alfresco Archive

1.1 STILL has problems with remoting and same error

rsfeir — Fri, 09 Dec 2005 20:40:26 GMT

I am back to the same spot I was before with 1.1, come on guys, this shouldn't be this complicated. I followed all the steps as closely as I can, and these normally work when I work with other webservices and yet I still get this error!I am running alfresco in its prepackaged jboss bundled download

Re: 1.1 STILL has problems with remoting and same error

rwetherall — Sun, 11 Dec 2005 21:09:00 GMT

Hi,

I'm sorry you are still having difficulties with this. I have just double checked running sample1 on the latest code line (1.1) and it works for me using Tomcat (I'll double check JBoss for you tomorrow).

Clearly we are missing something here so I'd gladly take up your offer to help debug the problem.

As you will have noticed the error messages returned from Axis are not helpful in diagnosing the problem so in order to start to get to the route of the issue could I ask you to turn debug output on for the web service packages.

The route cause of the exception should then be output as part of the debug messages also it should give us an indication of how far we are getting before the failure.

Let me know how you get on,

Thanks,
Roy

Add these lines to the log4J.properties file found in core/source/java to turn the webservice debug on:


log4j.logger.org.alfresco.repo.webservice=debug
log4j.logger.org.alfresco.example.webservice=debug
‍‍‍‍

Re: 1.1 STILL has problems with remoting and same error

rwetherall — Mon, 12 Dec 2005 14:34:59 GMT

Hi,

I've tried sample1 against jboss and I can't find any problems at this end.

Is it only sample1 you see a problem with or are there other samples/unit tests that are failing?

Hopefully the debug output will help to shed some light on the issue.

Thanks,
Roy

Re: 1.1 STILL has problems with remoting and same error

rsfeir — Mon, 12 Dec 2005 15:32:10 GMT

Sample 1 so far, did not try the others, but if I can't get a repository listing, then in my mind right now there is no point. I am going to turn up loggin as you suggested this AM and see what happens.

will update you soon.

R

Re: 1.1 STILL has problems with remoting and same error

rsfeir — Mon, 12 Dec 2005 16:10:51 GMT

Ok, here's a real weird one for you. When I started Alfresco with alf_start.bat, I had the problem. Then since I needed to see all the debug being spewed out at the command line, and the alfresco window didn't have enough buffer, so I started from the alfresco/jboss/bin dir running run.bat for jboss directly.

Well, now it works, no errors, with my own code, and I get this as the list of Stores:

system
alfrescoUserStore
lightWeightVersionStore
SpacesStore

I'm happy that I can move forward, but I am VERY curious as to why this might be so different in each case.

R

Re: 1.1 STILL has problems with remoting and same error

rwetherall — Mon, 12 Dec 2005 17:04:51 GMT

Hi,

I'm not sure why that should make a difference. I'll ask around here and see if anyone has an idea.

Cheers,
Roy

Re: 1.1 STILL has problems with remoting and same error

rsfeir — Mon, 12 Dec 2005 20:44:16 GMT

Thanks for looking into it. The diff will be important to know because I don't know if we'll hit the issue again on deploying to dev and production servers.

That said, in one afternoon I was able to query the repository, get the content and display it in my portlet. The examples have proven invaluable of course, so thanks in advance to whom ever worte them, and for putting comments in, it helped a lot in following the code.

Once I have a cleaned up version, I will check with my office to see if we could donate the code to Alfresco for inclusion. Our project is open source, but it being for the government I don't know if there are issues with this.

R

Re: 1.1 STILL has problems with remoting and same error

rwetherall — Tue, 13 Dec 2005 09:46:10 GMT

Hi,

Glad to hear you where able to make some progress with this. Any code you are able to contribute will be gratefully received.

Thanks,
Roy