Hi again Jean.
No, in the Karaf log there are nothing related to exception.
All of the logs are in severity INFO, so it seems like a James is up and running, but there are no TCP ports on which it listens for incoming connections. Now I will find bundle by bundle which is responsible to activate the services, and will try to produce a ConfigAdmin view related to every bundle.
Thank you for helping me on this problem.

BR
Dimitar

On 03/10/2014 12:38 PM, Jean-Baptiste Onofré wrote:
Hi Dimitar,

you don't have any exception or message from James ?

I like your idea about both support of James and implement some "backend" engine to ConfigAdmin using James.
Let me find the interfaces/services that you should implement.

Regards
JB

On 03/10/2014 11:24 AM, Dimitar Dimitrov wrote:
Hi team.
For several days I am trying to install and configure apache
James-3.0.0.beta5-SNAPSHOT to run into Apache Karaf (v3.0.0) but
unsuccessfully.
I tried with the last version of the Apache Karaf from the SVN
repository where I found the Apache James bundles and features file.
With little changes in the feature file I managed to install the core
James bundles. My features.xml includes the following artifacts:

bundle:install mvn:com.google.guava/guava/13.0.1
feature:install -v james-server-dnsservice-dnsjava
bundle:install
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_1

feature:install -v james-server-protocols-smtp

bundle:install mvn:org.apache.httpcomponents/httpcore-osgi/4.3.2
bundle:install mvn:org.apache.httpcomponents/httpclient-osgi/4.3.2
feature:install -v james-server-mailets

after that I have compiled the following artifacts

apache-jsieve-core-0.6-SNAPSHOT.jar
apache-mime4j-core-0.8.0-SNAPSHOT.jar
apache-mime4j-dom-0.8.0-SNAPSHOT.jar

and put it manually in the deploy folder.

So now James bundles are up and running as expected without errors, but
there are not a processes listened on TCP/25 or TCP/143, no matter that
I am starting the Karaf with Root user.

176 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
DNS Service :: Library
177 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
DNS Service :: API
178 | Active   |  80 | 2.5.1.SNAPSHOT       | Apache James :: Mailet API
180 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
DNS Service :: Implementation
181 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Lifecycle API
202 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Common Utilities
203 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Mail Queue :: API
204 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Filesystem API
205 | Active   |  80 | 0.6.0.SNAPSHOT       | Apache James :: jSieve ::
Manager API
207 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Data  :: API
209 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Core
210 | Active   |  80 | 2.5.1.SNAPSHOT       | Apache James :: Basic
Mailet Toolkit
212 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Protocols Library
213 | Active   |  80 | 1.6.3                | Apache James :: Protocols
:: API
214 | Active   |  80 | 1.6.3                | Apache James :: Protocols
:: Netty Implementation
216 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
SMTP
217 | Resolved |  80 | 1.6.3                | Apache James :: Protocols
:: SMTP
232 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Mailets
234 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
Data :: Library
235 | Active   |  80 | 0.6.0.SNAPSHOT       | Apache James :: jSieve ::
Mailet
236 | Active   |  80 | 0.6.0.SNAPSHOT       | Apache James :: Mailbox ::
API
247 | Active | 80 | 0.8.0.SNAPSHOT | Apache James :: Mime4j :: DOM
248 | Active   |  80 | 0.8.0.SNAPSHOT       | Apache James :: Mime4j ::
Core
249 | Active   |  80 | 0.6.0.SNAPSHOT       | Apache James :: jSieve ::
Core
269 | Active   |  80 | 1.6.3                | Apache James :: Protocols
:: IMAP
270 | Active   |  80 | 3.0.0.beta5-SNAPSHOT | Apache James :: Server ::
IMAP

Is there something that I'm missing? How I can configure James when it
is included in Karaf.
I cannot find Configuration Admin Service or blueprint config related to
James, so I suppose that the James configuration is in somewhere in the
bundles.
Could you give me some points from where I can start to develop my own
configration for theApache James in Karaf.
My idea is to develop Config Admin Service interface for the SMTP and
IMAP implementation of Apache James.

Thanks in advance.
Dimitar



Reply via email to