Issue 3 in ocpsoft-tools: socialpm-ws does not deploy on glassfish v3

1 view
Skip to first unread message

ocpsof...@googlecode.com

unread,
Dec 12, 2009, 10:16:05 AM12/12/09
to ocpsoft-soc...@googlegroups.com
Status: Accepted
Owner: dominik.dorn
Labels: Type-Defect Priority-Medium

New issue 3 by dominik.dorn: socialpm-ws does not deploy on glassfish v3
http://code.google.com/p/ocpsoft-tools/issues/detail?id=3

What steps will reproduce the problem?
1. build social-pm-ws with mvn clean compile package
2. deploy the generated war through glassfish v3 admin console

What is the expected output?
The application should be deployable.

What do you see instead?
Glassfish v3 webadmin console states whats attached in the file


Attachments:
stacktrace.txt 32.3 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

ocpsof...@googlecode.com

unread,
Dec 12, 2009, 11:14:06 AM12/12/09
to ocpsoft-soc...@googlegroups.com

Comment #1 on issue 3 by dominik.dorn: socialpm-ws does not deploy on
glassfish v3
http://code.google.com/p/ocpsoft-tools/issues/detail?id=3

Ok, the problem seems to be, that the JBoss JAX-RS implementation RestEasy
is bundled
with the application and conflicts with JavaEE default JaxRS implementation
Jersey.

ocpsof...@googlecode.com

unread,
Dec 14, 2009, 1:49:13 AM12/14/09
to ocpsoft-soc...@googlegroups.com

Comment #2 on issue 3 by lincolnbaxter: socialpm-ws does not deploy on
glassfish v3
http://code.google.com/p/ocpsoft-tools/issues/detail?id=3

I'll try to figure this one out tomorrow night. It's been a busy weekend.
This is
possibly a problem with RestEasy itself.

ocpsof...@googlecode.com

unread,
Jan 21, 2010, 10:33:28 AM1/21/10
to ocpsoft-soc...@googlegroups.com

Comment #3 on issue 3 by lincolnbaxter: socialpm-ws does not deploy on
glassfish v3
http://code.google.com/p/ocpsoft-tools/issues/detail?id=3

This is going to take some work, because the RestEasy JARs conflict with
Jersey...

Reply all
Reply to author
Forward
0 new messages