There might have been an issue with accessing the service description at some
point. Please remove the offending consumer and re-create it.
If it's still failing then you might have some other error and a more detailed
log would help.
View the original post :
http://www.jboss.org/index.html?mo
Look at the server log, there might be more details there. It might just be
that BEA's public producer is temporarly unavailable...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248464#4248464
Reply to the post :
http://www.jboss.org/index.html?module=bb&op
The wording is indeed confusing as it is not a strict absolute link but it
cannot be a relative link either. In essence, the link must be relative to the
root of the deployment, not to the location of the file.
default/images/back.gif will work assuming there's a default directory under
the roo
Thank you for this localization effort. We will look into incorporating it to
the Portal source code. Note that some new entries have been added to property
files since 2.7.2 so you might have to update your work for 2.7.3...
View the original post :
http://www.jboss.org/index.html?module=bb&op
Contrary to several other portals, JBoss Portal doesn't need to export a WSDL
definition per published portlet. You just need to use
http://localhost:8080/portal-wsrp/MarkupService?wsdl to access our producer
from a consumer. You should see the portlet there. See
http://docs.jboss.com/jbportal/
Use at your own risk! "With great power comes great responsibility!" ;)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240335#4240335
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240335
___
Ooops. The links again:
http://www.jboss.org/community/wiki/JBossPortalFAQ
http://www.jboss.org/community/wiki/UpgradingJSR-168PortletstoJSR-286
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240268#4240268
Reply to the post :
http://www.jboss.org/index.html
The solution to this problem is actually found here:
http://www.jboss.org/community/wiki/UpgradingJSR-168PortletstoJSR-286[/url] and
is mentioned in the FAQ: [url]http://www.jboss.org/community/wiki/JBossPortalFAQ
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p
The code is open source... You're welcome to contribute improvements... ;)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239732#4239732
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239732
The simple answer is: it won't. Portal works with portlets. Any web application
cannot be deployed within it and expected to work. I work on the Portal itself,
not on portlets so I don't have much experience on whether X framework would
work well in a portal context or not, unfortunately. Basica
If you create a JIRA issue for this, please reference this forum post in the
appropriate field of the JIRA issue as well.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239729#4239729
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&m
Seems like it might be a bug. Open a JIRA task for it and reference this forum
post in it. If you could also attach a portlet (with associated code) that
exhibits the issue and attach it to the JIRA task, that would also be helpful.
View the original post :
http://www.jboss.org/index.html?modul
It could be that the producer you're trying to access is down. However, judging
by the numerous error messages it seems that you have tried to deploy services
that were already deployed and you might want to fix these issues first.
View the original post :
http://www.jboss.org/index.html?module
Because we haven't seen much demand for WSRP 2 yet and there were other, more
requested features to implement first.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239083#4239083
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=r
You can write portlets using whatever technology you see fit. How you write
your portlets is outside of the Portal scope. As long as the portlets are
JSR-168 or JSR-286 compliant, they should work.
The question however is: does web framework X provide a bridge between the web
app and portlet wor
https://jira.jboss.org/jira/browse/JBPORTAL-2186
Still lots of work to do though...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237122#4237122
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237122
___
Fair enough. Like I said, feel free to open a JIRA for it if you think this is
something that is really missing and for which a valid set of use cases can be
identified.
We always consider new features if they make sense but we won't implement
something just because someone else supports it. :
JSR 286 events are meant for UI events. I'd argue that, and this is why we
haven't implemented cross-page wiring, wanting to change things across several
pages is not in the realm of UI anymore (since you won't be able to see
everything at the same time), rather it's a business domain issue wher
You'd need to modify all the Hibernate mappings in all the other Portal modules
as well (WSRP, identity, cms...). Basically, look for domain.hbm.xml files.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232649#4232649
Reply to the post :
http://www.jboss.org
We're not arguing the usefulness of such a feature. We're just saying that
there were other priorities that needed to be addressed first.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232110#4232110
Reply to the post :
http://www.jboss.org/index.html?module
Yeah, no kidding, eh? :) That is sure to motivate me to work on it!
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231902#4231902
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231902
___
There are only 2 votes for this JIRA issue, none of which seems to be yours...
We only have limited time and resources and have to prioritize things.
Priorities change. Votes for features influence which ones we work on...
View the original post :
http://www.jboss.org/index.html?module=bb&op=vi
"vivek_saini07" wrote :
| We build portal-core-lib.jar from SVN and deployed it in our setup. Problem
got resolved by this, although we got surprised by addition of two new
methods in CustomizationManager interface since we have our own implementation
for CustomizationManagerService.
By the way, the relevant JIRA issue is:
https://jira.jboss.org/jira/browse/JBPORTAL-2384
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230018#4230018
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230018
_
This issue should be fixed in subversion. Can you please give a try to the
latest revision and let us know how it works for you?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230001#4230001
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=po
For some reason, the comments don't show up in the article you linked to.
Please see: http://www.cmswatch.com/Trends/1569-Portal-JBoss-Red-Hat for some
opinions...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226555#4226555
Reply to the post :
http://www.
At this point, you need to initiate the configuration of explicit coordination
features using the *-object.xml deployment descriptors as explained in the
documentation. There's an issue with the admin portlet that prevents it to
display the proper information if no coordination elements have bee
The wiki is your friend (at least, when it's not broken as it seems the link to
the FAQ is currently broken):
http://www.jboss.org/community/docs/DOC-13228
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225648#4225648
Reply to the post :
http://www.jboss.org
Personally, I'd go with JSF. Our portlet bridge project is quite mature now and
well supported. We're using JSF + facelets for our admin portlets and we are
quite happy with it. Portlet bridge also supports RichFaces and Seam so that
would allow you to create portlets with a rich user experience
The bundled version uses the latest available unmodified community version of
JBoss AS (for the 4.2.x branch at this point) available when we release a new
Portal version. Until JBoss AS includes the proper JBoss WS version, you are
stuck with upgrading manually.
Now, if you had a support subscr
It's actually fixed in the portlet module as it wasn't a Portal issue per se.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219768#4219768
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219768
_
Should be fixed now. Please verify that it is indeed.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219530#4219530
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219530
___
j
https://jira.jboss.org/jira/browse/JBPORTAL-2349
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219287#4219287
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219287
___
jboss-
For the parameter issue, this looks like a Portlet Bridge issue. I have a work
around that would solve the issue in Portal but I'd rather have the issue
addressed at the Portlet Bridge level where it should really be fixed.
View the original post :
http://www.jboss.org/index.html?module=bb&op=v
Can you open a JIRA for it, please?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219121#4219121
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219121
___
jboss-user mailing
I will look into the issue.
"kharma" wrote :
| as a side note, i am also seeing this issue described as unreproducible.
https://jira.jboss.org/jira/browse/JBWS-1932
I see that as well. Feel free to chime in on that JIRA. I had given up on it
since it isn't adversely affecting Portal and ther
Any specific reason you're still using Portal 2.6.x?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218218#4218218
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218218
___
jb
"cpage" wrote : a JIRA has been created:
| https://jira.jboss.org/jira/browse/JBPORTAL-2338
Thank you.
"cpage" wrote : I haven't read carefully the WSRP documentation, i should not
create new properties on a remote portlet :-)
|
Indeed. :)
View the original post :
http://www.jboss.org/in
Why didn't you add it to the main content instead of as a comment? I can do the
switch if needed, but you might as well get credits for it... :)
I will review the content later.
Thanks again and keep contributing to Portal! :)
View the original post :
http://www.jboss.org/index.html?module=bb&op
I guess I need to look into it but adding preferences to a remote portlet
shouldn't be possible since only the producer can do so i.e. the consumer
doesn't have any control about the preferences/properties a portlet exposes via
WSRP. The only thing that can be done is read/set values.
That said
Hi George,
Care to document this in our Wiki? Maybe under
http://www.jboss.org/community/docs/DOC-12628?
Thanks in advance.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215644#4215644
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting
More precisely, the WSRP consumer will attempt to contact the producers marked
as [bold]active[/bold] in the database.
I am considering separating active and failed status in the database. However,
I cannot do so without breaking backward compatibility so it won't happen (if
at all) before a ne
"cpage" wrote :
| For me, during JBoss start (wsrp services start), all producers recorded in
the database and new producers of the xml should be contacted.
|
This is what happens.
However, this is not the use case you describe here as the consumer is started
and correctly attempts to co
Any specific reason why you're not using our admin portlets?
There are some WSRP administration operations that can only be done via the
WSRP admin portlet, in particular, activating an inactive producer.
Note also that the XML file is only used to seed the database. If a producer
with a give
Our WSRP implementation doesn't currently handle resources very well.
background:url in style elements are indeed not currently properly detected as
targets for rewriting.
A possible solution would be a store the static resources such as images in an
easily reachable location and refer to them
Use the WSRP admin console to refresh the consumer. That said, I will look into
the issue.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214973#4214973
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214973
___
Indeed, there seems to be an issue with this particular scenario.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214885#4214885
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214885
_
This is also addressed in the Wiki:
http://www.jboss.org/community/docs/DOC-13228
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212756#4212756
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212756
"sambit_dixit" wrote : Yes you can. Set it in PortletSession
Unless I am mistaken, this will only work for the portlets that have been
deployed within the same web application.
As of Portal 2.7 (and EPP 4.3), you can use an alias binding in coordination
with public render parameters. See
http
The portlet issue shouldn't cause the mangled interaction state. As far as WSRP
support with Microsoft, I don't know where you could ask. The WSRP
implementation in Sharepoint seems to have several issues...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=42094
It seems indeed like SharePoint is mangling the interaction state by appending
the navigational state to it. This seems like something you might want to see
with Microsoft as no WSRP producer can deal with modified interaction state
(which is supposed to be treated opaquely by the consumer).
An
Can you attach the SOAP request-response sequence for the action that is
failing, please?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208702#4208702
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208702
Seems like this is an SAP issue, the error reported by JBoss Portal is
appropriate: in the SAP response, note how the propertyDescriptions elements
have a type "prt0:QName" while no "prt0" namespace declaration exists in the
document.
View the original post :
http://www.jboss.org/index.html?mo
Thanks for the update. JBPORTAL-2306 should be fixed now for both 2.6 and 2.7.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208558#4208558
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208558
I have validated that the missing wsrp_rewrite is indeed an error:
https://jira.jboss.org/jira/browse/JBPORTAL-2306.
For the other issue, this is a SharePoint issue. Per the WSRP specification:
anonymous wrote : If a Producer indicates that it uses cookies, the Consumer
MUST ensure that any cooki
Hi Scott,
Could you please attach the SOAP message that is causing the issue?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208421#4208421
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208421
_
It's actually not currently possible to graphically edit the coordination
information without first "salting" the page coordination metadata with a
-object.xml file.
I've opened a JIRA for it: https://jira.jboss.org/jira/browse/JBPORTAL-2288
View the original post :
http://www.jboss.com/index.h
Can you send me your portlets, please?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205192#4205192
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205192
___
jboss-user maili
I'd like to see the SOAP interaction leading to the page that is causing you
problems. Specifically I'm looking for any issues in the getMarkup call which
would result in Sharepoint not rewriting the URL.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201823#
Is there a way that you can post the SOAP messages relevant to the particular
interaction?
Any reason you are using 2.6.7 instead of 2.7?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201728#4201728
Reply to the post :
http://www.jboss.com/index.html?module
To be more precise, what has been fixed is the automatic inclusion of the tag
library in the portlet application as was the case for JSR-168 portlets. If you
included the JSR-286 tag lib in your portlet manually, it should have worked
fine.
A side effect to this fix is that if you use JSR-286 fo
This should now be fixed in subversion. Thanks for the report!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199646#4199646
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199646
There is indeed a problem with the 2.0 taglib loading...
https://jira.jboss.org/jira/browse/JBPORTAL-2269
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199559#4199559
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=41995
I have just tested the JSR 286 in Portal 2.7 and it works as expected. I
haven't tested the old way to do things, though it should still work if you're
not using JSR 286.
Not sure what is wrong on your side.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189
64 matches
Mail list logo
