Details
Description
The recent URL handling refactoring has introduced a regression in determining the content type.
See the following exchange for details:
Hi Jim,
Sure , this contribution and some other ones are in '/repository' both
on standalone and 'tomcat+sca'.
fabric3-contribution-scanner-1.5-SNAPSHOT.jar
fabric3-contribution-scanner-war-1.5-SNAPSHOT.jar
fabric3-contribution-war-1.5-SNAPSHOT.jar
Ivan.
On Wed, 2010-04-07 at 01:43 +0200, Jim Marino wrote:
Hi Ivan,
Do you have fabric3-contribution-scanner-war in the /repository directory? You'll need to make sure that all of the extensions in the web profile (separately downloadable) are installed in the /repository directory.
Let me know if that solves your problem.
Thanks for the nice comment about the book too!
Jim
On Apr 7, 2010, at 1:19 AM, Ivan Palich wrote:
Thx for reply Jim & Tomas !!
Still fighting with bigbank, now bigbank.WAR under fire .
So here we are :
palmal@palmal-desktop:~/sca/servers/vm/target/image$ ls deploy/
bigbank-api-1.4.jar bigbank-services-1.4.jar README.txt
bigbank-loan-1.4.jar bigbank.war
palmal@palmal-desktop:~/sca/servers/vm/target/image$ java -jar
bin/server.jar
[INFO|main|2010.04.07|2:56:28] JTA extension installed
[INFO|main|2010.04.07|2:56:28] JMS extension installed
[INFO|main|2010.04.07|2:56:28] HTTP extension installed
[INFO|main|2010.04.07|2:56:28] WAR extension installed
[INFO|main|2010.04.07|2:56:28] REST extenson installed
[INFO|main|2010.04.07|2:56:28] Web services extension installed
[INFO|main|2010.04.07|2:56:28] Network extension installed
[INFO|main|2010.04.07|2:56:29] HTTP listener started on port 8181
[SEVERE|main|2010.04.07|2:56:29] An error was encountered deploying a
contribution
org.fabric3.contribution.UnsupportedContentTypeException: Type null in
contribution bigbank.war not supported
at
org.fabric3.contribution.ProcessorRegistryImpl.processManifest(ProcessorRegistryImpl.java:90)
at
org.fabric3.contribution.ContributionServiceImpl.processManifest(ContributionServiceImpl.java:516)
So standalone never wants to deploy war-file. The very same situation
happens with a "tomcat+sca" installation. Pity.
As for me, after making some debugging & reviewing it came out that
'WarContributionProccessor' is capable to handle *.war (at least at a
first glance). webapp-extention-....jar, which contributes this class
to runtime was missed in a 'repository/' directory, so i tried to add
it there .'Nobody dies'-were my thoughts, =)) hmm ... i was wrong -
server had another opinion. After saying
" org.fabric3.contribution.UnresolvableImportException: Unable to
resolve import [package: org.fabric3.runtime.webapp Min: 1.5.0 Required:
true] in fabric3-webapp-extension-1.5-SNAPSHOT.jar"
it gracefuly terminated, and neither hacking for contribution descriptor
'sca-contribution.xml' (export.java='<package>') nor
'MANIFEST.MF'(Export-Package: org.fabric3.runtime.webapp;version="1.5")
substitution for
'fabric3-webapp-api-1.5-SNAPSHOT.jar' were helpful.
So can you point out what steps were wrong or misleading ?
Thx in advance, Ivan.
PS . 2 Jim - "Understanding SCA" is great book and guidance
On Sun, 2010-04-04 at 10:35 +0200, Jim Marino wrote:
Hi Ivan,
Placing the JPA API in host will make its contents available to all applications. However, the recommended approach is to place the jar in the server repository (/repository) and import it into each application's sca-contribution.xml (under /META-INF) using the import directive:
<import.java package="javax.persistence" version="1.0.0"/>
The BigBank loan service module has an example of this. In this way, the persistence API will not need to be placed in host.
Jim
On Apr 4, 2010, at 2:28 AM, Ivan Palich wrote:
At last , got it.
JPA classes (OSGi bundle
'com.springsource.javax.persistence-1.0.0.jar' ) has to be placed to
<F3>/host directory so it can be shared.
Hmmmmm , too much copy/paste and duplication (same file is also present
in /repository ).
On Sun, 2010-04-04 at 00:47 +0200, Tomas Fecko wrote:
Hmm, I don't know, I'm just user of fabric3 - I'm not working on
release of 1.5.
It works for me on 1.4...
And I checked all the pom-s of 1.4, as I was playing with it for 2
weeks and still I like it more as ApacheTuscany...
there was some warnings, when I tried to use maven 3.0 to build it,
but with maven 2.2.1 it worked with minor changes good ...
2010/4/4 Ivan Palich <palmal.mozhay@gmail.com>
Grrr =)) Sorry for offtop BUT:
[INFO] Fabric3 Servers Parent POM ............................
SUCCESS
[1.355s]
[INFO] Fabric3 Single VM Setup ...............................
FAILED
[15.756s]
[INFO] Fabric3 Cluster Parent POM ............................
NOT BUILT
[INFO] Fabric3 Controller Setup ..............................
NOT BUILT
[INFO] Fabric3 Zone1 Setup ...................................
NOT BUILT
[INFO] Fabric3 Zone2 Setup ...................................
NOT BUILT
[INFO]
------------------------------------------------------------------------
[ERROR]
The following mojo encountered an error while executing:
Group-Id: org.codehaus.fabric3
Artifact-Id: fabric3-assembly-plugin
Version: 1.5-SNAPSHOT
Mojo: fabric3-assembly
brought in via: POM
While building project:
Group-Id: org.codehaus.fabric3.samples
Artifact-Id: servers-vm
Version: 1.5-SNAPSHOT
From file: /home/palmal/sca/servers/vm/pom.xml
Reason: Unable to read local copy of metadata: Cannot read
metadata from
'/home/palmal/.m2/repository/org/codehaus/fabric3/profile-ws/1.5-SNAPSHOT/maven-metadata-local.xml': only whitespace content allowed before start tag and not \ufffd (position: START_DOCUMENT seen \ufffd... @1:1)
org.codehaus.fabric3:profile-ws:zip:1.5-SNAPSHOT
Someone hacking POMs with notepad ? =)
On Sun, 2010-04-04 at 00:23 +0200, Tomas Fecko wrote:
Hi,
Try to run bigbank sample on servers, which are provided
with samples -
as stated in preference guide...
Just run mvn clean install over servers directory and maven
should
download the sever runtimes needed for samples.
Than when I wanted to run samples on standalone runtime
downloaded from
fabric3 page,
I used configs from servers provided with samples and it
worked for me...
maybe that helps...
Tomas
Ivan Palich wrote / napísal(a):
Good evening/night/morning !!!
I've a problem while launching bigbank sca-modules both on
tomcat and
standalone f3 runtimes. I've used both binary version from
a web site
(fabric3 1.4) and then svn build (1.5-SNAPSHOT).
Some logging here :
org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server} Setting property
'port' to
'${tomcat.server.port}5' did not find a matching property.
Apr 4, 2010 12:22:36 AM
org.apache.catalina.core.AprLifecycleListener
init
INFO: The APR based Apache Tomcat Native library which
allows optimal
performance in production environments was not found on
the
java.library.path: /usr/lib/jvm/java-6-sun-1.6.0.16/jre/lib/i386/server:/usr/lib/jvm/java-6-sun-1.6.0.16/jre/lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.16/jre/../lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.16/jre/lib/i386/client:/usr/lib/jvm/java-6-sun-1.6.0.16/jre/lib/i386:/usr/lib/xulrunner-addons:/usr/lib/xulrunner-addons:/usr/lib/xulrunner-addons:/usr/lib/xulrunner-addons:/usr/lib/xulrunner-addons:/usr/java/packages/lib/i386:/lib:/usr/lib
Apr 4, 2010 12:22:36 AM
org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Apr 4, 2010 12:22:36 AM
org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 624 ms
Apr 4, 2010 12:22:36 AM
org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Apr 4, 2010 12:22:36 AM
org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
Apr 4, 2010 12:22:36 AM
org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Apr 4, 2010 12:22:36 AM org.apache.jk.common.ChannelSocket
init
INFO: JK: ajp13 listening on /0.0.0.0:8001
Apr 4, 2010 12:22:36 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/30 config=null
[INFO|main|2010.04.04|12:22:38] WAR extension installed
[SEVERE|main|2010.04.04|12:22:38] An error was encountered
deploying a
contribution
org.fabric3.host.contribution.InstallException:
org.fabric3.contribution.UnresolvableImportException:
Unable to resolve
import [package: javax.persistence Min: 1.0.0 Required:
true] in
bigbank-loan-1.4.jar
at
org.fabric3.contribution.ContributionServiceImpl.installInOrder(ContributionServiceImpl.java:485)
at
org.fabric3.contribution.ContributionServiceImpl.contribute(ContributionServiceImpl.java:193)
at
org.fabric3.contribution.scanner.impl.ContributionDirectoryScanner.processAdditions(ContributionDirectoryScanner.java:350)
at
org.fabric3.contribution.scanner.impl.ContributionDirectoryScanner.recover(ContributionDirectoryScanner.java:213)
at
org.fabric3.contribution.scanner.impl.ContributionDirectoryScanner.onEvent(ContributionDirectoryScanner.java:155)
at
org.fabric3.fabric.event.EventServiceImpl.publish(EventServiceImpl.java:71)
at
org.fabric3.fabric.runtime.DefaultCoordinator.start(DefaultCoordinator.java:105)
at
org.fabric3.runtime.tomcat.Fabric3Listener.init(Fabric3Listener.java:144)
at
org.fabric3.runtime.tomcat.Fabric3Listener.lifecycleEvent(Fabric3Listener.java:93)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:715)
at
org.apache.catalina.startup.Catalina.start(Catalina.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by:
org.fabric3.contribution.UnresolvableImportException: Unable
to resolve import [package: javax.persistence Min: 1.0.0
Required: true]
in bigbank-loan-1.4.jar
at
org.fabric3.contribution.DependencyServiceImpl.order(DependencyServiceImpl.java:108)
at
org.fabric3.contribution.ContributionServiceImpl.installInOrder(ContributionServiceImpl.java:483)
... 17 more
[INFO|main|2010.04.04|12:22:38] Fabric3 ready [Mode:VM]
[INFO|main|2010.04.04|12:22:38] Server startup in 2474 ms
So any idea for that ?
Besides this - i couldn't managed to build Fabric3 from a
fresh
svn-checkout (/modules:trunk),
at least some prequisites worth mentioning like :
- standalone maven2 must be (for
fabric3-atomikos-install , i used
embedded one from eclipse) - jms-1.1 was not found through declared repositories.
Ivan