Hello.
I have several problems with version 4.0.3, possibly caused by my
inexperience with Karaf
1. I created a feature and a distribution using the archetypes of karaf
4.0.3.
When generating the feature I get the next item in the pom.xml:
(OBR)
And to start the distribution which includes that
Hi, thanks for the help.
1. So it's an error in the archetype?
2. Sorry. Rookie mistake. I forgot to include my minimum distribution
features.
What is the best way to do it in my own feature or in the distribution?
--
View this message in context:
Hi,
1. yes OBR resolver is now deprecated as we have the FeaturesResolver now.
2. Features are missing for your feature (it's not closed feature). In
your case, it looks like aries-blueprint feature is missing.
Regards
JB
On 11/13/2015 09:19 AM, conejo wrote:
Hello.
I have several problems
Hi,
1. yes, I agree. I will create a Jira and fix that. More over, for
backward compatibility purpose, it makes sense to support resolver
attribute even if we don't use it.
https://issues.apache.org/jira/browse/KARAF-4109
2. No problem ;)
Do you use feature validation (made by the
If I include this in my pom:
validate
process-resources
features-validate-descriptor
target/features.xml
I have an issue with deploying an updated WAB over the top of an existing one.
Services (created using Blueprint) are mapped to URLs. The WAB has a single
servlet that does a service lookup using JNDI based on the URL. Everything
works fine until I update the WAB by dropping an updated
Hi Scott,
did you try to do an update via command?
For example install the wab via shell:
bundle:install -s mvn:groupId/artifactId/version/war
and a later
bundle:update
does it also happen there?
If you want to update such bundles during development might also want to
take a look at
Hi!
I noticed that there is not much recent activity in Karaf-Cave. I also have a
vague recollection of a recent email on the list saying that "OBR is
deprecated".
Is anybody able to provide a little more clarity? I was planning on using the
OBR feature for provisioning.
Thanks!
=David
If I understand correctly the issue also shows when just restarting
karaf. In this case the feature service is not involved.
So the way you install the bundles the first time should not have any
influence.
I now tested the following:
I started an empty karaf 4.0.3 and installed the features
Hello.
I have a problem with a simple service. This service is created using
blueprint with the following file:
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:jpa="http://aries.apache.org/xmlns/jpan/v1.0.0;
xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.2.0;
And the code using the EntityManager too (all in the same bundle) ?
On 11/13/2015 02:47 PM, conejo wrote:
Yes i do.
One bundle for de api, and one bundle for de implementation.
--
View this message in context:
Yes. No more bundles. API only contains interfaces.
The Dao object uses EntityManager. The service calls the Dao.
--
View this message in context:
http://karaf.922171.n3.nabble.com/4-0-3-Karaf-JPA-problem-tp4043497p4043504.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Hi
what jpa and jpa engine features did you install ?
Regards
JB
On 11/13/2015 02:01 PM, conejo wrote:
Hello.
I have a problem with a simple service. This service is created using
blueprint with the following file:
http://www.osgi.org/xmlns/blueprint/v1.0.0;
Yes i do.
One bundle for de api, and one bundle for de implementation.
--
View this message in context:
http://karaf.922171.n3.nabble.com/4-0-3-Karaf-JPA-problem-tp4043497p4043502.html
Sent from the Karaf - User mailing list archive at Nabble.com.
The problem is that you probably have the persistence.xml and the entity
classes in the same bundle.
See:
https://issues.apache.org/jira/browse/ARIES-1433
Aries JPA container watches for bundles with the Meta-Persistence
header. If the bundle enters Starting or Active state then Aries JPA
wrap
obr
aries-blueprint
shell
shell-compat
feature
jaas
ssh
management
bundle
config
deployer
diagnostic
feature
instance
kar
log
package
Do you have all in one bundle (DAO, Entities and persistence.xml) ?
Regards
JB
On 11/13/2015 02:41 PM, conejo wrote:
wrap
obr
aries-blueprint
shell
shell-compat
feature
jaas
ssh
management
bundle
config
17 matches
Mail list logo