[jira] [Commented] (GERONIMO-6776) Let specify encoding for generated files
[
https://issues.apache.org/jira/browse/GERONIMO-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155418#comment-17155418
]
Antoni Reus commented on GERONIMO-6776:
---
You can do it, thanks.
> Let specify encoding for generated files
>
>
> Key: GERONIMO-6776
> URL: https://issues.apache.org/jira/browse/GERONIMO-6776
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: geronimo-maven-plugin
>Affects Versions: OpenAPI_1.0.12
>Reporter: Antoni Reus
>Priority: Trivial
> Attachments: encoding.patch
>
>
> Currently the geronimo-openapi-maven-plugin uses a FileWriter to generate the
> openapi.json. This defaults to de platform encoding.
>
> The user should be able to specify an encoding in the plugin configuration:
> UTF-8
> or use ${project.build.sourceEncoding} as default encoding, and only if this
> is not provided fallback to the platform encoding.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GERONIMO-6776) Let specify encoding for generated files
[
https://issues.apache.org/jira/browse/GERONIMO-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155409#comment-17155409
]
Antoni Reus commented on GERONIMO-6776:
---
you are right, default should be UTF-8
[https://tools.ietf.org/html/rfc7159#section-8.1|https://tools.ietf.org/html/rfc8259#section-8.1]
> Let specify encoding for generated files
>
>
> Key: GERONIMO-6776
> URL: https://issues.apache.org/jira/browse/GERONIMO-6776
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: geronimo-maven-plugin
>Affects Versions: OpenAPI_1.0.12
>Reporter: Antoni Reus
>Priority: Trivial
> Attachments: encoding.patch
>
>
> Currently the geronimo-openapi-maven-plugin uses a FileWriter to generate the
> openapi.json. This defaults to de platform encoding.
>
> The user should be able to specify an encoding in the plugin configuration:
> UTF-8
> or use ${project.build.sourceEncoding} as default encoding, and only if this
> is not provided fallback to the platform encoding.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GERONIMO-6776) Let specify encoding for generated files
Antoni Reus created GERONIMO-6776:
-
Summary: Let specify encoding for generated files
Key: GERONIMO-6776
URL: https://issues.apache.org/jira/browse/GERONIMO-6776
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: geronimo-maven-plugin
Affects Versions: OpenAPI_1.0.12
Reporter: Antoni Reus
Attachments: encoding.patch
Currently the geronimo-openapi-maven-plugin uses a FileWriter to generate the
openapi.json. This defaults to de platform encoding.
The user should be able to specify an encoding in the plugin configuration:
UTF-8
or use ${project.build.sourceEncoding} as default encoding, and only if this is
not provided fallback to the platform encoding.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GERONIMO-6760) There is no way to generate a response with no return value
Antoni Reus created GERONIMO-6760:
-
Summary: There is no way to generate a response with no return
value
Key: GERONIMO-6760
URL: https://issues.apache.org/jira/browse/GERONIMO-6760
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: OpenAPI_1.0.11, OpenAPI_1.0.12
Environment: Apache Maven 3.6.2
(40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T17:06:16+02:00)
Maven home: C:\dev\tools\apache-maven-3.6.2\bin\..
Java version: 11.0.6, vendor: AdoptOpenJDK, runtime: C:\dev\java\jdk-11
Default locale: ca_ES, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Tested with geronimo-openapi-maven-plugin 1.0.11 and 1.0.12
Reporter: Antoni Reus
If a response has no return value it must ommit the content information.
See
[https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#response-object]
Response with no return value:
{quote}{
"description": "object created"
}{quote}
For example, in case of a response with a 204 code.
Currently there is no way to achieve this, there is always a "content" element
with an empty "schema" in every response.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Error configuring servicemix snapshot in eclipse with cimero
Hi, I'm just compiled and installed servicemix from the servicemix-3.0 branch Seems that due to changes in the layout of the installation and jar renaming of servicemix, adding a servicemix server to eclipse with the cimero plugin doesn't work. Salut. -- Antoni Reus Darder Cap de Projecte Administració Digital, Negoci Electrònic i Sanitat F u n d a c i ó I B I T Illes Balears Innovació Tecnològica http://www.ibit.org Tel. +34 971 17 72 70/71 Fax. +34 971 17 72 79
build error
] [INFO] Total time: 7 seconds [INFO] Finished at: Fri Sep 08 09:50:24 CEST 2006 [INFO] Final Memory: 13M/24M [INFO] -- Antoni Reus Darder Cap de Projecte Administració Digital, Negoci Electrònic i Sanitat F u n d a c i ó I B I T Illes Balears Innovació Tecnològica http://www.ibit.org Tel. +34 971 17 72 70/71 Fax. +34 971 17 72 79
Re: build error
I seems that the problem is the last change in ./pom.xml
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifest
1494--
addDefaultSpecificationEntriestrue/addDefaultSpecificationEntries
1495--
addDefaultImplementationEntriestrue/addDefaultImplementationEntries
/manifest
/archive
/configuration
/plugin
removing lines 1494 and 1495 makes build work, but don't know about
side-effects.
Antoni Reus wrote:
Just updated from subversion and I get this error trying to build
servicemix
( tried both
mvn -Dmaven.test.skip install
and
mvn -Dmaven.test.skip -Dprofile=step1 install
with same result)
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] ServiceMix
[INFO] Servicemix :: Build
[INFO] ServiceMix :: JBI
[INFO] ServiceMix :: Services
[INFO] ServiceMix :: Core
[INFO] ServiceMix :: Tooling
[INFO] ServiceMix :: Maven2 :: Archetypes :: BindingComponent
[INFO] ServiceMix :: Maven2 :: Archetypes :: ServiceEngine
[INFO] ServiceMix :: Maven2 :: Archetypes :: ServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: ServiceAssembly
[INFO] ServiceMix :: Maven2 :: Archetypes :: SharedLibrary
[INFO] ServiceMix :: Maven2 :: Archetypes :: HttpConsumerServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: HttpProviderServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: JmsConsumerServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: JmsProviderServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: Jsr181WsdlFirstServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: LWContainerServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: EIPServiceUnit
[INFO] ServiceMix :: Maven2 :: Archetypes :: EmbeddedSimple
[INFO] ServiceMix :: Common
[INFO] ServiceMix :: Maven2 :: JBI Plugin
[INFO] ServiceMix :: Maven2 :: Archetypes :: ITests
[INFO] ServiceMix :: BeanFlow
[INFO] ServiceMix :: Components
[INFO] ServiceMix :: SOAP
[INFO] ServiceMix :: Shared
[INFO] ServiceMix :: Console
[INFO] ServiceMix :: HTTP
[INFO] ServiceMix :: BPE
[INFO] ServiceMix :: JMS
[INFO] ServiceMix :: JSR-181 Service Engine
[INFO] ServiceMix :: WS-Notification Service Engine
[INFO] ServiceMix :: Lightweight container Service Engine
[INFO] ServiceMix :: SCA Service Engine
[INFO] ServiceMix :: EIP
[INFO] ServiceMix :: ITests
[INFO] ServiceMix :: Samples
[INFO] ServiceMix :: Samples :: WSDL first
[INFO] ServiceMix :: Samples :: WSDL first :: JSR181
[INFO] ServiceMix :: Samples :: WSDL first :: HTTP
[INFO] ServiceMix :: Samples :: WSDL first :: SA
[INFO] ServiceMix :: Samples :: Loan Broker
[INFO] ServiceMix :: Samples :: Loan Broker :: LwContainer
[INFO] ServiceMix :: Samples :: Loan Broker :: BPE
[INFO] ServiceMix :: Samples :: Loan Broker :: SA
[INFO] ServiceMix :: Samples :: Bridge
[INFO] ServiceMix :: Samples :: Bridge :: HTTP
[INFO] ServiceMix :: Samples :: Bridge :: EIP
[INFO] ServiceMix :: Samples :: Bridge :: XSLT
[INFO] ServiceMix :: Samples :: Bridge :: JMS
[INFO] ServiceMix :: Samples :: Bridge :: SA
[INFO] ServiceMix :: Samples :: Web
[INFO] ServiceMix :: Samples :: Basic
[INFO] Servicemix :: Geronimo
[INFO] ServiceMix :: Geronimo :: ServiceMix service
[INFO] ServiceMix :: Geronimo :: Deployer service
[INFO] ServiceMix :: Geronimo :: ServiceMix plugin
[INFO] ServiceMix :: Geronimo :: Deployer plugin
[INFO] Servicemix :: Assembly
[INFO]
[INFO] Building ServiceMix
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[INFO] [install:install]
[INFO] Installing
/home/IBIT/areus/java/servicemix/servicemix-3.0-dev/pom.xml to
/home/IBIT/areus/.m2/repository/org/apache/servicemix/servicemix/3.0-incubating-SNAPSHOT/servicemix-3.0-incubating-SNAPSHOT.pom
[INFO] [maven-one-plugin:install-maven-one-repository {execution:
default}]
[INFO] Installing
/home/IBIT/areus/java/servicemix/servicemix-3.0-dev/pom.xml to
/home/IBIT/areus/.maven/repository/org.apache.servicemix/poms/servicemix-3.0-incubating-SNAPSHOT.pom
[INFO]
[INFO] Building Servicemix :: Build
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using default
Re: build broken
I build on a debian linux, perhaps is a platform issue?
Antoni Reus wrote:
I Just tried:
svn update
mvn -Dmaven.test.skip=true -Dprofile=step1 install
mvn -Dmaven.test.skip=true -Dprofile=step2 install
same error :-(
Guillaume Nodet wrote:
AFAIK, i have fixed that yesterday. Could you try with the svn head ?
On 8/11/06, Antoni Reus [EMAIL PROTECTED] wrote:
It seems there is a problem in samples:
It seems there is a problem with relative/absolute path of file
samples/wsdl-first/wsdl-first-jsr181-su/src/main/resources/xbean.xml
mvn -Dmaven.test.skip=true -Dprofile=step2 install, fails with:
[INFO]
[INFO] Building ServiceMix :: Samples :: WSDL first :: JSR181
[INFO]task-segment: [install]
[INFO]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
11/08/200It seems there is a problem with relative/absolute path of
file
samples/wsdl-first/wsdl-first-jsr181-su/src/main/resources/xbean.xml6
09:41:37 org.codehaus.xfire.gen.Wsdl11Generator generate
INFO: Generating code for WSDL at
file:/home/IBIT/areus/java/servicemix/servicemix-3.0-dev
/samples/wsdl-first/wsdl-first-jsr181-su/src/main/resources/person.wsdl
with a base URI of
file:/home/IBIT/areus/java/servicemix/servicemix-3.0-dev
/samples/wsdl-first/wsdl-first-jsr181-su/src/main/resources/person.wsdl
org/apache/servicemix/samples/wsdl_first/types/GetPersonRequest.java
org/apache/servicemix/samples/wsdl_first/types/GetPersonResponse.java
org/apache/servicemix/samples/wsdl_first/types/ObjectFactory.java
org/apache/servicemix/samples/wsdl_first/types/UnknownPersonFault.java
org/apache/servicemix/samples/wsdl_first/types/package-info.java
11/08/2006 09:41:37
org.codehaus.xfire.gen.jsr181.AbstractServiceGenerator generate
INFO: Creating class org.apache.servicemix.samples.wsdl_first.Person
11/08/2006 09:41:37
org.codehaus.xfire.gen.jsr181.AbstractServiceGenerator generate
INFO: Creating class
org.apache.servicemix.samples.wsdl_first.PersonServiceImpl
org/apache/servicemix/samples/wsdl_first/Person.java
org/apache/servicemix/samples/wsdl_first/PersonServiceImpl.java
org/apache/servicemix/samples/wsdl_first/PersonServiceService.java
org/apache/servicemix/samples/wsdl_first/UnknownPersonFault.java
[INFO] Executed tasks
[INFO] Registering compile source root
/home/IBIT/areus/java/servicemix/servicemix-3.0-dev
/samples/wsdl-first/wsdl-first-jsr181-su/target/jaxws
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 9 source files to
/home/IBIT/areus/java/servicemix/servicemix-3.0-dev
/samples/wsdl-first/wsdl-first-jsr181-su/target/classes
[INFO] [jbi:generate-jbi-service-unit-descriptor]
[INFO] Generating jbi.xml
[INFO] Created Service Unit Analyzer
[EMAIL PROTECTED]
2006-08-11 09:41:38,733 [main ] INFO
CollectionFactory - JDK 1.4+ collections available
2006-08-11 09:41:38,743 [main ] INFO
CollectionFactory - Commons Collections 3.x available
2006-08-11 09:41:38,785 [main ] INFO
XBeanXmlBeanDefinitionReader - Loading XML bean definitions from file
[/home/IBIT/areus/java/servicemix/servicemix-3.0-dev
/home/IBIT/areus/java/servicemix/servicemix-3.0-dev
/samples/wsdl-first/wsdl-first-jsr181-su/src/main/resources/xbean.xml]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to generate jbi.xml
Embedded error: Unable to generate service unit descriptor!
home/IBIT/areus/java/servicemix/servicemix-3.0-dev
/samples/wsdl-first/wsdl-first-jsr181-su/src/main/resources/xbean.xml
(No such file or directory)
Salut.
--
Antoni Reus Darder
Cap de Projecte
Administració Digital, Negoci Electrònic i Sanitat
F u n d a c i ó I B I T
Illes Balears Innovació Tecnològica
http://www.ibit.org
Tel. +34 971 17 72 70/71
Fax. +34 971 17 72 79
--
Antoni Reus Darder
Cap de Projecte
Administració Digital, Negoci Electrònic i Sanitat
F u n d a c i ó I B I T
Illes Balears Innovació Tecnològica
http://www.ibit.org
Tel. +34 971 17 72 70/71
Fax. +34 971 17 72 79
servicemix dependencies
Hi, It looks like servicemix have lots of dependencies with libraries in BETA or RC stage (activemq, spring, jaxen, jetty ) Are there any plans for a 3.0 stable version to depend only in stable versions of those libraries? Thanks in advance, Salut! -- Antoni Reus Darder Cap de Projecte Administració Digital, Negoci Electrònic i Sanitat F u n d a c i ó I B I T Illes Balears Innovació Tecnològica http://www.ibit.org Tel. +34 971 17 72 70/71 Fax. +34 971 17 72 79
Re: ServiceMix and security
I think that you are right with your example of a web container. JBI defines a container, just like a web container or a ejb container. En/na Guillaume Nodet ha escrit: The main problem of using a JBI component to provide security is that when you use a clustered ServiceMix, JBI exchanges may go to the security component using a clustered flow. In such a case, the exchange will be sent on the wire in an unsecured / unauthenticated way. I have always thought that security should be provided by the container. I would compare it to a web server which has built-in security to secure web applications. The application can always use a custom login / authentication scheme, but the prefered way is to delegate to the container (and implement a specific realm if needed), which is the only way to provide SSO afaik. Besides this, if security is handled by the container, it will be able to detect authorization failures earlier and even use them when implicit endpoint selection is used: if the jbi exchange target is an interface QName, the container could check matching endpoints for authorization instead of selecting one and having an authorization failure. Last point, if security is provided by a component, all components will have to be rewritten so that they can leverage this feature. It seems much more interesting that security is provided transparently by the container... I really think that container security is the most flexible and pluggable way to handle security as it is centralized. Any thoughts ? Cheers, Guillaume Nodet On 4/19/06, Hossam Karim [EMAIL PROTECTED] wrote: Just thinking: - Security is a service - A component installed inside SM can support a SM specific security contract, in which a security provider implementing this contract can be bound to one or more installed components. This provider can provide authentication, digital signature verification, XML encryption and decryption, integration with LDAP, etc. - A component that has a security provider installed should delegate all security operations to its provider. - A component that has a security provider should provide additional management operations through JMX to secure its lifecycle management. Hossam -Original Message- From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 19, 2006 2:57 AM To: servicemix-dev@geronimo.apache.org Subject: ServiceMix and security One of the important feature ServiceMix does not address yet is security. I' m not really familiar with this aspect so please forgive my ignorance and speak if you have any idea / corrections. Security can be applied in different areas: * secure transports * secure messages * secure services Securing transports can be done using SSL on JMS or HTTP. Securing the JMS broker is beyond ServiceMix scope, but ActiveMQ supports SSL on tcp transport. So this works fine for both the JMS binding component and any clustered flow. Securing HTTP will be done asap (we already have a patch, see http://issues.apache.org/activemq/browse/SM-372). Securing messages is not handled yet, but can be done using WS-Security on soap enabled transports (servicemix-jms and servicemix-http binding components). Is there a need to secure messages within the bus ? Securing services seems to be the most difficult part. The JMS specs only mention the use of the subject property on a NormalizedMessage http://java.sun.com/integration/1.0/docs/sdk/api/javax/jbi/messaging/Normali zedMessage.html#setSecuritySubject(javax.security.auth.Subject). The main problem is how to set / use this information and how informations about service authorizations. Such security informations may be embedded in the service unit / service assemblies deployment, or may be configured separately on the container. When a component sends a jbi exchange, the container could check the authorizations for the destination endpoint (or service, interface ?). However, I do not have any clue on how this information will be provided by binding components when an external message comes in. HTTP transport could leverage HTTP authentication, but what about the other transports ? All this security has also to be integrated with J2EE containers security when ServiceMix is deployed into such a container. Cheers, Guillaume Nodet -- Antoni Reus Darder Cap de Projecte Administració Digital, Negoci Electrònic i Sanitat F u n d a c i ó I B I T Illes Balears Innovació Tecnològica http://www.ibit.org Tel. +34 971 17 72 70/71 Fax. +34 971 17 72 79
